Every page points home
What we check
On each page we sample, we look in the structured data for an entity that says what the page is — a WebPage, Article, BlogPosting, Product, Service, Event, FAQPage, or a more specific kind of one — and that ties it to your home page’s identity through isPartOf, publisher, provider, or author.
A tie counts if it uses the identity’s @id, or repeats the identity with the same url, or names an entity of the same type and name. It can go through a step or two: a page that points at your WebSite, which in turn names your organization, is tied. A page that is the identity (a product’s own page) is tied too. The score is the fraction of sampled pages that are tied; a page with no structured data counts 0. If the home page declares no identity, the check is skipped, since the structured identity rule already says so. The report names each page that falls short, and why.
Why it matters
Without a tie, each page is an orphan: an AI assistant reading your pricing page or a blog post can’t be sure it belongs to the company on your home page. With one, every page adds to what it knows about the same entity — this article was published by Example, this product is made by Example — and it can say so when it cites you.
How to pass
Give each page a JSON-LD entity for what it is, pointing at the @id your home page declares:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "WebPage",
"@id": "https://example.com/pricing",
"name": "Pricing",
"isPartOf": { "@id": "https://example.com/#website" },
"publisher": { "@id": "https://example.com/#org" }
}
</script>For a blog post, use BlogPosting with an author and publisher. Most site builders and SEO plugins can add this to every page from one template.