Skip to content

Odduel

We put the odds in your favour

Insights

Website content plan before launch

How to build a website content plan before launch: what it contains, the steps, a copyable checklist, who writes and owns the content, and how often to review it.

A content planning wall with printed page outlines, photographs and sticky notes before a website launch

A website content plan is the document that lists every page and piece of content a new site needs, who writes, supplies and approves each one, and when it is due, so the site launches complete rather than full of placeholders. Make it before design starts: when content leads, layouts fit real words and pictures, deadlines hold and search rankings have something solid to stand on. This guide explains what the plan contains, a step-by-step process, a checklist you can copy, who should own it and how often to review it after launch.

Last updated: 19 November 2026.

Why does a website need a content plan before launch?

Content is the part of a website project most likely to run late. Designers and developers work to a schedule, while the copy, photographs, case studies and product data usually come from people who also have day jobs. Without a plan, the build finishes on time and then waits weeks for words.

A content plan fixes that in three ways:

  • It makes the work visible. Every page, every block of copy and every picture becomes a line with an owner and a date.
  • It lets design fit reality. Layouts drawn around real headlines and real photographs do not break when the content arrives.
  • It protects search performance. Pages planned around what people search for, and written to answer it, start ranking sooner than pages filled at the last minute.

At Odduel, a creative and technology agency in Barcelona and São Paulo, a content plan is one of the first deliverables of our website development service, agreed before the first wireframe.

In short: list every page from the sitemap, define the purpose and search intent of each, inventory what you have, assign who writes, supplies and approves each item, set dates that land before development needs them, and track it in one shared document until launch.

What does a website content plan contain?

A useful plan is a table with one row per page and columns for everything that page needs. The core columns are:

ColumnWhat it holdsExample
Page and addressName and planned URLServices, /services/branding/
PurposeWhat the page must achieveExplain the service, lead to an enquiry
Audience and intentWho arrives and what they wantMarketing leads comparing agencies
Primary keywordThe main search phrase, if anybranding agency
Content itemsCopy, pictures, video, downloads, dataHero text, three case studies, process steps
SourceExisting, to adapt, or newNew copy; existing photographs
Writer or supplierPerson responsible for draftingMarketing manager
ApproverPerson who signs it offManaging director
Due dateWhen the final version is neededTwo weeks before the template is built
StatusNot started, draft, review, approved, loadedDraft
The columns of a website content plan, with examples

Add columns for languages if the site is multilingual, for legal review if the sector requires it, and for accessibility notes such as alt text and captions.

What are the steps to build a website content plan?

Follow these steps in order; each one feeds the next.

  1. Confirm the goals and audiences. Write down what the site must achieve and for whom. Every page in the plan should serve at least one of these.
  2. Fix the sitemap. List every page and page type: home, services, products, case studies, about, contact, articles, legal pages, the thank-you page and the 404 page.
  3. Research search intent. For pages that should be found, note the main query, related questions and what currently ranks. This decides the depth and format of each page.
  4. Audit existing content. If you are replacing a site, list what can be kept, what needs rewriting and what should be dropped. Keep the content of pages that already rank well.
  5. Define each page’s content items. Break pages into their parts: headline, introduction, sections, proof, calls to action, pictures, downloads.
  6. Write a short brief for each page. Purpose, audience, key messages, keyword, length range, tone and the proof points it must include.
  7. Assign owners and approvers. One writer and one approver per page. More approvers means slower sign-off.
  8. Set dates backwards from the build. Content for each template is due before developers build it, with time for review.
  9. Plan pictures and video. Decide what will be photographed, filmed, licensed or drawn, and book shoots early.
  10. Track and load. Keep the plan as the single source of truth and update status weekly until every row reads “loaded”.

If you have not yet written the overall project brief, our guide to writing a website brief covers the inputs the content plan depends on.

The block editor of the Nothing To Eat website by Odduel, where approved copy and pictures from the content plan are loaded page by page

Who writes the website content?

There are three common models, and many projects mix them.

ModelStrengthsWatch out for
Your team writes everythingDeep knowledge of the business, no extra costTime pressure, uneven tone, late delivery
Agency or copywriter writes from interviewsConsistent voice, search-aware structure, on timeNeeds access to experts and fast approvals
Mixed: your experts draft, a writer editsAccuracy plus polishClear hand-offs and version control needed
Who writes the website content, three models compared

Whichever model you choose, the people who know the subject must check the facts, and one person should own the voice across the whole site. For technical or regulated topics, add a reviewer with the right expertise.

What belongs on a website content plan checklist?

Use this checklist to make sure nothing is missing before launch.

Strategy and structure

  • Goals and audiences written down and agreed.
  • Final sitemap with every page and page type.
  • Search intent and primary keyword noted for each page meant to rank.
  • Navigation labels chosen in the words visitors use.

Copy

  • Headline, introduction and sections for every page.
  • Calls to action that match each page’s purpose.
  • Page titles and meta descriptions for search results.
  • Microcopy: buttons, form labels, error messages, confirmation messages, empty states.
  • Legal pages: privacy notice, cookie policy, legal notice or terms, as your country requires.

Pictures, video and files

  • Photographs or illustrations for every template, at the right sizes.
  • Descriptive file names and alt text for every meaningful picture.
  • Captions and transcripts for video and audio.
  • Downloadable files checked, current and accessible.

Proof

  • Case studies, testimonials or reviews, used only with permission and never invented.
  • Logos of clients shown only where you have the right to show them.
  • Facts and figures with their sources.

Quality

  • Tone and spelling consistent with your style guide.
  • Headings in order, one main heading per page.
  • Accessibility checks on contrast, link text and reading level; our website accessibility guide explains what to look for.
  • Every link tested.

Content-first planning changes the design process. Instead of designing with placeholder text and then squeezing real copy into the boxes, designers work with draft headlines and real picture choices. Long German compound words, dense product data or a missing photograph show up while they are still easy to solve.

It also changes how the site performs in search. Google’s guidance on creating helpful, reliable, people-first content stresses content written for people, with clear expertise and purpose. A plan that defines each page’s audience, intent and proof points produces exactly that kind of page, rather than a page written to fill a layout.

Finally, a content plan makes testing more reliable. When every row is approved and loaded, the final quality check can focus on real issues; our website QA checklist picks up from there.

Who should own the content plan inside the company?

Name one content owner for the whole plan, usually from marketing or communications. Their job is not to write everything but to keep the plan current, chase late items, resolve conflicts between departments and make the final call on voice and structure.

Around them:

  • Subject experts supply knowledge and check facts for their areas.
  • Approvers sign off within agreed times, ideally one per page.
  • The agency or web team advises on structure, search and length, and loads the content.
  • Legal or compliance reviews pages that need it, on a fixed schedule.

Clear ownership is the difference between a plan that drives the project and a spreadsheet nobody opens.

How often should the content plan be reviewed?

Before launch, review it weekly in the project meeting: status per page, blocked items and decisions needed. After launch, the plan becomes a content inventory and keeps its value.

  • Monthly: check new pages, articles and updates against the plan; add rows for anything new.
  • Quarterly: review the pages that matter most to the business for accuracy, freshness and search performance.
  • Yearly: a full content audit, removing outdated pages, merging duplicates and planning what to add.

Assign each page a review date and an owner in the plan itself, so updates do not depend on memory.

What are the most common content planning mistakes?

  • Starting content after design. Layouts then dictate words, and the result reads like filler.
  • Too many approvers. Every extra reviewer adds days and dilutes the message.
  • No microcopy. Forms, errors and confirmations are written by developers at the last minute.
  • Forgetting legal pages. Privacy and cookie notices are needed from the first day the site collects data.
  • Copying the old site as it is. Migration is a chance to cut and improve, not just move.
  • Ignoring pictures. Photography shoots booked late are the most common cause of launch delays after copy.

Questions people ask

Who writes the website content?

Either your team, an agency or copywriter working from interviews, or a mix where your experts draft and a writer edits. The mixed model often works best: subject experts ensure accuracy and a writer ensures a consistent voice and search-aware structure. Whatever the model, one person should own the voice across the site.

What belongs on a website content plan?

Every page in the sitemap, each with its purpose, audience, search intent, content items such as copy, pictures and downloads, its source, writer, approver, due date and status. Add microcopy, page titles and descriptions, legal pages, alt text and captions. Multilingual sites need a column per language and a translation owner.

When should you start the website content plan?

Start it before design begins, straight after the sitemap is agreed. Content due dates should fall before developers build each template, with time for review. Starting early lets layouts fit real words and pictures, keeps the launch date realistic and gives photography and video shoots time to be booked.

Who should own the content plan inside the company?

One content owner, usually from marketing or communications, keeps the plan current, chases late items and decides on voice and structure. Subject experts check facts, one approver per page signs off, legal reviews where required, and the agency or web team advises on structure and search and loads the approved content.

How often should website content be reviewed after launch?

Check new content monthly against the plan, review the most important pages quarterly for accuracy and search performance, and run a full content audit once a year to remove outdated pages and merge duplicates. Give each page an owner and a review date so updates are scheduled rather than left to memory.

Open a spreadsheet, list every page in your sitemap and add the columns above; the gaps will show you where the work is. When you want a team to plan, write and build the site with you, see our website development service or tell us about your project.

More articles

More from our Insights.

Explore all insights

Get in touch

Let’s change your odds.

Odds do not change on their own. If you have something to build, launch or fix, tell us about it and we will show you how we would approach it.

    Need an NDA before you share details? Start a project

    Chat with us