Skip to content
Application notes · 8 min read

Part of Page Indexing Report in Google Search Console: Every Status Explained

Alternate Page With Proper Canonical Tag: Should You Fix It?

Alternate page with proper canonical tag means Google indexed the canonical instead. When that's expected, when it's a real problem, and how to check.

Alternate page with proper canonical tag means the URL names another page as its canonical, Google accepted it, and that canonical page is indexed. Google's Page indexing report help says there is “nothing you need to do”, and for most of these URLs that's right: they are variants (an AMP page, a mobile URL, a link with a tracking or sort parameter), and their content is in search through the canonical. It's a problem in one situation: the URL is a page you wanted indexed in its own right.

It's one of the not-indexed reasons in the page indexing report, and one of three about canonicals. Duplicate without user-selected canonical means the page declared no canonical and Google picked one. Duplicate, Google chose different canonical than user means you declared one and Google picked another. This one is the case where Google did what your tag asked.

What Alternate page with proper canonical tag means

When several URLs show the same or very similar content, Google groups them and indexes one of them, the canonical (What is canonicalization). A rel="canonical" link element or HTTP header is a strong signal for which URL that should be, though Google treats it as a hint, not a rule. When Google follows it, the URL carrying the tag is reported as an alternate and stays out of the index, and the signals Google has for it, links included, are consolidated into the canonical (How to specify a canonical URL).

The help page gives three examples: an AMP page with a desktop canonical, a mobile page with a desktop canonical, and a desktop page with a mobile canonical. The same page calls a duplicate or alternate status usually a good thing, since Google found the canonical and indexed it, and names filter and sort parameters as the likely reason for large counts. A count bigger than your number of real pages isn't a fault on its own.

In the URL Inspection tool (labels as of October 2026), an affected URL reads URL is not on Google, the Page indexing section is headed Page is not indexed: Alternate page with proper canonical tag, and User-declared canonical shows the URL your tag names. An AMP alternate gets its own verdict, URL is an alternate version, with the indexed URL shown as the Google-selected canonical (URL Inspection tool help). The URL Inspection API returns the reason in coverageState and your tag in userCanonical; its reference says googleCanonical is absent when the page isn't indexed.

When the alternate status is expected

Most alternates fit one of these patterns. In each, the canonical is the URL you want in search.

PatternExample URLWhy it's an alternate
AMP versionexample.com/amp/giraffesThe AMP page has rel="canonical" to the regular page, which links back with rel="amphtml" (amp.dev).
Separate mobile URLm.example.com/giraffesGoogle says the desktop URL is always the canonical and the mobile page its alternate (mobile-first indexing).
Tracking parameters?utm_source=newsletter, ?gclid=…The same page with a tag added. Google's canonical guide uses a gclid URL as its example of a duplicate.
Sort and filter parameters?sort=price, ?color=greenThe same collection, reordered or narrowed. The help page names these as the likely source of large counts.
Platform URL variants/collections/sale/products/coat, ?pr_prod_strat=…Shopify notes that collection-scoped product URLs have the same content as the product page, and its recommendations add tracking parameters to product links.
Other file formatsguide.docx pointing to guide.pdfA rel="canonical" HTTP header can name the preferred version of a non-HTML file, as in Google's own .docx to PDF example.

For these, leave the status alone. Don't request indexing for them, and don't add noindex or a robots.txt rule to shrink the count. Google's canonical guide recommends against noindex for choosing a canonical within a site, and warns that a URL disallowed in robots.txt may still be indexed without its content.

Volume is the one reason to act on expected alternates. Faceted navigation can create thousands of filter URLs, and crawlers have to fetch one to learn it's useless. Google's faceted navigation guide says rel="canonical" may reduce their crawl volume over time, but is generally less effective than robots.txt or URL fragments. Its crawl budget guide is aimed mainly at sites with a million or more pages that change weekly, or 10,000 or more that change daily. More in faceted navigation SEO.

When it's a real problem

“Proper” in the status name means Google accepted your tag, not that the tag is right. If a group is made of pages you want people to land on from search, the canonical is wrong and Google followed it.

A page you want indexed points at a similar page

Google won't choose a declared canonical that isn't similar to the page, the help page says, so a bug that points every page at the home page tends to be ignored rather than obeyed. The canonicals that do damage point at a near-duplicate, which Google is likely to accept:

  • Paginated pages pointing at page 1. Google's pagination guidance says not to use the first page of a sequence as the canonical and to give each page its own. More in pagination SEO.
  • Variant pages you built to rank. Google's product variant documentation says a single page with a variant selector has one canonical URL, typically the one without a variant pre-selected, and that there is no single canonical URL for the group when each variant has its own page. A blue coat page built to rank for “blue coat” should be its own canonical.
  • Template pages a CMS points at a main version. Location or service pages that a plugin canonicalizes to one page. Google's canonicalization troubleshooting guide names CMSs and plugins that point canonicals at undesired URLs as a common cause.

In frameworks, a common cause is a canonical set at layout level. In the Next.js App Router, a page inherits the metadata fields it doesn't set from its layouts, so a canonical in the root layout becomes the canonical of every page without its own:

// app/layout.tsx: no alternates.canonical here, or every page inherits it
export const metadata = {
  metadataBase: new URL("https://example.com"),
};

// app/blog/[slug]/page.tsx: each page names itself (resolved against metadataBase)
export async function generateMetadata({ params }: { params: Promise<{ slug: string }> }) {
  const { slug } = await params;
  return { alternates: { canonical: `/blog/${slug}` } };
}

Language or region versions point at each other

The help page says alternate language pages are not detected by Search Console, so correctly tagged translations don't appear under this reason. If a translated page is here, its rel="canonical" names another language version. Google says to declare language versions with rel="alternate" hreflang, and to pick a canonical in the same language, or the best possible substitute (How to specify a canonical URL). Pointing a regional version at another version in the same language (an en-GB page at its en-US twin) fits that guidance if you only want one of them in search, but it has a cost. In Google's Search Off the Record episode on how to read the indexing report, John Mueller explained that each language version has to be indexed on its own, and hreflang then swaps in the local version when results are shown. That suggests a version that is only an alternate can't be swapped in. Hreflang and indexing covers the annotations.

Your sitemap or internal links point at the alternate

Set the report's sitemap filter to All submitted pages. Alternates left in that view are URLs your sitemap lists while their canonical tag names another URL, a combination Google's canonical guide lists as a mistake: don't name one URL in a sitemap and a different one in rel="canonical" for the same page. The same guide says internal links should point at the canonical URL. Typical causes are a sitemap listing http:// or trailing-slash URLs while the tag names the other form, and UTM parameters on your own navigation links. Pick the canonical form, then make the tag, the sitemap, internal links and redirects agree.

The canonical changed without you

Google's JavaScript SEO basics say JavaScript shouldn't change the canonical from the value in the original HTML, and a page should have a single rel="canonical". The troubleshooting guide also describes hacks that inject a cross-domain canonical pointing at spam: a canonical on a domain you don't recognize is a security issue. URL Inspection shows details of the canonical only if it's in a property you own (URL Inspection tool help).

How to check your alternate pages

  1. Group the examples. Open the reason in the Page indexing report, first with All submitted pages, then All known pages. The examples table is limited to 1,000 rows and doesn't necessarily list every affected URL, so export it and group the URLs by pattern: /amp/, m., ?utm_, ?sort=, /page/.
  2. Inspect one URL per group. Read User-declared canonical, then inspect that canonical: it should be URL is on Google.
  3. Read the tag at the source. The live test can't evaluate this reason, because Google decides canonicals at indexing time (URL Inspection tool help), but View tested page shows the rendered HTML, where a JavaScript rewrite would appear. From a terminal, check the HTML your server sends and any canonical header:
curl -s "https://example.com/shoes?color=green" | grep -io '<link[^>]*rel="canonical"[^>]*>'
curl -sI "https://example.com/files/guide.docx" | grep -i '^link:'

How to fix a wrong canonical

Make the page you want indexed name itself: one rel="canonical" in the <head>, with an absolute URL, through one method (the HTML element or the header, not both), as Google's canonical guide recommends. List the page in your sitemap and link to it from related pages. Google's troubleshooting guide says it may keep pages in a duplicate cluster for up to two weeks after a fix, and suggests Request Indexing only for your most important URLs, since it's subject to quotas. Canonical tags covers how Google weighs the other signals.

How IndexCyborg handles alternate pages

Once you connect Search Console, IndexCyborg inspects the URLs in your sitemaps with the URL Inspection API and stores Google's coverageState word for word, with the user-declared canonical and, when Google returns one, the Google-selected canonical. This reason is filed under Duplicate / canonical exclusion: GET /v1/sites/{id}/urls?status=excluded_duplicate lists those pages, and the MCP tool get_unindexed_pages includes them. Because the inventory comes from your sitemaps (plus any URL you register through the API), the alternates you see there are URLs you submitted, not every variant Google has found. Its technical check reads the canonical link element of every page that returns 200 and, when it names another URL, raises Canonical points to a different URL with the declared canonical as evidence. A page that was indexed and comes back under any other reason raises Previously indexed page is no longer indexed, which is how a deploy that changed canonicals shows up.

The Chrome extension's own picks skip duplicate and canonical exclusions, since a request can't change Google's choice while the tag points elsewhere. After you make a page self-canonical, queue it by name with the REST API or the MCP tool request_google_indexing; it counts toward the cap of 10 requests per property per rolling 24 hours. More on the features page.

Frequently asked questions

Does Alternate page with proper canonical tag hurt SEO?

Usually not. It means Google followed your canonical tag and indexed the page it points to, and Google says signals for duplicate URLs, such as links to them, are consolidated into the canonical. It only costs you traffic when the alternate is a page you wanted in search in its own right.

Should I request indexing for a page marked Alternate page with proper canonical tag?

Not while it points to another page as its canonical: Google has already indexed that canonical, and requests are limited by a daily quota. If the page should be indexed itself, make it self-canonical first, then request indexing once.

Should alternate pages be listed in my sitemap?

No. Google says to pick a canonical URL for each page and submit those in your sitemap, and warns against naming one URL in the sitemap and a different one in rel="canonical" for the same page.

Why does the number of alternate pages keep growing?

Google reports every URL it knows, not only those in your sitemap, and new tracking, sort or filter parameters create new URLs each time they appear in links. If those URLs point to the right canonical, a growing count isn't a problem on its own.

How long does it take for a fixed page to leave this status?

Google has to crawl the page again and re-evaluate it. Google says it may keep pages in a duplicate cluster for up to two weeks after a fix, and the Page indexing report reflects the last crawl, so check the page in URL Inspection rather than waiting for the report.