It’s tempting to jump straight into design. Moodboards, colour palettes, homepage concepts – the fun stuff.
But in most website projects, the fastest way to end up with a site that looks good and underperforms is to design first and work out the structure later. When structure comes last, you usually end up with messy navigation, unclear page priorities, and important content squeezed in wherever there’s space.
At Media Village, we plan website structure before design because structure determines everything that follows: user journeys, content clarity, SEO visibility, and how confidently a visitor takes the next step.
This approach underpins how we deliver our website design and development services – ensuring every site is structured to perform before visual design decisions are made.
🔑 Key Takeaways
- Website structure should be planned before visual design begins
- Clear structure improves usability, SEO visibility, and conversion flow
- Sitemaps and page hierarchy shape how users and search engines navigate the site
- Planning content early prevents delays and design compromises later
- Strong structure makes design decisions clearer, faster, and more effective
🧭 Jump to:
Why structure comes before design
Website structure is basically the “blueprint” of your site – what pages exist, how they connect, what gets prioritised, and how a visitor moves from curiosity to action.
If that blueprint is weak, design can only do so much. You might end up with:
- Visitors who can’t quickly find what they need.
- Pages trying to do too many jobs at once.
- Important services buried in navigation.
- Content written to fit the layout, rather than the user journey.
- SEO being treated as a bolt-on later (usually meaning compromises).
When structure is planned properly up front, design becomes the final layer – not the thing holding the whole project together.
Step 1: Define goals and user intent
We start with the simplest question:
What should this website make easier for the business?
That might be generating enquiries, booking consultations, selling products, reducing admin time, or building credibility in a competitive market. Once the goal is clear, the structure can support it.
We also consider the kinds of users arriving on the site and what they’re trying to do. For example:
- Someone comparing providers may need proof, clarity, and a way to ask questions.
- Someone ready to buy may need reassurance, speed, and a clear call-to-action.
- Someone arriving from Google often needs a specific page that matches their query.
This is where UI/UX design starts long before any visuals – because structure is about decision-making, not decoration.
Step 2: Build a sitemap that makes sense
A sitemap isn’t just a list of pages. It’s a prioritisation exercise.
Most businesses don’t need dozens of pages. They need the right pages, organised in a way that matches how customers think and search.
Typically, we’ll separate pages into clear groups such as:
- Core services (the pages most likely to drive enquiries or sales)
- Proof (projects, case studies, testimonials)
- About and trust (team, process, credentials)
- Support content (blogs, guides, FAQs)
- Contact / conversion pages (forms, calls, booking)
This is also where we avoid one of the most common issues we see when taking over existing sites: everything is thrown under one “Services” page, and Google has no clear signal about what the business actually offers.
Step 3: Map journeys and decision paths
Even simple websites have multiple user journeys. People don’t all land on the homepage first, and they don’t all decide in the same way.
We plan for common paths such as:
- Search → service page → proof → enquiry
- Homepage → services → project → enquiry
- Blog → relevant service → enquiry
- Referral → proof → contact
This is why we often build landing pages as part of a wider structure – especially for campaigns and lead generation. Our landing page design work is built around clarity and intent, not just visuals.
Step 4: Plan content before visuals
Structure decisions don’t just determine what pages exist – they determine what content needs writing, what proof needs gathering, and what the site has to communicate clearly.
Before design starts, we’ll typically outline:
- What each page needs to achieve.
- The questions the page must answer.
- The proof needed to build trust.
- The next action the visitor should take.
This is also where projects can speed up dramatically or slow down. If content and assets are unclear, design stalls. If content is planned early, the build moves smoothly.
If you’re preparing for a new build, these guides can help you get your ducks in a row:
Step 5: Wireframe key pages
Wireframes are a structure tool. They let you plan hierarchy and flow without getting distracted by fonts, colours, or visuals.
Wireframes help answer questions like:
- What does the user need to see first to understand the offer?
- Where does proof belong so it supports the decision at the right moment?
- How do we avoid burying the CTA?
- How do we keep pages skimmable without becoming thin or vague?
If you’re unfamiliar with wireframes, this is a useful primer: What Is a Wireframe in Web Design?
Step 6: Build in SEO from the start
SEO works best when it’s part of the structure – not something added after the site is built.
Early structure planning gives you control over:
- What pages should exist (and what each one should target)
- What content belongs where (instead of everything being forced onto one page)
- Internal linking (so Google can understand which pages matter most)
- Navigation clarity (helpful for users and search engines)
This is also why SEO is often included as part of a build, then carried forward as an ongoing strategy. If you want the site to grow after launch, the best results come when design, build, and SEO are aligned from day one.
Step 7: Design becomes easier (and better)
Once structure, content, and page goals are clear, design becomes far more effective because it has something solid to support.
Instead of “designing a homepage”, you’re designing a page that:
- Explains the offer clearly in the first few seconds.
- Routes visitors to the right service or next step.
- Builds trust with proof in the right places.
- Makes enquiry or purchase feel like the natural outcome.
That’s what people usually mean when they say a website “feels professional”. It’s not just aesthetics – it’s clarity.
Common website structure mistakes we see
When businesses come to us after a disappointing website build, the issues are often structural rather than visual.
- Navigation that reflects internal departments instead of how customers search.
- Everything forced onto one “Services” page, with no dedicated service pages.
- Homepage doing too much, while service pages feel thin or generic.
- No proof near decision points (case studies and testimonials buried).
- SEO added late, meaning compromises on page structure and content.
If this sounds familiar, you might find this helpful: Why Your Website Isn’t Working
A practical checklist before design begins
Before any layouts are designed or visuals explored, these are the structural decisions that need to be clear. Skipping them often leads to revisions, delays, and a site that looks polished but struggles to support real user behaviour or search visibility.
- Do we know the site’s primary goal (enquiries, sales, bookings, credibility)?
- Do we know the top 3–5 pages the site needs to get right?
- Do we have dedicated pages for the key services we want to be found for?
- Have we identified what proof needs collecting (projects, testimonials, results)?
- Do we know what content is needed for each page?
- Are we planning internal links so important pages are reinforced?
- Have we planned for post-launch growth (blogs, new pages, SEO)?
FAQs
These are the questions we’re most often asked by clients before a website project begins – especially when structure, SEO, and long-term performance are part of the brief.
Do you always need a sitemap before design?
For most projects, yes. Even if it changes slightly during build, having a clear structure early prevents the site becoming a patchwork of pages added “as we go”.
Isn’t structure the same as UX?
They overlap. Structure is the foundation of UX because it determines how easy it is for someone to find what they need and take the next step.
Can SEO be done after a website goes live?
It can – but it’s often more effective (and cheaper) when key pages, page hierarchy, and internal linking are planned early. Retrofitting SEO later can mean rewriting pages or rebuilding structure.
What usually slows website builds down?
The biggest cause is unclear content and missing assets. When copy, imagery, and page priorities aren’t planned early, decisions get pushed into the build stage and timelines extend.
Next step
If you’re planning a new website and want it built around clarity, performance, and long-term growth, our website design and development team can help you define the right structure before design begins.
👉 Speak to our team about your project: Start your project.
Written by Austin
Head of UI & UX and Web Design at Media Village
Austin leads the UI, UX and web design side of projects at Media Village. He works closely on website structure, user experience, and front-end design decisions that influence how a site feels, functions, and performs commercially. His input helps ensure new websites are not only visually strong, but properly aligned with the goals, complexity, and growth plans behind each project.
