Before You Design the Website, Decide What the Website Needs to Be

There is a stage in almost every website project where everyone wants to talk about design.

What should the homepage look like? Which colors should we use? Should the hero section have a video? Where should the buttons go? Should the menu be transparent or solid?

Those are real design questions, but they are not always the first questions that need answers.

Before deciding how the website should look, it helps to decide what the website actually needs to contain.

For a service business, that might mean figuring out which services need their own pages, which locations matter, what belongs in the main navigation, what information customers need before contacting the business, and which pages deserve the most attention.

These decisions may sound like planning work rather than design work.

They are both.

A Website Is Easier to Design When You Know Its Parts

Think about building a house.

You would not normally choose the color of every room before deciding how many rooms the house needs.

Website projects work in a similar way.

The structure comes first. The visual design then gives that structure a useful and attractive form.

A sitemap is one of the simplest ways to make the structure visible. Nielsen Norman Group describes a sitemap as a visual representation of a website's organization and hierarchy and explains that it is commonly used as a planning document.

You do not need anything complicated.

Even a simple list can help:

Home → Services → Locations → About → Contact

Then you can ask what belongs underneath each section.

That small exercise can prevent a surprising amount of confusion later.

Start With What Customers Actually Need to Find

A website structure should not simply copy the way the business is organized internally.

Your company might have separate departments, teams, packages, territories, and internal processes.
Your customers may not care about any of those distinctions.

They usually want answers.

A homeowner might want to know whether you repair a specific problem. Someone looking for a consultant may want to understand the service before booking a call. A customer searching for a local provider may want to know whether you serve their area.

The website structure should help those people find the information that matters to them.

Research from Nielsen Norman Group has long highlighted the importance of organizing websites around how users look for information rather than simply reflecting internal organizational structures.

That is why the first planning question should be less about design and more about findability.

What will someone come here looking for?

Decide Which Services Deserve Their Own Pages

This is one of the most useful decisions to make early.

Suppose a company offers:

• Air conditioning repair
• Air conditioning installation
• Heating repair
• Heating installation
• Maintenance

Should each service have a separate page?

Maybe.

But that decision should come from the actual business, customer needs, content, and search intent rather than from a desire to make the website look bigger.

If two services are genuinely different and customers need different information to understand them, separate pages may make sense. If two pages would contain almost identical information, combining them may produce a clearer experience.

Making that decision early helps in several ways.

You know how many pages need to be designed. You know how many layouts may be required. You know what the navigation needs to accommodate. You also have a clearer idea of how much content needs to be prepared.

That is much easier than discovering all of this halfway through the design process.

Your Navigation Is Part of the Structure

Navigation often gets designed as a visual element.

But before you decide how the menu looks, decide what the menu needs to contain.

If the main navigation changes every time another page is added, the design process becomes a moving target.

A better approach is to establish the main categories first.

For example:

Services | Areas We Serve | About | Resources | Contact

Now the designer can work with a defined framework.

The visual treatment can still change. The menu can become a dropdown, mega menu, mobile drawer, or another appropriate pattern. But the underlying structure is already understood.

Google recommends creating a logical site structure and linking important pages from other relevant pages. Its documentation also explains that Google's systems analyze a site's link structure when generating sitelinks.

So the menu is not just decoration.

It is part of how the website communicates its organization.

Content Should Be Considered Before Layout

One of the easiest ways to create design rework is to design around content that does not actually exist.

Imagine a designer creates a service page with a small introductory paragraph because that is what the project brief originally suggested.

Later, the business provides:

• A detailed service explanation
• Five common questions
• A step-by-step process
• Customer reviews
• Certifications
• Project photos
• A service area explanation

Now the page needs much more room.

The designer may have to redesign sections that were already approved.

This does not mean every word needs to be finished before design starts.

It means the designer should know what kind of content the page needs.

A simple content outline can be enough to answer that question.

For example:

Service page

Introduction → Problem → Service explanation → Process → Trust → FAQ → Contact

The actual words can change later.

The structure gives the design somewhere sensible to put them.

Early Planning Helps You Avoid Designing the Same Thing Twice

Imagine you are designing eight service pages.

If you do not identify the common structure early, you might design each page separately.

That can lead to eight slightly different layouts, different spacing, different button positions, and different ways of presenting similar information.

Later, someone asks why the service pages do not feel consistent.

Now you have to bring them back together.

If you identify the shared pattern first, you can create a reusable page structure and customize the content for each service.

That usually makes both design and development easier.

The important distinction is that reusable does not mean identical.

A roofing service page and a consulting service page may need different content and different visual emphasis. But if they serve the same basic purpose, they can still share a sensible underlying system.

Think About Mobile Before the Desktop Design Is Finished

Late structural changes also create problems on smaller screens.

A desktop menu may comfortably hold six navigation items. A mobile menu needs a completely different interaction.

A desktop service page may have three columns. On mobile, those columns may become a long vertical sequence.

A desktop layout may have room for a large comparison section. On a phone, that same section might become difficult to scan.

The earlier you understand the content hierarchy, the easier it becomes to decide what should remain prominent when the screen gets smaller.

This is one reason structure is not only an SEO or planning issue.

It directly affects the design experience across devices.

Even Your URLs Benefit From Early Planning

There is another small detail that is easier to handle before the website is built: URLs.

If your website structure is:

Services → Web Design → Ecommerce Web Design

you may naturally end up with a URL structure that reflects that hierarchy.

Google recommends using simple, descriptive URLs and making the overall structure understandable to people and search engines.

You do not need to make every URL complicated.

In fact, the opposite is usually more useful.

The point is simply to avoid creating URL structures by accident and then changing them later when the website is already live.

What Should You Decide Before Opening the Design File?

You do not need to spend weeks planning.

For many website projects, a focused planning session can answer the most important questions.

Start with these:

What is the website supposed to help people do?

Is the main goal getting calls, quote requests, bookings, consultations, store purchases, or something else?

What are the main services?

Which ones need individual explanations?

Who needs to find what?

Think about the questions visitors are likely to have.

What should be in the main navigation?

Keep the structure understandable before worrying about visual styling.

Which pages are essential?

Separate must-have pages from ideas that can wait.

What does each important page need to communicate?

This gives the designer a content framework.

Which pages can share a layout pattern?

This can reduce unnecessary design work.

Are there important locations or service areas?

If location matters to the business, decide how those pages fit into the structure.

What should the URLs roughly look like?

Make the hierarchy intentional before development.

That is enough to create a much clearer starting point.

Planning Does Not Mean You Have to Know Everything

This is important because planning can easily go too far.

You do not need to decide every color, animation, button style, image, icon, or spacing value before design begins.

You also do not need a perfect sitemap that can never change.

The purpose of early planning is not to remove creativity.

It is to remove avoidable uncertainty.

During design, you may discover that a section works better somewhere else. You may realize that two pages should be combined. You may find that a particular customer journey needs a different approach.

Those are useful discoveries.

What you want to avoid is spending hours designing a page and then discovering that the page should never have existed in the first place.

A Small Planning Step Can Save a Large Design Change

This is where early structure becomes valuable.

A five-minute conversation about whether a service needs its own page can prevent hours of redesign.

A simple sitemap can reveal that the navigation is becoming too complicated.

A content outline can prevent a page from being designed around the wrong amount of information.

A decision about reusable page types can prevent five pages from being designed independently when they could share a system.

None of these activities are particularly glamorous.

But they make the actual design work much easier.

The Better Time to Make Big Website Decisions

The easiest time to change a website structure is before the structure has been turned into detailed design.

Once that structure becomes a navigation system, responsive layout, content system, development build, internal links, and live URLs, changing it becomes more complicated.

That does not mean every decision has to be perfect from day one.

It means the expensive decisions deserve attention early.

If you are planning a new website or redesign, start by mapping the pages, grouping related information, identifying the most important customer journeys, and deciding which content deserves its own space.
Then let the visual design grow from that foundation.

A good website does not become less creative because it was planned.

It becomes easier to design because the creative work has a clearer purpose.