Schema Markup for AI Search

Structured data is machine-readable information about a page, written in the shared schema.org vocabulary. JSON-LD is the encoding Google recommends — one JSON block inside a <script type="application/ld+json"> tag. A schema type names what something is: Organization, Service, FAQPage. A property states one attribute of that thing: name, logo, areaServed.

Google's generative-AI optimization guide sets the ceiling in its own words: "Structured data isn't required for generative AI search, and there's no special schema.org markup you need to add", then keeps markup in scope because "it helps with being eligible for rich results on Google Search" (checked 2026-09-21).

Two functions survive that sentence. Schema states a fact once, in a fixed form, and an identifier property ties the record to a public database. Neither function produces a citation by itself.

Verbalization is the practice of stating in readable text every value a page also encodes as data. Google words the same requirement as a best practice that outlives its own "not required" position: "Making sure your structured data matches the visible text on the page" (checked 2026-09-21).

The failure is silent, which is what makes it common. A validator passes a JSON-LD block no visible text supports. A rich-result test renders a preview. The page ships one set of facts to a parser and a smaller set to every text extractor reading it.

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "AI Visibility Audit",
  "provider": { "@id": "https://kcaiseo.com/#org" },
  "areaServed": { "@type": "City", "name": "Overland Park, Kansas" }
}

That block asserts three facts: a service named AI Visibility Audit exists, the organization at https://kcaiseo.com/#org provides it, and the area it serves is Overland Park, Kansas. A page carrying that block states all three in body text, so an extractor reading the rendered output alone loses nothing.

Each row restated against the audit minimum: Organization requires name, url, logo, sameAs and contactPoint. Service requires name, provider, areaServed and description. FAQPage requires a mainEntity list whose entries carry name and acceptedAnswer. BreadcrumbList requires an itemListElement list whose entries carry position and name. LocalBusiness requires address, telephone and openingHoursSpecification, and belongs only on a page displaying that street address as text.

Placement follows those four names. Organization sits in one sitewide block referenced by @id. Service sits on the page selling it. FAQPage and BreadcrumbList sit where visible questions and a visible trail exist. All four are machine-readability fixes an audit returns.

• logothe image representing the organization record.
• sameAsthe URLs of that organization's own records elsewhere, which is how entity resolution works past one domain.
• providerthe link from a Service back to the Organization selling it.

Google marks none of the three mandatory: "There are no required properties; instead, add the properties that apply to your organization" (Organization documentation, checked 2026-09-21). The five-property minimum above is this audit's standard.

Our own audit of nine Kansas City competitor pages, September 2026, measured the identifier gap: zero of the nine emitted a Wikidata QID, and two — 360automation.ai and techtency.com — linked a Wikipedia article carrying no QID.

"@type": "Article",
"about": { "@id": "https://www.wikidata.org/wiki/Q134083964" }

Those two lines assert that the document is an Article whose subject is Wikidata item Q134083964, generative engine optimization. An identifier resolves to a record; a name resolves to nothing.

A rich result is a search listing rendered with extra visual elements drawn from structured data. Both statuses trace to one source.

Google's changelog entry "Removing the FAQ rich result", dated 15 June 2026, records the 7 May stop and the deletion of the documentation; the former FAQPage URL now 301-redirects to that entry. The How-to documentation was withdrawn on 14 September 2023, and its URL redirects the same way. Both checked 2026-09-21.

Neither removal deletes the meaning. Google states that unused structured data "does not cause problems for Search" while producing no visible effect. FAQPage still marks a question and its answer as one pair. HowTo still marks an ordered procedure as one sequence. Whether a given site emits either type correctly is a measured property, and the structured-data category of the examination reports it per page.