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. Website Planning Checklist: From Discovery to Launch

Website Planning Checklist: From Discovery to Launch

A website planning checklist for every phase: discovery, structure, content, SEO, review, build handoff and launch. Use it to plan a new site or a redesign.

This website planning checklist takes you from the first conversation about a new site to the day it goes live. It is split into seven phases: discovery, structure, content, SEO, review, build handoff and launch. Each phase ends with a clear output, so you know when it is done and what the next phase starts from.

Use it as it is, or copy it and cut the items that don't apply. A five-page brochure site needs less than a multilingual store with hundreds of products. The order matters more than the length: most expensive website problems come from doing a later phase before an earlier one is finished.

If you are new to planning a site before building it, read pre-CMS planning first for the reasoning behind this order.

Phase 1: Discovery

The aim of discovery is to agree what the site is for and what you are starting with.

  • Write down the site's goals in one or two sentences each (for example "Take grooming bookings online").
  • List the main audiences and what each needs to do on the site.
  • Name the decision-makers and the person who gives final approval.
  • Agree the launch date and any fixed deadlines (a campaign, a product release, a contract end).
  • Confirm the CMS or platform, or the criteria for choosing one.
  • List the languages the site needs at launch, and any planned later.
  • If there is an existing site, take an inventory of its pages (import its XML sitemap or crawl it). See the website content migration guide.
  • Gather existing material: brand guidelines, copy decks, product data, images, documents.
  • Note integrations the site depends on (booking, payments, search, forms, a CRM).
  • List competitors or reference sites, and what you like or dislike about each.

Output: a short brief everyone has agreed, plus an inventory of existing content.

Phase 2: Structure

This is where you design the sitemap and the page types.

  • Draft the main navigation: the top-level sections under Home.
  • Add sub-pages to each section.
  • Separate utility pages (search, account, cart, log in) from main pages.
  • List footer pages (privacy policy, terms, delivery and returns, accessibility).
  • Mark pages that are just groupings, and links that point to other sites.
  • Check depth: can visitors reach important pages within two or three clicks?
  • Check naming: are labels clear to visitors, not just to the team?
  • Give every page a page type (for example "Product listing", "Article", "Store location").
  • Map the key user journeys (such as browse to checkout, or search to booking) as diagrams.
  • Share the sitemap with stakeholders and collect comments.
  • Get sign-off on the structure before content writing starts.

Output: an approved visual sitemap and a list of page types. See Visual sitemap vs XML sitemap if you need to explain the difference to a client.

Phase 3: Content

Content is usually the longest phase. Plan it like a project, with owners and dates.

Templates

  • Define a template for each page type.
  • For each template, list the fields: plain text, rich text, images, video, documents, forms, FAQs, cards.
  • Mark which fields are required before a page can be approved.
  • Set limits: character or word counts, image sizes, number of items.
  • Add writer instructions to fields that need them.
  • Define metadata that isn't body copy: categories, tags, dates, flags such as "Show on home page".
  • Ask a developer to review the templates.

Writing

  • Assign a template to every page.
  • Assign an owner and a due date to every page.
  • Agree a workflow, for example Draft, In progress, In review, Changes requested, Approved, Complete.
  • Agree tone of voice and style rules (spelling, capitalisation, how to write dates and prices).
  • Write copy directly into the template fields, not into separate documents.
  • Gather and upload images, documents and video, with alt text.
  • Check internal links point to pages that exist in the sitemap.
  • Track overdue pages every week.

Languages

  • Decide whether every page is translated, or only some.
  • Wait until default-language content is stable before translating.
  • Assign translators per language, with their own due dates.
  • Plan language-specific slugs (for example /es/tienda/perros).

Output: every page written, with its media, in the right template, and moving through the workflow.

Phase 4: SEO

  • Confirm the URL pattern and set a slug for every page.
  • Check for duplicate paths.
  • Write an SEO title and meta description for every indexable page.
  • Keep titles and descriptions within typical display lengths.
  • Set focus keywords for important pages.
  • Mark pages that should not be indexed (thank-you pages, internal search results).
  • Set canonical URLs where two pages have similar content.
  • Add social preview images for pages likely to be shared.
  • Plan structured data (JSON-LD) where it applies: organisation, products, FAQs, articles.
  • For multilingual sites, plan hreflang links between language versions.
  • If you are replacing a site, map every old URL to its new URL for redirects.

Output: every page has a planned path and search metadata, and old URLs have a destination.

Phase 5: Review and approval

  • Decide who reviews each page and who approves it.
  • Share the plan with clients or stakeholders in a way they can open without training.
  • Collect feedback as comments on the page it concerns, not in email threads.
  • Use tracked changes or suggestions for edits from reviewers, so writers can accept or reject them.
  • Resolve every comment thread before approval.
  • Check required fields are filled in before a page is approved.
  • Record who approved each page and which version they approved.
  • Re-review any approved page that is edited afterwards.
  • Get final sign-off on the whole plan.

Output: every page approved, with a record of who approved which version.

Phase 6: Build handoff

  • Export the sitemap as a PDF or image for the design and development team.
  • Export a page inventory (CSV) with templates, statuses and metadata.
  • Export the content in a format developers can import or copy from (HTML, JSON or a content document).
  • Hand over templates as a field specification.
  • Hand over the list of old-to-new URL redirects.
  • Hand over media with file names and alt text.
  • Agree how late content changes will be handled once the build starts.
  • Walk the development team through the plan and answer questions.

Output: the build team has everything it needs, and a single source for any changes.

Phase 7: Launch

  • Check every page in the sitemap exists on the built site.
  • Check every page has its approved content, not placeholder text.
  • Check navigation, utility and footer menus match the sitemap.
  • Check SEO titles, descriptions, canonicals and robots settings on the live pages.
  • Test forms, search, bookings and other integrations.
  • Test redirects from old URLs.
  • Generate and submit the XML sitemap to search engines.
  • Check each language version and the language switcher.
  • Check accessibility basics: headings, alt text, contrast, keyboard navigation.
  • Agree who owns the site and its content after launch.

Output: a live site that matches the approved plan.

How PagePot helps

PagePot covers phases 1 to 6 in one workspace. You can start a project by importing an existing site's XML sitemap or crawling it, or let the AI website planner draft a sitemap from a brief. The sitemap builder handles main, utility and footer pages, and the diagram maker maps user journeys. Templates, statuses, assignees and due dates live in the content planner, SEO fields in SEO planning, and client review in review and approval. Exports include a visual sitemap PDF or PNG, a CSV inventory, a search-engine sitemap XML and a content handoff ZIP for developers.

FAQ

What should a website planning checklist include?

At minimum: goals and audiences, a sitemap, page templates, content with owners and dates, SEO metadata, an approval step, and a handoff to the build. Add languages, migration and redirects if they apply.

What is the first step in planning a website?

Agree what the site is for and who it is for. Then take stock of what you already have. Structure and content decisions are much easier once goals and existing content are written down.

Should the sitemap be approved before content is written?

Yes. Writing content for a structure that later changes wastes effort. A quick sitemap review with stakeholders before writing starts is one of the cheapest ways to avoid rework.

How long does it take to plan a website?

A small site can be planned in days. A large redesign with many stakeholders can take weeks or months, mostly spent on content and approvals. Assigning owners and due dates to every page is the best way to keep it moving.

Who should own the website plan?

One person, usually a project manager or content strategist, should own the plan and make sure each phase finishes. Others contribute, but a single owner stops the plan splitting into several versions.