A primary entity refers to a different variant of this page

Why it matters

A consistent page reference helps readers of the markup identify which URL the primary entity describes. This review item does not establish which canonical Google selected.

What to do

1. Read the original declaration, both normalized URLs and their normalization steps in the report.
2. If the entity describes this page, align its url or mainEntityOfPage with the intended canonical and check the template that emits it.

When to leave it as it is: Keep a deliberate reference to another page, such as an original syndicated article. A nested publisher, author or breadcrumb URL need not equal this page’s canonical.

What we read

We use complete captured JSON-LD, Microdata or RDFa, the qualified HTML-head canonical and the same response’s final and requested URL. We do not run JavaScript or fetch remote contexts.

Only positive current-page references or an entity explicitly nominated by a self-referencing WebPage are considered. Unresolved or conflicting primary-page references remain not checked. Nested or graph-linked secondary entities do not self-nominate through their page reference; an explicit WebPage.mainEntity edge can establish a genuine nested primary entity.

Supported comparison resolves relative URLs and normalizes scheme and host case, default ports, fragments and one trailing slash. Path case, query strings, different schemes and subdomains remain distinct.

The report shows up to ten of the retained mismatch declarations and the actual total, with bounded original markup and source byte ranges. Long displayed normalization steps are marked as truncated without changing the compared URL.

Example & evidence

Illustrative URL variant; this is not a live audit.

<link rel="canonical" href="https://article.example/article">
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","mainEntityOfPage":"https://article.example/article?ref=nav"}</script>

When the captured page URL is https://article.example/article?ref=nav, this explicit self-reference differs from its declared canonical. Confirm the intended reference before changing it.

Confirm & check again

Check for yourself: Compare the structured-data declaration and canonical in the HTML served at the reported URL. Confirm that an apparent cross-page reference is not intentional.

Check again: Full audit — Run another full site audit. The same page needs sufficient current coverage and no remaining mismatch to confirm a correction. Missing coverage, ambiguous canonical, render-dependent markup or an unqualified HTTP Link header cannot close the finding.

Limits & sources

The canonical owner here qualifies HTML-head declarations only. Any captured HTTP Link field remains not checked because its canonical meaning is not qualified by this check.

This is a bounded consistency review, not a Google requirement that every entity URL equal its page canonical. Google’s selected canonical, indexing, ranking and rich-result display are not determined.

Confidence: High The finding records an explicit current-page identity qualification, captured declarations and deterministic URL normalization. Intentional or unproved references to other pages are not guessed to be errors.

Sources

• Google, Article structured data — Explains Article markup and page canonical guidance; it does not make mainEntityOfPage a required Article property. Checked 4 October 2026.
• Schema.org, mainEntityOfPage — Defines the page for which an entity is the main subject. Checked 4 October 2026.
• Google, How to specify a canonical URL — Describes canonical signals in HTML and HTTP and the need for consistent declarations. Checked 4 October 2026.

Editorial review: 2 November 2026