/a-geo-optimizer

More and more people never reach your page. They ask an assistant, and the assistant answers from whatever it could fetch and parse. If yours was not in that set, you were not in the answer, and no amount of ranking fixes it.

a-geo-optimizer does for that surface what SEO does for search engines. The industry calls it generative engine optimization, GEO, which is where the name comes from and has nothing to do with geography. Being useful is not enough if the assistant cannot fetch the page, cannot work out what it says, or cannot find a claim in it worth quoting.

It covers four things. Crawler access, because the AI user agents are not the Googlebot rules you already wrote, and plenty of sites are blocking them without knowing it. llms.txt, and what actually belongs in one. Structured data aimed at citation rather than at rich snippets, which is a different target with different markup. And content shaped so an answer can be lifted out of it: a direct claim near the top of a section rather than four paragraphs of throat-clearing before the point.

It is meant to fire while you are building the page, not only when you audit one. That is why it stays model-invocable: the cheapest moment to fix any of this is before publishing, and by the time you think to ask, the page is already live and the fix is a rewrite. Claude reaches for it when the output is a web page, whether or not anyone said the words "AI search".

It changes nothing on its own. It produces findings and a plan; you decide what lands.

Ships in the search-visibility plugin, alongside a-seo-gsc. That one starts from your measured data and tells you where the loss is. This one starts from the page and asks whether it can be quoted at all. Run a-seo-gsc first when you have data, and this one on anything new, where there is no data yet.

/plugin marketplace add imisic/claude-marketplace
/plugin install search-visibility@imisic

Then the command is /a-geo-optimizer.