Alternate page with proper canonical tag: what it means, and when to leave it alone

The short version

• It isn’t an error. Google found a second address for one of your pages. The page told Google which address is the original, and Google agreed.
• The original is indexed. The copy isn’t, and it doesn’t need to be.
• Look closer only if the address in the list is the one you want people to find, or a page you care about is missing from Google.
• One look-alike can need work: “Duplicate, Google chose different canonical than user”. You named an original and Google picked another page.
• To check any page, use URL Inspection in Search Console and compare “Google-selected canonical” with “User-declared canonical”.

What “Alternate page with proper canonical tag” means

Google’s help page for the Page indexing report defines it in two sentences: "This page is marked as an alternate of another page (that is, an AMP page with a desktop canonical, or a mobile version of a desktop canonical, or the desktop version of a mobile canonical). This page correctly points to the canonical page, which is indexed, so there is nothing you need to do."

“Canonical” is Google’s word for the original: the one address, out of several showing the same thing, that it puts in search results. The examples in that definition are AMP and mobile pages, which few small sites have any more. The more everyday causes are in Google’s guide to canonicalization, which lists, among others:

• Protocol variants: "the HTTP and HTTPS versions of a site".
• Site functions: "the results of sorting and filtering functions of a category page".
• Device variants: "a page with both a mobile and a desktop version".

Tracking tags are another: Google’s own canonical how-to uses the example of a product page reached through an address ending in ?gclid=ABCD, a tracking tag. And the canonicalization guide says: "Some duplicate content on a site is normal and it's not a violation of Google's spam policies."

Our own homepage is an “alternate page”

We ran Google’s URL Inspection tool over a handful of addresses for our own site on 18 October 2026, and again on 20 October 2026, the morning we published. Both times it reported the same:

/index.html is the file our homepage is stored as, so the homepage answers at both addresses. We fetched both: they return exactly the same page, byte for byte, and both carry the same line in their code:

<link rel="canonical" href="https://www.lolasquared.com/">

Google crawled the /index.html address on 15 October, read that line, and kept the homepage at its proper address. Its own choice of original and ours are the same. Nothing to fix.

Every page on our site can be reached with /index.html on the end. We checked four more, and Google hasn’t come across any of them. We don’t know how it found the homepage’s.

One oddity: the wording depends on the language you ask in. Asked in US English, or with no language set, the inspection tool says “Alternate page with proper canonical tag”, as the help page does. Asked in British English, it says “Alternative page with proper canonical tag”. It’s the same status, so if you see “Alternative”, everything here still applies.

What is a canonical tag?

It’s one line in the <head> of a page that names the address you want treated as the original, like ours above. Google’s canonical how-to lists the ways to tell it which page is the original, "in order of how strongly they can influence canonicalization":

• Redirects: "A strong signal that the target of the redirect should become canonical." That’s our no-www and old addresses in the table.
• The canonical tag: "A strong signal that the specified URL should become canonical."
• Your sitemap: "A weak signal that helps the URLs that are included in a sitemap become canonical."

None of them is an order. The canonicalization guide says "indicating a canonical preference is a hint, not a rule", and the how-to adds that "none of them are required; your site will likely do just fine without specifying a canonical preference."

On WordPress, Wix and similar systems you usually don’t write this line yourself. Google’s how-to says "your CMS might have a search engine settings page or some other mechanism to tell search engines about the canonical URL." We couldn’t read Shopify’s help pages from where we work, so we haven’t checked what Shopify does. Its theme or an app is the place to look.

The look-alike statuses, side by side

Search Console has four statuses that sound alike. Only one of them usually needs you to do anything:

For the second, the help page says: "This is not an error, but is working as intended, because Google does not serve duplicate pages." For the third, it explains that "Google thinks another URL makes a better canonical", and adds a line worth remembering: "A duplicate page must be similar to the canonical. (That's what duplicate means.)" For the fourth: "This is a non-canonical URL that redirects to another page. As such, this URL will not be indexed."

When it is worth doing something

• The address in the list is the one you want found. If your main product page shows up as the “alternate” of a filtered or tagged version, the canonical tag is pointing the wrong way. Fix the tag on the page.
• A page you care about isn’t in Google at all. Inspect it. If it says “Discovered - currently not indexed” instead, that’s a different problem, and we wrote up what that status means and what to check separately.
• Google chose a different original from you. Google’s troubleshooting guide says to "Use the URL Inspection tool to check which page Google considers canonical and think about whether the Google-selected canonical makes more sense than your preferred canonical URL for your users coming from Google Search."

Two warnings from the same guides. Don’t try to tidy it up with robots.txt or the removal tool: "Don't use the robots.txt file for canonicalization purposes", and the removal tool "hides all versions of a URL from Search." And if you change a page so that Google treats it as separate, "Google might hold pages in a duplicate cluster for up to two weeks". How long Google takes to look at a page again is its own question; our post on when Google looks at a page again has our measured examples.

What the guides on page one say, and what Google says

Four of the nine results we saw for this search had “fix” in the title, for a status Google says needs nothing doing. (Our search tool shows US results, so the British page one may differ.) One marketing agency’s guide, last updated in April 2026, also says "AMP pages, print versions, and multi-language sites also trigger this status". Google’s help page, in the definition quoted above, says: "Alternate language pages are not detected by Search Console."

To be fair to the guide, Google does count some regional copies as duplicates: its canonicalization guide gives the example of "separate USA and UK URLs with hreflang, but essentially the same content in the same language". Pages in different languages are a different matter.

What argues the other way

• Our case isn’t one of Google’s examples. The help page names AMP and mobile pages. We read “there is nothing you need to do” as covering our homepage too, because the copy names the original and Google agreed with it. That is our reading, not Google’s words.
• One small site isn’t a big shop. A shop with thousands of filter pages can have thousands of these. Each one is fine, but Google gives "To avoid spending crawling time on duplicate pages" as a reason to name the original, so a very large count can be worth tidying.
• The labels move. Search Console’s status for a page can change between checks without Google crawling it again. The crawl date is the steadier figure.
• We have an interest. We build websites for small businesses, and our own site is the example, so it suits us that it looks fine. The statuses and dates are as Google’s tool reported them.

Sources, and what we checked

• Google Search Console Help: Page indexing report (the definitions of all four statuses) and Duplicate URL.
• Google Search Central: What is URL canonicalization (last updated 20 August 2026), How to specify a canonical URL with rel="canonical" and other methods (last updated 10 July 2026) and Fix canonicalization issues (last updated 21 August 2026).
• Our own site: Google’s URL Inspection tool, run through the Search Console API on 18 October 2026 and again on 20 October 2026, for the ten addresses summarised in the table (the same results both times; we also asked for the homepage copy in British and US English), and both homepage addresses fetched and compared.
• Page one: the results for this search, seen through a US search tool, and the guide we quote, read in full.
• Every page above was read on 18 October 2026, and again on 20 October 2026, the morning we published. The wording we quote was the same both times.
• Every quotation above was tested automatically against the text of its source before publication.