Why it matters
Google's site name system reads WebSite from the home page, and Organization supplies logo, sameAs and the canonical brand entity that other pages reference by @id.
How to fix it
Put one @graph with Organization and WebSite (stable @ids) on the home page; reference them from other pages.
Example
// app/page.tsx
<JsonLd data={{
'@context': 'https://schema.org',
'@graph': [
{ '@type': 'Organization', '@id': 'https://acme.example/#org', name: 'Acme', url: 'https://acme.example/',
logo: 'https://acme.example/logo-512.png', sameAs: ['https://github.com/acme'] },
{ '@type': 'WebSite', '@id': 'https://acme.example/#website', name: 'Acme', url: 'https://acme.example/',
publisher: { '@id': 'https://acme.example/#org' } }, // no SearchAction: sitelinks search box is gone
],
}} />References
More ai search rules
void geo reports 41 rules in this category. Generative-engine optimisation: whether AI crawlers that don't run JavaScript see the same content, valid and visible JSON-LD, an explicit AI robots policy, llms.txt, Markdown mirrors and answer-first writing.
jsonld-parse-errorJSON-LD block is not valid JSONjsonld-unsafeJSON-LD contains a literal </script or <!--jsonld-missingPage has no JSON-LDjsonld-not-in-rawJSON-LD is injected by JavaScriptjsonld-schemaJSON-LD @context isn't schema.org or @type isn't a schema.org typejsonld-requiredStructured data type is missing Google-required propertiesjsonld-recommendedStructured data missing recommended propertiesjsonld-datesStructured data dates are invalid, lack a timezone, or modified < published