A website content plan is a written system for deciding what goes on every page, why it exists, and how you'll know it's working. The first action is simple: pick one page, write down its purpose in a single sentence, and attach one measurable goal to it. Everything else in this guide, from audits to editorial calendars, builds on that habit.
TL;DR:
- Pages in the "produce nothing" bucket should be redirected or removed to eliminate unnecessary clutter and improve site focus.
- Mapping content to specific funnel stages ensures each page addresses relevant buyer questions for better engagement and conversion.
- Setting measurable objectives like traffic, rankings, or conversions for each page guides targeted improvements and prioritization.
- Regular quarterly reviews and clear ownership prevent content from becoming outdated and ensure consistency in tone and claims.
- Budget allocation should be based on page type, prioritizing high-value funnel pages and avoiding spending on underperforming or irrelevant content.
Table of Contents
- What is a website content plan and where do you start?
- Content inventory and audit: what to measure and how to sort
- Map content to structure: sitemap and information architecture
- Decide content types and messaging hierarchy
- Write page briefs and templates: 'write for extraction' checklist
- Production workflow and editorial calendar: roles, approvals and handoffs
- Measure and maintain: KPIs, review cadence and unpublishing
- Jarvis & Co practises: templates, proofs and what to expect from an audit
- Content personalization strategies and dynamic content planning
- Governance policy including style guides and brand voice consistency
- Budgeting and resource allocation for content production
- Author perspective: common pitfalls and practical shortcuts
- How Jarvis & Co can help: services and next steps
- Sources
What is a website content plan and where do you start?
A website content plan sets the purpose, audience, and measurable goal for every page on a site, then tracks that content through production and review. Without it, teams write pages because someone thought they'd be "nice to have", not because a user needed them. That's how sites end up with twelve blog posts answering the same question and no page that actually closes a sale.
Start by writing a positioning statement of 40 to 60 words for your site or a key section. State who it's for, what problem it solves, and what makes your approach different. Then work backwards from your buyer's questions.
Map those questions to where they sit in the decision journey:
- Awareness stage: "What is X?" and "Why does this matter?" style questions, usually served by guides and explainers.
- Consideration stage: comparison and "how does this work" questions, served by feature pages and case studies.
- Decision stage: pricing, process, and "what happens next" questions, served by service pages and contact forms.
Attaching a buyer question to each funnel stage clarifies what a page actually needs to say, a point the Nielsen Norman Group's content strategy research backs up directly.
Once you know the stage, set a measurable objective per page:
- Traffic or ranking target (organic sessions, keyword position)
- Conversion or lead target (form fills, calls, downloads)
- Task completion (did the user find the answer without bouncing?)
Name a sign-off owner for each page before drafting starts. Someone has to be responsible for approving the claim it makes, or you'll be arguing about wording after it's already live.
Content inventory and audit: what to measure and how to sort
An inventory is a spreadsheet listing every URL on your site with the data needed to judge it. That single deliverable anchors every decision that follows, because it replaces guesswork with numbers.
Collect these columns for each page:
- URL and page title
- Organic traffic (last 12 months)
- Conversions or goal completions
- Last updated date
- Content owner
- Notes (accuracy issues, broken links, outdated claims)
Pull the traffic and conversion figures from analytics and Google Search Console. Then run a manual quality pass: does the page still say something true, does it match current pricing or services, does it read well on mobile? A content audit that catalogues traffic, conversions and quality gives you the evidence base for what to keep, rewrite, or bin during a migration.
Sort every page into one of three buckets:
- Pipeline — keep improving; it's driving traffic or conversions and has room to grow.
- Traffic only — it ranks and brings visitors but converts nobody; needs a stronger call to action, not a rewrite.
- Produce nothing — no traffic, no conversions, no strategic reason to exist. Redirect or remove it.
Finish with a gap analysis: list the buyer questions from your audience mapping that no existing page answers. Those gaps become your new-page brief list.
Map content to structure: sitemap and information architecture
Information architecture is the skeleton that holds your content plan together. Get it wrong and even excellent pages get buried where nobody finds them.
Three principles keep IA sane:
- Match user mental models, not your internal org chart. Visitors think in tasks ("book a survey", "get a quote"), not departments.
- Use progressive disclosure. Give the short answer first, then let users click deeper for detail. Don't cram everything onto one page.
- One job per page. If a page tries to explain, sell, and reassure all at once, it usually fails at all three.
Build a content map that links each URL to its funnel stage and the buyer question it answers. This becomes your master reference when you're deciding whether a new topic needs its own page or a section on an existing one.
Migration decisions follow directly from the audit buckets: pages in "produce nothing" get 301 redirected to a relevant survivor, near-duplicate pages get merged, and genuine gaps get commissioned as new pages. A migration checklist helps avoid the most common mistake here, losing rankings because redirects were mapped after launch instead of before.
Keep your sitemap labelling consistent. Use the same term for the same concept everywhere. If you call it "Case Studies" in the nav, don't call it "Client Stories" in the footer.
Decide content types and messaging hierarchy
Every page format has one job. Confuse the jobs and readers leave without doing anything.
- Guide or explainer: educate, answer a question, build trust. No hard sell.
- Service page: state what you do, for whom, and what happens next. Light on theory, heavy on process.
- Case study: prove the claim with a specific, named outcome.
- Pricing page: remove uncertainty. State ranges or a clear "get a quote" path.
- Blog post: capture a specific search query and funnel readers towards a relevant service or guide.
A strong content strategy names positioning, content types, and the job each one does before a single word gets written, which is exactly why the one-job-per-page rule matters more than most teams assume.
Write a top-level messaging statement of 40 to 60 words for each key page: the claim, who it's for, and the proof. Then back that claim with evidence suited to the page type, a metric for service pages, a client outcome for case studies, a genuine testimonial for anything trust-dependent.
Claim-first writing isn't just good manners to a skimming visitor. Content that leads with a clear, specific claim and follows with evidence is also more likely to get picked up and cited by AI answer engines, because structuring content for extraction makes the key fact easy to lift.
Write page briefs and templates: 'write for extraction' checklist
A page brief is a one-page document that tells the writer, designer, and developer exactly what the page must achieve before anyone opens a blank document.
Include these fields in every brief:
- Purpose (one sentence)
- Core claim (the single thing this page must prove)
- Audience and funnel stage
- Evidence to include (data, case study, testimonial)
- Primary and secondary calls to action
- SEO target (primary keyword, related terms, search intent)
Writing rules for the draft itself: answer the reader's question in the first sentence, follow with evidence, use descriptive headings rather than clever ones, and use concrete numbers wherever you have them. Building a page one section at a time, headline, intro, body, layout, assets, keeps the brief honest and stops scope creeping mid-draft.
For designers and developers, break the brief into modules: headline, supporting intro, proof block, call to action, and (where relevant) a short answer block. Document the SEO intent explicitly in the brief itself, not in a separate spreadsheet nobody checks.
Production workflow and editorial calendar: roles, approvals and handoffs
Nothing kills a content plan faster than unclear ownership. Assign a role matrix before drafting begins:
- Owner: accountable for the page's outcome
- Writer: drafts the copy against the brief
- Editor: checks accuracy, tone, and claim strength
- SEO lead: confirms keyword targets and internal links
- Designer/developer: builds the page against the module brief
Approval workflows work best with a fixed order: content approval, then SEO check, then design sign-off, then publish. Running these in parallel instead of sequence is the single biggest source of bottlenecks, since clear approval workflows and calendars reduce delays specifically by removing back-and-forth rework.
Your editorial calendar needs, at minimum: topic, owner, draft date, review date, publish date, and status. Weekly or fortnightly cadence works for most small teams. A content calendar built for small teams gives you a starting template rather than building one from scratch.
Use shared documents or a lightweight project tool with version history, so nobody overwrites someone else's edit the night before launch.
Measure and maintain: KPIs, review cadence and unpublishing
Match your KPI to the page type. A guide's success metric is organic traffic and time on page. A service page's metric is conversion rate. A case study's metric is assisted conversions further down the funnel.
Set a quarterly review cadence as a default, tightening to monthly for your highest-traffic or highest-converting pages. At each review, check traffic, conversions, and accuracy against a simple threshold: has performance dropped meaningfully, or has the information gone out of date?
Pro Tip: Set an automatic calendar reminder for every page's review date the moment it publishes. Content that isn't scheduled for review never gets reviewed.
Content strategy doesn't stop at publish. It's an ongoing cycle of planning, creation, maintenance and unpublishing, and pages sitting in maintenance need a genuine decision, not indefinite neglect.
Apply four decision rules at review:
- Update: facts or figures are stale but the core content still works.
- Rewrite: the topic still matters but the approach or structure has failed.
- Merge: two pages compete for the same query and split authority.
- Unpublish: no traffic, no conversions, no strategic reason to keep it live; redirect the URL.
Feed every outcome back into your roadmap so next quarter's priorities reflect what actually happened, not what you hoped would happen.
Jarvis & Co practises: templates, proofs and what to expect from an audit
Jarvisandco has run this exact process for SME clients across the UK for more than 15 years, from initial audit through to a published, measured site. The templates above aren't theoretical; they're the working documents used on client projects.
What you can lift directly for your own team:
- A page brief template covering purpose, claim, audience, evidence, and SEO targets.
- An inventory spreadsheet with the audit columns listed earlier, ready to populate from analytics.
- A quarterly review checklist matching KPIs to page type.
On audits handled this way, the biggest time saving usually comes from resolving the "produce nothing" bucket early, before a single new page gets drafted. That single step tends to remove more clutter than a full rewrite of the pages people actually visit. Case studies demonstrating specific client results are available on request through Jarvisandco's project archive.
Content personalization strategies and dynamic content planning
Personalisation means showing different content to different visitors based on what you already know about them, rather than serving the same static page to everyone. For most SME sites, that doesn't mean building a recommendation engine; it means smaller, achievable adjustments that fit an existing content plan.
The simplest form is behavioural: showing a returning visitor a different call to action than a first-time one. Someone who's already viewed your pricing page three times doesn't need another explainer, they need a way to book a call. Segment your highest-traffic pages by visitor type (new versus returning, organic versus referral) and write a second CTA variant for each.
Geographic personalisation works well for service businesses with multiple locations: a visitor from Solihull sees local case studies and contact details relevant to that branch, rather than a generic head-office number.
Dynamic content blocks, testimonials that rotate, case studies filtered by industry, pricing tables that adjust to selected options, let one page serve several audience segments without maintaining several near-duplicate pages. That keeps your inventory smaller and your governance simpler.
Build personalisation into the brief stage, not as an afterthought. If a page brief specifies "show manufacturing case studies to visitors arriving from manufacturing-related search terms", your developer knows to build that logic in from day one, rather than retrofitting it after launch when it's more expensive to implement.
Start small. One personalised element, tested and measured, beats five untested ones.
Governance policy including style guides and brand voice consistency
Governance is the set of written rules that decide who can publish what, and to what standard. Without it, five different writers produce five different tones, and visitors notice the inconsistency even if they can't name it.
A style guide should cover, at minimum: tone and voice (formal or conversational, second person or third), terminology (pick one term per concept and ban the synonyms), formatting conventions (how headings, numbers, and dates are written), and a list of claims that always need evidence attached before publishing.
Brand voice consistency matters more on a website than almost anywhere else, because visitors move between pages written months apart by different people. A strong content strategy documents governance clearly, naming exactly who approves what and how often content gets reviewed, precisely because inconsistent tone and contradictory claims are what erode trust fastest.
Assign a single governance owner, usually the content lead or marketing manager, whose job is to maintain the style guide and arbitrate disputes about tone or claims. Without a named owner, the style guide becomes a document nobody enforces.
Review governance rules alongside your quarterly content review, not separately. If three pages have drifted from the agreed tone since the last check, that's a governance failure worth fixing before it spreads to a fourth.
Budgeting and resource allocation for content production
Budget your content plan by page type, not by a flat annual figure. A service page needing professional photography and a developer's time costs far more to produce than a blog post drafted internally.
Break your budget into three categories: production (writing, design, photography, video), tools (calendar software, analytics, SEO platforms), and review (editor time, SEO audits, quarterly checks). Most small teams underbudget the third category entirely, then wonder why content quality slips after the first few months.
Resource allocation should follow your audit buckets. Pages in the "pipeline" bucket, the ones already driving results, deserve the bulk of your production budget for improvement. Pages in "produce nothing" get zero further spend beyond the cost of redirecting them.
If you're working with limited in-house capacity, prioritise ruthlessly: fund the pages tied to your highest-value funnel stage first (usually decision-stage service and pricing pages), then work backwards towards awareness content as budget allows.
For teams without in-house design, photography, or development resource, project-based agency support often costs less overall than hiring for each skill separately, particularly for a one-off content build or annual refresh rather than ongoing weekly output. Weigh that against a retainer model only if you genuinely need continuous production rather than periodic projects.
Whichever route you choose, put a number against each content type before the year starts. A content plan without a budget attached is a wish list, not a plan.
Author perspective: common pitfalls and practical shortcuts
The mistake I see most often isn't a bad page. It's teams skipping the audit because it feels slower than just writing new content. That's backwards. Without an inventory, you're rewriting pages that were already working and ignoring the ones actually losing you traffic.
Second mistake: briefs with no evidence field, so writers invent proof under deadline pressure. Third: nobody owns the quarterly review, so the whole plan quietly stops after launch.
If you're a small team, don't try to fix everything. Audit your top 10 pages by traffic, template the brief once, and fix your calls to action before touching the copy itself. Then run a 90-day audit followed by a 90-day sprint to close the biggest gaps. That's a realistic pace most teams can sustain.
— Luke
How Jarvis & Co can help: services and next steps
Running a full audit, sitemap rebuild, and brief-writing process alongside a full-time role is where most content plans stall, not from lack of knowledge, but lack of hours. That's the gap Jarvisandco fills: a team that's done this exact process repeatedly for SMEs, start-ups, and clinics across the UK, rather than a single hire juggling it between other duties.
A discovery call typically covers your current site's biggest gaps, a rough inventory read, and whether a full audit or a targeted rebuild makes more sense for your budget. From there, website design projects fold the content plan directly into the build, so structure, copy, and design get decided together rather than one dictating the other after the fact.
If your brand voice or visual identity needs work before the content plan makes sense, logo design support is available as a starting point. Book a discovery call through Jarvisandco to get a straight answer on what your site actually needs first.
Sources
For further reading on the frameworks used throughout this guide:
- Content Strategy 101 - NN/g
- Website content strategy: why your site says too much
- How to plan website content in one place with Milanote
Downloadable brief and audit templates matching the fields covered above are available from Jarvisandco on request.