A canonical tag is a simple HTML element placed in the page head that tells search engines which URL is the "original" version when several similar or duplicate pages exist. It is one of the most important tools in
What is a canonical tag and why does it matter?
The canonical tag is written inside the <head> section in this form:
<link rel="canonical" href="https://example.com/page/" />
When Google finds several URLs with identical or near-identical content, it becomes unsure which to rank, and may split backlink strength between them, weakening them all. The canonical tag settles the matter: it directs all signals toward one preferred version, so it ranks with consolidated strength. Think of it as pointing every duplicate back to a single authoritative source that absorbs all the ranking value.
The duplicate content problem and its sources
Duplicate content is rarely deliberate copying, it usually stems from technical causes:
- URL parameters: sort, filter and tracking links such as
?utm_sourcegenerate countless versions. - HTTP, HTTPS, www and non-www versions: four possible versions of every page.
- Product pages in multiple categories: very common in stores in Riyadh and Dammam.
- Print or AMP versions: extra copies of the same content.
Rather than relying on Google to guess the correct version, we settle it ourselves with the canonical tag.
Correct usage and self-referencing canonicals
The best practice we apply is the self-referencing canonical: every page carries a tag pointing to its own clean version. This automatically hardens the site against versions created by parameters.
Core rules for a healthy canonical:
- Use full absolute URLs, not relative ones.
- Always point to the single preferred version (HTTPS, no parameters).
- Ensure the URL in the tag returns a 200 status, not a
- Never place more than one canonical tag on a page, as the contradiction voids it.
Canonical tags and pagination
On blog and store pages split into pages 1, 2 and 3, current practice differs from the old one. Google no longer supports the rel=next and rel=prev tags. Today's recommendation is that each paginated page should self-reference with its own canonical, not point to page one, because each page carries different products or articles that deserve indexing.
The common mistake is pointing all paginated pages to page one, which hides the rest of your products from indexing.
Interaction with hreflang on bilingual sites
This is a sensitive point for bilingual Saudi sites. When you link Arabic and English versions via hreflang tags, each canonical must point to its own language version, not to the other language.
| Case | Correct behavior |
|---|---|
| The Arabic page | canonical points to the Arabic URL itself |
| The English page | canonical points to the English URL itself |
| The language relationship | hreflang links them reciprocally |
The common mistake is having the English version's canonical point to the Arabic one, which cancels the work of hreflang and hides your English version.
Common canonical tag mistakes
We watch for these mistakes in every audit:
- Pointing to a noindex, 404 or redirected page: conflicting signals that confuse Google. Review how they relate to
- A canonical to the homepage on every page: a serious error that consolidates your whole site into one page.
- Relative URLs or the wrong protocol: breaks the tag entirely.
- A canonical that conflicts with your sitemap or internal links: weakens the credibility of your signal.
Correct canonical usage consolidates your site's strength instead of scattering it. To make sure your site in Saudi Arabia is free of duplicate content issues, get a comprehensive