What An AI SEO Agency Should Report Every Month

Treat markup as something with a maintenance cost rather than a one off implementation. Prices change, people leave, products are discontinued, and structured data quietly keeps asserting the old version long after the visible page has been updated. Adding a schema review to whatever process already updates your pages costs minutes and prevents the most damaging failure mode, which is confidently stating something that is no longer true.

Frame It as Insurance Where Appropriate For businesses whose category shows light assistant use, the honest framing is not growth. It is that the cost of entering rises as third party coverage fills in, and that a baseline taken now is what will let you attribute any future decline.

Refusals matter. A report that only contains successes is either describing a suspiciously easy month or omitting the parts that did not work, and the omitted parts are usually where the useful information is.

Structured data attracts a particular kind of over-investment. Teams implement a dozen schema types, validate them all, and conclude the job is done, having spent most of their effort on markup that changes nothing about how a machine understands the business.

Good versions read like this: mention rate on evaluation prompts rose from two in fifteen to six in fifteen, which we attribute to the three directory corrections completed in week two, though a competitor also stopped publishing during the same period.

The sustainable version is small and continuous: the prompt set run monthly, listings checked quarterly, a handful of pages updated rather than a burst of new ones, and someone who owns it. That costs less over a year than the three month push and holds its ground. llm visibility tracking

The Mistake That Undoes Everything Markup is a claim, not evidence. Structured data asserting that you own a profile only helps when that profile exists and points back at you. Markup naming an author only helps when the author can be found elsewhere.

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.

It is also worth asking for the report a day before the meeting rather than seeing it in the room. A document presented live is experienced as a narrative and approved on the strength of the delivery. The same document read beforehand is experienced as evidence, and the questions that occur to you reading it alone are usually the ones worth asking.

Ask What Happens in Month One A proposal that opens with content production has skipped the diagnosis. There is no way to know what to write before you know which questions matter, which assistants answer them badly and which sources they draw on.

Ask how they will handle being wrong. Every engagement in this field produces at least one confident recommendation that does not work, because the systems change and the published research is thin. What matters is whether that gets reported or quietly dropped from the next deck, and asking the question directly at the outset makes it considerably more likely to be reported.

Accuracy Beats Coverage The most common real defect is not missing markup, it is markup that disagrees with the page or with the rest of the web. A founding year in your schema that differs from your about page. A logo URL that returns a 404. A contact point nobody monitors.

None of them are harmful. They just consume implementation and maintenance time that would achieve more if spent making the Organization markup accurate everywhere, or correcting the directory listing that has your old address on it.

One test separates a report written to inform from one written to reassure. Read it and try to write down a question it does not answer. In a good report you will find several, because it contains enough specifics to make new questions obvious. In a padded one you will struggle, not because everything is covered but because there is nothing specific enough to interrogate.

Audit for contradiction before adding anything new. Run your key pages through a validator, then read the output against what the page actually says and against your main directory listings. Contradictions are more damaging than gaps, because they actively undermine confidence in the record.

That matters most for the facts that establish identity, because those are the facts that let scattered mentions of you resolve into one record. It matters far less for content, where the model is going to read the prose anyway and is reasonably good at it.

What to Do About llms.txt and Similar Files Proposals for machine readable files aimed specifically at language model consumers appear periodically. Adoption is inconsistent and support varies by provider, so treat these as low cost and speculative rather than as a requirement.

Retrieval behaviour changes, competitors keep publishing, listings go stale, product details change and reviews accumulate. A position secured once is not held without maintenance, which is the same lesson search taught over twenty years and which is being relearned rather than transferred.