Alternate Page With Proper Canonical Tag

"Alternate page with proper canonical tag" is the status most people are relieved to see once they understand it. It means a canonical tag you wrote did its job and Google agreed. This post explains what it reports, which pages belong in it, the two cases where it is hiding a mistake, and how to check every canonical on the site in one pass, with a live example from our own Search Console checked on 6 October 2026.

What "Alternate page with proper canonical tag" means

Google's definition, from its Page indexing report documentation:

"This page is marked as an alternate of another page. This page correctly points to the canonical page, which is indexed, so there is nothing you need to do."

Read the three parts separately. The page carries a canonical tag naming a different URL. Google looked at both and agreed the other URL is the better one. And that other URL is in the index. All three have to be true for this status; if Google disagreed with the tag, you would see Duplicate, Google chose different canonical than user instead.

A live example from our own site

https://www.crawlcove.com/pricing inspects as "Alternate page with proper canonical tag" in our Search Console, last crawled 16 July 2026. Google's chosen canonical and our declared canonical are the same: https://crawlcove.com/pricing. When Google last fetched the www address it served the pricing page with a canonical tag naming the non-www URL, Google accepted that, and the non-www page is the one in the index.

That address now returns a 301 redirect to the apex URL instead of serving the page, which means the next time Google fetches it the status will change to page with redirect. Nothing is wrong in either state. It is a reminder that the report describes the last crawl, not today's site.

Which pages belong here

Any URL that deliberately defers to another one should sit in this bucket. The common residents:

• Host and scheme variants. www and non-www, http and https, when both serve content with a canonical pointing at the preferred one. A redirect is the cleaner fix, but a canonical works, as long as it points at the https:// version and not back at insecure HTTP.
• Tracking parameters. ?utm_source=, ?ref=, ?fbclid= and similar. The page is the same; the canonical strips the parameter.
• Sort and filter views. ?sort=price on a category page, when the sorted view is not meant to rank on its own.
• Paginated series where every page canonicalises to the first. Google's own guidance is that each page in a series should self-canonicalise, so this one is worth a second look.
• Print, AMP and mobile variants of a desktop page.
• Syndicated or mirrored copies that name the original.
• Trailing-slash and letter-case variants that a server rule did not fold into one address.

On an e-commerce site this status can carry thousands of URLs and still describe nothing wrong.

The two cases worth checking

1. The canonical points at the wrong page

A canonical tag is easy to generate incorrectly. Templates that hard-code the homepage, pagination that points every page at page one, localised pages that all canonicalise to the English version, and a staging domain left in the tag after launch all produce "proper" canonicals that Google honours. The status says the tag is correctly formed and Google agreed with it. It does not say the URL in the tag is the one you meant.

Pull the list of alternates, group by the canonical target, and look at the groups. A target with hundreds of unrelated alternates is almost always a template bug. We wrote up the patterns in canonical tag mistakes.

2. A page that should rank on its own has been folded in

Sometimes the tag is deliberate and still wrong. A product variant that gets its own search demand, a city page canonicalised to a national one, or a long-form article that canonicalises to a summary. Google is doing what you asked; the ask was the mistake.

The fix is to make the page self-referencing, make sure it has enough distinct content to stand on its own, link to it internally, and wait for a recrawl. A page that loses its canonical and has nothing distinctive to offer tends to land in crawled currently not indexed rather than the index, so check the content before changing the tag.

How to check a single URL

1. Inspect the alternate in Search Console and read both canonical rows: user-declared and Google-selected. For this status they match.
2. Open the canonical target and confirm it is the page you intended. Then inspect it separately; the status on the alternate says the target is indexed, but it is worth seeing the target's own result.
3. Check the last crawl date. If you changed the canonical after that date, the report is describing the old tag.
4. Check the alternate is not in your sitemap. A sitemap should list canonical URLs only. Listing alternates is a mixed signal and the sitemap non-indexable URL issue page explains what to do about it.

For a handful of URLs that is quick. For a site with a few thousand alternates it is not, which is where a crawl comes in.

Auditing canonicals across the whole site

Search Console lists the alternates Google has fetched. It does not show you every canonical on the site, where each one points, or which targets are themselves broken. A crawl does.

Crawl Cove reads the canonical tag on every page it crawls and runs four checks against it. The canonical check flags pages with a missing or relative canonical, and pages whose canonical names a same-site URL the crawl never saw. canonical-to-redirect catches a canonical that points at a redirecting URL rather than the final one, which is a common way for a "proper" canonical to quietly stop being proper. canonical-to-noindex catches a canonical whose target is noindexed or non-200, which takes both pages out of the index. insecure-canonical flags an HTTPS page pointing its canonical at its own http version. Alongside those, the near-duplicate-content check surfaces pages that look like duplicates but carry no canonical relationship at all.

For any page where you want Google's current view, the Live Index Status panel calls the URL Inspection API and shows Google's canonical next to the declared one, flagging the pair when they differ. Run a full SEO audit to see every canonical target on the site grouped in one place, which is the quickest way to spot a template pointing a whole section at the wrong page.

Wrap-up

"Alternate page with proper canonical tag" is a canonical working as intended. Most of the URLs under it are parameter, host and format variants that should never rank on their own, and the right move is to leave them. Spend your time on the two exceptions: a target that is wrong, which usually means a template, and a page that deserves its own place in the index but has been folded into another. A site-wide view of where every canonical points finds both faster than inspecting URLs one by one.