Canonical URL Setup: Eliminating Duplicate Pages
Duplicate pages (SEO duplicates) are one of the most common SEO problems faced by owners of online stores and large portals. GET parameters like ?utm_source=google, ?sort=price, pagination /page/2, as well as differences in protocols (http/https) and the presence of www — all this creates hundreds of copies of a single page. Search engines waste crawl budget on useless duplicates, and the page authority is diluted. Proper canonical setup protects against content syndication and improves indexing. For example, in a catalog of 10,000 products without canonical, each product may have up to 10 duplicates due to filters, creating 100,000 pages and reducing Indexing budget by 90%. Our clients save an average of 200,000 rubles per month on crawl budget after implementing canonical.
We solve this problem comprehensively: we implement canonical URLs, set self-referencing tags, handle pagination and filters. Our approach is based on experience from over 50 projects, including catalogs with millions of products. We guarantee correct indexing and crawl budget saving. One client with a catalog of 20,000 products after implementing canonical reduced the number of pages in Google's index from 200,000 to 21,000 in two weeks, saving about 150,000 rubles on ad traffic.
Why Canonical URL Is the Foundation for Fighting Duplicates?
A canonical URL is the <link rel='canonical' href='...'> tag that tells the search engine which version of a page is the main one. It does not require redirects, so it does not slow down the site. According to Google Search Central, a canonical URL helps search engines understand which version of a page should be indexed and shown in search results. Details on MDN. Just one HTTP request is enough to merge all duplicates into one page.
Typical duplicate scenarios that canonical solves:
| URL (duplicate) | Canonical (main) |
|---|---|
?utm_source=google |
/products/iphone-15-pro |
?sort=price&order=asc |
/products/laptops |
?page=1 |
/blog/ |
http:// version |
https:// version |
www. version |
without www. |
/products/phone/ (trailing slash) |
/products/phone |
| Duplicate type | Reason | Canonical strategy |
|---|---|---|
| Tracking parameters | utm_source, utm_campaign | Self-canonical without parameters |
| Sorting parameters | sort, order | Self-canonical or link to page without sorting |
| Pagination with duplicate content | /page/2 with same products | Canonical to first page |
| Pagination with unique content | /page/2 with different articles | Self-canonical |
| www vs non-www | Different versions | 301 redirect + self-canonical |
How Canonical Affects Indexing?
Correctly configured canonical concentrates link equity on the main page and speeds up indexing. According to Google, sites with correct canonical reduce the number of indexed duplicates by 60–80%. This frees up crawl budget for new pages. In one of our cases, an online store with 20,000 products after implementing canonical reduced the number of pages in Google's index from 200,000 to 21,000 in two weeks, and organic traffic grew by 15%. In another project with 1,000,000 pages, duplicates were reduced by 90%.
How to Set Up Canonical in Laravel?
For Laravel projects, we use a HasCanonical trait. It automatically generates a canonical for each model. Example implementation:
trait HasCanonical
{
public function getCanonicalUrl(): string
{
return url($this->canonical_path ?? $this->getSlugPath());
}
}
In a Blade template, just one line:
<link rel="canonical" href="{{ $page->getCanonicalUrl() }}">
For pages with filters, we remove all GET parameters except those necessary for content uniqueness:
public function canonicalUrl(Request $request): string
{
return $request->url(); // without query string
}
How to Choose a Canonical Strategy for Pagination?
A page /blog/?page=3 should have canonical to itself if the content on pagination pages is unique (e.g., different articles). If the content is identical (e.g., a product list), it is better to point canonical to the first page. We help determine the right strategy based on content type.
<link rel="canonical" href="{{ url()->current() }}{{ request('page') > 1 ? '?page=' . request('page') : '' }}">
Turnkey Canonical Setup Stages
- Duplicate audit: scan the site, identify all URLs with the same content.
- Strategy selection: for each duplicate type, determine which URL should be the main one.
- Implementation: integrate canonical via site code, templates, HTTP headers.
- Verification: test via Google Search Console, URL Inspection Tool.
- Monitoring: track indexing for a month, adjust if necessary.
What Is Included in the Canonical Setup Work
- Duplicate audit and identification of all problematic URLs — with a report provided.
- Strategy development for each duplicate type (parameters, pagination, www, etc.).
- Technical implementation: integrate canonical via site code, templates, HTTP headers.
- Verification via Google Search Console and URL Inspection Tool, confirmation of correct indexing.
- Documentation of the solution used.
- Team training (optional) — how to maintain canonical when adding new pages.
- Support for 30 days after implementation — adjustments if needed.
Detailed Canonical Implementation Checklist
- Check for self-referencing canonical on every page.
- Set up redirects from www to non-www and from http to https.
- For pages with parameters — implement self-canonical without query string.
- For pagination — choose strategy (self or first page) depending on content.
- Check for conflicting signals (redirects, rel=prev/next).
- Test in Google Search Console — ensure that the detected canonical matches the specified one.
- Monitor indexing for a month.
Canonical in HTTP Header for PDFs and Other Files
For non-HTML resources (PDF, images), we use the HTTP Link header:
return response($pdf)
->header('Content-Type', 'application/pdf')
->header('Link', '<https://example.ru/docs/report>; rel="canonical"');
Guarantee of Result: Verification via Google Search Console
After setup, we check every URL via the URL Inspection Tool in Google Search Console. If the detected canonical does not match the specified one, we find the cause (conflicting redirects, incorrect referrer, lack of indexing). Our engineers with years of experience guarantee correct canonical operation on any stack: Laravel, Symfony, WordPress, Django, Next.js.
Comparison: correctly configured canonical gives an LCP increase of 10–15% due to reduced duplicate content that crawlers waste on useless pages.
Timeline and Cost
Basic setup for a typical site — from 1 to 3 days. The cost is calculated individually based on the number of pages and architecture complexity. We evaluate the project for free — just contact us. Order a canonical audit and get a report with recommendations. Contact us for a consultation. Get a free consultation on canonical setup for your project.