Cross-Domain Canonical Tags

What a cross-domain canonical tag is

A cross-domain canonical is a rel=canonical tag that points to a URL on a different domain than the page it appears on, rather than to another URL on the same site. It's most often seen in content syndication, where an article published on one site is republished, in whole or in part, on another.

The markup looks the same as any other canonical tag — only the target domain differs from the page's own:

<link rel="canonical" href="https://original-site.com/original-article/">

If that tag appears on a page at https://partner-site.com/republished-article/, it's telling Google that the content on original-site.com is the version to index, and that the partner-site.com copy should be treated as a duplicate rather than indexed separately.

Google supports cross-domain canonicals technically, as a hint, the same way it treats any other canonical: it's a signal, not a directive, and Google can choose to follow or ignore it.

When a cross-domain canonical is the right tool — and when it isn't

There are legitimate uses for a cross-domain canonical. One is consolidating genuinely identical content that you own and publish across more than one domain — for example, the same page mirrored on two domains you control, where you want ranking signals to consolidate on one of them. Another is a syndication partner voluntarily canonicalizing a near-identical republished article back to the original source, as a courtesy to the original publisher.

Where it gets shakier is the broader syndication use case in general. Because a cross-domain canonical is only a hint, and because syndicated pages are often not truly identical to the original — different surrounding template, added commentary, different formatting, sometimes an edited excerpt — Google may simply decline to follow the canonical. When the pages differ meaningfully, treating one as a strict duplicate of the other doesn't hold up, and the mechanism is not reliable for that purpose.

Why Google now prefers noindex for syndication

Since around May 2023, Google has explicitly stopped recommending cross-domain canonicals as the way to handle syndication. In Google's words: "The canonical link element is not recommended for those who want to avoid duplication by syndication partners, because the pages are often very different." Instead, Google says the most effective solution is for syndication partners to block indexing — using noindex — on the syndicated copy.

The reasoning follows from the same problem described above: syndicated pages frequently aren't close enough duplicates of the original for a canonical hint to be a reliable signal. Rather than asking Google to treat two meaningfully different pages as one, noindex on the syndicated copy sidesteps the ambiguity entirely — it simply keeps that copy out of the index, with no need for Google to judge how similar the two versions are.

How to implement a cross-domain canonical

For the narrower, legitimate cases where a cross-domain canonical still makes sense — such as content you own mirrored across domains, or a willing syndication partner pointing back to the original — the implementation follows the same rules as any other canonical tag. Use an absolute URL pointing to the exact preferred version on the target domain, place it in the raw HTML head (or HTTP header) rather than injecting it only via JavaScript, and use exactly one canonical tag on the page.

<link rel="canonical" href="https://original-site.com/original-article/">

Because this is a hint that Google evaluates on its own, and because it depends on the two domains agreeing to the arrangement, it's worth confirming with the partner site that the canonical target is stable, returns a clean 200 response, and isn't itself redirected or noindexed — the same target-quality requirements that apply to any canonical.

Risks and how to monitor it

Cross-domain canonicals carry a few specific risks beyond the usual canonical caveats:

• It's only a hint. Google may ignore a cross-domain canonical entirely, particularly if the two pages differ meaningfully in content, which is common in syndication.
• Injected cross-domain canonicals are a known hijacking technique. A malicious actor who can inject a cross-domain canonical into a page — through a compromised plugin, ad script, or other vulnerability — can attempt to redirect a site's ranking signals toward a domain it doesn't control. This is a recognized attack pattern, not a theoretical one.
• Propagation delays have been reported. Cross-domain canonical signals don't necessarily take effect quickly, and there can be a lag before Google's index reflects the intended consolidation.

Given these risks, monitoring matters. Use Google Search Console's URL Inspection tool to check the Google-selected canonical for pages that carry a cross-domain canonical, and compare it against the user-declared one — a persistent mismatch is a sign Google isn't honoring the hint. Periodically auditing a site's own pages for unexpected cross-domain canonical tags is also worth doing, precisely because an injected one can be hard to notice without a deliberate check.

Frequently Asked Questions