Digital Content · Practical guide

Content repurposing: one article, thirty pieces, one home

Content repurposing done properly is derivation, not recycling: the guide on your domain is written once, with the data and the named sources, and everything else, the posts, the clips, the chart card, the email, the portal article, is cut from it and links back to it. The guide is the only piece that compounds. This guide gives the five-step pipeline we run on our own articles, the thirty pieces and where each goes, the order that compounds, and how to measure it.

1source: the guide on your domain, written once with the data and the sources
30pieces, about, derived from it in a day of the team's time
5steps: extract, cut, draw, write, schedule with links home
1direction: every derivative sends the reader to the guide. The feed is the door

The short answer

One article, thirty pieces: the Snowball Effect applied to distribution

Content repurposing is turning one piece of content into many, for many places, without writing it again. Done properly it is not recycling but derivation: the guide on your domain is written once, with the data and the named sources, and everything else, the posts, the clips, the chart card, the email, the portal article, is cut from it and links back to it. The guide is the only piece that compounds, because it is the one that ranks and gets cited; the rest exists to send people to it. About 20 Australians a month search "content repurposing" at difficulty 71, and the businesses asking are usually trying to make more content. The answer is to make one thing well and derive the rest.

Key takeaways

01

The guide on your domain is the source. It is written once with the data and the sources, and it is the only piece that ranks and gets cited.

02

Everything else is derived: claims extracted, clips cut, the chart redrawn, the platform versions written, all linking home.

03

Five steps, about a day of the team's time per guide, produces roughly thirty pieces and a month of distribution.

04

Measure the derivation by what it sends to the guide, and the guide by rankings, citations and enquiries. The posts are doors.

The basics

Derivation, not recycling

Content repurposing has a bad name because most of it is recycling: the same post reformatted for five platforms, or a blog chopped into tweets. What works is derivation. There is one source, the guide on your own domain, built to the standard every article on this site follows: a question from the search map, the answer first, the data with named sources, a bespoke chart, a named author, valid schema. Everything else is derived from that source and points back to it. The post is a claim from the guide; the clip is the founder saying that claim; the chart card is the guide's figure redrawn; the email is the guide's opening paragraph; the portal article is the guide with the customer's own numbers.

The distinction matters because only the source compounds. A post lives days, a clip lives weeks in search on a good day, an email lives until it is archived. The guide lives as long as the site does, ranks for the question, is cited by the AI engines, and is linked from the service page. Repurposing is the discipline of making sure every short-lived piece leaves the reader on the long-lived one. Our guide to content that ranks and gets cited covers how to write the source; this guide covers what to do with it.

One source

The guide, on your domain, with the data and the sources. Written once. The only piece that ranks and is cited.

Many derivatives

Posts, clips, cards, email, portal article. Cut from the source, never written from scratch, all linking back.

One direction

Every derivative sends the reader to the source. The feed is the door; the guide is the room.

The demand

Why the guide is the source, in numbers

The derivatives are cheap. The source is the work. Figures from our own Snowball SEO platform, country set to Australia, the Edelman-LinkedIn 2024 report, and our own pipeline.

20monthly Australian searches for "content repurposing", at difficulty 71, with a traffic potential of about 820 across the clusterSnowball SEO platform (AU), Edelman-LinkedIn 2024, our own pipeline
103guides on this site when this article was first drafted, each derived into a month of distribution by the pipeline belowSnowball SEO platform (AU), Edelman-LinkedIn 2024, our own pipeline
95%of B2B buyers not in market at any moment (Edelman-LinkedIn, 2024): the derivatives reach them; the guide is what they find laterSnowball SEO platform (AU), Edelman-LinkedIn 2024, our own pipeline
30pieces, about, per guide: what our own pipeline produces from one article in a day of the team's timeSnowball SEO platform (AU), Edelman-LinkedIn 2024, our own pipeline

The method

The five-step pipeline

One guide, thirty pieces: the pipeline we run on our own articles Counts are what our own pipeline produces per article. The guide is written once; everything else is derived. 1. EXTRACTPull the one-sentence claims, the key figures and the named sources from the guide. Six to ten claims per guide.Output: a claims list. Who: the writer, twenty minutes. 2. CUTMatch each claim to footage: the founder's hour, the demo, the webinar, the team's clips. Caption, one claim per clip.Output: eight vertical clips. Who: the editor, an afternoon. 3. DRAWRedraw the guide's chart as a card with the figures visible and the source on it, plus a carousel of the claims.Output: one chart card, one carousel. Who: the designer, an hour. 4. WRITEFour LinkedIn posts under the founder's name, one email to the list, one Google Business Profile post, one portal article.Output: seven written pieces. Who: the writer, two hours. 5. SCHEDULELinks home: every piece carries a tagged link to the guide, in the first comment where links in the body are punished.Statics first, clips staggered over the month, the email on the day the guide goes live.Output: a month of distribution. Who: whoever runs the socials, an hour. Held as drafts until approved.

The pipeline we run on our own articles. About a day of the team's time per guide, none of it the founder's.

The pipeline is deliberately boring, because it has to run every day. Extract the claims (the one-sentence positions, the key figures, the named sources). Cut the clips by matching each claim to footage that already exists: the founder's hour from our founder-led guide, the demo, the webinar, the team's clips. Draw the chart card and the carousel. Write the platform versions: four LinkedIn posts in the founder's voice per our LinkedIn guide, one email, one Google Business Profile post, one portal article. Schedule everything with tagged links home, held as drafts until approved. On this site the last step is a scheduled task that builds the pack in the social platform as drafts; a person approves and times every post.

The output

The thirty pieces, and where each one goes

PieceCountWhereLinks to
LinkedIn position posts4The founder's profile, one a weekThe guide, in the first comment
Short vertical clips8Reels, TikTok, Shorts, ThreadsThe guide via the bio link; the demo page for demo cuts
Chart card1Every feed, the email, the LinkedIn carouselThe guide
Claims carousel1Instagram, LinkedIn as a documentThe guide
Team how-we-do-it post1 to 2Team members' profilesThe service page for the work
Email to the list1The day the guide goes liveThe guide
Google Business Profile post1The map listingThe guide or the service page
Portal article1Behind the login, personalised where possibleThe customer's own next step
Pinned first comments8 to 10Under every post that allows oneThe guide, and a question to invite replies

The portal article is the piece most repurposing plans miss and the one that pays best: the same guide, behind the login, with the customer's own numbers where the data layer has them, becomes the most-read version of the article, because the reader it is written for has already paid. The client portal guide covers where it lives; the personalisation guide covers how it knows who is reading.

The sequence

The order that compounds

Five steps in order. It is the Snowball Effect as a schedule: data first, the owned page second, the derivatives after, the portal last.

The data layer picks the question

Not the derivatives, not the calendar. The search map and the topical map decide what the guide answers, so the source is a page prospects search for before it is written.

The guide is published first, on the open site

With the data, the sources, the chart, the author and the schema. It starts ranking and earning citations before any derivative exists. The derivatives point at something that is already there.

The email goes the same day

The list is the one audience you own on both ends. The guide's opening paragraph and the chart, one link, sent the day it goes live.

The statics go out first, the clips are staggered

Chart card and carousel in the first week; the eight clips across the month; the LinkedIn positions one a week. A month of doors to one room.

The portal article closes the loop

The customer's version, with their numbers, is the last derivative and the one that keeps them. The guide won the stranger; the portal article keeps the customer.

The measure

Measuring the derivation

Measure the derivatives by what they send to the source: sessions to the guide from each tagged link, and what those sessions do there. Measure the source by rankings, citations and the enquiries that come through the service page it links to. The two numbers together tell you which derivative formats are worth the editor's time for your audience, since a format that sends fewer readers who finish the guide is usually worth more than one that sends many who leave, and which guides deserve a second month of distribution. Views, reactions and reach are the platforms' numbers, and they measure the platforms' goals. Our Snowball SEO platform tracks the guide's rankings and citations and the traffic each derivative sends it, which is the data layer the pipeline reports to.

Write it once, where you own it. Derive everything else.The one-line discipline. The guide is the only piece that compounds; the thirty derivatives exist to send readers to it and to keep customers once they have arrived.

The investment

What content repurposing costs

About a day of the team's time per guide: twenty minutes to extract, an editor's afternoon to cut, an hour to draw, two hours to write, an hour to schedule. None of it is the founder's, and none of it is new creative work; it is derivation from a source that was worth writing properly. The saving is the second draft that never gets written, the shoot that never gets booked for the feed, and the calendar meeting that never happens because the data layer already picked the question. Our Snowball SEO platform picks the questions, tracks the guides and reports what each derivative sends home, which is the heavy lifting other agencies bill by the hour, so the budget goes to the guide and the editor. See our articles and written content service for the source and our social channels service for the derivation.

Sources: Keyword volume, difficulty and traffic potential from our Snowball SEO platform, country = Australia, pulled August 2026. Buyer behaviour from the 2024 Edelman-LinkedIn B2B Thought Leadership Impact Report. Piece counts and timings are what our own pipeline produces per guide, not a published benchmark.

Anthony Betzis
Founder, Snowball Productions

Anthony founded Snowball Productions to help Australian businesses win the searches that actually bring in work. He writes about the data behind SEO, AI search and the content that converts.

Start here

Want one guide a month turned into thirty doors home?

Get a free audit and we will show you which of your existing content is a source worth deriving from, and what the first month's pipeline would produce.

Get your free audit

Good questions

Content repurposing FAQs

What is content repurposing?

Turning one piece of content into many for many places without writing it again. Done well it is derivation: one source (the guide on your domain, with the data and named sources) and many derivatives (posts, clips, a chart card, an email, a portal article) cut from it, each linking back. Done badly it is recycling: the same post reformatted five times.

How many pieces can you get from one article?

About thirty in our own pipeline: four LinkedIn position posts, eight short vertical clips, a chart card, a claims carousel, one or two team posts, an email, a Google Business Profile post, a portal article and eight to ten pinned first comments. About a day of the team's time, none of it the founder's.

Which piece of repurposed content matters most?

The source. The guide on your domain is the only piece that ranks, gets cited by AI engines and is linked from the service page, and it lives as long as the site does. The derivatives live days or weeks and exist to send readers to it. A weak source with thirty derivatives is thirty doors to an empty room.

In what order should repurposed content be published?

The guide first, on the open site, so it starts ranking before any derivative exists; the email the same day; the chart card and carousel in the first week; the eight clips staggered across the month; the LinkedIn positions one a week; and the portal article last, personalised with the customer's numbers where the data layer has them.

How do you measure content repurposing?

Derivatives by the sessions they send to the guide from tagged links and what those sessions do there; the guide by rankings, citations and the enquiries through the service page it links to. Together they show which formats send readers who finish the guide and which send more people who leave sooner, which is what decides the editor's time next month. Views and reach are the platforms' numbers.

What does content repurposing cost?

About a day of the team's time per guide: twenty minutes to extract the claims, an editor's afternoon to cut clips from footage that already exists, an hour to draw the chart card, two hours to write the platform versions, an hour to schedule with links. No new creative work and no second draft. Timings are what our own pipeline runs, not a benchmark.