The two meanings
| AI for SEO | SEO for AI | |
|---|---|---|
| What it means | Using models to produce SEO work | Making your site usable by models |
| What it changes | Your production speed | What an agent receives from your server |
| Who reads the result | Search crawlers, then people | A parser on a token budget |
| Is it new | No, it is a faster version of existing work | Yes, the reader is new |
| Risk if done badly | Thin content at scale | Being unreadable and not knowing |
Both are legitimate. They are simply not the same purchase, and conflating them is how a team ends up with a content generator when their actual problem is that assistants cannot fetch their pricing page. The rest of this page is the second column.
What SEO for AI actually requires
Four things, in this order, because a failure early makes everything after it irrelevant. Most sites fail one of the first two and have never been told.
- The fetch is allowed. A
robots.txtline or a CDN bot rule ends it silently, with no error on your side. - The response is parseable without a browser. Facts that appear only after JavaScript runs do not exist to an agent.
- The facts are cheap to reach. Agents read under a token budget, so a first fact buried behind markup may be skipped for a shorter source.
- The facts agree with themselves. When your prose and your structured data differ, the assistant picks one and you do not choose.
What the change is worth, measured
Two reference captures, deterministic and rebuilt from committed fixtures on every build. They are quoted separately and never averaged, because a product page and a services page carry different amounts of chrome.
| Capture | Before | After | First fact moves |
|---|---|---|---|
| Commerce product page | 91,226 bytes | 1,315 (−98.6%) | Character 23,185 → line 4 |
| Clinic services page | 13,581 bytes | 1,412 (−89.6%) | Character 10,152 → line 8 |
That is roughly 69× less context on the commerce capture and 9.7× fewer tokens on the document one, for identical facts. Use whichever matches your own site.