“Alternate page with proper canonical tag” usually needs no fix. Google is reporting that this URL is an alternate version of another page, the canonical relationship is correct, and the canonical page was indexed. The useful question is whether that canonical is the page you actually want people to find.
A campaign URL that points to the clean service page can belong in this report indefinitely. A genuinely separate service page that accidentally points to the homepage needs investigation. The same label can therefore describe a sensible setup or reveal that the wrong business decision was encoded in a template.
Start with the intended page, not the excluded count
Google’s Page indexing report documentation treats this alternate state as expected. Your target is to have important canonical pages indexed, rather than to make every discovered URL indexable.
Classify the affected URL before editing anything:
| What the URL does | Intended search outcome | First decision |
|---|---|---|
| Adds campaign parameters to an otherwise unchanged page | The clean page represents the content | Keep the canonical relationship if Google selected that clean page |
| Offers another view of the same content, such as a print version | One main page represents both versions | Keep the alternate available when visitors need it |
| Has a separate product, service or substantive article | That page should be considered independently | Investigate why it declares another page as canonical |
| Exists only because of an obsolete URL pattern | Visitors should reach the permanent equivalent | Consider a permanent redirect, after confirming the destination |
Do not assume every filtered shop page belongs in the first group. Some filters produce useful landing pages; others simply rearrange the same products. Make the search and navigation decision for that filter pattern first.
Record Google’s decision for one exact URL
Open the affected example in URL Inspection and record the following from the indexed view:
- the full inspected URL, including its parameters, host and trailing slash;
- User-declared canonical;
- Google-selected canonical;
- Last crawl, the inspection date and the date of any recent canonical change.
Inspect the selected canonical separately if it is in a property you can access. Check its own indexing state instead of assuming an old alternate report proves the destination is indexed today.
These dates matter. Suppose you corrected a template on 28 October but the indexed view says Google last crawled the alternate on 24 October. Today’s source and Google’s older record can disagree without the correction having failed.
Google explains that canonical selection is available in indexed data. Test live URL can check current availability and returned content; it cannot tell you which canonical Google will choose after processing the page.
Compare the alternate with the destination
Use the Canonical URL Checker to read the current HTML canonical and HTTP Link header. It follows the page redirect and can inspect a bounded canonical chain. It does not render JavaScript or query Google’s selected canonical.
Then inspect the two pages as a visitor:
- Compare the main content. Ignore repeated navigation and footers. Does the alternate answer the same question or offer the same product as the destination?
- Check the exact destination. It should be the stable preferred URL, rather than an old host, a preview domain, an unrelated category or a redirecting intermediary.
- Check the preferred page’s response. The Google Index Checker can pre-check public HTTP, robots, noindex and canonical signals for one URL. A clean result means no tested blocker was found; it does not establish indexing.
- Check your own references. Navigation, contextual links and the sitemap should consistently identify the preferred version when they refer to this content.
Google’s canonical guidance describes canonical annotations and redirects as strong signals and sitemap inclusion as a weaker signal. Agreement helps express your preference, but none of these checks turns that preference into an indexing guarantee.
Example: a correct alternate that should stay excluded
The examples in this article are illustrative, not Search Console captures or client results.
A business shares this campaign address:
https://example.com/services/roof-repair/?utm_source=newsletterIt returns the same service content as the clean URL and declares:
<link rel="canonical" href="https://example.com/services/roof-repair/">In the illustrative indexed record, Google selects the clean URL. That is the intended result. Changing the campaign URL to a self-reference would tell Google that both identical pages should represent themselves, without making either more useful.
The before-and-after decision is deliberately small:
| Before review | After review |
|---|---|
| Owner sees one more excluded URL and considers removing the canonical | Owner confirms the clean canonical and records “intentional campaign alternate” |
| No distinction between the campaign address and the actual service page | The clean service page is checked for indexing and linked internally |
No canonical edit is necessary. If internal navigation repeatedly creates tracking versions, clean up those links where appropriate; that is a link-management task, rather than a reason to index the campaign copies.
Example: a service page incorrectly treated as an alternate
A template for /services/emergency-roof-repair/ inherits the canonical of /services/roof-repair/. The emergency page contains distinct availability information, a different service process and relevant project evidence. The business wants it considered independently.
The correction is to express that actual relationship:
<!-- On the distinct emergency service page -->
<link rel="canonical" href="https://example.com/services/emergency-roof-repair/">Review the main content as well as the tag. If the “separate” page only changes the title while repeating the same service description, a self-reference alone does not resolve the underlying duplication. Either develop a useful separate page or keep one stronger service page.
After the correction, use relevant internal links and include the intended canonical in the sitemap. Keep the established URL when it already serves the right purpose. A new slug is not required to correct a template’s canonical field.
Choose the action your evidence supports
| Evidence | Action |
|---|---|
| The alternate is intentional and Google’s selected canonical is correct | Leave it alone; document the URL pattern and intended destination |
| The alternate is useful to visitors but represents the same content | Keep it accessible and point directly to the preferred equivalent |
| The alternate has no remaining purpose | Plan a permanent redirect to the equivalent destination |
| The page should stand alone but declares the wrong canonical | Correct the declaration and review whether the page has sufficiently distinct content |
| Today’s declaration differs from a crawl before your release | Verify the live response and wait for a later indexed record before judging the outcome |
| Google selected a URL different from your declaration | Follow the different canonical diagnostic workflow |
Avoid adding noindex or a robots.txt block merely to make this label disappear. Those controls answer different questions. A robots block can prevent Google from reading your canonical, while noindex asks for exclusion rather than expressing the preferred representative of duplicate content.
Verify the change without chasing a zero
If you made a genuine correction, save the previous and current declarations and your deployment date. Check both URLs live, then request indexing for an important changed page when appropriate. Revisit URL Inspection after Google’s recorded crawl advances and compare the selected canonical with your intended outcome.
An unchanged live test immediately after a request is not proof that Google reprocessed the duplicate cluster. Repeated requests do not supply the missing evidence.
For an intentional alternate, there is no fix to validate. For an accidental alternate, success is the correct relationship and a useful canonical page being considered for indexing. The number of URLs in this report can remain substantial on a healthy site.
If your report instead says Duplicate without user-selected canonical, start with the guide for a missing canonical preference. For implementation details beyond this status, read canonical tags explained.
Google documentation and the linked tool capabilities reviewed on 28 October 2026.
Frequently asked questions
Is alternate page with proper canonical tag an error?
Usually no. Search Console is reporting that the inspected URL is an alternate and correctly points to a canonical page that Google indexed. Check that the selected canonical is the page you want found. An intentional duplicate does not need its own index entry.
Should I remove the canonical to get the alternate indexed?
Only reconsider the canonical if the page should serve a distinct search need. Removing a tag does not make duplicate content different or force Google to index the URL. Keep the existing setup when the alternate and its selected canonical represent the same content intentionally.
Can a canonical checker confirm that Google accepted my canonical?
No. A public checker reads the site's current declarations. Search Console URL Inspection's indexed view shows Google's selected canonical. Even Google's live test cannot predict the canonical selected during indexing.
