Articles Are Not The Destination: Turning Refreshed Content Into A Funnel

Winning the traffic back was the easy part. A global endurance sports brand then had thousands of new readers a week landing on pages that ended in the wrong call to action, with hero images nobody could legally approve.

Here is how the content got a path, a set of tools, and a visual system, without a development sprint. If you have not read how the traffic came back in the first place, that story is in reviving a dead content library.

The Problem: Traffic With Nowhere To Go

The refresh program was working. Pages that had been dead for 18 months were pulling thousands of new users a week, and the client's leadership was paying attention for the first time in years. Which is exactly when the second problem became visible.

The pages had no path.

• A reader who landed on "what to eat before a workout" got a good answer and then a button to sign up for a race.
• A reader who finished a 16-week training plan and wanted to know whether they were ready had no link to the readiness article sitting three folders away.
• The brand's two primary conversions, app downloads and race registration, were bolted onto every page regardless of where the reader was in their decision.

There was no funnel, only a library with a checkout counter in every aisle.

Seventy percent of that audience was on mobile. That changes what "engagement" means. A 2,500-word article read on a phone at the gym is not going to be finished, bookmarked, and returned to.

The brand needed something a reader could take away, keep on their device, and come back to, and it needed a way to move someone from reading about training to doing something the brand could measure.

Then there were the images. This is a sports brand with a large athlete community and a deep photo library, and almost none of it could be used.

Athlete photography requires sponsor-approved apparel in shot, which turns every feature image into a rights check with a legal queue behind it. The content lead was already the single approver for copy; adding image approvals to her plate would have stalled the program. The first batch of refreshed articles shipped with generic imagery, which was safe and looked like everyone else's.

And all of this had to happen without a development sprint. The site runs on an enterprise CMS with a component-based page builder, the platforms team was consumed by a mobile app launch, and a ticket for a new interactive component was a quarter away at best. Whatever we built had to be something an editor could paste.

What We Did And Why

Sequence The Cluster Into A Path

We started with Conductor's view of which refreshed pages were earning intent, not just traffic. A page with rising impressions on preparation queries is a page where the reader is deciding something. Those became the entry points.

From there we mapped a deliberate sequence that follows the athlete's own logic rather than the brand's org chart: a pre-workout nutrition article leads to a workout strategy piece, which leads to an interactive race analyzer, which leads to the race finder. Each step is a small commitment. Nobody is asked to register on the page where they were asking about breakfast.

The agentic content system's scaffolding pass already proposed internal links for search reasons. We extended it to carry the funnel logic: every article now declares its funnel stage at intake, and the link proposals and the closing call to action are generated to match. That is journey orchestration applied to a content library.

• A stage-one article closes with the next article.
• A stage-three article closes with the tool.
• Only the final stage closes with registration.

The mismatch that had every page ending in a sign-up button was fixed at the pipeline level, not page by page.

Build The Tools As Something An Editor Can Paste

The race analyzer is the centerpiece. A reader enters their weekly schedule and their experience level and gets back the race formats and distances that fit, with a link into the race finder pre-filtered to match. The bike selector does the same for gear: answer a few questions about budget, course type, and experience and get a recommendation with the reasoning shown.

Both were generated by our in-house agentic system as self-contained HTML: markup, styles, and logic in one block, no external dependencies, no calls to a server, responsive by default because most of the audience would use them on a phone.

The client's editors pasted the block into the page builder the same way they paste an article. No component was built in the CMS, no developer ticket was raised, and the first version went live in days rather than a quarter. When the client wanted a change to the analyzer's logic, we regenerated the block and they pasted it again.

We considered building these properly as CMS components and rejected it for now, for the obvious reason that the platforms team had no capacity and the tools needed to exist this quarter. It is a trade-off. Pasted HTML is harder to maintain across many pages and does not benefit from the CMS's component library. It is also the reason the tools exist.

Give The Reader Something To Keep

For the mobile audience we added downloadable summary cards to the training and checklist articles: a single image with the plan's key numbers or the race-week checklist, sized for a phone screen and generated from the article's own content by the pipeline. The reader saves it, the brand stays on their device, and the article has a reason to exist beyond the one visit.

Replace The Photo Shoot With A Visual System

The images problem we solved by changing what an image was for. Instead of athlete photography, each tier-one article gets custom branded diagrams and illustrations: an anatomical illustration for a piece on running form, a fueling timeline for race-day nutrition, a training block diagram for a plan.

They are produced by the pipeline from the article's own structure, in the brand's palette and typography, with no apparel, no sponsor logos, and no rights question. They are also more useful than a photo of someone running, because they show the thing the article is explaining.

The effort is tiered, as with everything else in this program. Training plans and checklists get diagrams and a downloadable card. Community and mindset pieces get a single branded feature image and nothing else. Conductor's data on which pages carry intent is what decides which tier a page is in.

What Changed

The clearest signal is in read time and engagement. Across the refreshed set, the articles with embedded visuals and a downloadable summary card show the highest engagement and the longest read times of anything on the site.

• The 16-week training plan, which carries a training block diagram and a summary card, averages more than four and a half minutes of read time and drew 1,855 sessions at an 8.7 percent click-through rate in the reporting period.
• The gear-selection explainer that hosts the bike selector drew 1,007 sessions.
• In the latest reported week the refreshed group recorded 16,844 content views and 5,469 engaged sessions.

The funnel itself now exists, which it did not before. A reader can move from a nutrition question to a training question to a personalized race recommendation to a filtered race list without ever being asked to commit early, and every one of those steps is a page the brand owns. The client's marketing leadership has taken that structure into a broader conversation about nurture sequences across web, email, and the app, which is the right next conversation and one that was not possible when every page ended in the same button.

The visual system removed the images bottleneck entirely. No article in the program has waited on a rights approval since the diagrams replaced photography, and the client's content lead approves visuals in the same flag list as copy.

The honest edge. We cannot yet attribute registrations or app downloads to the funnel. The conversion layer, including persona-level personalization and testing, is being built by a separate workstream, and the tagging that would let us follow a reader from a nutrition article through the analyzer to a registration is on the roadmap, not in the data.

What we can say is that the engagement metrics moved in the direction a funnel should move them, and that the pages now have somewhere to send people. The registration number is the one that matters and we do not have it.

The pasted-HTML approach is also carrying technical debt on purpose. Two tools live in a handful of pages today. If that becomes ten tools in fifty pages, they should become CMS components, and the argument for that sprint will be much easier to make with this data than it would have been without it.

What You Can Take From This

Audit your calls to action by reader stage, not by page template. Pull your twenty highest-traffic informational pages and write down what each one asks the reader to do next.

If the answer is the same on all twenty, you do not have a funnel. You have a template. The fix is a funnel-stage field on every article and a rule that the closing CTA is generated from it, so the mismatch cannot recur one page at a time.

Treat interactive tools as content, not as features. A calculator, a selector, a readiness check: these are the highest-engagement pages a content program can produce, and the reason most teams do not have them is that they are waiting on a development queue.

A self-contained HTML block an editor can paste is not the elegant answer. It is the answer that exists this quarter. Build it that way, measure it, and use the measurement to justify the component later.

Let your analytics platform decide where the visual effort goes. Custom diagrams and downloadable cards are expensive relative to a stock image, and they earn their cost on pages where readers are deciding something. Conductor's intent data told us which pages those were. Without it we would have spread the effort evenly and diluted it.

And if photography is a rights problem, stop treating it as an image problem. A diagram of the thing the article explains is more useful than a photo of someone doing it, needs no approval, and looks like your brand rather than a stock library.

Related Reading

• Four Hours Per Article Is Not A Content Strategy
• What An SEO Platform Cannot Catch
• The CMS Last Mile For AI-Assisted Content

Map Your Reader Path With Us

If your content is earning traffic and your conversion numbers have not noticed, we would be glad to map your reader path with you and show you where a tool or a sequence would change it.

Want to see what an interactive tool looks like as pasted HTML on one of your own pages? Send us the article and we will build the prototype.