“Alternate page with proper canonical tag” usually confirms that Google recognized an alternate version and indexed its canonical representative. You normally do not need to make that alternate URL appear in search separately.
Check whether the selected page is the one you intended. A tracking URL pointing to its clean article URL can be correct. An original article pointing to an unrelated page deserves investigation, even when the report describes the tag as proper.
The practical task is to compare the alternate with its canonical, decide whether they should represent the same content, and change only the pattern that produces an unintended result.
What ‘Alternate page with proper canonical tag’ means
A canonical URL is the preferred representative of duplicate or very similar content. An alternate can remain accessible to visitors while another address represents that content in search.
Google's Page indexing documentation[1]Source 1Page indexing documentationView source ↗ says this status identifies a page that correctly points to its indexed canonical. If that arrangement matches your intention, no corrective action is needed.
Keep neighboring report states separate:
| Search Console state | Main distinction | First useful check |
|---|---|---|
| Alternate page with proper canonical tag | An alternate correctly points to its canonical | Does that relationship match your intention? |
| Duplicate without user-selected canonical | Google selected a representative without a declared preference for this duplicate | Inspect which URL Google selected |
| Duplicate, Google chose different canonical than user | Google's selection differs from the declared preference | Compare the declared and selected pages |
| Page with redirect | The address forwards elsewhere | Trace the destination and inspect it separately |
Canonical annotations do not move visitors. A browser can stay on the alternate address while Google uses another representative. A redirect changes the request path, so the two methods produce different browsing behavior.
Compare the canonical URL with the alternate
Open Indexing > Pages in Search Console, select Alternate page with proper canonical tag, and choose an example. Copy the exact URL, including any query parameters.
Open that page and the canonical target side by side. Compare their main content and purpose. A different URL alone does not establish a different page, and a shared header does not establish duplicate content.
Canonical comparison workflow
- Record the affected URL and what you want it to represent.
- Inspect its declared canonical and Google's recorded selection.
- Open the alternate and selected page.
- Compare their useful main content and intended audiences.
- Decide whether to retain the relationship or investigate a specific mismatch.
For a public check on this site, we requested our redirect guide at its clean URL and with ?utm_source=canonical-check appended. Both returned 200, identical normalized article text, and the clean URL as their declared canonical.
That is a concrete example of two addresses delivering the same article. The check establishes the site's output only. We did not access Google's selected canonical or a private indexing report for those requests.
Read user-declared and Google-selected canonicals
In the URL Inspection tool, compare User-declared canonical with Google-selected canonical when those fields are available.
The first describes the preference Google detected. The second records Google's choice. Record the crawl date too, because the indexed view can reflect an earlier configuration.
View source or inspect the rendered HTML to check the current canonical. That verifies what the page declares now. It cannot reveal Google's current selection by itself, and a successful live access test does not prove that a URL is indexed as canonical.
If the fields disagree, use the guide to Google choosing a different canonical. That is a separate investigation from confirming an expected alternate.
Decide whether the alternate should be indexed separately
Use the content and visitor task to make this decision. Do not change every alternate to a self-referencing canonical merely to make the exclusion disappear.
| Observed pattern | Usually keep or review? | Reason |
|---|---|---|
| Tracking parameters deliver the same article | Keep the intended relationship | The parameter does not create a new article |
| A print layout repeats the same guide | Keep if the main guide is the intended representative | Presentation differs while the content is equivalent |
| A product has multiple paths with the same details | Check a sample, then retain a correct mapping | Several paths can represent one product |
| A distinct article points to another article | Review | A template or custom field may suppress unique content |
| A filtered page has a separate useful purpose | Review its content and indexing plan | A parameter can change meaning, not just tracking |
| The target is missing, empty or unrelated | Review | A syntactically valid tag can still express a bad preference |
A large alternate count can reflect many combinations of paths and parameters. Sample those patterns before concluding that important content is missing. A small site with many URL variants needs an explanation of the variants, not an automatic site-wide rewrite.
Treat pagination and translated pages carefully
Do not strip all parameters from canonical targets. A parameter such as page=2 can identify a different set of products, while a campaign parameter may leave the content unchanged.
Google's pagination guidance[2]Source 2Pagination guidanceView source ↗ recommends a unique URL and its own canonical for each page in a paginated sequence. It also states that Google no longer uses rel="next" and rel="prev" to identify pagination relationships. Adding those tags is not a repair for an incorrect canonical target.
Translated content needs its own language strategy. Google's status documentation explicitly says alternate language pages are not detected by this report. Do not point every translation to the English page simply because the pages cover the same subject.
For language and region annotations, consult Google's localized-page guidance[3]Source 3Localized-page guidanceView source ↗. Check the content, language and intended market rather than assuming every locale URL is an unwanted duplicate.
Check the canonical tag and supporting signals
A typical HTML canonical annotation belongs in the document's <head>. This illustrative example declares the clean guide URL as preferred:
<link rel="canonical" href="https://example.com/guide">The alternate and the preferred page can both declare that same preferred address. On the preferred page, the annotation is self-referencing because it points to that page's own URL.
Google's canonicalization guidance[4]Source 4Canonicalization guidanceView source ↗ recommends absolute URLs, consistent signals and a self-referencing canonical on the preferred page. Check the protocol, hostname, path and slash instead of assuming a nearly identical target is correct.
Open the target directly. Confirm it serves the intended content and can be considered for indexing. If it displays an empty template or missing-page message, investigate that response and content mismatch before treating the mapping as healthy.
Keep source and rendered canonicals consistent
Inspect both the original HTML and the rendered document when JavaScript or plugins can change page metadata. Look for multiple declarations, a staging hostname, an old path or a template that assigns the same target to unrelated pages.
Check who owns the output. A CMS default, SEO plugin, custom field and theme override can all interact. Change the responsible setting, then inspect the delivered page rather than relying solely on the editor's saved value.
Google's canonical troubleshooting guide[5]Source 5Canonical troubleshooting guideView source ↗ discusses incorrect canonical elements and rendering-related changes. Use the actual difference you observe to guide the repair.
Fix the URL pattern that creates the wrong result
Group affected URLs by their shared cause: campaign parameters, collection paths, print formats, slash variants or a particular content template. Record a working example alongside a faulty one.
For a genuine duplicate that must remain accessible, retain the appropriate canonical relationship. If an obsolete address should disappear from normal navigation, a relevant permanent redirect may suit the intended behavior better.
For a unique page mistakenly pointing elsewhere, correct the declaration and check that the page delivers its distinct content. Changing only the tag will not make two otherwise identical pages serve different purposes.
Pattern repair workflow
- Identify the template or setting producing the unintended target.
- Correct one representative example safely.
- Compare the delivered HTML and rendered page after the change.
- Check another affected page and an unaffected control.
- Apply the verified rule to the appropriate pattern.
Align internal links and sitemap entries with your intended representatives. For example, normal article navigation can link directly to the clean URL while campaign links retain the parameters needed for measurement.
Avoid using robots.txt as a canonical-selection switch. Blocking a URL can prevent Google from reading its content and canonical annotation. Noindex is also a different decision: it asks for search exclusion rather than expressing which duplicate should represent the content.
Verify ‘Alternate page with proper canonical tag’ against your goal
After an actual repair, confirm the current target, response and content first. Then compare fresh Search Console evidence as Google recrawls and reprocesses the pages.
For an intentional alternate, success means the right representative is selected and the duplicate relationship remains useful. The alternate can continue to appear in this report.
For a unique page excluded by mistake, success means it now serves its intended content, declares the appropriate preference and is evaluated accordingly. A new annotation does not guarantee a particular indexing outcome.
Record one alternate, its declared target, Google's recorded selection and your intended representative. If those agree and the content relationship is correct, keep the setup. If they do not, repair the specific cause and repeat the same comparison.
Sources
Google Search Console Help. Page indexing documentation.
Google Search Central. Pagination guidance.
Google Search Central. Localized-page guidance.
Google Search Central. Canonicalization guidance.
Google Search Central. Canonical troubleshooting guide.
