What does Homepage Blueprint do?
Decide what goes on the page, in what order, and why, before choosing colors or writing code. A homepage that is structured around the visitor's questions converts better than one structured around what the business wants to say.
Start with four answers
Ask for these if they are missing. Without them the blueprint is generic.
- Who is the visitor, and what did they just search for or click?
- What is the one action the page should produce (enquiry, call, purchase, signup)?
- What proof exists (reviews, client logos, numbers, case studies)?
- What services or offers must appear?
The visitor's question order
Each section answers the next question a visitor has. Order sections by this sequence and drop any section whose question the business cannot answer honestly.
| Visitor asks | Section | Minimum content |
|---|---|---|
| Am I in the right place? | Hero | What you do, for whom, one CTA |
| Can I trust this? | Proof strip | Rating, logos or one number |
| Who are you? | About | Two short paragraphs, one image |
| What exactly do you do? | Services | 3 to 6 cards, each with a link |
| Why you over others? | Differentiators | 3 to 5 concrete points |
| How does it work? | Process | 3 to 4 steps |
| What will it cost? | Pricing or engagement models | Ranges or "how we scope" |
| Did it work for others? | Testimonials | Real quotes with names and roles |
| What if I have doubts? | FAQ | 6 to 10 real objections |
| What do I do now? | Contact | Short form, alternative channels |
A blog preview and a closing CTA band are optional extras after the FAQ.
Rules that keep the page honest and effective
- One primary action. Repeat the same CTA label through the page. Competing CTAs split attention.
- Real proof only. Never invent testimonials, client names, ratings or statistics. If proof is thin, use a process or guarantee section instead, and say what the person should collect.
- Number the sections in the design (
01,02) only if there are five or more; it helps long pages feel navigable. - Each section has one job. If a section answers two questions, split it.
- Above the fold: headline, one supporting line, CTA, and one proof element. Nothing else is required there.
Output format
Produce a table, then notes.
# Homepage blueprint: [Business]
Goal: [single action] Visitor: [who]
| # | Section | Job | Content slots | CTA |
|---|---------|-----|---------------|-----|
## Content the business still needs to supply
- ...
## Sections deliberately left out, and why
- ...
The "left out" list matters: it shows the structure was a choice, and tells the person what to add when they have the material.
Variations
- Solo freelancer: merge About into the hero, lead with portfolio pieces instead of a services grid.
- Local service business: add service area and opening hours near the contact section; put the phone number in the header.
- Product or SaaS: replace Services with a feature walkthrough and Process with "how it works" screenshots.
- E-commerce: this skill does not fit; category and product discovery lead instead.