How to plan a website layout
See how to order a website page around the visitor’s next decision, with an annotated desktop and mobile example and a simple planning checklist.
When I plan a page, I start with what someone needs to decide. A visitor may need to understand the offer, see proof and know what to do next. The grid comes after those questions.
I’ll use my own homepage to show how I put those pieces in order, what changes on mobile and where the layout makes a trade-off. This is a worked example of the decisions behind a page, rather than a claim that the design increased traffic or enquiries.
Give the page one main job
Write down who is arriving, what they need to know and what a useful next step would be. That step changes with the page.
- A service page: help someone judge whether the service fits their problem and decide whether to enquire.
- An article: answer the question they came with. A relevant service or project link can offer a next step once the explanation has been useful.
- A portfolio homepage: explain the kind of work I do and help someone choose between seeing examples and discussing a project.
For my homepage, the three questions are simple: “Can you help with this?”, “Can I see the work?” and “How do I start a conversation?” I use them to judge which content belongs near the top.
A desktop example: my own homepage
The opening introduces the offer, gives two possible next steps and follows with client logos. The navigation also gives the portfolio a direct route. Here is the actual page, with the decisions labelled.
My homepage, desktop view. Captured 17 October 2026.
An actual page capture with numbered annotations. It illustrates the layout, rather than a measured conversion result.
- A route to the work
Portfolio is named in the navigation so visitors can recognise where the project examples live.
- An offer before detail
The heading says what I build and who I work with. The next sentence explains the wider scope.
- Two useful next steps
See my work supports someone still evaluating. The enquiry link is available for someone with a brief.
- Proof near the promise
The logo strip follows the introduction. Detailed project examples appear after the service overview.
Why I kept two actions
“See my work” is useful when someone is still deciding whether I am the right person. “Tell me about your project” serves someone who already has enough context to start a conversation. Keeping both is a deliberate choice; I would simplify to one action on a campaign page with a narrower audience and goal.
The logos are a short introduction to previous work. They do not explain what I delivered. That is the job of the portfolio and project case studies, where someone can read about the scope, decisions and implementation.
A trade-off further down the page
My homepage puts a short service overview before the selected projects because I work across websites, apps, search and ongoing support. It helps explain that range, but it adds scrolling before the detailed proof.
If visitors mainly needed to judge the work, moving selected projects ahead of that overview would be a sensible thing to test. I would check it with real tasks and enquiry data before calling it an improvement.
What changes on mobile
The offer and actions keep the same order. The heading wraps, the actions have room to stack, and navigation moves into a menu. Portfolio is the first, most prominent link in that menu, so someone looking for examples can recognise the route.
My homepage, mobile view. Captured 17 October 2026.
An actual page capture with numbered annotations. It illustrates the layout, rather than a measured conversion result.
- Navigation stays available
The menu gives Portfolio the first, most prominent link. Visitors can get straight to examples.
- The same offer comes first
The headline and supporting sentence keep their reading order as the available width changes.
- Actions have room to wrap
The two routes stay visible without squeezing their labels into narrow columns.
- Proof follows the introduction
Client logos remain below the offer. The service overview and selected projects continue further down.
Further down, the service cards use a horizontal row with a “Swipe to explore” prompt. That saves vertical space, but it means all options are not visible at once. I would check whether people notice and use that row before choosing the same pattern for a task-critical page.
On a narrow screen, I check the real headline, long button labels, the menu and the next section together. A tidy desktop mockup does not tell me whether those parts still work when the content wraps.
A section-order checklist you can reuse
This is a starting point for a service or portfolio page. Change the order when the visitor’s questions require it.
- Orient the visitor. Say what the page offers and who it is for, using a clear heading and a short explanation.
- Make the next step recognisable. Give the main action a specific label. Keep another route only when it serves a distinct need.
- Bring in relevant proof. Put an example, demonstration or client evidence near the claim it helps someone assess.
- Explain the work. Cover what is included, important constraints and how delivery works, rather than listing every possible feature.
- Answer the remaining objections. Explain the parts people need before deciding, such as ownership, scope or what happens after launch.
- Offer a useful next step. Repeat the enquiry route once the page has given someone enough context to use it.
For a concrete example of explaining specialist work, see the Ficus Health case study. For a fuller planning document, use the existing website brief template.
Choose the grid around the content
A column count does not decide what the page needs to say. I use a readable width for longer copy, enough space for the actual content, and columns where the items benefit from sitting together. The content order should still make sense when those columns become one.
Before committing to a layout, I try a longer heading, a less flattering screenshot and a label that needs another line. If the design only works with short sample text, the page system needs more work.
Check the journey before calling the layout finished
- Ask someone to explain the offer, find a relevant project and locate the enquiry route.
- Use the menu and important links with a keyboard, and check that focus stays visible.
- Check narrow and wide screens for clipped text, horizontal overflow and actions that become awkward to reach.
- Follow the form or booking journey through its success and failure states.
- Measure completed enquiries or booking submissions separately from link clicks.
A layout can be clearer without an immediate change in search traffic. If I am checking this article’s search performance, I compare its relevant queries, clicks, impressions and click-through rate over comparable periods. I would not use a bounce-rate change or a better average position on its own as proof that the layout worked.
Frequently asked questions
What should I decide before designing a website layout?
Decide who the page is for, what they need to understand and the next action the page should support. Then choose the content and proof needed for that decision before arranging the grid.
Should the mobile layout match the desktop layout?
Keep the meaning, reading order and important actions consistent. Columns, spacing, navigation and image placement can change to fit the screen. Check the actual content on a narrow screen rather than assuming a desktop layout will scale down.
Does a better layout guarantee better search rankings or more enquiries?
No. A clear layout can make content easier to use, but that is not evidence of a ranking or conversion increase. Check the page with real tasks, then compare relevant search traffic, completed enquiries and booking submissions over an appropriate period.

.jpg)
