Syndicating articles between sibling brands without wrecking either one in search

Somebody on the group content team writes a good explainer for the packaging show, and within a week it has been pasted into the food ingredients site and the logistics site because it is good and the audiences overlap. Three brands, one piece of work, three pages. That feels like efficiency.

Syndicating articles between sibling brands this way creates three URLs competing for the same query, and search engines resolve that competition by picking one and suppressing the rest. The one they pick is frequently the sibling with the strongest domain, which is rarely the show whose editor paid for the piece.

What cross-posting does to three sites at once

Work an illustration through. A portfolio publishes one explainer in full on three show sites. Over a quarter, the search console data for the three URLs might look like this: the packaging site's version gets 4,100 impressions and 180 clicks at an average position of 11, the food site's version gets 1,350 impressions and 38 clicks at position 19, the logistics site's version gets 900 impressions and 21 clicks at position 24.

Total, 6,350 impressions and 239 clicks. Now consider the counterfactual where the same effort produced one page on the packaging site, carrying the links and the internal links the other two would have earned. Ranking is not additive, so you cannot simply add the three positions together. What you can say is that a single page holding all the external references and all the internal links from three brands is competing with more evidence behind it than any of the three had alone, and that the two suppressed pages contributed 59 clicks between them for a full production and publication cycle each.

The second cost is invisible in that table. Editorial teams update the version they remember. Nine months later the packaging site's copy has a corrected figure and the logistics site's copy does not, and the logistics one is the one an answer engine happens to retrieve.

What search engines call this when it goes wrong

There is a policy line here and it is worth reading in the original. Google's search spam policies, in their 2026 form, define site reputation abuse as "a tactic where third-party content is published on a host site mainly because of that host's already-established ranking signals, which it has earned primarily from its first-party content".

Sibling brands inside one portfolio are not obviously third party, and a piece written by your own editorial team for your own audience is not the target of that policy. The risk arrives when the reason for the cross-post is the receiving site's rankings rather than the receiving site's readers. A group that pushes every piece onto whichever domain ranks best, with no editorial connection to that brand's audience, has built the pattern the policy describes using internal content.

The related policy is closer to home for portfolios adopting machine drafting. The same document defines scaled content abuse as when "many pages are generated for the primary purpose of manipulating search rankings and not helping users". Eight brand-specific rewrites of one explainer, each varied enough to avoid looking identical, sits inside that definition more comfortably than most people running it would like.

The test worth applying before a syndication: would you still run this piece on this brand if it earned no search traffic at all? If the answer is no, the piece is being placed for the domain.

Should siblings get the full text or an excerpt?

Full text on the sibling, with a canonical tag pointing home, is the arrangement most groups reach for. It works, with a caveat about what the tag actually does. Google's own documentation on consolidating duplicate URLs, updated in 2026, describes rel="canonical" as "A strong signal that the specified URL should become canonical" and states that where you do not specify one, "Google will identify which version of the URL is objectively the best version to show to users in Search". A strong signal is not a directive. Redirects are stronger, and a redirect is not available to you here because the sibling page has to exist for readers.

Excerpt plus link is the arrangement I would default to, for three reasons that have nothing to do with tags.

The sibling page becomes a genuinely different document, written for a different audience, which removes the competition instead of managing it. It gives the receiving brand's editor something to do beyond pressing paste, which is where the audience-specific framing comes from. And it survives a mistake: if somebody forgets the canonical tag on a full-text copy, you have a duplicate in the index, whereas a forgotten tag on a 300-word excerpt with original framing costs you nothing.

The excerpt should be two to four paragraphs of the original plus a paragraph or two of framing for the receiving audience, and the link to the full version belongs in the first screen rather than at the foot. Where a full-text arrangement is genuinely needed, the tag policy that governs it, including what to do for translations and derivative formats, belongs with setting a canonical strategy for repurposed content.

The syndication register

Whatever policy you pick, the thing that makes it survivable is a record, and almost nobody has one.

Five fields.

• Source URL. The canonical home, in full.
• Receiving brand and URL. One row per receiving site, so a piece syndicated three ways has three rows.
• Date of syndication. For working out what a sibling copy was based on when the source changed.
• Form. Full text, excerpt, or headline and link.
• Canonical treatment. The tag applied, or noindex, or nothing.

The register answers questions that are otherwise unanswerable. Which sibling copies exist for a piece you are about to update. Which brand actually earned the links. Whether a page you are about to delete during a site migration is somebody else's canonical target.

Keep it next to the commissioning ledger rather than in a separate system, because the reuse licence decided at commissioning and the syndication actually executed are the two halves of one record. The commissioning half is covered in editorial operations across event brands.

How do you audit last quarter's cross-posts?

This is a half-day exercise and it usually surprises people.

Take the last quarter's published pieces from the brand with the strongest domain. For each, take a distinctive sentence of about twelve words from the middle of the body, not the opening, and run it as an exact-match search restricted to each of your own domains in turn. Count how many of your own sites return a hit.

Score the result three ways. Count the pieces appearing on more than one owned domain, and divide by pieces published, which gives you a syndication rate. For each of those, check whether a canonical tag exists on the copies and where it points, which gives you a coverage figure. Then check whether the copy search actually shows for the piece's main query is the one you intended, which is the number that matters.

An illustrative outcome: 48 pieces published, 17 appearing on more than one owned domain, so a 35 per cent syndication rate. Of those 17, canonical tags present on 9, absent on 8. Of the 9 tagged, 7 pointing at the intended home and 2 pointing at the sibling because the tag was copied along with the article. Of all 17, the version showing for the main query matches the intended home in 10 cases.

Ten out of seventeen is not a disaster and it is not a policy either. It is what happens when the decision is made piece by piece by whoever is publishing that afternoon.

What to fix first, in order

Fix the pointing-the-wrong-way tags first, because they are actively telling a search engine to prefer the page you did not want, and there are usually only a handful.

Then handle the untagged full-text copies. Cutting them to excerpts is better than tagging them, because it removes the ambiguity rather than signalling about it, and it takes an editor twenty minutes per page.

Then set the default. One line in the editorial handbook naming excerpt plus link as the standard form, the exceptions that are allowed, and who signs off an exception. Without the line, the audit result will reappear next quarter.

Leave the internal link graph until last. Which sibling links to which, and how to stop the strongest domain absorbing every ranking in the portfolio, is a separate problem with its own trade-offs, handled in internal linking across sibling brands.

Where this stops

The audit method above finds text copies and misses everything else. A piece rewritten by a second freelancer from the same brief will not match on any twelve-word string and will compete just as hard, because search engines resolve near-duplicates on meaning as well as on strings. Measuring similarity across a corpus properly needs a different technique and is treated as its own subject.

The canonical mechanics also assume your sites are separate hosts with separate content management systems, which is common in portfolios assembled by acquisition and rare in ones built in place. Where all eight brands are sections of one platform, the syndication question turns into an information architecture question, and the register still helps while the tag advice mostly does not.

The honest limit on the arithmetic is that nobody can tell you what the consolidated page would have ranked. The 59 clicks the suppressed copies produced are measured. The clicks a single stronger page would have produced are not, and anybody offering you that figure is estimating. What the register buys you is the ability to run the comparison forward: syndicate as excerpts for a quarter, hold the commissioning volume flat, and read the source pages' positions against the previous quarter.

Take the ten pieces your strongest show brand published last month, run the twelve-word exact-match check against your own domains, and write down how many appear more than once. That number, and where the canonical tags point, is enough to decide whether this needs a policy or a morning's tidying. The broader approach sits on the content studio page.