Why it matters
A unique identifier, such as the homepage URL in an organisation's url property, lets Google tell which specific entity is meant instead of reading a bare name. Said at Search Central Live: markup can also carry stable identifiers that the visible text lacks, for example for user-generated content.
How to meet it
Give the Organization a url (the homepage) and a logo and reference it by @id from other blocks; give products sku or gtin values; give each entity a stable @id URL with a fragment (https://www.example.com/#organization) and keep it constant across pages and releases.
How to test it
The Rich Results Test shows url and @id on the Organization and other entities, and the @id values are identical on every page.
How Regensbot covers it
Decided automatically once Regensbot crawls your verified site.
The crawl is polite: sitemap first, one request per second per host. A problem it finds is definite, and “none found” passes only on a complete crawl.
Sources
Google documents01
Claims in the knowledge base03
- D2-C502ConfirmedWhat is Structured Data and why we need it on the internet.Said on stage
- D2-C463UndocumentedWhat is Structured Data and why we need it on the internet.Shown on screen
- D2-C468n/aWhat is Structured Data and why we need it on the internet.The author's interpretation
Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)
- Confirmed
- Google's documentation states the same thing.
- Undocumented
- Said or shown at the event, not in the documentation.
- n/a
- Nothing to verify: a quotation, framing, opinion or analysis.