PagePotPagePotPagePot
  • Features
    • All features
    • Sitemap builder
    • Content planner
    • Diagram maker
    • AI assistant
    • Review and approval
    • Multilingual planning
    • Tree testing
    • SEO planning
  • Solutions
    • All solutions
    • Agencies
    • Marketing and digital teams
    • Education
    • Government
    • Website redesigns
  • Integrations
    • All integrations
    • AI agents (MCP)
    • Drupal
    • WordPress
    • API and webhooks
  • Pricing
  • Help Center
PagePot
  • Features+
    • All features
    • Sitemap builder
    • Content planner
    • Diagram maker
    • AI assistant
    • Review and approval
    • Multilingual planning
    • Tree testing
    • SEO planning
  • Solutions+
    • All solutions
    • Agencies
    • Marketing and digital teams
    • Education
    • Government
    • Website redesigns
  • Integrations+
    • All integrations
    • AI agents (MCP)
    • Drupal
    • WordPress
    • API and webhooks
  • Pricing
  • Help Center
Start free trialSign In

Plan your next website with PagePot

Sitemap, content, diagrams and client approval in one workspace.

Start free trial
14-day Pro trialNo credit card neededFree client reviewersSitemaps, content, assets and approvals in one placeFor new websites and established onesExport to PDF, Word, CSV and XMLImport pages into DrupalPlan every language on one structure
14-day Pro trialNo credit card neededFree client reviewersSitemaps, content, assets and approvals in one placeFor new websites and established onesExport to PDF, Word, CSV and XMLImport pages into DrupalPlan every language on one structure
PagePotPagePot

PagePot is a collaborative workspace for website content: sitemaps, page content, assets, feedback and approvals in one place.

Contact us

Features

  • All features
  • Sitemap builder
  • Content planner
  • Diagram maker
  • AI assistant
  • Review and approval
  • Multilingual planning
  • Tree testing
  • SEO planning

Solutions

  • All solutions
  • Agencies
  • Marketing and digital teams
  • Education
  • Government
  • Website redesigns

Integrations

  • All integrations
  • AI agents (MCP)
  • Drupal
  • WordPress
  • API and webhooks

Resources

  • Templates
  • Blog
  • Help
  • Changelog
  • FAQ
  • Compare

Company

  • About
  • Pricing
  • Security
  • Contact

© Copyright 2026 PagePot. All Rights Reserved.

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
Features
Solutions
Integrations
  1. Home
  2. Guides
  3. Pre-CMS Planning: Plan Your Website Before You Build It

Pre-CMS Planning: Plan Your Website Before You Build It

A practical guide to pre-CMS planning: why content-first website planning saves rework, what to plan before the build, who does what, and mistakes to avoid.

Pre-CMS planning is the work you do before anyone opens the content management system: agreeing the site structure, deciding what each type of page needs to hold, writing and approving the content, and settling SEO and languages. It is the heart of content-first website planning. When it is done well, the build becomes a matter of putting agreed decisions into software. When it is skipped, the CMS becomes the place where those decisions get made, slowly and expensively.

This guide covers why pre-CMS planning matters, what to plan, who should be involved, a process you can follow, and the mistakes that cause the most rework.

Why plan before the CMS?

A CMS is built to publish content, not to decide what the content should be. Once developers have set up content types, fields and navigation, every change to the plan costs build time. Moving a section, splitting a page type in two or adding a field for a price list all mean changes to code and configuration, not just to words.

Planning first fixes that order of work:

  • Structure is cheap to change on paper. Dragging a page to a new place in a sitemap takes seconds. Moving it in a built site can mean new templates, menus and redirects.
  • Content shapes the design, not the other way round. Designers who see real copy lengths, real images and real page counts design for what the site will hold. Lorem ipsum hides problems until launch week.
  • Developers get a clear specification. A list of page types with their fields, limits and example content is far easier to build from than a set of mock-ups.
  • Approvals happen at the right time. A client who signs off the sitemap and page copy before the build is much less likely to ask for a new section two weeks before launch.
  • Writers can start early. Content is usually the slowest part of a website project. Planning lets writing run alongside design instead of waiting for a finished CMS.

What to plan

Pre-CMS planning covers six areas. You don't need every one on a small site, but you should decide consciously which ones you are skipping.

1. The sitemap

The sitemap is the list of pages and how they relate: what sits under Home, what goes in the main navigation, which pages are utility pages (search, account, cart) and which live in the footer (privacy, terms, delivery). A visual sitemap makes this easy to review with people who don't read spreadsheets. See Visual sitemap vs XML sitemap for the difference between the planning sitemap and the one search engines read.

2. Templates and content models

A template (or content model) describes what a type of page contains. An "Article" might need a title, a summary, a hero image, body copy and an author. A "Store location" might need an address, opening hours, a map embed and a phone number.

For each template, decide:

  • The fields and their types (plain text, rich text, image, video, document, and so on).
  • Which fields are required before the page can be approved.
  • Limits: character counts, image sizes, number of items.
  • Instructions for writers, such as "One sentence, under 160 characters".
  • Structured data that isn't body copy, such as categories, tags or a publish date.

These decisions map closely to the content types a developer will build, which is why they belong in the plan.

3. The content itself

Write the actual copy and gather the actual images and files, page by page, in the fields the template defines. Track each page through a workflow (for example Draft, In review, Approved) with an owner and a due date, so you always know what is late.

4. SEO

Plan the slug and path of every page, its SEO title and meta description, focus keywords, and any pages that should not be indexed. Doing this during planning means URLs are agreed before they are built, and duplicate paths or missing descriptions are caught early.

5. Review and approval

Decide who approves what, and how. Many teams approve in two stages: the sitemap first, then page content. Record approvals against a specific version of the page, so everyone can see when an approved page has been edited again.

6. Languages

If the site will be multilingual, decide which languages, whether every page is translated, and who translates. Each language usually needs its own title, slug, content and SEO, and its own status so translators can be tracked separately.

Who is involved

RoleResponsibility in pre-CMS planning
Project manager or strategistOwns the sitemap, templates and workflow; assigns work; approves pages
Content writers and editorsWrite and revise copy in the agreed templates; send pages for review
SEO specialistSets slugs, titles, descriptions and keywords; checks for duplicate paths
DesignerReviews real content to design page layouts and components
DeveloperReviews templates and fields early to confirm they can be built as planned
Client or stakeholdersReview the sitemap and content; comment; give final approval
TranslatorsProduce and check each language version

On small projects one person may hold several of these roles. What matters is that each responsibility has a named owner.

A pre-CMS planning process

  1. Discovery. Collect goals, audiences, existing content and constraints. If there is an existing site, take an inventory of its pages. The website content migration guide covers this in detail.
  2. Draft the sitemap. Start with the main navigation, then add sub-pages, utility pages and footer pages. Keep it rough at first.
  3. Review the sitemap with stakeholders. Share it, collect comments, and agree the structure before writing starts.
  4. Define templates. Group pages by type and write down the fields each type needs. Ask a developer to check them.
  5. Assign and schedule content. Give every page a template, an owner and a due date.
  6. Write, review, revise. Writers fill in pages; reviewers comment or suggest edits; pages move through the workflow.
  7. Plan SEO and languages. Set slugs and metadata; start translations once the default language is stable.
  8. Approve. Get sign-off page by page, and record it.
  9. Hand off to the build. Give developers the sitemap, templates and approved content in a format they can use, such as a page inventory, a content document or structured files.

For a step-by-step list you can tick off, see the website planning checklist.

Common mistakes

  • Designing before the sitemap is agreed. Page designs built on a guessed structure get redesigned.
  • Planning in too many places. A sitemap in a slide deck, copy in a dozen documents and statuses in a spreadsheet drift apart within a week. Nobody knows which version is current.
  • Templates with no limits. If a hero heading has no character limit, someone will write three lines, and the design will break.
  • Writing into the CMS as the first draft. CMS editors are built for publishing. Reviewing, commenting and approving there is awkward, and half-finished content can end up live.
  • Leaving SEO until launch week. Late URL changes break internal links and complicate redirects.
  • Approval without a record. "The client said it was fine" is not an approval. Record who approved which version, and when.
  • Translating too early. Translating copy that is still changing doubles the rework. Wait until the default language is approved, or close to it.

How PagePot helps

PagePot is a pre-CMS planning workspace. You build the structure in a visual sitemap builder, define templates with required fields, limits and writer instructions, and write and track content in the content planner with statuses, assignees and due dates. Clients review through share links without an account, and approval records the exact revision that was signed off (see review and approval). SEO fields and languages live on each page, and the plan exports as a PDF or Word content document, a CSV page inventory or a developer handoff ZIP. Teams building on Drupal can import the plan with the Drupal integration.

FAQ

What is pre-CMS planning?

It is planning a website's structure, templates, content, SEO and approvals before building it in a content management system. The goal is to make decisions where they are cheap to change, then build from an agreed plan.

Is pre-CMS planning the same as content-first design?

They are closely related. Content-first design means designing around real content rather than placeholders. Pre-CMS planning is the process that produces that real content, along with the structure and templates it fits into.

Can't I just plan in spreadsheets and documents?

You can, and many teams do. The trouble is keeping the sitemap, copy, statuses and approvals in sync across separate files. A dedicated planning tool keeps them in one place, so there is one current version.

How long does pre-CMS planning take?

It depends on the size of the site and how quickly content is written and approved. Content is usually the slowest part. Starting it early, alongside design, often shortens the whole project even though planning adds a phase at the start.

When should developers get involved?

Early, when templates are being defined. A developer can confirm that each field can be built as planned and point out anything the CMS handles differently, before content is written into the wrong shape.