Canonical, noindex, and 301 redirect are frequently confused because all three serve to manage "non-primary" pages. But they have very different behaviors: canonical consolidates signals, noindex excludes from the index, and 301 transfers all value to another URL. Using the wrong one can disperse PageRank, waste crawl budget, or remove pages you need.
What each one does exactly
| Tool | What it does | Page remains accessible | Transfers PageRank |
|---|---|---|---|
| Canonical | Indicates the preferred URL. Google consolidates signals on the canonical. | ✅ Yes | ✅ Partially (it is a signal, not a directive) |
| Noindex | Excludes the page from Google's index. Google may still crawl the URL. | ✅ Yes | ❌ No (the page does not pass signals) |
| 301 redirect | Permanently redirects traffic and signals to another URL. | ⚠️ Only via redirect | ✅ Yes (more deterministically than canonical) |
When to use canonical
Canonical is the right tool when you have multiple URLs with the same content and all must remain accessible, but you want to tell Google which is the main version.
- •Pages with UTM or tracking parameters that do not change content (/page?utm_source=email → canonical to /page).
- •Syndicated content on another domain that should point to the original.
- •URL variants with and without trailing slash when both must be accessible.
- •Print version pages that duplicate main content.
- •Pages with ecommerce sorting or filter parameters that generate highly similar content variants.
Do not use canonical to exclude pages from the index — that is what noindex is for. A canonical does not guarantee Google will not index the "non-canonical" page; it simply prefers the canonical. If you need the page NOT to appear in results, use noindex.
When to use noindex
Noindex is the right tool when the page must exist and be accessible to users, but it adds no SEO value and you do not want Google to consume crawl budget indexing it.
- •Internal site search results pages.
- •Cart, checkout, and user account pages.
- •Order confirmation or form submission pages.
- •Accidentally exposed admin pages.
- •WordPress tag pages that generate content with very few posts.
- •Deep pagination pages (/category/page/15/) with no exclusive content.
Noindex does not block crawling — Google can still visit the page, it just stops indexing it. If you also want to prevent crawling (for pages with sensitive information), combine noindex with robots.txt Disallow. But note: if you block in robots.txt, Google cannot read the noindex tag.
When to use a 301 redirect
The 301 redirect is the right tool when a URL has permanently changed and it no longer makes sense for it to remain accessible at its original location.
- •Definitive URL changes: changed slug, restructured section, domain change.
- •Consolidation of duplicate content that does not need to maintain the original URL.
- •Migration from HTTP to HTTPS or from www to non-www.
- •Deleted pages with valuable external backlinks — redirect to the most relevant available content.
- •Merging multiple similar pages into a single more comprehensive page.
Quick decision table
| Situation | Correct tool |
|---|---|
| URL with UTM parameters duplicating content | Canonical on the variant → clean URL |
| Cart page I do not want in Google | Noindex |
| Old URL that has permanently changed | 301 redirect |
| Syndicated content on external publication | Cross-domain canonical on the external site |
| Internal site search page | Noindex (or Disallow in robots.txt if sensitive) |
| HTTP version of the site (already have HTTPS) | 301 redirect from HTTP → HTTPS |
| Pagination page /page/2/ | Noindex or Canonical → page 1 (depends on strategy) |
| Duplicate article on the same domain | 301 redirect to the original article |
The most dangerous error: combining canonical and noindex on the same page
Using canonical and noindex together on the same page sends a contradictory signal. The canonical tells Google "this URL is important, consolidate signals here." The noindex tells it "do not index this URL." Google may interpret this in different ways and the result is unpredictable. Never combine canonical with noindex on the same page.
Verify your site's canonical configuration
iRankly's Canonical Checker detects whether your pages have a canonical, whether they point to the correct URL, whether there are cross-domain canonicals, and whether the canonical is in HTML or in an HTTP header. Analyze the most important URLs on your site to confirm the configuration is consistent.
Try the tool for free
Canonical CheckerAnalyze your URLs with {tool} by iRankly. No sign-up, no credit card.