The Case For Auditing Your AI Visibility This Quarter

Put someone's name against this. Crawler rules sit between marketing, development and whoever administers the content delivery network, which in most organisations means nobody checks them. The failures documented here are not difficult to find, they are simply nobody's job, and a quarterly review taking half an hour prevents the most complete form of invisibility available.

What Not to Do in the Name of Legibility Hidden text intended only for machines fails on every axis. It is detectable, it violates most guidelines, and it produces exactly the uniform low quality signal you were trying to avoid.

What you are looking for is whether the questions sound like a buyer wrote them. If every prompt contains the client's category name phrased the way an internal marketing team would phrase it, they have tested how the brand talks rather than how customers ask.

The Cheapest Fixes Have a Deadline That Already Passed Audits routinely surface mechanical problems that have been quietly costing visibility for months. Crawlers blocked in robots.txt. A bot management product returning challenges to legitimate retrieval agents. Key content rendering only after JavaScript executes. Specifications trapped in a PDF.

Ask to See a Prompt Set The first question is the most revealing. Ask them to show you the prompt set from a current or recent client, with the client's name removed. A team doing real work has this and will show it, because the prompts are craft rather than secret sauce.

Vague answers about digital PR are a warning sign. Good answers are concrete: they have read your baseline source list, they know which platforms allow corrections, they have a view on which comparison articles are worth approaching, and they will tell you which ones are out of reach.

When to Test More Often Three situations justify a tighter loop. During an active campaign where you need to attribute a specific change, weekly runs on a subset of prompts are reasonable, provided you accept the variance.

A Reasonable Sequence Fix rendering first, since content a machine cannot see is the only total failure in the list. Then work through your commercially important pages one at a time, moving the direct answer to the top and replacing the vaguest paragraph with concrete figures.

Why One Snapshot Proves Almost Nothing Generation involves randomness, and retrieval can return different pages between runs. The same prompt asked twice in a row can produce different companies in different orders.

Where to Put Them Individual pages for questions with real volume and commercial weight, grouped sections for the smaller ones. Both work, and the decision should follow how much there is to say rather than a rule.

Ask What They Cannot Measure A competent practitioner will volunteer limitations before you ask. Assistant answers vary between sessions. Referral attribution is inconsistent. Some assistants cannot be measured reliably at all. Sample sizes in the published research are small.

Equally, do not publish a stripped alternate version of your site for crawlers. Serving different content to machines than to people is cloaking, it has been penalised for two decades, and there is no reason to expect a more forgiving treatment here.

The fix is not abandoning modern frameworks. Server side rendering or static generation produces the same interface with meaningful content in the initial response, and it is faster for humans too, which is the usual pattern in this area.

The complication is that AI systems use several distinct agents for different purposes. One may crawl for training corpora, another may fetch pages live when composing an answer, and a search provider's traditional crawler may feed both search results and an AI summary.

There is also a straightforward test that costs nothing and tends to end the debate internally. Ask an assistant the question your best customer would have asked before they found you, and read the answer out in the next management meeting. llm seo

And do not let anyone rewrite your entire site in the flat, listicle heavy register that is currently fashionable in this discipline. It reads as machine assembled to human beings, and content that reads that way tends to be treated as low quality by both audiences.

The second is content behind interaction. Accordions, tabs and modals are good interface patterns and their content is sometimes absent from the initial response. Check whether yours is present in the HTML even when collapsed, which is usually a configuration question rather than a design one.

Log the conditions with every run, including which assistant, which mode, whether web access was enabled and the date. When a result moves sharply, the conditions log is usually what tells you whether the world changed or your setup did.

All three of those are worth knowing regardless of channel size, and two of them improve traditional search as a side effect. The cost of finding out is a few days. The cost of not knowing is discovering it in a quarter where the number has grown enough to hurt.