Notes on AI visibility

Short pieces answering one question each, written from our own measurement rather than from a category overview.

When there is something measured to say. We would rather publish four useful pieces a quarter than a weekly cadence nobody finishes.

Closer to a resource. Product news lives in the release notes; this is for the questions buyers keep asking.

Only with the data attached. An opinion about how engines behave is worth reading when it says which runs produced it.

Yes, and the best suggestions are questions you could not find an honest answer to anywhere. Those make the most useful posts.

Into all eight languages, reviewed by someone in that market rather than published straight from a model.

When the engines make one wrong. The change is noted at the top instead of the page being quietly rewritten.

An excerpt with a link, yes. For a full republication, write to us and we will usually agree with attribution.

The sitemap lists every post, and the newsletter carries the new ones. A feed is on the list rather than in place.

Anybody who has to explain to somebody else why answers changed. The posts are written to be forwarded, not to keep you on the site.