A Moz canonicalization warning is a prompt to inspect a URL, not proof that Google has indexed the wrong page. Compare what Moz found in the crawl with the canonical tag and redirects WordPress actually serves, then check whether those signals agree with your sitemap and internal links. Google makes its own canonical choice for duplicate or very similar pages.
What Moz’s canonical report does—and does not—tell you
Moz Site Crawl records page-level crawl and canonical information. Its crawled-page view includes a Canonical URL field for the canonical URL found in the page source. That is evidence of what Moz observed during its crawl, not a report of Google’s chosen canonical. See Moz’s crawled-page guide.
A canonical URL is the preferred representative for duplicate or very similar content. Your canonical tag expresses a preference; it does not compel Google to use that URL. Google may choose another representative based on the signals it collects. Google’s canonicalization guide explains that a canonical preference is a hint, not a rule.
Start with the exact affected URL
- In Moz Site Crawl, record the full affected URL, the issue label, any canonical URL shown, and the crawl date.
- Group affected URLs by pattern: posts, category or tag archives, pagination, query parameters, HTTP versus HTTPS, www versus non-www, trailing slash, alternate host, or custom rewrite routes.
- Choose representative URLs from each pattern and inspect them before making a sitewide change. A repeated pattern can point to a shared template, plugin, site setting, rewrite, or proxy rule, but the crawl data alone does not identify the cause.
Inspect the response WordPress actually serves
Check each representative URL in the browser and inspect its full redirect chain, starting from the original requested address. Then view the served HTML source and find every <link rel="canonical"> element. Confirm there is one intended canonical, that it is an absolute URL, and that its destination resolves to the intended indexable page rather than redirecting elsewhere.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Compare protocol, hostname, path, letter case, and trailing-slash format with the preferred URL.
- Check whether the original URL returns the intended status and whether robots directives or a noindex setting affect the page.
- Compare the source HTML with the rendered DOM if JavaScript may alter the canonical.
- Check internal links and the XML sitemap for conflicting URL versions.
Do not assume a missing canonical tag from the issue label alone. WordPress core documents rel_canonical() as outputting a canonical for singular queries; archive, custom rewrite, plugin, and theme behavior can differ. See the rel_canonical() reference and the wp_get_canonical_url() reference.
Separate WordPress canonical tags from redirects
WordPress has two distinct mechanisms that are easy to confuse. rel_canonical() outputs an HTML link element. redirect_canonical() redirects incoming URLs toward a proper URL based on the site URL; WordPress gives www and non-www variants as an example of alternate URLs that may lead to the same content. A redirect changes the requested destination, while a canonical tag leaves the page reachable and declares a preferred representative.
Inspect WordPress Address and Site Address settings, permalink settings, HTTPS and proxy configuration, and the active SEO plugin and theme. Plugins, themes, filters, caching, custom code, and server or CDN rules may affect production output, so verify the live response before editing PHP or server configuration. WordPress documents the redirect_canonical filter; returning false cancels that redirect, but it is for narrow, justified cases—not a default fix.
Compare the signals pointing to the preferred URL
For a page you intend to represent a duplicate set, compare the site’s signals and whether the pages genuinely belong together:
| Signal or check | What to verify |
|---|---|
| Redirect | If an old URL should no longer be independently accessible, check that it redirects to the intended destination. Google treats redirects as a strong canonical signal. |
| HTML canonical | Check that the declared target is the preferred equivalent page, is reachable, and does not conflict with other signals. Google treats rel="canonical" as a strong signal. |
| XML sitemap | List the preferred URL consistently rather than competing variants. Sitemap inclusion is a weaker canonical signal. |
| Internal links | Link consistently to the preferred version instead of splitting links among URL variants. |
| Content and purpose | Use canonicalization for duplicate or very similar pages, not pages that serve distinct purposes simply because they share some content. |
Google can combine these signals. It advises against using noindex to select a canonical among pages on the same site: noindex changes eligibility rather than declaring a preferred representative. Read Google’s duplicate-URL consolidation guidance and its canonicalization guidance.
Choose a fix based on what the URL is for
The URL is an accidental duplicate and should go away
Use a permanent redirect when the old URL should no longer be independently accessible. Update internal links and sitemap entries to the destination. Check that the redirect does not loop and that the destination is the intended equivalent page.
Rank #4
The URL must remain accessible but duplicates another page
Keep it reachable and set its canonical link to the preferred equivalent page. Make sure the target is valid and that links, sitemap entries, and redirects do not point toward competing versions.
The URL serves a distinct purpose or user need
Do not canonicalize it away solely because Moz reports similarity. First consider whether it is a useful alternate or has materially distinct content or function. Protocol, device, region, filtering, and accidental URL variants are among the duplicate sources Google recognizes; that does not mean every alternate, filtered, paginated, or localized URL should be consolidated.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The report is a known, intentional duplicate
If you have confirmed that a flagged URL is intentional and its site signals are correct, Moz’s Ignore function may be suitable for suppressing a known issue in reporting. Ignoring a finding affects Moz’s report; it does not change the page, redirect, or Google’s canonical selection. Moz’s available help wording for this behavior has not been verified on a current Moz-hosted page, so check the current Moz Help Hub for the feature and its interface before relying on specific instructions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Check Google Search Console when the concern is indexing
In Search Console, inspect the affected URL when you need to understand Google’s canonical choice. The status “Duplicate, Google chose different canonical than user” means Google selected a different representative for a duplicate cluster. Compare the user-declared canonical with Google’s selected canonical before changing anything. If Google’s choice is not the one you intend, review page equivalence and the consistency of redirects, canonical tags, internal links, and sitemap entries. See Search Console’s URL Inspection documentation.
Quick Recap
Re-crawl and verify the outcome
- Request the original URL and its intended canonical destination. Check the HTTP status, redirect chain, and canonical element in the served source.
- Confirm that internal links and sitemap entries use the intended URL and that the destination itself does not redirect to a different version.
- Run Moz Site Crawl again to see whether its observation has changed.
- Use Search Console’s URL Inspection for indexing and Google canonical questions; a refreshed Moz crawl does not prove Google has reprocessed the URL.
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.
