Required properties before more schema types: the eligibility chain

Schema types get counted like currency: add one more object, wait for the citations to arrive. The documentation that governs eligibility does not work that way. Google states plainly that you don't need to create new machine-readable files, AI text files, or markup to appear in AI Overviews or AI Mode. What it does require is more boring than a type list, and it sits earlier in the chain than any markup decision.

The gate before the markup

To be eligible to be shown as a supporting link in AI Overviews or AI Mode, Google says a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements. That is the gate. A page blocked from indexing, or ineligible for a snippet, does not become eligible because it carries three more schema types. Markup enhances display on top of eligibility; it does not replace it.

This is why launch-time technical hygiene is the first GEO deliverable rather than a later cleanup phase. On the Abbys Consult platform, we shipped fast server-rendered pages, hardened security headers and clean search signals from day one: technical SEO issues at launch, 0, with time to first byte under 200 ms. None of that work is markup. All of it is the precondition that markup depends on to mean anything at all.

Complete objects beat a longer type list

Google's structured data guidance contains an ordering rule most schema audits ignore. You must include all the required properties for an object to be eligible for appearance in Google Search with enhanced display, and it is more important to supply fewer but complete and accurate recommended properties rather than trying to provide every possible recommended property with less complete, badly formed, or inaccurate data. Coverage is not the metric. Completeness per object is.

A site with two fully specified objects sits in a better documented position than a site with a dozen half-filled ones. Missing a required property means the object is simply not eligible for the enhanced display it was added to win. Google's own example joins scale to completeness: Rotten Tomatoes added structured data to 100,000 unique pages and measured a 25% higher click-through rate for pages enhanced with structured data, compared to pages without.

Two prohibitions in the same guidance set the boundary. Don't create blank or empty pages just to hold structured data, and don't add structured data about information that is not visible to the user, even if the information is accurate. That rules out the common shortcut of stacking answer-shaped markup onto thin pages. If you want an entity described in markup, put it on the page in visible text first.

Fan-out rewards subtopic coverage, not type count

Google documents that both AI Overviews and AI Mode may use a query fan-out technique, issuing multiple related searches across subtopics and data sources to develop a response. That changes what a page competes for. A single answer gets assembled from several related queries, so the useful work is covering the subtopics a reader would ask next, in readable prose. Schema does not create subtopic coverage. Published content does.

The Tatano Energy platform was built on that assumption. A biomass boiler manufacturer present in four European markets arrived with one generic site, no structured data and no localised content, facing competitors established in every country. We deployed a multilingual e-commerce platform across four country domains with a daily SEO autoblog driven by search trends. Country domains indexed separately: 4. Languages served: 7. SEO articles published every day: 8. Manual intervention required: 0.

Who you let read the page

Google eligibility is not the only gate. OpenAI uses OAI-SearchBot and GPTBot robots.txt tags to enable webmasters to manage how their sites and content work with AI. Sites that are opted out of OAI-SearchBot will not be shown in ChatGPT search answers, though they can still appear as navigational links. Disallowing GPTBot indicates a site's content should not be used in training generative AI foundation models. Two separate decisions, two separate tags.

That distinction matters when a schema experiment looks like it failed. If OAI-SearchBot is disallowed, no amount of markup produces a ChatGPT search citation, and the cause sits in a text file rather than in your JSON-LD. OpenAI also notes that for search results it can take ~24 hours from a site's robots.txt update for their systems to adjust, so a same-day reading of a change is not a reading of anything.

Measure where it is reported

Measurement is the part that gets invented. Google documents that these features are reported on in the Performance report, within the Web search type. There is no separate AI citation dimension to isolate, which means a per-schema-type attribution study has nowhere to read its result from. Anyone presenting type-by-type citation counts over a tracking window is presenting a model of the data rather than the data itself.

The practical order is unglamorous. Confirm the page is indexed and snippet-eligible, check which bots you allow and when that change takes effect, complete the required properties on the objects you already publish, and write content that covers the subtopics a fan-out would ask. Then read the result where it is reported rather than in a bespoke dashboard. Every step in that sequence is checkable, which is exactly why it beats a type-count experiment.

Sources

Google Search Central — AI features and your website — https://developers.google.com/search/docs/appearance/ai-features

Google Search Central — Introduction to structured data markup in Google Search — https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data

OpenAI — Overview of OpenAI Crawlers — https://developers.openai.com/api/docs/bots

Neurolinks case study — Four markets, one codebase — https://neurolinks.be/work/tatano-energy

Neurolinks case study — A consulting firm, dressed for trust — https://neurolinks.be/work/abbys-consult