Skip to the indexed answers
Digital Marketing Index

usdigitalmarketingindex.com SEO

How should an original publisher manage articles syndicated to third-party websites?

Settle the terms in a written agreement before any article is shared, and make the central term how the partner’s copy will be kept from competing with the original in search. Google’s current guidance is specific on this point: “The canonical link element is not recommended for those who want to avoid duplication by syndication partners, because the pages are often very different. The most effective solution is for partners to block indexing of your content” (Google’s guidance on canonicalization issues). A cross-site canonical tag is a hint that may be ignored. A noindex rule on the partner’s copy is a direct instruction. The rest of the arrangement covers attribution, timing, links, and the right to withdraw.

Original source and license terms

The agreement establishes who owns the article and what the partner may do with it.

  • Ownership: the original publisher retains copyright, and the partner receives a license to republish.
  • Scope: which articles, in full or in part, for how long, on which properties.
  • Changes: whether the partner may edit, retitle, or shorten, and whether changes need approval.
  • Attribution: a visible credit naming the original publisher, with a link to the original article.
  • Timing: how long after original publication the partner may publish.
  • Updates and corrections: how the partner applies changes made to the original.
  • Withdrawal: the right to have the copy taken down.

Timing matters because the original should be discovered first. Publishing the original, confirming it is indexed, and only then releasing it to partners gives search engines a clear first sighting.

Publisher canonical requests

Ask the partner for one of the following, in this order of preference.

Request What it does Limit
Noindex on the syndicated copy Tells search engines not to index the partner's copy The partner gets no search visibility from it, which some will refuse
Canonical tag on the copy pointing to the original Signals a preference for the original A hint; Google's guidance says it is not recommended for syndication because the pages are often very different
A visible link back to the original, near the top Attributes the source for readers and crawlers Does not prevent the copy from being indexed
A shortened version with a link to the full original Leaves the complete article only on the original site Requires the partner to accept an excerpt

The first is what Google’s guidance names as most effective. Where a partner will not agree to it, combine the others, and accept that the outcome is uncertain.

Cross-domain limitations

Be clear with stakeholders about what cannot be controlled.

  • Canonical preferences are advisory. Google’s documentation states that “indicating a canonical preference is a hint, not a rule”, and that it “may choose a different page as canonical than you do” (Google’s explanation of canonicalization).
  • The partner controls its own pages. A tag agreed in the contract can be removed in a redesign, and nothing on your site will tell you.
  • A syndicated copy on a large, frequently crawled site may be found before the original, especially if published at the same moment.
  • The partner’s page differs from yours in template, navigation, and surrounding content, which is the reason the guidance gives for canonical tags being unreliable here.
  • Even with a noindex rule in place, the copy remains visible to the partner’s own readers, which is the purpose of syndication.

None of this means syndication should be avoided. It means the publisher should decide whether the audience gained on the partner’s site is worth the possibility that the partner’s copy appears in search in place of the original.

Measurement and monitoring

Check that the terms are being met, since they are implemented on someone else’s site.

The agreement checklist below gives the input to verify, the action, and the pass or fail condition for each term.

Input to verify Action Pass or fail
Written license Confirm scope, duration, and properties are stated Fail if any is undefined
Indexing term Confirm the agreement requires noindex, or states which alternative applies Fail if the agreement is silent on indexing
Partner's live copy View the page source for the robots meta tag or canonical tag agreed Fail if absent
Attribution Check for a visible credit and a working link to the original Fail if missing, or if the link is not near the top
Publication timing Compare publish times Fail if the copy appeared before the agreed delay
Edits Compare the copy with the original Fail if changed beyond what was permitted
Corrections After correcting the original, check the copy Fail if the correction was not applied in the agreed time
Withdrawal clause Confirm it exists Fail if absent

After each article is syndicated:

  1. Search for a distinctive sentence from it and note which site appears. Record the date.
  2. Inspect the original URL in Search Console and confirm Google’s selected canonical is your own URL.
  3. Recheck the partner’s copy periodically for the agreed tags, since templates change.
  4. Track referral visits from the partner in analytics, which is the benefit the arrangement is meant to produce.

If the partner’s copy is appearing in results in place of the original, raise it under the agreement and ask for the noindex rule. If that is refused, the remaining options are to shorten what is syndicated or to end the arrangement.

This guide concerns copies on other sites. Republishing an article at a new address on your own site raises a related set of issues with different remedies, covered in the guide to the risks of republishing an unchanged article at a new URL.

The measure of a sound syndication arrangement: the indexing term is written down, it is visible in the partner’s page source, and someone checks it.

Link trail

Reader comments on this answer

Add your comment to this answer

Your email address will not be published. Required fields are marked *