A canonical URL is the web address a site owner marks as the preferred, master version of a page when duplicate or very similar content exists at more than one URL. It’s set with the rel="canonical" link tag, and it tells Google which page to index and rank so that duplicates don’t split ranking signals or compete against each other.
For a local service business, canonical URLs matter most on pages that get generated automatically: product filters, printer-friendly pages, session IDs in the URL, or the same content served on http and https, or with and without www. Without a canonical tag, Google has to guess which version matters, and it doesn’t always guess the way you’d want.
Key takeaway
The canonical tag is a hint, not a directive. Google usually honors it, but it can pick a different canonical if your signals (internal links, sitemap, redirects) point elsewhere.
How does a canonical URL work?
A canonical URL works through a line of HTML in the page’s <head>: <link rel="canonical" href="https://example.com/preferred-page/"/>. When Google crawls a page with this tag, it treats the linked URL as the version to index, consolidating ranking signals like backlinks and content relevance onto that one URL.
Every indexable page should have a canonical tag, even if it’s self-referencing — pointing to itself. This is standard practice and prevents accidental duplication issues later, such as when a page gets accessed through URL parameters like ?ref=email.
Why does canonicalization matter, and what doesn’t it do?
Canonicalization matters because duplicate or near-duplicate pages dilute page authority across multiple URLs instead of consolidating it into one strong page. A properly set canonical folds that authority into a single ranking candidate.
It doesn’t guarantee indexing, and it doesn’t fix duplicate content caused by copied text from another site. It also won’t rescue a thin or low-value page just because you point its canonical somewhere else. Canonical tags manage which URL represents a set of near-identical pages; they don’t substitute for unique content.
Common causes of duplicate URLs
Most duplication problems come from a short list of technical setups, not intentional copying.
| Cause | Example |
| URL parameters | /services/?utm_source=fb vs /services/ |
| www vs non-www | www.site.com vs site.com |
| HTTP vs HTTPS | Both versions live and crawlable |
| Print or AMP versions | Separate URL with identical content |
| Faceted navigation | Filter and sort combinations on ecommerce category pages |
Canonical URL vs redirect: what’s the difference?
A canonical tag lets both URLs stay live but tells Google which one to index, while a redirect sends users and crawlers to a different URL automatically, removing the old one from circulation entirely.
| Canonical tag | 301 redirect |
| Both URLs remain accessible | Old URL forwards to the new one |
| Use when both versions serve a purpose (tracking, filters) | Use when a page has permanently moved or merged |
| A hint Google can override | A directive Google follows |
Good vs bad canonical setups
A good setup uses one consistent, self-referencing canonical per page and matches it to the URL in your sitemap and internal links. A bad setup points canonicals to unrelated pages or creates a chain where page A canonicalizes to B, which canonicalizes to C.
- Self-referencing canonical on every indexable page.
- Canonical URL matches the version submitted in the XML sitemap.
- HTTPS, non-www version chosen consistently sitewide.
- Canonicalizing a page to one that no longer exists.
- Mixing relative and absolute URLs in the tag.
- Pointing every paginated page in a series to page 1.
How do you check your canonical tags?
Check canonical tags by viewing a page’s source code for the rel="canonical" line, then confirm Google agrees with it in Search Console under URL Inspection, which shows both the “declared canonical” and the “Google-selected canonical.”
Example: A Tampa moving company had product-style location pages that all pulled the same service description, differing only in city name in the URL. Google was choosing a different page as canonical than the one the business wanted ranked for its main city, based on internal linking patterns. Adding unique intro paragraphs to each city page and strengthening internal links to the primary location page resolved the mismatch.
Costly mistake Setting a canonical tag and then blocking that same URL in robots.txt. Google can’t verify a canonical it isn’t allowed to crawl, so the signal gets ignored.
How do you fix canonical issues?
Fix canonical issues by auditing your site for duplicate content patterns, standardizing on one URL format, and making sure canonical tags, sitemaps, and internal links all agree.
- Crawl the site with an SEO tool. Export all canonical tags and flag pages with none or with mismatched targets.
- Standardize the preferred domain format. Pick HTTPS and either www or non-www, then redirect all other variants.
- Add self-referencing canonicals sitewide. Confirm through page source that every indexable URL has one.
- Recheck in Search Console. Confirm Google’s selected canonical matches your declared one for key pages.
For a step-by-step walkthrough with tool settings, see how to
