Schema for AI Search: What Actually Helps in 2026?
Structured data is valuable when it makes the page more explicit. It becomes risky when the markup claims services, ratings, locations or answers that visitors cannot verify in the visible content.
Is a special AI schema required?
No. Google states that there are no additional technical requirements for AI Overviews or AI Mode and no special schema.org markup to add. A supporting page must be indexed, eligible for a snippet and compliant with normal search requirements.1
This distinction matters. Schema is a standardised description layer; it is not an “AI Overview switch”. Google still recommends useful content, crawl access, internal links, text availability, good page experience, current business profile information and structured data that matches visible text.
Creative Orbit framework — Visible Truth → Structured Identity → External Proof: state the fact clearly on the page, encode the same fact consistently in structured data, then corroborate important claims through reviews, citations, profiles and credible third-party sources.
Which schema types are useful?
Choose the most specific type that reflects the page’s main purpose. Google’s guidelines require structured data to be a true representation of visible content and recommend placing markup on the page it describes.2
Organisation or LocalBusiness
Define the business identity, URL, contact details, address or service area, and trusted sameAs profiles. Use a specific subtype where it genuinely applies.
Service
Describe one visible service, its provider and the area served. Do not generate a catalogue of services that the page never discusses.
BlogPosting
Identify the article headline, author, publisher, dates, image and canonical page so ownership and freshness are explicit.
BreadcrumbList
Express the page’s place in the site hierarchy and align the markup with visible, crawlable navigation.
FAQPage
Mark up genuine questions and answers visible on the page. Keep the schema text aligned exactly with the rendered FAQ content.
JSON-LD is Google’s recommended format in most cases because it separates the data block from visible markup and is generally easier to maintain.3
What changed for the FAQ schema?
Google stopped showing the FAQ rich-result feature in search from 7 May 2026.4 That change removes the old visual incentive; it does not make clear, useful on-page FAQs irrelevant.
Keep FAQPage markup where the page genuinely contains an FAQ and the structured answer matches what users can read. Remove low-value boilerplate written only to occupy search-result space. The strategic purpose is now semantic clarity and answer usability, not an expandable rich-result promise.
Use FAQ markup when
- The questions are specific to the page’s topic and actual audience needs.
- Each answer is visible, self-contained, factual and current.
- The JSON-LD matches the on-page wording.
- The section improves the page even if no search feature appears.
How should entities connect?
Use stable identifiers and consistent relationships so the same organisation, person, service and webpage are not described as disconnected objects.
- Give the organisation a stable
@id, usually based on its canonical website URL plus a fragment. - Reference that same entity as the publisher, provider or parent organisation where appropriate.
- Use canonical URLs for the webpage and article.
- Link the named author to a substantive profile page.
- Use sameAs only for authoritative profiles representing the same entity.
- Keep names, URLs, service areas and contact details consistent with visible content.
For Creative Orbit, that means a clear connection between Simon Bayliss, the Creative Orbit organisation, the Wollongong service location, the SEO Wollongong service and the AI search optimisation service. The graph should clarify real relationships, not manufacture authority.
What technical checks matter?
Valid schema cannot rescue a page that crawlers cannot access or users cannot read. Test the full delivery path, not only the JSON-LD syntax.
Run this deployment checklist
- Confirm the page returns a successful response and is indexable.
- Ensure important content is present in the rendered and source HTML.
- Validate schema syntax and the requirements of any targeted Google feature.
- Compare every marked-up claim with the visible page.
- Check canonical, dates, author, image URLs and breadcrumb destinations.
- Allow the search crawlers needed for the platforms you want to reach.
- Monitor Search Console and server logs after deployment.
OpenAI says OAI-SearchBot is used to surface websites in ChatGPT search and that sites opting it out will not be shown in ChatGPT search answers, although navigational links may still appear.5 Crawler access and schema solve different problems: access enables retrieval; structured data improves explicitness.
Does llms.txt replace schema?
No. Google explicitly says llms.txt and other special AI text files are not required for Google Search or its generative AI capabilities.6
An llms.txt experiment may be maintained for systems that choose to use it, but it should not compete with the essentials: crawlable server-delivered content, accurate canonical pages, internal links, valid standard schema and a coherent external entity footprint. Treat it as optional documentation, not a substitute for technical SEO.
A page-specific SEO and AI-readiness audit should therefore test retrieval, rendering, structured data, entity consistency and content evidence as one system.
Frequently asked questions
Is there a special schema for Google AI Overviews?
No. Google states that no special schema.org structured data is required for AI Overviews or AI Mode. Pages still need standard crawlability, indexability, snippet eligibility, helpful content and structured data that matches the visible page.
Does schema guarantee an AI citation?
No. Structured data can reduce ambiguity and help machines understand page entities, but it does not guarantee selection, ranking or citation. Content quality, technical eligibility, authority, corroboration and the needs of each generated answer still matter.
Should FAQPage schema still be used in 2026?
FAQPage remains a valid Schema.org type, but Google stopped showing its FAQ rich-result feature in Search from 7 May 2026. Use FAQ markup only when the page contains genuine visible questions and matching answers, not to chase a discontinued visual result.
Which schema types suit a local service business?
Use the most specific valid types that match the page: Organisation or LocalBusiness for the entity, Service for an actual service, BlogPosting for an article, BreadcrumbList for navigation and FAQPage for a genuine FAQ section. Required and recommended properties depend on the type and search feature.
Does Google use llms.txt for AI search?
Google says llms.txt and other special AI text files are not needed for Google Search or its generative AI features. Other systems may handle such files differently, but llms.txt is not a substitute for crawlable HTML, internal links, accurate content or standard technical SEO.
Make your entity data reliable
Audit schema, crawler access and visible content as one connected search system.
Contact Creative OrbitBook an SEO Health Chat!References
- Google Search Central — AI features and your website
- Google Search Central — General structured data guidelines
- Google Search Central — Introduction to structured data
- Google Search Central — Documentation updates
- OpenAI — Overview of OpenAI crawlers
- Google Search Central — Optimising for generative AI features
