Alternate page with proper canonical tag: Google agreed to keep the other URL

Read the status as agreement, not a penalty

‘Alternate page with proper canonical tag’ means Google fetched a URL, saw that it named a different canonical, and agreed. The alternate is a copy. The canonical is the URL that can rank and be cited. This is the healthy twin of ‘Duplicate, Google chose different canonical than user’, where your tag and Google’s choice disagree. Here they match, so the status is not a bug by itself.

Teams still search for the phrase because the page indexing report lists thousands of URLs and looks like an indexing failure. A parameter, a trailing slash, an http copy, or a print view should sit in this bucket. A service page, a guide, or a Traditional Chinese URL should not, if that address is the one a person or an answer engine is supposed to find. The SEO issue is a page you needed, filed as an alternate. The GEO issue is the same URL: an answer engine cites the canonical, not the passage left on the copy that search agreed to fold.

• Treat this status as consolidation that worked.
• Keep it separate from a canonical Google refused.
• Check whether the folded URL was supposed to be a source.

Sort copies you meant from pages you still need

Open the sample URLs and write the declared canonical beside each one. If the alternate is a tracking parameter, a session id, or the non-preferred host, leave the status alone. Those URLs are doing their job by pointing at the page you want kept. Removing the canonical to force them into the index recreates the duplicate the tag was there to close.

If the alternate has its own query, it was filed in the wrong bucket. A Hong Kong site often does this to a language version: the zh-HK page canonicalises to English, or a district page canonicalises to the citywide service page, and both disappear from the report as healthy alternates. They are not healthy. Each of those URLs answers a different search, and only the canonical remains available to quote. Compare the body. If the first answer, the place, or the language is different, the pages are not duplicates.

Put the answer on the URL that will be kept

When the consolidation is correct, make the canonical the page you would send to a colleague. Internal links and the XML sitemap should name that URL, and the alternate should keep pointing at it. Put the bounded answer on the canonical, with the organisation and the place next to the claim, so the passage an answer engine lifts is the one search will keep. Requesting indexing for the alternate asks Google to undo an agreement it has already made.

When the pages should stay apart, give each a self-referencing canonical, a distinct title, and a first paragraph that could not be swapped. Link both from pages Google already crawls, and list both in the sitemap only if both should be indexed. Then re-check URL inspection. The alternate status should clear on the URL you reclaimed, and it should remain on the copies you still intend to fold. That split is the fix.

• Leave true duplicates consolidated.
• Reclaim a URL only when it answers a different query.
• Do not request indexing for an alternate you still want folded.

Is Alternate page with proper canonical tag an error?

Usually no. It means Google accepted the canonical you declared and indexed that URL instead of the alternate. It is a problem only when the folded URL is a page you still want found or cited.

How is this different from Google chose different canonical than user?

Here your canonical tag and Google’s selected canonical match. In ‘Duplicate, Google chose different canonical than user’, Google indexed a different URL from the one your tag named. One is agreement. The other is a disagreement.