Content Loop

For a long time, bringing people in with writing was treated purely as a line item. You counted what an article cost and how many signups it produced. Content marketing — the practice of earning demand with writing worth reading instead of with ads — got measured on exactly that scale.

The meeting always went the same way. A marketer would report that five blog posts last month cost $3,000 and brought in 60 signups. The founder would ask what 60 signups cost through ads. If the ad number came out lower, the content budget shrank next quarter. As long as content was measured against advertising with the same ruler, that conversation had only one ending.

Then something odd showed up as products got more users. Pages the company had never written a word of — documents users had created inside the product and published — started ranking in search and bringing people in. Company writing doesn't grow unless you hire more writers. This other kind grew on its own as the user base grew. Content loop is the name for what happens when you stop reading that traffic as a budget line and start reading it as a structure.

Three steps form a circle, and the output of the last one becomes the input of the first. It's one species of growth loop, the general shape where output feeds back in and the thing keeps turning on its own.

1. A user leaves something behind that's visible from outside the product — a published document, a template, a profile, a question and its answers. Material users make themselves is called user-generated content (UGC).
2. That artifact ranks in search and pulls in someone looking for the same topic. This is the step that routes through a search engine, and the work of making it rank is search engine optimization (SEO).
3. Some fraction of those visitors sign up, and some fraction of those publish something of their own. The next turn starts with step 1 holding a larger number than before.

Put numbers on it. Say 1,000 published documents each bring in 3 visitors a month, so 3,000 visits. Two percent of them — 60 people — sign up, and 30 percent of those, 18 people, publish a document of their own. Next month starts at 1,018. That's 1.8 percent growth, small enough to miss on a chart, but it isn't traffic you can switch off the way you switch off ads. Stop working on it entirely and those 1,000 documents keep bringing people in.

Three numbers set the speed: visitors per document, the share of visitors who sign up, and the share of new users who publish. Double any one of them and the whole turn doubles, so when you're picking where to work, measure all three separately and start with the lowest one. Teams that skip that measurement usually pour effort into search rankings when the real blockage sits in the publish step.

This applies to products that leave behind something readable from outside while people use them. A product that only handles internal payroll data has no reason for anyone to publish anything, and the loop never turns there. You can ship a sharing toggle, but nobody flips it.

At Pagedeck the loop runs on meeting-note templates. Someone builds a "weekly sync template," publishes it, the page ranks, and a person who finds it signs up to copy it. That's Ravi's patch of the map, and the number he watches isn't ad performance — it's how many documents got published this month.

Two other options sit beside this one when a team picks a structure. A viral loop has existing users bring in new ones directly, so it turns first in products where inviting someone is natural. A paid loop puts revenue back into advertising, which makes the payback period on customer acquisition cost (CAC) the thing that decides whether it turns at all. The content loop is the slowest of the three and the longest-lasting. An article takes three or four months to reach the top of a results page, and once it's there it keeps delivering for years without ad spend.

So a team that picks this one has to sit through a flat first half-year. Like the early stretch of any compounding growth curve, month six still looks like nothing happened, and the shape only becomes visible somewhere around month twelve.

"This is a content loop, so there's nothing to show this quarter. Check back in six months."

A request not to judge the work on current numbers.

"Published documents haven't moved in three months. Step 3 of the loop is stuck."

People are signing up but not publishing anything of their own.

"Our output never leaves the product, so a content loop won't turn for us."

A judgment that the team needs a different growth structure.

At Pagedeck this came up while the team decided where to put the publish button. Noa argued for pulling the sharing setting out of a submenu and onto the toolbar, and Mia framed that change as work on step 3 of the loop. The publish rate doubled within two months; search traffic moved four months after that. That lag between fixing one step and seeing the far side of the circle respond is the thing teams trip over most often here.

The most common misreading is that a company publishing a lot of articles has a content loop. Both bring people in through writing, so the confusion is understandable. But company output is capped by headcount — doubling it means doubling the team. The end never connects back to the beginning, which makes it a line, not a circle. Teams that miss this distinction announce a content loop, raise their publishing quota, and a year later have doubled their production costs and nothing else.

Assuming the loop turns by itself once sharing exists is the same kind of error. If step 3 sits near zero — new arrivals who never publish anything — the circle stops after one turn. A thousand published documents can keep delivering visitors indefinitely, but if none of those visitors publish, a thousand stays a thousand forever. Raising that rate is usually product work, which means a marketing team can't do it alone.