A visitor opens the homepage, reads “Shaping the future together” and sees a large image. Yet it is still unclear whether the company builds websites, introduces service providers or looks after buildings. The design may be carefully considered; the initial explanation is missing. Someone who must piece together the service from the menu cannot yet judge whether the provider is suitable.
A clear homepage therefore connects the offer, intended audience, actual service area and next step. It provides enough orientation to make a decision, then leads to the relevant details. The number of sections needed depends on the business model and visitors’ questions.
Salestudia develops websites for businesses in Germany. This guide focuses on homepage messages: you will create a logical sequence, set limits on promises and use concrete tasks to check whether other people understand the page. The examples are editorial drafts, not documented client results.
1. Structure a homepage around orientation
The homepage has a different role from an individual service page. It introduces the company, makes relevant routes visible and helps people get started. A service page then explains a particular offer, including its prerequisites, scope and process. Not every detail belongs on the homepage, but choosing where to go next should not depend on chance.
The central question is whether a suitable person can recognise that this company could help with their task and see how to establish that. The page does not have to push for an immediate booking. For a service that needs explanation, the sensible next step may be selecting a service category or reading the requirements for an enquiry.
Give the editorial team a concrete task
Before working on the layout, write one sentence: “The homepage should help people with task X understand offer Y and choose step Z.” X, Y and Z must be specific. “Inspire everyone and increase revenue” is too vague as an editorial assignment. The business outcome still matters; the editorial team also needs an observable task.
2. Derive the main messages from real questions
Collect questions from relevant enquiries, conversations and existing research. Separate questions asked before first contact from details only needed for a particular job. One vocal customer request is not sufficient reason to shape the entire homepage around it. Record the situation each question came from.
The GOV.UK guidance on user needs relates content to tasks and existing evidence. For a business homepage, this suggests a practical question: what information helps a visitor make their next decision? The hierarchy below is an editorial proposal, not a requirement set by the source.
Worksheet: connect each message to its evidence
| Visitor’s question | Message needed | Basis within the company | Suitable position |
|---|---|---|---|
| What does the company offer? | A specific service category | Services actually available | Opening section |
| Is this relevant to my task? | A suitable situation or audience | Approved service scope | Opening or selection |
| Does it work in my area? | Actual service coverage | Current service or delivery conditions | Close to the offer |
| Why should I consider it? | Relevant, verifiable experience | Approved examples and information | Beside the relevant claim |
| What do I need to prepare? | Required starting information | Actual enquiry process | Before the next step |
| What happens afterwards? | Nature and limits of the follow-up | Agreed responsibilities | Beside the proposed action |
3. Write the opening as a clear explanation
The first visible area does not have to contain every answer. It should name the service clearly enough for the sections that follow to make sense together. A caption or short supporting line can explain the audience and service area. A memorable tagline can add something, but should not displace the factual introduction.
The GOV.UK guidance on content structure recommends putting the most important information first. Applied to a homepage, this means explaining what is offered before describing the distinctive approach. It does not establish a fixed word count for a headline.
A possible opening for a fictional business
“Office cleaning for small businesses within the agreed service area” could be a draft that can be checked. The line below could describe the cleaning services actually provided and the floor-area information required. This assumes that the service and coverage really exist. An invented list of towns would not make the explanation more reliable.
Temporarily remove the logo. Is the activity still clear? Then remove the large photograph. Can you still identify the offer and next step? These editorial checks do not replace research with users, but they can expose reliance on ambiguous images and unfamiliar brand names.
4. Explain audience and geography as conditions
“For businesses” may be sufficient if the offer genuinely serves many sectors. Often, a more specific situation helps: updating an existing website, building a first online shop or presenting several services clearly. Describe the problem the company can help with, without artificially listing every industry.
Service area, registered or operating location and communication language answer different questions. An office in one town does not establish a branch in every region served. German-language consultation says nothing by itself about the availability of on-site appointments. State only the reach your service process actually supports.
Include local detail where it changes the choice
For on-site services, the service area may already limit the first step. For digital collaboration, supporting businesses in Germany may be the more useful description. Additional regions make sense when they explain a real condition. Repeating town names does not in itself add information.
Also establish whether enquiries outside the stated area are excluded, assessed individually or handled through another process. The homepage need not reproduce the contract terms, but should not suggest general availability that will be withdrawn after contact.
5. Turn several offers into understandable routes
A long service list communicates breadth, but does not yet explain which entry is relevant. Organise the main offers by situations or tasks if visitors understand those terms. The company’s internal departmental structure does not have to be the homepage’s main organising principle.
The USWDS header guidance recommends clear labels and an emphasis on user tasks rather than organisational structure. We use that principle as inspiration for the selection below. The rows describe fictional starting situations, not actual products from a particular company.
| Starting situation | Visible entry point | What is clarified next | Common ambiguity |
|---|---|---|---|
| Planning a website for the first time | Plan a new website | Goal, content and appropriate scope | A format is chosen too early |
| Renewing an existing website | Modernise a website | Existing content and necessary changes | Modernisation sounds purely visual |
| Assessing a specific service | Choose a service category | Scope, prerequisites and responsibility | Every card leads to the same generic form |
| Continuing an existing project | Find your existing contact | Appropriate contact or established process | Existing clients enter the sales form |
Each entry point needs useful destination content. If two cards explain the same thing and lead to the same destination, check whether separating them helps. The number of tiles should follow the tasks, not the available width of the grid.
6. Support claims with relevant evidence
A homepage need not try to build trust entirely through ambitious claims. An understandable work example, an explained process or a clearly described responsibility can address a specific uncertainty. Place the evidence where it helps explain the claim. An unrelated logo next to a general quality promise does not establish a working relationship.
The Google guidance on helpful content includes clear sourcing and demonstrable expertise among its self-assessment questions. This does not guarantee rankings. The editorial implication is that statements should be traceable to verifiable information and should not rely on fabricated references for persuasive force.
Evidence must match the scope of the claim
A screenshot shows an interface, not commercial success. A testimonial describes an experience under particular conditions. A project example should explain the company’s own role and be approved for use. Where reliable results are unavailable, explain the actual service scope and required starting information. Missing evidence is a reason to limit the promise.
7. Make your role and service boundaries visible
Clients should be able to recognise whether they are speaking to the company carrying out the work, an intermediary or another party. Include that distinction in the explanation of the offer when it materially affects the engagement, responsibility or next step. A detail page available later cannot by itself correct a contradictory opening statement.
An example from the connected project network is the HandMen guide to caretaker-service tasks and boundaries (German). It distinguishes property care from other activities and explains the intermediary role: HandMen introduces enquiries, while the businesses commissioned carry out the work. The point here is that verbal distinction, not an assessment of the homepage or its commercial effect.
Compare promises with the actual process
Check statements such as “We take care of everything” against the real division of responsibilities. If the first step is finding a partner or assessing feasibility, the proposed action should announce that. Adopt the HandMen model only if it matches your own business model. It is not a general requirement for service companies.
8. Offer a next step with a clear expectation
“Discuss a project”, “Check the service scope” and “Book an appointment” announce different processes. Choose wording that matches the actual destination. If it only opens an enquiry form, the label should not create an expectation of a confirmed booking. A short sentence beside the action can explain the information required and what the company will assess afterwards.
The W3C explanation of link purpose describes making a link’s purpose identifiable from its text or determinable context. The USWDS button guidance recommends short, action-oriented labels. Both help with wording; neither determines a single CTA suitable for every business model.
A primary action can appear again at useful points, provided it refers to the same process. Informational routes to services or contact options can sit alongside it. Problems arise when equally prominent actions compete for attention and their differences remain unclear. Make the decision around the task, not the number of buttons available.
9. Arrange the page around unanswered questions
One possible sequence starts with orientation, opens relevant service routes and adds evidence and necessary conditions. It then offers a clearly described next step. A complex offer may need a short process explanation earlier. An established client audience may also need a direct route to the appropriate contact.
The W3C tips on accessible writing recommend meaningful headings that convey structure and meaning. Use section headings that announce actual information. “Services for existing websites” says more than “Our world”. The sequence below is a working draft for a business homepage, not a universal blueprint.
| Section | Its task | What is enough here | What generally belongs on a detail page |
|---|---|---|---|
| Opening | Introduce the company and offer | Service, relevant situation and next step | The complete company history |
| Selection | Open the relevant service route | Clear categories and their differences | Every service variant |
| Evidence | Make an important claim understandable | An approved example explaining the company’s role | An unexplained project gallery |
| Working process | Explain essential expectations | Actual steps and responsibilities | Internal organisational details |
| Conditions | Show important suitability limits | Coverage and required starting information | Complete contractual documents |
| Closing | Enable the next step | Action, expectation and suitable contact route | Competing additional offers |
10. Use images as part of the explanation
A large image can show an activity or an object. It should not create a false impression of what the company itself does. A photograph of somebody else’s team, for example, can appear to make a claim about the people involved. Review image content, rights and context together before giving it the homepage’s most prominent area.
The W3C images tutorial distinguishes informative and decorative images, among other types; text alternatives depend on function in context. For the homepage, this means an image carrying essential information needs an appropriate alternative. Decoration should not be the sole carrier of the service description.
Use work photographs when they show something relevant, and explain the connection. If the image only establishes a mood, visible text must provide the professional context. The image should also work with tighter mobile cropping, without losing an important subject or making essential wording readable only inside the photograph.
11. Check the mobile sequence and interaction
On a small display, statements positioned side by side become sections read one after another. Check that actual sequence. A condition should not appear far below the action it qualifies. A floating contact button should not cover important text or form instructions. Longer translated labels must also remain readable.
The W3C explanation of reflow addresses content adapting without loss of information or functionality under the stated conditions. The W3C explanation of minimum target size describes size and spacing requirements with exceptions. Measuring a single control therefore does not establish that the whole homepage is accessible.
Follow a concrete task through the page
Read the opening at increased zoom, open the menu using the keyboard and follow the next step announced. Check visible focus, understandable link names and reachable controls. This inspection helps identify problems; a comprehensive assessment needs further criteria and suitable tests. Document the actual obstruction rather than making a blanket judgement that the page is “mobile optimised”.
12. Give returning visitors a direct route
Not everyone arrives for an initial introduction. Some already know the company and want a particular service or an existing contact. An opening that helps new visitors should not make those routes unnecessarily difficult. Use recognisable labels and avoid continually renaming familiar destinations for purely visual reasons.
The W3C explanation of consistent navigation addresses maintaining the relative order of repeated navigation mechanisms unless users initiate a change. For planning, the homepage should remain part of a coherent system. New section names need to match the terms actually used on the destination pages.
Check separately whether a new visitor understands the offer and a returning visitor can find a familiar destination. Success on one route does not establish success on the other. Main navigation should support real tasks; the homepage does not need a second complete sitemap.
13. Keep multilingual messages equivalent in meaning
A translation should not broaden or narrow the offer simply because shorter wording fits the layout better. Align the service, coverage, intermediary role and next step across DE, EN, RU and UK. Sentence lengths may change; the underlying factual statement should stay the same.
Check the destination pages as well. A clear translated opening offers little help if the advertised service route unexpectedly switches language or describes a different service. Destination pages need not have identical text lengths, but conditions material to the decision should agree.
The guide to content-first web design explains preparing text, images and necessary information before the layout. For the homepage, the central messages in particular should be available before final visual agreement. You can then check whether the layout supports the actual statements, instead of removing important qualifications later to save space.
14. Prepare a short comprehension test
Test a specific version with people whose tasks match your audience. Agree beforehand which questions the test should answer and which page or prototype will be shown. An internally agreed viewing time can make the procedure consistent; it is not a universal attention span or evidence of commercial success.
The GOV.UK guidance on moderated usability testing recommends realistic tasks and neutral instructions that do not reveal the solution. Apply that principle to the homepage. Let the person explain and act independently before clarifying anything they found unclear.
| Test objective | Neutral task or question | Record the observation | Do not supply |
|---|---|---|---|
| Recognise the offer | Describe in your own words what this company offers. | Activity named and uncertainty | The technical term from the heading |
| Assess suitability | What information helps you decide whether this offer fits your task? | Clues used and missing information | The intended audience |
| Understand coverage | What can you say about its service area? | Statement actually found | An assumed location |
| Find the next step | How would you clarify your task further with this company? | Chosen route and obstacles | The target button’s name |
| Check expectations | What do you expect when you take that step? | Expected follow-up process | The internally planned response |
15. Interpret observations without inventing results
A fictional example: person A recognises the service but expects “Secure an appointment” to produce a firm booking. Person B finds the same route and expects only a reply. Person C first looks in the footer for regional availability. This identifies two things to examine: the expectation created by the action and the discoverability of the service area.
These invented observations are not test data and support neither a success rate nor an extrapolation. Even in a real small qualitative study, a finding would initially be a signal for revision. Record the task, literal observation, affected part of the page and proposed change. Separate what was said from your interpretation.
An unclear button label does not automatically require redesigning the whole page. If several people misunderstand the business model, a different colour may be insufficient. Check the revised version again with the same kind of task. Record which version was shown so that different drafts are not mixed together.
16. Prioritise changes and hand them over clearly
Address misunderstandings about the service, role and availability first. Then consider obstacles in the next step and supplementary questions. This sequence is a practical working rule; a specific interaction barrier may require immediate correction. What matters is which part of the task the ambiguity blocks.
For each change, hand over the previous wording, replacement, supporting basis and person responsible. Decide who approves the service facts, who aligns the translations and who checks destination pages. Changes to coverage or the enquiry process must reach the homepage too.
Assess understanding and commercial effect separately
A comprehension test shows which explanation or route causes problems. Whether a change generates more suitable enquiries is another question, with additional influencing factors. The guide to conversion rate optimisation covers landing pages, forms and tests. Use that broader perspective when an editorial improvement needs to become a reliable investigation of its effect.
17. Frequently asked questions about homepage structure
How long should a business homepage be?
Long enough for suitable visitors to understand the offer and choose a sensible next step. A fixed number of words or sections does not answer that task. Keep important conditions visible and move detailed variants to appropriate pages. Then check whether the transitions are understandable.
Does the main service have to appear at the top?
The service essential to understanding the company should be recognisable early. For several business areas, a clear shared category followed by a selection can help. Decide from visitor tasks and the actual offer. A service the team especially wants to promote is not automatically the best opening for everyone.
Does every homepage need prices?
A reliable price or understandable range can help when it enables a choice. Without a sufficient basis, avoid creating misleading starting prices. Where appropriate, explain the information needed for an assessment and what that assessment includes. The homepage need not present an incomplete service catalogue with prices that appear comprehensive.
Can there be several calls to action?
Yes, if they support different, understandable tasks. A direct contact route and an informational route into the services can both be useful. Make the primary action recognisable and explain the differences. Repeated controls with identical wording should not unexpectedly open different processes.
Is a test with colleagues sufficient?
An internal walkthrough helps find obvious mistakes and prepare the research. People within the company already know its terminology, service boundaries and processes. Add feedback from suitable people outside the project team. The research question and usage conditions determine who needs to participate.
Must the homepage list every town?
No. Describe actual coverage as precisely as the decision requires. Specific service-area conditions may matter for on-site work; for digital collaboration, an accurate description of the market served is often more useful. Do not invent branches or describe individual assessment as general availability.
Can an attractive image replace the explanation?
Only if the necessary information is actually communicated clearly and accessibly; a mood image rarely does that alone. Write the factual introduction as text. Check cropping and the text alternative in context. The image should support the explanation without suggesting false claims about the team or activity.
Does a clear homepage prove higher revenue?
No. Clarity supports an informed decision, but does not demonstrate additional revenue. Demand, offer, price, contact handling and other factors also contribute. Keep qualitative observations separate from measured business outcomes. Describe an editorial improvement only through the evidence actually available.
18. Use a clear sequence as the basis for design
A sound homepage begins with an accurate explanation and leads through relevant choices and evidence to an understandable next step. The connection matters: the opening claim, service boundaries and follow-up process must describe the same offer.
If you are planning or revising your business homepage in Germany, you can discuss the offer, central messages and route to an enquiry with Salestudia. Describe your services, available content and the main questions still unresolved.
Sources and scope
The twelve primary sources linked in the text come from GOV.UK, USWDS, W3C and Google. The British and US design guides provide methodological inspiration here, not requirements for German businesses. The W3C explanations address individual aspects of accessibility; this article is not a complete conformance assessment. The tables, priorities and fictional observations are editorial working tools. They do not establish revenue or conversion effects. Sources and linked destination pages checked on 29 October 2026.