iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
“Alternate page with proper canonical tag” is not automatically an error. It means Google has grouped the URL with duplicate or very similar pages and selected another URL as the representative. If that representative is the page you want indexed, the status may be expected. Investigate when the reported URL should stand on its own or Google chose the wrong representative.
What the status means in Search Console
Google uses a canonical URL as the representative of a group of duplicate or very similar URLs. The URL you declare as canonical is a signal, not a command: Google may select a different URL. The status describes Google’s selection; by itself, it does not show that your WordPress site is broken. See Google Search Console Help: Duplicate URL and Google Search Central’s canonical guidance.
- Expected: the reported URL is an intentional alternate, and Google selected the preferred page.
- Worth fixing: the reported URL should be indexed separately, or Google selected a page you do not want representing the content.
How to diagnose the affected URL
- Inspect the URL in Search Console. Record the user-declared canonical and Google-selected canonical. Decide whether the reported URL is meant to remain an alternate or should stand on its own. The status alone cannot make that decision for you.
- Check the page’s actual output. Fetch the affected page and inspect its HTML source or rendered output. The canonical link should be in the document’s
<head>, use an absolute URL, and identify an equivalent page that you want Google to prefer. The preferred page should also point to itself as canonical. For example:<link rel="canonical" href="https://example.com/preferred-page/" />. - Look for conflicting declarations. Check theme output, SEO-plugin settings, custom code, HTTP headers, and sitemap entries. Multiple canonical declarations or inconsistent targets can send mixed signals. Google recommends using one canonical-link delivery method; combining an HTTP header and an HTML link can introduce conflicting declarations.
- Check redirects and site URLs. Review your WordPress Address and Site Address settings and test what happens when you visit the affected URL. WordPress’s
redirect_canonical()function can redirect incoming URLs toward a proper URL based on the site URL, but its presence does not mean every Search Console status needs a custom redirect. See the WordPressredirect_canonical()reference. - Align links and sitemap entries. Point internal links to the preferred URL and include that URL consistently in your sitemap. Google treats sitemap inclusion as a weaker canonical signal than redirects and
rel="canonical". - Choose the right correction. Use a permanent redirect if the duplicate URL is being retired. Use a canonical link if both versions need to remain accessible and their content is duplicate or very similar. Do not redirect distinct content to an unrelated page.
- Request a fresh evaluation if appropriate. After correcting the signals, use Search Console URL Inspection to request indexing or evaluation where available. Google does not guarantee a fixed timeline for a URL’s status to change.
Choose a fix based on what should happen to each URL
| Situation | Suitable signal | What to do |
|---|---|---|
| Both equivalent URLs should remain accessible | rel="canonical" |
Point the alternate URL to the preferred page, and have the preferred page declare itself canonical. |
| The duplicate URL is being retired | Permanent redirect | Redirect it to the surviving equivalent URL so users and crawlers reach the page that remains. |
| You want to reinforce preferred URLs across the site | Sitemap | List the preferred URLs consistently. Sitemap inclusion is a weaker signal, so do not rely on it alone. |
Google describes redirects and rel="canonical" as strong signals and sitemap inclusion as weaker. Consistent signals reinforce one another, but none guarantees that Google will select your preferred URL. Google Search Central also says: “While we encourage you to use these methods, none of them are required; your site will likely do just fine without specifying a canonical preference.”
Recommended Free Tools
WordPress-specific checks before changing code
WordPress documents rel_canonical() as outputting a canonical link for singular queries using wp_get_canonical_url(). That does not establish what a particular site’s theme and plugins are outputting; inspect the live page and response headers before adding code or changing settings. See the WordPress rel_canonical() reference.
#1 Best Overall
Because core, themes, plugins, custom code, and server behavior can all affect canonical signals or redirects, first identify which component is responsible. Adding another plugin or a PHP snippet without checking existing output can create duplicate or contradictory signals.
Quick Recap
Common fixes that make canonicalization worse
- Do not use
robots.txtto canonicalize. Blocking crawling does not select a preferred URL, and Google may still index a disallowed URL without its content. - Do not use
noindexto choose a canonical within the same site. It blocks a page from Search rather than serving as a canonical-selection signal. - Do not make signals disagree. The canonical tag, redirect destination, internal links, and sitemap should support the same preferred URL.
- Do not assume the canonical tag forces Google’s choice. Google selects its representative based on its signals and may choose a different URL.
- Do not redirect unrelated pages. A redirect is appropriate when retiring a duplicate URL in favor of an equivalent surviving page, not as a way to merge distinct content.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
