Duplicate content confuses search engines and dilutes ranking power. Two tools fix it: canonical tags and redirects. They look similar on the surface but behave very differently, and choosing the wrong one costs you visibility.
This post covers the operational difference, when each tool wins, and the mistakes that waste months of crawl budget.
TL;DR
Use a 301 redirect when you want to permanently merge two URLs into one, retire old versions, or consolidate parameter variations. Use a canonical tag when duplicate versions must stay live (different domains, session IDs, tracking parameters) but should funnel ranking power to one preferred URL. Redirects are stronger; canonicals are flexible. Pick wrong and you either waste crawl budget or lose ranking signals.
How Redirects Work
A 301 redirect tells the browser and search engines: "This URL no longer exists. Go to this new one instead." The browser automatically fetches the new page. Google treats it as a permanent move and transfers nearly all ranking power to the destination.
When you set up a 301 redirect, Google crawls the old URL, sees the redirect, and follows it to the new one. Over time (typically 4–6 weeks), Google updates its index to point to the new URL. The old URL eventually drops out of the index entirely.
A 302 redirect says "temporarily moved." Google may keep indexing the old URL, treating it as the primary version. Use 302 only when you're genuinely testing a change for a few weeks. Most permanent duplicate content needs 301.
How Canonical Tags Work
A canonical tag is an HTML signal that says: "This page is a duplicate of another. Use that one for ranking." Both URLs stay live and indexable. Google reads the canonical tag and treats the destination as the primary version for ranking purposes.
The key difference: the user still lands on the original URL. The browser doesn't redirect. The page stays online. Google just deprioritizes it in favor of the canonical target.
Canonicals work across different domains. You can put a canonical tag on example.com/page pointing to cdn.example.com/page, and Google will credit the CDN version. Redirects cannot span domains without actually moving traffic.
Redirects: When They Win
Old site migrations. You're moving from oldsite.com to newsite.com. Every page has a new home. Set up 301 redirects from old URLs to new ones. Google merges the ranking history, and users land on the new site automatically.
Retiring old content. You had five versions of a product page. Now you have one canonical version. Redirect the old URLs to the new one. This consolidates all backlinks and ranking power into a single page.
Removing tracking or session parameters. Your site creates URLs like example.com/page?utm_source=email&utm_medium=newsletter and example.com/page?session_id=xyz123. These are duplicates of the base URL. Set up redirects to strip the parameters and send users to the clean URL. This prevents Google from indexing dozens of parameter variations.
Consolidating www and non-www versions. If both www.example.com and example.com are live, pick one and redirect the other to it. This is cleaner than a canonical tag because you're actually merging two domain roots.
Collapsing URL structure changes. You reorganized your site from /blog/post-title to /posts/post-title. Redirect old URLs to new ones. Ranking power transfers; users go to the right place.
Canonical Tags: When They Win
Cross-domain syndication. You publish the same article on your site and Medium. Your article is the original; Medium's is syndicated. Put a canonical tag on the Medium version pointing back to yours. Google credits your site with the original content, and the Medium version stays live for its own audience.
CDN and origin servers. Your content lives on a CDN (cdn.example.com) but also on your origin (example.com). Both URLs are live. Add a canonical tag on the CDN version pointing to the origin. Google ranks the origin; users can access either.
Session IDs and tracking parameters you cannot remove. Your platform generates session-specific URLs: example.com/page?sid=abc123 and example.com/page?sid=xyz789. You cannot redirect them all to a clean base URL without breaking functionality. Use a canonical tag on the parameterized URL pointing to the clean base. Google treats all variations as one.
Multiple product variations on separate URLs. You sell a shirt in three colors. Each color has its own URL (/shirt-red, /shirt-blue, /shirt-green), but the content is nearly identical. If you want all three URLs to stay live for user choice, add a canonical tag on each pointing to a primary version (e.g., /shirt). Users can still access the color variants; Google ranks the primary.
Printer-friendly and mobile versions. Legacy sites sometimes had separate printer-friendly URLs or mobile subdomains. If both versions must stay live, use a canonical tag on the alternate version pointing to the primary one. This is rare now (responsive design is standard), but it still applies to old platforms.
Common Mistakes
Canonical tag when you should redirect. You're retiring a URL entirely. No one needs to access it. But you add a canonical tag instead of a redirect. The old URL stays in the index. Crawlers waste budget on a page that serves no purpose. Users might land on it via old bookmarks or links and see stale content.
Redirect when you should use canonical. You have a CDN and origin server, both live and both necessary. You set up a 301 redirect from CDN to origin. Now all CDN traffic goes to the origin, defeating the purpose of the CDN. The canonical tag was the right choice.
Canonical pointing to itself. A page should never have a canonical tag pointing to its own URL. This wastes crawl budget and confuses Google. Every page has an implicit self-canonical; you only need an explicit tag when pointing elsewhere.
Multiple canonicals on one page. A page can have only one canonical tag. If you add two, Google ignores both. Use one canonical per page, or none.
Canonical tag on redirect destination. If page A redirects to page B, do not add a canonical tag to page B. The redirect already tells Google where to go. The canonical is redundant and can cause confusion.
Diagnostic Order
Before choosing, ask these questions in order:
- Should this URL stay live? If no, use a redirect. If yes, move to step 2.
- Is this a permanent structural change? If yes (site migration, URL reorganization), use a redirect. If no, move to step 3.
- Do both URLs need to serve traffic? If yes (CDN, syndication, parameter variations), use a canonical. If no, use a redirect.
- Are the URLs on different domains? If yes, canonical is your only option (redirects cannot merge domains). If no, either works, but prefer redirect for cleaner consolidation.
Crawl Budget & Indexing Impact
Redirects cost crawl budget. Google follows the redirect, crawls the destination, and updates the index. This takes time. On large sites with thousands of redirects, crawl budget can become a bottleneck.
Canonical tags cost less crawl budget. Google reads the tag and deprioritizes the page without following a redirect chain. If you have hundreds of duplicate URLs, canonicals are more efficient.
However, redirects are more reliable. Google always follows a 301. Canonicals are hints; Google respects them most of the time, but may ignore them if the content is very different or the target is on a low-authority domain.
Mixing Canonicals and Redirects
You can use both on the same site, but not on the same URL. For example, redirect old site URLs to new ones, then use canonicals on the new site to handle parameter variations. This is normal and correct.
Do not redirect to a page that has a canonical pointing elsewhere. This creates confusion. If page A redirects to page B, and page B has a canonical to page C, Google may not follow the chain correctly. Consolidate: either redirect A directly to C, or remove the redirect and use a canonical on A.
Reality Check: Implementation Timing
Redirects take 4–6 weeks for Google to fully process. During this time, the old URL may still appear in search results alongside the new one. This is normal. Be patient before assuming the redirect failed.
Canonical tags are processed faster (days to weeks), but Google may take weeks to fully reindex the page. If you add a canonical to a high-traffic page, monitor Search Console to confirm Google recognized it.
Test redirects with a small batch first. Redirect 5–10 URLs, wait a week, check Search Console to confirm they're being followed. Then roll out the rest.
What to Do Next
Audit your site for duplicate content. Use Google Search Console to find parameter variations and duplicate pages. Then apply the diagnostic order above to decide whether each duplicate needs a redirect or canonical. Start with high-traffic pages and work down. If you need help identifying which approach fits your structure, technical SEO assessment can clarify the strategy before implementation.
FAQs
Will a canonical tag hurt my rankings?
No. A canonical tag deprioritizes a page but does not penalize it. The page stays live and accessible. Rankings transfer to the canonical target.
Can I use a canonical tag on a different domain?
Yes. Canonicals work across domains. This is one of their main advantages over redirects.
What if I redirect to the wrong page?
Users will land on the wrong page. Update the redirect to point to the correct destination. Google will reprocess it within a few days.
Do I need to remove old redirects after a few months?
No. Permanent 301 redirects should stay in place indefinitely. They cost minimal server resources and protect against broken links if old URLs are shared again.
People Also Ask
What's the difference between a 301 and 302 redirect?
A 301 is permanent and transfers ranking power. A 302 is temporary and may keep the old URL in the index. Use 301 for duplicate content.
Can Google index a page with a canonical tag?
Yes. A canonical tag does not prevent indexing. It just tells Google to prioritize a different version for ranking.
How many URLs can point to one canonical?
Technically unlimited, but best practice is to keep canonical groups small (under 50 variations per canonical target). Large groups may signal low-quality content to Google.
Will canonicals fix my duplicate content penalty?
Canonicals prevent future duplicate issues but do not reverse a manual penalty. If Google has penalized your site for duplicate content, you need to remove the duplicates or use redirects, then request a reconsideration in Search Console.
Should I use a canonical tag on my homepage?
Only if your homepage has duplicate versions (e.g., both example.com and example.com/index.html are live). Otherwise, no.
Can I canonical tag to a noindex page?
Google discourages this. If the canonical target is noindex, the canonical may be ignored. Keep canonical targets indexable.
What happens if I redirect a page to itself?
This creates an infinite redirect loop. Avoid it. The page will not load, and Google will flag it as an error in Search Console.
Do I need to update internal links when I set up a redirect?
No. Redirects work automatically. However, updating internal links to point to the new URL directly is cleaner and saves crawl budget.
How do I set up a redirect in my CMS?
Most CMS platforms (WordPress, HubSpot, Drupal) have redirect plugins or built-in tools. Check your CMS documentation for the specific steps. If you're using a web server directly, consult your hosting provider's docs on .htaccess (Apache) or web.config (IIS).
If this post is wrong, outdated, or you would take a different path
I write from work I have done on real sites. Search products change, and a step that was right when I published can go stale. I can also be wrong about the method.
If you disagree with the approach, the facts, or the outcome, I want the detail. Tell me what is off, what you would do instead, and where you saw it. I use that to correct the post so the next reader is not stuck.
This is not a comment thread. Use Contact me so the note is tied to this post and I can reply.
You are sending feedback for
When to Use Canonicalization vs. Redirects for Duplicate Content
Technical SEO
https://hammadshk.com/blog/when-to-use-canonicalization-vs-redirects-for-duplicate-content
