Once we understand the business, the audience, and the content, I can plan the structure of the website.
This usually begins with a sitemap that shows which pages are needed and how they fit together.
We’ll look at the main navigation, the relationships between different services, and the journey someone might take from arriving on the website to making an enquiry.
The structure should make sense to the people using the site, not just the people who built it.
Visitors shouldn’t have to dig through endless menus, decode clever page names, or click five times to find a telephone number. They should be able to understand what you do, find the information they need, and know what their next step is.
SEO is considered during this stage too.
A clear site structure helps search engines understand your business, services, topics, and locations. Planning this properly from the beginning gives us much stronger foundations than trying to force SEO into the website once everything else is finished.
We’ll also decide what functionality the website genuinely needs. This may include contact forms, appointment booking, payments, email sign-up forms, a blog, or connections with other systems you already use.
This is also where I may question some of your ideas.
That isn’t me being difficult — it’s because features should be included for a reason.
A huge slider, elaborate animation, or a collection of plugins may look impressive in a demonstration, but it can also slow the website down, distract visitors, and create more things to maintain.
Just because something can be added doesn’t mean it will help your website do its job.