Planning the pages a new website actually needs

A New Website Usually Gets Too Many Pages Too Early

One of the quickest ways for a new website project to become harder than it needs to be is to let the page list grow without enough discipline.

At the beginning, that often feels harmless. Someone says the site should probably have a page for this, another page for that, a separate page just in case, and perhaps a few extra sections because they might be useful later. None of those suggestions sound unreasonable on their own.

The problem is that every extra page creates more writing, more design decisions, more internal linking, more navigation pressure and more chances for the message to blur.

A stronger starting point is usually smaller and clearer.

The First Question Is Not “What Can We Add?”

Before deciding on pages, I want to understand what the site has to help a visitor do.

That usually means clarifying:

• what the business most wants enquiries about
• what a visitor needs to understand first
• which services need dedicated explanation
• where proof and reassurance should appear
• what content will need to be updated later

Once those points are clearer, the page structure becomes easier to justify.

A page should exist because it has a job, not because it feels like a normal thing for a website to contain.

Core Pages Need Clear Roles

Most new websites benefit from identifying the small set of core pages first.

That often includes:

• a homepage that explains the offer and points visitors in the right direction
• service pages that answer real buying questions
• an about page that builds context and trust
• a contact or enquiry route that feels easy to use

From there, supporting pages can be added carefully.

The key is that each core page should have a distinct role. If two pages are trying to do the same job, that usually creates confusion rather than clarity.

Supporting Pages Should Earn Their Place

After the core structure is defined, the next step is deciding which extra pages genuinely improve the site.

Some do.

For example, a pricing explainer, FAQ, case study section or process page can be very useful if it answers questions people already have. But those additions should be tied to real needs, not assumptions about what a site is supposed to include.

When a page is added without a strong reason, one of two things tends to happen. Either it becomes thin and repetitive, or it steals attention from a more important page that needed the focus.

Navigation Gets Harder When The Page List Gets Loose

People often notice page bloat first in the menu.

Navigation starts to feel crowded. Labels begin overlapping. Service distinctions become harder to understand. The homepage has to compensate by linking everywhere. Suddenly the site looks organised on paper but feels uncertain when someone tries to use it.

That is why page planning and navigation planning belong together.

If the menu cannot support the structure cleanly, the structure probably needs more editing before design work begins.

New Websites Need Room For Content Decisions Too

A page list is not just a technical sitemap. It is also a content decision.

Every page on a new site needs:

• a clear purpose
• a main question it answers
• a reason to exist separately
• enough substance to justify its place

If those points are weak, the page is probably premature.

This matters because a new website often looks more polished than it really is during the early stages. Wireframes can make a long page list seem settled even when the content logic is still uncertain. It is better to challenge that early than to design around weak assumptions.

Fewer Better Pages Usually Create A Stronger Launch

There is a temptation to believe that a fuller site feels more complete.

In practice, a new website usually launches more convincingly when the essential pages are clearer, more useful and better written. A tighter structure also makes future improvements easier because the site has room to grow deliberately rather than being overloaded from day one.

That tends to help with:

• easier page writing
• cleaner design decisions
• stronger internal links
• better search foundations
• simpler maintenance after launch

A Good Page List Makes The Whole Project Calmer

When the pages a website actually needs are agreed early, the whole project tends to settle down.

Design becomes more purposeful. Writing gets easier. The build feels less like guesswork. Conversations about scope become clearer because the team is working from a structure that already makes sense.

That is why I treat page planning as one of the most valuable parts of a new website project.

It is not just a preparation task. It is one of the decisions that shapes whether the finished site feels focused or fragmented.