Planning a website structure: pages, navigation and connections
Planning a website structure: pages, navigation and connections
Valeria Gruzdeva
Founder of Web Gruzdeva
feeds:number
min read
5
min read
Website structure determines which pages exist, how they are grouped and how people reach the information they need. It is more than a list of menu items.
If the structure does not match customers' needs, visual design may only hide the problem. Plan the page map before design and content production.
What structure includes
Sections group related materials. Individual pages explain offers or answer questions. Navigation and internal links connect them.
URLs help organise the site too, but a clear address cannot replace a useful page. A section's name should match the purpose of its content.
For a business owner, the practical deliverable is a map explaining who each page is for, what it contains and which action it supports.
Where to start
Collect your actual services, products and customers' questions. Identify the main tasks separately: choose an option, compare terms, request an estimate, explore your experience or find contact details.
Research search queries, but do not automatically turn them into pages. Similar phrases often reflect the same task.
For example, questions about the price and scope of one service may belong on the same page. Services with different processes and audiences may need separate pages.
How to group pages
By offer
Group services or products around how customers choose. A company's internal departments do not always match that logic.
If visitors seek a solution to a specific problem, sections named after employees' job titles may get in their way.
By purpose
Commercial pages help visitors choose an offer. Informational pages explain a topic. Case studies demonstrate experience, while contact pages provide ways to get in touch.
Connect these materials, but avoid making every text a catalogue, company history and instruction manual at once.
By differences in content
A separate page makes sense when it covers a distinct offer or a sufficiently useful answer. If only a city name changes in otherwise identical copy, check whether the service and terms actually differ.
A service website example
An illustrative map for a small studio might look like this:
Home — a concise offer and routes to the main sections.
Services — an overview with links to individual services.
Service page — terms, process, examples and an enquiry action.
Case studies — completed projects with their briefs explained.
Blog — useful material to support a decision.
About — the working approach and supporting evidence.
Contact — real ways to get in touch.
This is an example, not a mandatory template. A project with one service and little content may combine some information on a single page.
Connecting the content
An article can lead to a service that addresses the issue it discusses. A service can link to a relevant case study. A case study can lead to the terms for similar work.
An internal link should explain the destination. “Read more” can work in a clear card, but a standalone paragraph benefits from a descriptive label.
Do not link every page to every other page. Too many unrelated routes make choosing harder and do not automatically improve the structure.
Menus and breadcrumbs
The main menu should reflect important journeys. It does not need to list every URL.
Breadcrumbs can show a page's position in the hierarchy. They are particularly useful on content-rich sites when visitors arrive directly from search.
Check access to nested sections on a smartphone. Navigation that works only on mouse hover does not solve the mobile task.
If the website already exists
List the current URLs and compare them with the new map. Mark which pages stay, merge or move to a new URL.
Plan redirects and link updates during a migration. Do not remove important URLs without understanding who visits them and where they come from.
Also check for pages without internal links. They may remain accessible directly while being poorly integrated into the site.
Testing the structure
Give someone a few tasks: find service terms, view an example and request a quote. Ask them to use the website without your guidance.
Record where they choose the wrong section or misunderstand a label. Fix the specific issue rather than merely moving a menu item.
Check that the destination page contains what visitors need. Good navigation is unhelpful if it leads to an empty promise.
Checklist
Every page has a purpose and an audience.
Related search queries are grouped by meaning.
Unnecessary near-duplicate content is avoided.
Section names make sense to customers.
Important pages are accessible through navigation.
Articles, services and case studies connect meaningfully.
URL changes are accounted for during migration.
Main journeys work on smartphones.
Frequently asked questions
Are more pages always better for search?
Not necessarily. You need useful, distinct content rather than a high number of URLs.
Can structure be planned before design?
Yes, and it is useful to do so. Check the logic first, then design the pages.
Getting started
Collect your offers and customers' questions. We can use them to plan the page map, section purposes and routes to an enquiry, making the website easier to populate and develop.