Alternate page with proper canonical tag: when to fix it
Understand this Search Console status, decide which alternate URLs should stay excluded, and correct unintended canonical targets with a verification checklist.
Start with the intended canonical page
Alternate page with proper canonical tag usually describes an expected duplicate: Google is treating another URL as the canonical version. The alternate itself is not indexed. If the selected canonical is the page you want in search, you normally have no correction to make.
A tracking URL such as /pricing?utm_source=newsletter can serve the same page as /pricing. The useful question is whether /pricing is eligible and selected as intended, rather than how to make every tracking variant appear in search.
Decide whether the alternate needs a fix
| Example | Desired behavior | Action |
|---|---|---|
| Tracking parameter on an otherwise identical page | Clean page is canonical | Keep the relationship; link internally to the clean URL |
| An HTTP or obsolete URL with a replacement | Visitors arrive at the replacement | Use an appropriate permanent redirect if the old page is retired |
| A distinct feature page canonicalized to the homepage | Feature page is independently indexable | Correct the template; use its own canonical and meaningful unique content |
| Duplicate print or sorting view | Primary view represents the content | Keep a consistent canonical if the content is equivalent |
| Translated page pointing to another language | Each language has its own eligible page | Review canonical and hreflang implementation rather than treating translations as duplicates |
Inspect the affected URL and its target
- Choose one important example from the report. Record its exact URL and why you think it should or should not be indexed.
- Use URL Inspection to compare the user-declared canonical with Google's selected canonical in the indexed data.
- Fetch the HTML and response headers. Look for a canonical in the head and any HTTP Link header that declares another target.
- Open the canonical target: confirm it resolves to the intended content and does not redirect to an unrelated page.
- Review the same page template on other examples. A hard-coded homepage canonical can affect an entire content type.
curl -L -D headers.txt https://example.com/features/export -o page.html
<!-- In the document head, when this is the preferred page: -->
<link rel="canonical" href="https://example.com/features/export" />Make the site's signals agree
For a page intended to stand alone, make its canonical, internal links, and sitemap entry use the same public URL. Remove accidental noindex instructions and allow the content to be crawled. Resolve conflicting template or HTTP-header declarations.
A canonical is a signal, and Google can choose a different URL. Distinct content and consistent links make your preference easier to interpret. Changing the tag alone does not turn a near-identical collection of pages into useful independent search results.
Avoid fixes that create another indexing problem
- Do not add noindex to a duplicate merely to force Google to select another canonical; use canonicalization methods for that purpose.
- Do not block the page in robots.txt and then expect Google to read a corrected canonical in its HTML.
- Do not redirect a useful, distinct page to the homepage to clear a report status.
- Do not add tracking and sorting duplicates to the sitemap to request indexing for every variation.
Record the change and review Google's later crawl
Save a before-and-after record of the URL, declared canonical, target response, and template change. Inspect the live page to confirm the deployed output; later, check the indexed inspection data to see whether Google has processed it. A live inspection is not evidence that the canonical selection has already changed.
If the preferred page remains unindexed, investigate its reported reason and content. For a sitemap that was successfully processed, repeatedly resubmitting it does not resolve a page-level canonical or quality issue.
Ready for a pre-launch audit?
Run the public analyzer and get a prioritised report for the URL you are about to share.
Run the SEO audit