Canonical URL QA checklist for Shopify, WordPress, and headless sites

Canonical tags are small, but canonical mistakes can spread across thousands of URLs. A Shopify filter, WordPress archive, headless product route, staging domain, or campaign parameter can tell search engines that the wrong page is the primary version.

This checklist is for redesign launches, Shopify theme updates, WordPress theme development, headless commerce migrations, and technical SEO maintenance. Use it when URLs are close to final but there is still time to fix templates, redirects, internal links, and CMS rules.

Do not start by checking one homepage canonical. Start by listing every way the same content can appear under more than one URL. Crawl staging, crawl production, export URLs from analytics, review Search Console, and ask the ecommerce or content team which links customers actually use.

The inventory should include normal page templates and edge cases. Canonical bugs usually hide in filters, pagination, preview URLs, product variants, localized paths, tracking URLs, and older links that survived a redesign.

• Shopify: product URLs under collections, variant URLs, collection filters, sorting, search results, markets, and app-generated landing pages.
• WordPress: category archives, tag archives, author pages, paginated archives, attachment pages, preview URLs, and custom post type archives.
• Headless sites: CMS preview routes, API slugs, trailing slash variants, case variants, localized routes, and client-side filter states.
• Redesigns: legacy URLs, redirect chains, UTM links, paid campaign links, old sitemap URLs, and URLs still used by partners or sales teams.

A rule table prevents one developer, one SEO lead, and one content editor from making three different decisions. For each URL pattern, define the canonical owner, whether the URL can be indexed, whether it belongs in the sitemap, and where internal links should point.

Keep the table practical. Each row should include page type, example URL, canonical target, indexability rule, sitemap rule, hreflang rule, redirect rule, owner, and QA status. If a rule cannot be written clearly, the site structure probably needs a decision before implementation.

• Mark self-canonical pages separately from pages that should canonicalize to another URL.
• Decide whether filtered collection pages, search pages, and archive pages are useful landing pages or crawl noise.
• Document exceptions for strategic SEO landing pages so they are not accidentally canonicalized away.
• Assign an owner for future changes because apps, plugins, and CMS editors can create new URL patterns after launch.

CMS settings are not enough. Test the rendered HTML that search engines receive. A theme file, SEO plugin, Shopify app, headless layout component, or middleware rule can change the canonical output after the CMS field looks correct.

Every indexable page should have exactly one canonical tag, and that tag should point to an absolute HTTPS URL that resolves cleanly. It should not point to staging, a redirected URL, a mixed-case variant, a tracking URL, or a page blocked by noindex or robots rules.

• Check homepage, product pages, collection pages, service pages, blog posts, custom post types, landing pages, and localized templates.
• Confirm the canonical URL uses the final host, protocol, path format, trailing slash rule, and lowercase convention.
• Test rendered HTML with JavaScript enabled for headless sites and app-heavy Shopify storefronts.
• Make sure there are no duplicate canonical tags from themes, plugins, injected scripts, or legacy SEO code.

Canonicals should support the URL rules, not compensate for broken redirects. If a URL redirects, the canonical target should match the final destination after the redirect chain. If a URL keeps parameters, the canonical rule should match the indexing decision for that parameter pattern.

Pagination needs a deliberate decision. Some paginated pages should self-canonicalize, some archives should consolidate, and some search or filter states should stay out of search results. The wrong default can hide useful pages or waste crawl budget on duplicates.

• Test HTTP to HTTPS, www to non-www, trailing slash rules, uppercase paths, old URLs, and redirected product or post slugs.
• Check UTM, email, paid media, affiliate, internal search, sorting, filtering, and session parameters.
• Verify paginated collections, blog archives, resource hubs, and WordPress archives do not canonicalize every page to page one unless that is intentional.
• Confirm canonical targets return 200 status codes and are not blocked, noindexed, password protected, or removed from the sitemap by mistake.

Multilingual websites add another failure mode. Each localized page should usually canonicalize to itself while hreflang connects the language or regional alternatives. If every language points canonically to English, the non-English pages may never earn their own search visibility.

Check this on real templates, not only the homepage. Product pages, collection pages, blog posts, resource pages, and legal pages often use different routing or CMS fields. The canonical and hreflang clusters should agree with the final localized URL structure.

• Confirm each localized page has a self-canonical URL in the same language or region.
• Make hreflang alternates point to indexable, canonical URLs that return 200 status codes.
• Check x-default, regional variants, translated slugs, fallback pages, and unavailable product states.
• Avoid mixing canonical rules from one locale with hreflang links from another locale or market.

A sitemap full of non-canonical URLs sends mixed signals. The same is true when navigation, breadcrumbs, cards, related posts, XML sitemaps, and schema markup all point to different versions of the same page.

Before launch, compare the canonical rule table against internal links and generated sitemaps. The goal is not just valid tags. The goal is a site where every major signal points to the same preferred URL.

• Export XML sitemap URLs and confirm they are all canonical, indexable, final 200 URLs.
• Check navigation, breadcrumbs, cards, faceted links, related products, related posts, and footer links.
• Make structured data URLs match the canonical page where relevant, especially Product, BreadcrumbList, Article, and Organization entities.
• Update CMS references, menu builders, app settings, and hard-coded theme links that still point to duplicate URLs.