Ranking Fixer Alternate Page With Proper Canonical Tag: When It's Fine and When It Isn't
"Alternate page with proper canonical tag" means the URL in the report points to another page as its canonical, Google agreed, and it indexed that other page instead. Most of the time it needs no fix: the report is just listing the copies Google grouped under the main URL.
It becomes a problem when the URLs listed are pages you want in search, or when the count jumps after a release. That usually means a template is writing the wrong canonical, which is where indexing fixes in the code come in.
What the status means
Google's Page indexing report puts it this way: the page "is a duplicate of a page that Google recognizes as canonical. This page correctly points to the canonical page, so there's nothing for you to do." The URL stays out of search, and the canonical page is shown instead.
It is one of three canonical statuses in the report. If you see "Duplicate without user-selected canonical" or "Duplicate, Google chose different canonical than user" next to it, the guide to duplicate URLs and canonicals compares all three.
Which URLs are normal to see here
Open the report and look at the example URLs. Their pattern tells you whether there is anything to do.
| URL type | Example | Verdict |
|---|---|---|
| Tracking and campaign URLs | /page?utm_source=newsletter | Expected |
| Sort and filter parameters | /shoes?sort=price | Expected |
| AMP or separate mobile URLs | /page/amp, m.example.com/page | Expected |
| Print or share versions | /page?print=1 | Expected |
| Pages 2, 3, 4 of a list pointing to page 1 | /blog?page=3 | Problem: the products or posts on those pages lose a path in |
| Language or country versions pointing to one version | /en-gb/page → /page | Problem: the local version cannot rank in its country |
| Every page pointing to the home page | /services → / | Problem: a template bug hiding the whole site |
| Product variants people search for by name | /shirt-blue → /shirt | Depends: a problem if the variant has its own demand |
When it hides a real problem
- The count jumped after a release. A theme update, a new CMS plugin or a framework change started writing a canonical to the home page or to a category on every page.
- Local or language versions are listed. The UK or Canadian page points to the US one, so Google never shows the local version in that country.
- Paginated pages are listed. Pages 2 and beyond point to page 1, and the products or posts only linked from them become harder to reach.
- The canonical points to the old site. After a migration, staging or the previous domain is still declared as canonical.
- JavaScript changes the tag. The HTML from the server says one URL and the rendered page says another. Google uses what it sees after rendering, so the two can disagree.
How to check a URL in two minutes
- Open URL Inspection for an example URL and compare "User-declared canonical" with "Google-selected canonical". For this status they match.
- Ask whether that URL should rank. If not, you are done. If yes, the canonical on the page is wrong.
- Compare the source and the rendered HTML. View the page source, then the rendered HTML in URL Inspection, and look for a different or second
rel="canonical". - Crawl the site with any SEO crawler and list the pages whose canonical is not themselves. A whole page type pointing elsewhere is a template issue.
How to fix a wrong canonical
- Decide which URLs should rank. List the page types that deserve their own place in search: services, products, articles, local and language versions. Everything else can point elsewhere.
- Make every indexable page point to itself. Each page that should rank declares its own URL in <link rel="canonical">, with the same protocol, host and trailing slash as your internal links.
- Fix the template, not page by page. When hundreds of URLs appear at once, one template is writing the wrong canonical. Fix it in the theme, layout or CMS setting that generates the tag.
- Give each language version its own canonical. Every language or country page points to itself and links to the others with hreflang. A canonical pointing to another language tells Google to drop the local page.
- Let paginated pages point to themselves. Page 2 is not a copy of page 1. A self-referencing canonical keeps the products or posts listed there reachable.
- Line up the other signals. Internal links, redirects and the sitemap should all use the URL you want indexed. List only canonical URLs in the sitemap.
- Ask Google to look again. Use Request indexing in URL Inspection for a few key pages, then watch the count in the Page indexing report as Google recrawls the rest.
Migrations are where wrong canonicals pile up, which is why checking them is part of every SEO website migration. On online stores, variants and filters are the usual source, covered in ecommerce technical SEO.
Questions about alternate pages and canonicals
What does "Alternate page with proper canonical tag" mean?
It means the URL in the report points to another page as its canonical, Google agreed, and Google indexed that other page instead. Google says there is nothing to do: the status only lists the copies it found and grouped under the main URL.
Is "Alternate page with proper canonical tag" bad for SEO?
Usually not. Links and signals from the copies are consolidated on the canonical page. It only costs you when the URL in the report is a page you want ranked, such as a local version, a paginated list or a product variant with its own searches.
How do I get Google to index an alternate page?
Make it its own canonical: change the tag to point to itself, give it content that is meaningfully different from the other page, link to it internally and list it in the sitemap. Then request indexing in URL Inspection.
Should alternate pages be in the sitemap?
No. The sitemap should list only the URLs you want indexed. Listing a URL whose canonical points elsewhere sends Google two different answers about the same page.
Pages you need are listed as alternates?
Email the site and one example URL from the report. I reply with where the canonical comes from and how I would fix it.
- Email: calebe.development@gmail.com
- WhatsApp: +55 11 98838-5247
- Who replies: Calebe Araujo, the developer who does the work
Page updated on .