Content engine: pillar, cluster, refresh, all on a weekly cadence.

What this is

The content engine is the throughput layer of the engagement — the part that produces the pillar / cluster pages and refreshes top-10 rankings on a weekly cadence. Without throughput, positioning is academic and schema is decorative. With throughput but no positioning, you get volume without compounding. We ship both.

The architecture is the Adalo Blueprint content pyramid: one canonical pillar page (your homepage), and eight layers of supporting pages threaded back to it. Platform pages, capability pages, use-case pages, audience pages, comparison pages, docs, blog, methodology. Every layer below the pillar contains the eight anchor components in the first 200 words and links back to the pillar with component-aware anchor text.

How we run it

Months 1–2: cluster-fit audit + refresh queue

In parallel with the positioning sprint and the technical SEO baseline, we audit your existing content against the cluster architecture. Every existing post lands in one of three buckets: refresh (earns investment), decommission (301 redirect to the canonical it was diluting), or orphan (no inbound links — flagged for the cadence’s first reset move).

The output is the cluster-fit map — written, signed off, executed in Month 2.

Months 2–5: weekly cadence

The cadence is fixed-shape because the same shape works. Each week:

• One net-new cluster page (rotating between platform, capability, use-case, audience, comparison layers — not random; following the query map’s priority list).
• One refresh of an existing top-10 ranking post (the agent watches Search Console for ranking decay and proposes the refresh; the curator approves; the post ships).
• One internal-link audit pass (the agent checks that new pages thread back to the pillar with component-aware anchor text and that orphans are progressively reconnected).

Quarterly: one pillar-level edit. The pillar gets updated as the engagement learns — it does not get rewritten.

Month 6: the cadence handover

By Month 6 you have a documented cadence, the refresh queue is calibrated to your specific ranking-decay signal, and the cluster architecture is mature enough that the agent fleet can run the throughput with curator oversight only. If you renew on the multi-year retainer, we keep running it. If you do not, the cadence ships in writing — including the briefs, the refresh signal definitions, and the agent-fleet integration — and your in-house team takes it over.

What you get

• Cluster-fit map — every existing post categorised against the cluster architecture; refresh / decommission / orphan decisions in writing.
• Pillar / cluster architecture — your homepage threaded as the canonical pillar, eight layers of supporting pages mapped to the query bank, internal-linking rules in writing.
• Weekly cadence — 1–2 net-new pages per week, monthly refresh, monthly internal-link audit. Calibrated to your specific ranking-decay signal by Month 6.
• Refresh queue — the algorithm that identifies which top-10 posts need an update next, ranked by ranking-decay rate × revenue impact. Documented; portable.
• Agent-fleet integration — the agents that produce drafts, schema bundles, and citation tests; documented so your team can keep running them post-engagement.

How this connects

The content engine cannot run without positioning (the brief input) and technical SEO (the schema graph cluster pages emit). It is the layer that makes the LLM discoverability play work — answer engines reward sites with clear pillar / cluster signals over sites with flat content libraries.

For the throughput side specifically — how the cadence ties to revenue — see the attribution dashboard.