Repurposing content without competing with yourself

On your own domain, a topic gets one page. Everywhere else, it can appear in as many forms as you have the energy for, as long as each points back to that page.

• The guide is the page. It is the thing that ranks, collects links and gets refreshed.
• The thread, the newsletter issue, the video, the talk and the podcast answer are distribution. They bring people and mentions to the page.
• A second page on your site covering the same ground is not repurposing. It is cannibalisation with extra steps.

The test is the search, not the format. If two of your URLs would be reasonable answers to the same query, you have one page too many, however different the writing is.

In every row the page stays where it is. The channel version is shorter, looser and tuned to its audience, and it names the page it came from.

Google does not penalise duplicate content in the way people fear. What it does is pick one URL as canonical and fold the others, and it may not pick the one you wanted.

• The same guide as a blog post and as a documentation page. Pick one home and link from the other.
• A long guide and a short summary of it, both indexable. Make the summary a section of the guide.
• A "2025 edition" and a "2026 edition". Update the page, keep the URL, change the modified date.
• The same case study on /case-studies and on /blog. One URL, linked from both listings.
• A page per format of the same answer: the checklist, the template and the guide, when all three say the same thing.

Syndication is a different thing from repurposing: the same text, published on another site. It is worth doing when that site has readers you cannot reach, and it is worth doing carefully.

1. 1

   Publish on your own site first

   Give Google time to crawl and index it there before the copy appears. Days, not hours.

2. 2

   Ask for a canonical to your URL

   A cross-domain canonical on their copy tells search engines yours is the original. Publishers who syndicate regularly know how to do this.

3. 3

   Accept a noindex instead

   If they will not set a canonical, a noindex on their copy achieves the same thing for search while keeping their readers.

4. 4

   Take a link at minimum

   If neither is possible, insist on a visible link back with your page's title as the anchor, and accept that their copy may outrank yours.

The risk is real but bounded: if the other site is much stronger, their copy can be the one that ranks. That trade is sometimes worth making for the audience, as long as you make it knowingly.

Take a fictional product, yourproduct.com, which has published /guides/import-csv after a week of support tickets about encoding errors.

1. The guide stays at /guides/import-csv, with the steps, the error table and the screenshots.
2. A thread takes the one table of encoding errors and their causes, and links the guide for the fixes.
3. The newsletter issue tells the story of the support week that prompted it, and links the guide.
4. A two minute screen recording shows the fix being applied, published on the video platform with the guide linked in the description.
5. In the community where the question keeps appearing, the answer is written out in three sentences, with the guide linked because it genuinely goes further.
6. Six months later the guide is refreshed rather than rewritten, and the channels get a second pass with the new table.

One URL, six appearances, no competition with itself. The guide accumulates the links and the rankings; the channels bring the people.

Sometimes what looks like duplication is really two questions that deserve two pages. The test is whether the searches are different, not whether the subjects are related.