Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Content Marketing › Troubleshooting

Syndicated Copy Outranking the Original

Why a syndicated copy outranks your original and how to fix it: the copy went live first, an edited copy, mixed signals, a robots block and only a link.
Troubleshootingintermediate8 min readUpdated

First, confirm which copy search prefers

Three checks settle the question. Search for an exact sentence from the article in quotation marks and note which address appears first. Open the search performance report for the original's URL and compare impressions for the article's main queries before and after the copy went live; a fall that starts on the copy's publication date is the signature of this problem. Then inspect the original's URL: the crawling and indexing guide explains that URL inspection shows both the canonical you declared and the one Google selected, and a selected canonical on the partner's domain is direct evidence that search treats the copy as the main version.

Then read the copy itself as a crawler would. Open the partner's page source and note any canonical element and any robots meta tag, check the response headers for a robots directive, and check the partner's robots.txt for a rule covering the page. Compare the copy's title, headings and length with the original. With those facts written down, the table below names the cause; the options for protecting an original, and when each suits, are set out in the guide to syndicating and republishing content and are not repeated here.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
The copy was found and indexed before the original existedPublication dates and first-crawl dates of both pagesThe partner's copy went live before the originalPublish first on your own site; for live copies, add a directive
A canonical points at the original, yet the copy is shownThe copy's title, sections and length against the originalA canonical on a copy edited until it is no longer a duplicateRestore a faithful copy, or replace the canonical with a noindex
A noindex is on the copy, yet it still appearsWhether a canonical sits beside it, or robots.txt blocks the pageCanonical and noindex on the same copy, or a robots.txt block hiding the noindexKeep one directive, and let the crawler fetch the page
The copy carries no canonical and no noindexThe copy's source and headers for any directive at allOnly an attribution link, which says nothing about which version to preferAsk for a canonical or noindex; otherwise stop syndicating that piece
Directives are correct, yet the copy still winsInternal links pointing at the original on your own siteThe original weakly linked within its own site, so the copy carries more signalsLink the original from hubs and related pages with descriptive anchors

Fix, verify and prevent each cause

A copy that existed first

If the partner published before you did, the copy was the only version for a while, and search had no original to prefer. The syndication guide's written terms put timing first for that reason: the original goes live on your site before any copy appears.

Fix: for a copy already live, the timing cannot be undone, so the remedy is a directive on the copy that search can read; ask the partner for a canonical on a faithful copy or a noindex, as the agreement allows.

Verify: the exact-phrase search starts returning the original, and the original's impressions for its main queries recover.

Prevent: write the publication order into every agreement, and send the partner the original's live address rather than a draft.

A canonical on a copy that is no longer a duplicate

A partner that retitles the article, adds sections or cuts it down has made a different page, and the canonical on it describes a relationship that no longer exists. The canonical tag versus permanent redirect comparison records that a canonical is a hint weighed against other signals, and that a duplicate whose content differs substantially may be treated as its own page. Google's documentation on consolidating duplicate URLs is the source those pages draw on.

Fix: either ask the partner to restore a faithful copy, moving its additions to a separate article, or replace the canonical with a noindex that does not depend on the pages matching.

Verify: URL inspection of the original shows your own URL as the selected canonical again.

Prevent: agree in writing what the partner may change, and review the copy whenever the partner redesigns its templates.

Directives that contradict or cannot be read

Two set-ups look protective and are not. A copy carrying both a Canonical Tag and a noindex sends signals the crawling and indexing guide describes as contradictory. A copy with a noindex behind a robots.txt rule is never fetched, so its noindex is never read; Google's help page on blocking indexing with noindex explains that the crawler must be able to access the page to see the directive, and the noindex versus robots.txt comparison adds that a blocked but linked page can still be indexed from links alone.

Fix: keep one directive on the copy and remove any robots.txt rule that stops it being fetched.

Verify: the copy's source shows a single directive and the partner's robots.txt allows the page.

Prevent: add "one directive, crawlable" to the checks you run when each copy goes live.

A credit line and a link back are the minimum in any arrangement, and they help readers find the source. They do not tell search which version to show, so a copy on a larger, busier site may simply win. The syndication guide is plain that when the link is the only protection, the copy may be the version shown.

Fix: ask the partner whether its system can add a canonical or a noindex; if it cannot and the article matters for search, end syndication of that piece or replace the copy with an excerpt that links to the original.

Verify: either a directive appears on the copy, or the full copy is replaced and the original regains its queries.

Prevent: confirm before agreeing which directive the partner's system supports, and decline full copies of search-critical pieces where it supports neither.

An original its own site ignores

Sometimes every directive is right and the original still looks weaker. A copy linked from a busy partner's homepage and newsletter, against an original reachable only through an archive page, gives search a lopsided picture. The internal linking guide explains that pages linked from important pages are found sooner and refetched more often, and that internal links distribute the authority the site earns from each Backlink.

Fix: link the original from its hub, from related articles where the topic comes up and from the newsletter, with anchors that describe it.

Verify: a crawl shows the original's inlinks rising, and the original's impressions recover for its queries.

Prevent: before any piece is offered for syndication, check that it is already well linked on your own site.

A prevention routine for syndicated pieces

Keep a register of every syndicated article: the original's address and publication date, the partner, the copy's address, the directive agreed, the date the copy went live, and the date it was last checked. Publish on your own site first, link the original into its hub and related articles, and only then send it to the partner. On the day the copy appears, read its source and headers and the partner's robots.txt, and record what you found in the register.

Each month, run the three confirmation checks for every live copy: an exact-phrase search, the original's search performance for its main queries, and URL inspection of the original. Re-read the copy's directives whenever the partner changes its design, since a new template is the commonest way for a canonical to disappear. When a partner asks to edit, extend or retitle a piece, treat it as a change of arrangement: agree a noindex or a separate article before the edit goes live, not after the copy starts appearing in your place.

Finally, end arrangements that cannot be protected for pieces that matter in search, and keep syndicating only the pieces where reach is the point. Copies made without permission are not part of this routine; they belong to the spam policies guide. The content troubleshooting section lists the neighbouring symptoms, such as an archive losing traffic over many months, that have different causes.

Illustrative example — not a real result

Pibblesprout Home Brewing wins back its own guides

Pibblesprout Home Brewing, an invented home-brewing supplier, lets a hobby magazine republish six of its brewing guides under a cross-domain canonical. Within two months, three of the magazine's copies appear for the guides' main queries instead of the originals. An exact-phrase search returns the magazine first for all three, the originals' impressions for their main queries have fallen from about 4,800 a week to 1,300, and URL inspection shows the magazine's address as the selected canonical. Reading the copies shows why: the magazine retitled all three, added reader tips and an equipment box, and roughly doubled their length. The other three copies, left as published, still defer to the originals. Pibblesprout and the magazine agree to switch the edited copies to a noindex and to allow the crawler to fetch them. Pibblesprout also links each original from its brewing hub, where they had been reachable only through a dated archive. Six weeks later the originals appear for their queries again, and weekly impressions are back to about 4,600.

Common mistakes

Asking for a canonical and then letting the partner rewrite the piece. Stacking a canonical and a noindex to be doubly safe. Blocking the copy in robots.txt. Treating an attribution link as protection in search. Sending the partner a piece before it is live on your own site.

Frequently asked questions

Is a partner's copy outranking us a penalty?

No. A copy made by agreement is not spam, and nothing has been held against your site. Search has picked one version of a set of near-identical pages to show, and the signals it was given favoured the partner's. The fix is to change those signals: protect the copy with a canonical or a noindex that search can read, and make the original the stronger page on your own site. Copies made without permission are a different matter, covered by the spam policies guide.

Should we ask the partner to take the copy down?

Only if the agreement cannot be repaired. A copy that carries a working noindex, or a canonical on a faithful duplicate, keeps reaching the partner's readers without competing with the original in search. Removal ends the reach the arrangement was made for. If the partner cannot add either directive and the piece matters for search, ending that piece's syndication, or replacing it with a short excerpt that links to the original, is the cleaner choice.

How long does a fix take to show?

It depends on when search next fetches the copy, so there is no fixed period to promise. A directive added to the partner's page only takes effect once the crawler has read it, which is why a robots.txt block that stops the page being fetched also stops the fix working. Check the copy's directives the day they are added, then watch the original's search performance report and an exact-phrase search over the following weeks.

Terms used on this page

Also related

Sources

  1. Consolidate duplicate URLs — Google Search Central
  2. Block Search indexing with noindex — Google Search Central

Related