--- type: Article name: "\"AI can just read the page, you don't need structured data.\" It's solving the wrong layer of the problem." id: "https://selfe.ai/insights/myth-vs-fact/ai-can-just-read-the-page-you-dont-need-structured-data-we-tested-that-claim-it-" url: "https://selfe.ai/insights/myth-vs-fact/ai-can-just-read-the-page-you-dont-need-structured-data-we-tested-that-claim-it-" publisher: "did:web:selfe.ai" description: "The usual fix people reach for is extending the markup already on a page, more tags, richer fields, describing more of the business in the same place. That's still a page-shaped answer. The facts an AI agent needs don't have to live on a page at all, marked up or not." datePublished: "2026-09-15T15:35:35.873Z" author: The Selfe team --- # "AI can just read the page, you don't need structured data." It's solving the wrong layer of the problem. > The usual fix people reach for is extending the markup already on a page, more tags, richer fields, describing more of the business in the same place. That's still a page-shaped answer. The facts an AI agent needs don't have to live on a page at all, marked up or not. ## In short - The usual fix, extending page markup, is still solving a page-shaped problem with a bigger page-shaped answer. - That markup was built to help a search engine show a nicer result to a person, not to answer an agent's question directly. - An agent doesn't want a richer description of a page. It wants the fact, without needing to find the page first. - Selfe connects the real facts directly, live, rather than asking a business to write more markup. A richer page is still a page. The fix that actually closes the gap was never going to be a bigger version of the same thing. ## What that markup was built for A guesthouse owner adds more structured markup to her existing pages, room types, amenities, opening hours, the works, and assumes that settles the question of being agent-ready. It's a reasonable thing to try. It's also solving the wrong layer of the problem. The markup vocabulary most businesses reach for was built years ago to help a search engine understand a page well enough to show a nicer result: a star rating in the results, an address on a map, opening hours in a knowledge panel. It was always an annotation on a page meant for a person to click through to. Extending it, adding more fields, describing more of the business in the same format, doesn't change what it fundamentally is: metadata sitting on top of a document. ## Why that's not the same job an agent needs done An agent checking whether a guesthouse takes two dogs of any size doesn't want a richer description of the page it's on. It wants the fact, directly, in a form it can check without first finding the page, then finding the markup on it, then parsing that markup correctly. Adding more of the same kind of annotation just makes the annotation longer, not more useful. ## What closes it The facts don't need to be attached to a page at all. Not a bigger markup vocabulary, not a smarter version of the same idea, something genuinely different: a business's specific facts, how many dogs, which dates, what the cancellation terms really are, made directly reachable as their own thing, queryable on its own terms rather than discovered by first locating and then decoding a page. ## Where this shows up for a business Selfe doesn't ask a guesthouse to write richer page markup. It connects the actual facts, live, from the business's own systems, so an agent gets the real answer directly rather than needing to find, load and correctly interpret a page first. ## Should we stop adding structured markup to our pages? It's not harmful, and it still helps a search engine. It just isn't the thing that makes a business agent-ready on its own. ## What's different about connecting facts directly? There's no page in the loop at all. An agent gets the fact directly, nothing to find or decode. ## Act on this - [Check whether an agent can buy from you](https://selfe.ai/agentic-commerce/buyability-check) — the free readiness scan. - [Discover venues](https://selfe.ai/api/registry/discover) — `POST`, semantic browse across the registry. - [Match a bookable answer](https://selfe.ai/api/registry/match) — `POST` with dates and party size. - [Verify Selfe's identity](https://selfe.ai/.well-known/did.json) — `did:web:selfe.ai`. - [Agent card](https://selfe.ai/.well-known/agent-card.json) — how to connect over A2A or MCP.