"Alternate page with proper canonical tag" is a Google Search Console status that means this URL names another page as its canonical (the main version), Google agrees, and Google indexed that other page instead. In most cases it is not an error and there is nothing to fix. Google's Page indexing report help says such a page "correctly points to the canonical page, which is indexed, so there is nothing you need to do." Fix it only when the canonical points to the wrong page, or when this URL is the one you want in search.
The tricky part is telling the two apart. Below: what the status means, which cases are expected, the mistakes it can hide, how to check it in Google Search Console step by step, how to fix the real problems, and how common it is across 1,513 sites.
What does "alternate page with proper canonical tag" mean?
The name has two halves:
- Alternate page: Google sees this URL as a version of another page, not as a page of its own.
- Proper canonical tag: the URL tells Google which page is the main one, usually with a
<link rel="canonical">tag in the HTML head, and the page it names is valid and indexed.
Google's own examples are an AMP page that points to its regular version, and separate mobile and desktop URLs that point to each other's canonical. On most sites today, the URLs in this list are more ordinary: links with tracking or sort parameters, product variants, print views and copies of the same content under a second path.
Why Search Console says "Page is not indexed"
Google indexes one URL for each set of duplicate pages and shows that one in search. The alternate is not indexed under its own address, so its Page indexing details in URL Inspection read Page is not indexed: Alternate page with proper canonical tag (an AMP page is reported as URL is an alternate version). That sounds alarming, but the content is in Google's index: it is just filed under the canonical URL. Searchers who would have found the alternate find the canonical instead.
Is it an error? When to leave it alone
Usually not. "Proper" only means Google accepted your canonical, so the question is whether you picked the right page. This table covers the common cases:
| Situation | Example: alternate to canonical | Expected? | What to do |
|---|---|---|---|
| Tracking parameters | /shoes?utm_source=newsletter to /shoes | Yes | Nothing |
| Sort and filter parameters | /shoes?sort=price to /shoes | Yes | Nothing |
| AMP pages | /post/amp to /post | Yes | Nothing |
| Separate mobile site | m.example.com/page to www.example.com/page | Yes | Nothing |
| Print or plain-text versions | /guide/print to /guide | Yes | Nothing |
| Product variants | /shirt?color=blue to /shirt | Yes, if variants are not searched for on their own | Nothing, or give each variant its own canonical if it should rank |
| Paginated lists | /blog/page/2 to /blog | No | Give every page in the series its own canonical |
| Language versions | /es/guide to /guide | No | Each language should be its own canonical, linked with hreflang |
| A real content page | /pricing-guide to the homepage | No | Fix the canonical in the template |
If everything in your list matches the first six rows, you are done. The report is doing what it should: telling you Google saw the duplicates and indexed the right page.
When "alternate page with proper canonical tag" hides a real problem
Google accepting a canonical does not make the canonical right. It only means the pages looked similar enough for Google to go along with it. These are the mistakes that show up in this list:
- A template points every page to one URL. A theme or plugin bug sets the canonical of every post to the homepage or to its category. When the pages are short or similar, Google agrees, and a whole section disappears from search without a single error in the report.
- Paginated pages point to page 1. Google's pagination guidance says not to use the first page of a paginated sequence as the canonical, and to give each page its own. Pointing page 2 and beyond at page 1 can keep the items listed on them from being found.
- Translations point to the main language. Each language version should be its own canonical, connected to the others with hreflang. If translated pages appear in this list, check their canonical first. Our guide to hreflang tags vs geo-targeting explains how the language versions should reference each other.
- Your sitemap lists the alternate, not the canonical. The sitemap says
/page/, the canonical tag says/page, or one uses http and the other https. Google follows the tag, and the URL you submitted lands in this list. Nothing is lost in search, but your sitemap and canonical tags contradict each other on every page. - A page you want to rank is one of the alternates. It had its own traffic, a content update or a migration changed its canonical, and now its content counts toward another URL.
The warning signs: URLs you want in search appear in the examples, the count jumps right after a release, or the alternates are URLs from your own sitemap.
How to check alternate pages in Google Search Console
- Open Google Search Console and select your property.
- In the left menu, under Indexing, click Pages.
- Change the filter at the top of the report from All known pages to All submitted pages. Now you only see URLs from your sitemaps, the pages you told Google you want indexed. Alternates in this view are the ones worth a look.
- Under Why pages aren't indexed, click Alternate page with proper canonical tag.
- Look at the chart. A flat line is normal; a sudden jump after a deploy usually means a template changed.
- Scroll to Examples and click Export to get the list into a spreadsheet. Group the URLs by pattern: parameters,
/amp/,/page/2, language folders, or ordinary content pages. - For any URL that looks wrong, click it and choose Inspect URL. Under Page indexing, read User-declared canonical and Google-selected canonical. For this status both show the other page.
- Inspect that canonical URL too. It should say URL is on Google. If it does not, the content is in neither place, and you have a bigger problem.
To see the canonical a page declares right now, without waiting for a crawl, run it through the free Google index checker: it fetches the page and shows its canonical tag, status code and robots rules. Our URL Inspection tool guide explains the rest of that screen. Other reasons in the same table have their own fixes; for example, our guide to soft 404 errors covers pages Google judges empty.
How to fix alternate page with proper canonical tag
When the alternates are expected
There is nothing to fix in the pages themselves. Two cleanups still help:
- Keep alternates out of your sitemap. A sitemap should list only canonical URLs. Every alternate in it is a URL you asked Google to index and then told Google not to.
- Link to the canonical. Internal links, navigation and buttons should point to the canonical URL, not to parameter or variant URLs. Consistent links make Google's choice easier and save crawling.
When the canonical points to the wrong page
- Fix the canonical at the source. In the template, plugin or CMS setting, make the page point to itself:
<!-- On https://example.com/blog/page/2 -->
<!-- Wrong: --> <link rel="canonical" href="https://example.com/blog">
<!-- Right: --> <link rel="canonical" href="https://example.com/blog/page/2">
- Make every signal agree. The canonical tag, the URL in your sitemap, your internal links and any hreflang tags should all use the exact same URL, with the same protocol, host and trailing slash. Our canonical tag checklist covers absolute URLs, chains and the other syntax rules.
- Test the live page. In URL Inspection, run Test live URL, open View tested page and confirm the new canonical tag is in the HTML.
- Request indexing for the URL that should now be indexed, so Google crawls it with the new canonical sooner.
- Watch the status change. After the next crawl, the URL should move to indexed. If Google still treats the pages as duplicates, it moves to "Duplicate, Google chose different canonical than user" instead: then the pages are too similar, and the fix is distinct content, not another tag.
Alternate page vs the duplicate statuses
Search Console has three canonical-related statuses that look alike. The difference is who picked the canonical and whether Google agreed:
| Status | Your canonical | Google's choice | Usually |
|---|---|---|---|
| Alternate page with proper canonical tag | Points to another URL | Agrees and indexes that URL | Fine; check the canonical is the page you want |
| Duplicate, Google chose different canonical than user | Points to this URL or to one you chose | Indexes a different URL | Worth a look: your signals disagree |
| Duplicate without user-selected canonical | None declared | Picks one of the duplicates itself | Add canonical tags so you decide |
How common is it? Canonical statuses across 1,513 sites
We looked at the sites connected to IndexMachine: on October 31, 2026, about 1.17 million sitemap URLs on 1,513 sites, each with its latest state in Google's URL Inspection data. We counted how many sites had at least one sitemap URL in each canonical-related status. Aggregate counts only, with no site or URL named; these are sites whose owners signed up for an indexing tool, so they lean toward sites with indexing trouble. Most of these sites are on free accounts, where IndexMachine has not requested anything yet, so the numbers show where sites stand before indexing is turned on.
| Status in Search Console | Sites with at least one sitemap URL in it | Share of the 1,513 sites |
|---|---|---|
| Duplicate, Google chose different canonical than user | 139 | 9.2% |
| Alternate page with proper canonical tag | 61 | 4.0% |
| Duplicate without user-selected canonical | 51 | 3.4% |
In URLs, 5,838 sitemap URLs (0.5%) were alternates with a proper canonical, and 13,741 (1.2%) were duplicates where Google chose a different canonical. What that tells you:
- Alternates come in batches. The 61 sites averaged about 96 alternate URLs each. That is a template or a parameter pattern, not a single page, so one fix in one place clears most of the list.
- They were all in sitemaps. Each of those URLs was submitted for indexing while its own canonical tag pointed elsewhere: exactly the sitemap and canonical contradiction from the list above.
- Disagreement is more common than agreement. More than twice as many sites had URLs where Google rejected the declared canonical as had URLs where Google accepted it on an alternate.
Our own site is the clean case. On October 31, 2026, we ran URL Inspection on all 71 URLs in the indexmachine.co sitemap: the Google-selected canonical matched our declared canonical on all 71, and none were alternates. Every page declares itself as its canonical, and the sitemap lists exactly those URLs, so the two never contradict each other.
Request indexing only for pages that can be indexed
An alternate page will not be indexed under its own URL no matter how often you ask, so a Request indexing click on it is wasted. On a site with hundreds of parameter or variant URLs in the sitemap, that adds up quickly against Google's daily limit.
IndexMachine avoids that automatically. A free account imports every site in your Search Console and shows the coverage state of every sitemap page, so alternates and duplicates appear as a list instead of a handful of examples. With indexing turned on, its Chrome extension presses Google's own Request indexing button in your Search Console every day, on autopilot, using your full daily Google quota on every site. Your quota goes only to canonical pages Google can actually index, never to alternates or broken pages. Pages Google already shows as indexed are skipped, every other engine gets unlimited IndexNow, and you get 404 alerts and a weekly email report. You can pay once for lifetime access or subscribe.
See which of your sitemap pages Google filed as alternates
A free IndexMachine account imports your Search Console sites and shows the coverage state of every sitemap page, alternates and duplicates included. Turn on daily Request Indexing in your own Search Console plus unlimited IndexNow when you are ready.
FAQs
Is "alternate page with proper canonical tag" bad?
No, not by itself. It means Google found a duplicate version of a page, accepted the canonical you declared and indexed the canonical instead. It is only a problem if the canonical points to the wrong page, for example page 1 of a series or the homepage.
Should I fix alternate page with proper canonical tag?
Only if the URL is one you want in search under its own address. Parameter URLs, AMP pages, mobile versions and print views need no fix. If a real content page, a paginated page or a translation is in the list, change its canonical to point to itself and request indexing.
Why does Search Console say "Page is not indexed: Alternate page with proper canonical tag"?
Because Google indexes only one URL per set of duplicates. This URL points to another page as its canonical, Google agreed, so the other URL is the one in the index. The content is still searchable through the canonical URL.
Should alternate pages be in my sitemap?
No. A sitemap should list only canonical URLs, the pages you want shown in search. Remove alternates from it, or change their canonical if they are pages you want indexed.
How long does it take for the status to update after I change a canonical?
Until Google recrawls the page, which can take days or weeks. Requesting indexing for the page in URL Inspection usually brings the crawl forward. The Page indexing report then updates after it processes the new crawl.