Website Planning Mind Map: free template for site structure

A website planning mind map template: audience, pages, navigation, content, features, SEO, analytics and integrations. Agree the shape of a site before design begins.

A website planning mind map lays out who the site is for, which pages it needs and what each must do, so the structure is agreed before design or development starts.

Website Planning Mind Map: free template for site structure

The interactive MindMap canvas for this explanation — every lane, row and arrow above is a real QueryChart diagram you can open and edit.

How to read this mindmap

  • Begin with “Audience and goals”, since it drives every other branch, then read “Pages and structure” and “Navigation” as the structure. “Content” and “Features” fill the structure, and “SEO and speed”, “Analytics” and “Tools and services” cover how it is found, measured and run.
  • Dashed arrows connect branches that depend on each other. An action in “Visitor actions” needs a page in “Offer pages”, and the questions behind “Main term” feed the key messages in “Key messages”.

Audience and goals

“Audience and goals” comes before any page. “Visitor groups” lists who will visit and what each group wants, “Business goals” says what the business needs from them, and “Visitor actions” turns that into the actions you want visitors to take.

Write “Visitor actions” as verbs: request a quote, read a guide, book a demo. Pages that do not support one of them are candidates for removal.

Pages and structure

“Pages and structure” is the sitemap. “Core pages” are the pages every visitor expects, “Offer pages” are the pages that carry your offer, “Support and legal” are supporting pages such as legal and help, and “Later phase” is anything planned for later.

Check “Offer pages” against “Visitor actions”. Each key action needs a page that makes it, and a page nobody would link to is a sign it may not be needed.

Navigation

“Navigation” decides how people move between the pages in “Pages and structure”. “Main menu” is the main menu, “Footer and in-page links” covers links in the footer and inside pages, and “Search and filters” is how visitors search or filter when the site is large.

Keep “Main menu” to a handful of items, labelled in the words your visitors use rather than internal names.

Content

“Content” covers the words and media. “Key messages” is the key message for each page, “Writers and deadlines” lists who writes what and by when, and “Images and media” covers images, video and documents.

Content is the usual cause of late launches. Assign owners in “Writers and deadlines” now, so you are not waiting for copy on launch day.

Features

“Features” lists what the site has to do beyond showing pages. “Forms and sign-ups” are forms and sign-ups, “Shop or booking” is a shop or booking function if you need one, and “Accounts and logins” covers accounts and logins.

Compare each feature to “Visitor actions”. A feature without an action it supports tends to add cost and maintenance without helping anyone.

SEO and speed

“SEO and speed” makes the site findable and fast. “Keywords per page” maps each page to the search terms it should answer, “Titles and URLs” covers titles, descriptions and URLs, “Speed and mobile” is performance and mobile use, and “Redirects” is what happens to old addresses.

Start “Keywords per page” from the questions in “Visitor groups”. Redirects under “Redirects” matter on a redesign, since changing an address without one can lose existing traffic.

Analytics

“Analytics” decides how you will know if the site works. “Key metrics” lists the numbers worth tracking, “Goal tracking” says how each visitor action will be counted, and “Consent and privacy” notes how the visitor's consent and privacy are handled.

Define “Key metrics” from “Visitor actions”. Counting visits is easy, but whether people finished the action you wanted is the number that matters.

Tools and services

“Tools and services” lists the outside things the site depends on. “Hosting and domain” is where it is hosted and who manages the domain, “Content system” is the tool that holds the content, and “Third-party services” is the third-party services the site connects to, such as payments or newsletters.

Write the owner of each next to “Hosting and domain”. Expired domains and lost logins are avoidable launch-week problems.

How the branches connect

The audience branch sets the bar for the rest. Every page in “Pages and structure”, every feature in “Features” and every metric in “Analytics” should trace back to an action in “Visitor actions”.

“Content” and “SEO and speed” overlap more than they appear to. The search terms you choose under “Keywords per page” should shape the headings and wording under “Key messages”, so plan them together rather than adding keywords afterwards.

Where a mind map stops and other charts start

The mind map agrees what the site contains. For how a visitor moves through it, such as a checkout or a sign-up, draw a flowchart with the decisions and error paths. A launch plan with deadlines and dependencies is easier to track in a Gantt chart.

If several teams contribute, a swimlane diagram shows who passes work to whom, from copy to design to development. Keep this map as the overview all of them can refer to.

Key relationships and takeaways

  • Visitor actions decide which pages exist, not the other way round.
  • Each page in the sitemap needs a message, an owner and a search purpose.
  • Navigation labels should use the visitor's words, not internal names.
  • A feature without a supporting action adds cost and nothing else.
  • Measures are defined before launch, because it is hard to reconstruct them afterwards.

When to use this visual

  • Briefing a designer or agency with a shared picture of pages, content and features.
  • Planning a redesign by comparing the current sitemap with the one you want, including redirects.
  • Scoping a small business site so that what is in the first release and what waits is explicit.

How it works

  1. Define the visitors and actions

    Rename “New website”, list the audiences under “Visitor groups”, and write the one action you want from each under “Visitor actions”.

  2. Build the sitemap

    Add every page under “Pages and structure”, then check that each key action has a page and each page has a reason to exist. Sketch the menu in “Main menu”.

  3. Assign and share

    Name owners for content in “Writers and deadlines” and for services in “Tools and services”, set the metrics in “Key metrics”, then share the map for comments before design starts.

Frequently asked questions

What should I plan first for a new website?

Start with the audience and what you want them to do, not the design. Once the actions are clear, the pages, menu and content follow from them. This template begins with that branch for the reason that every later decision depends on it.

Can I use the mind map as a sitemap?

Yes, the pages branch works as a simple sitemap, with groups of pages and the later phase marked separately. For a very large site, keep the top levels here and draw the deeper structure as an org-tree style hierarchy or a separate map.

Do I need to plan SEO before the site is built?

It is easier to do it early. Search terms influence page structure, headings and URLs, and existing addresses need redirects if you are redesigning. Mapping keywords per page now avoids rewriting pages and breaking links after launch.

How do I get feedback from clients or colleagues?

Share the chart and ask people to comment on specific nodes, such as a page they think is missing or a menu label they would not use. Version history shows what changed between rounds, which helps when sign-off is needed.

Plan your site on this mind map

Open this map as your own editable canvas, name the site and start with who it is for.

Plan your site on this mind map

More in Mindmaps