Last modified on 13 August 2026, at 15:18

Structured Data That AI Search Engines Actually Read

Revision as of 15:18, 13 August 2026 by VivianNagel8471 (Talk | contribs) (Created page with "Then add the structural markup, then check the whole thing with a reader in mind rather than a crawler. If a page has become harder for a person to use, something has gone wro...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Then add the structural markup, then check the whole thing with a reader in mind rather than a crawler. If a page has become harder for a person to use, something has gone wrong and the change should be reversed.

Then segment by query type. If the decline concentrates in informational and definitional queries while transactional and comparison queries hold, the cause is almost certainly something above you answering the question. If the decline is even across every query type, look elsewhere, because that is a different problem.

Crawler access restored on a date. Listings claimed and corrected, with a count. Factual errors fixed on third party sources, with a count. Pages published that answer prompts your baseline showed were being answered badly. Reviews responded to.

The Types That Rarely Earn Their Keep Elaborate breadcrumb hierarchies, speakable markup, deeply nested item lists and most of the specialised types outside their intended vertical produce little observable difference in how a brand is understood or recommended.

This matters more than any subtlety about model training. It means recommendations are built largely from pages that exist right now, which is why a page published this month can influence an answer this month, and why a brand absent from the retrievable web is absent from the answer regardless of how well known it is offline.

The test that keeps this honest is simple. Show the rewritten page to somebody who buys from you and ask whether it is clearer. If the answer is no, no amount of extraction friendliness makes it a good page. where to find a good ai seo services company

Read alongside the first displacement, the picture is consistent: the top of the list is worth less than it was on the results page, and worth considerably less again in a channel that does not use lists.

We also know the picture is unstable. Retrieval strategies are revised without announcement, and a method that explained answers well six months ago may explain them poorly today. Anyone selling certainty here is selling something they do not have.

A frequently quoted comparison showing assistant referrals converting several times better than search came from a vendor selling the service, across 312 business to business brands. A widely shared claim about explosive referral growth rested on nineteen analytics properties. Both are legitimate observations and neither supports the confident generalisation usually attached to them.

One section most briefs omit is worth adding: what has already been tried and what happened. Agencies frequently propose work that was done two years ago and abandoned, because nobody told them. Listing previous efforts, including the ones that failed, saves a month and signals that you will be a straightforward client to work with.

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.

The reasonable reading is that ranking gets a page considered while quotability and corroboration decide whether it is used. Treating a strong search position as an entitlement to appear in answers is the mistake that catches out established brands most often.

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.

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.

Direct Answers Beat Positioning When a model composes a recommendation it needs sentences it can attribute. Positioning language supplies none. A paragraph about being a trusted leader committed to excellence contains no attachable claim, so it is passed over in favour of a competitor who wrote down their turnaround time.

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.

Use the Soft Signals Deliberately Two free signals carry more information than their informality suggests. Add a how did you hear about us question to your enquiry form and read the free text monthly rather than the categories.

The change worth making is editorial direction. Stop commissioning new pages whose entire value is a fact a summary can state, and redirect that effort toward comparison, judgement, original data and anything requiring a transaction. Keep the existing pages, keep them current, and structure them to be quoted.

A weak brief produces a generic proposal, and a generic proposal produces a generic engagement that spends the first two months discovering things you already knew. The brief is the cheapest lever you have over the quality of the work.