Showcase site home page: prioritize the offer and the evidence

9 min read

The home page of a showcase site must allow a visitor to recognize the company, understand its offer and choose a suitable suite. It welcomes several intentions: looking for a repair, preparing a maintenance contract, checking a contact. The hierarchy makes these choices readable without transforming the screen into a catalog.

A good entry introduces the activity, distinguishes the needs, shows verifiable evidence and leads to the right page. The plan below suggests an editorial order, to be adapted to your actual scope and then controlled on mobile.

Clarify requests before choosing blocks

Start by collecting recurring requests from people who answer the phone or messages. Note the terms used, the material concerned, the function of the requester, their context and the information necessary to guide their request. Also note the exclusions: equipment not supported, missing services, geographical limits or conditions of intervention.

Then classify visitors by question, rather than just by profession. A site manager may need a repair today and seek organized maintenance next. These intentions deserve different routes, not two competing presentations of the company.

Reception distributes these routes while maintaining a common identity. An advertising page generally responds to a targeted offer and action; the method of consistency between offer and call to action addresses this separate case. Here, choose a dominant entry based on actual activity, then make the others visible.

Google defines people-first content as content created primarily for them, not to manipulate rankings^[16]. This benchmark favors readable needs rather than the accumulation of keywords.

Make the home page of your showcase site identifiable

The entry screen must answer three questions: who are you, what do you support, for whom? Place a specific business title near the company name. A phrase such as “Your daily partner” can accompany a proposal, but should not replace it.

In our entirely fictitious example, Atelier Repère maintains professional cleaning equipment and offers repair and maintenance. This case does not describe a client of 4SYSTEM. A usable proposal would be: “Repair and maintenance of professional cleaning equipment for operators and site managers”. The list of equipment actually accepted must then specify this scope.

Under this sentence, place two explicit choices: “Describe a breakdown” and “Prepare for maintenance”. Avoid calling the repair urgent if the organization does not have a corresponding device. Do not display permanent availability or guaranteed deadlines without a documented commitment.

Finally keep the name of the company, access to the contact and the presentation pages identifiable. Identity must not disappear behind the buttons.

Distinguish offers without fragmenting the company

Present each offer with the need addressed, the elements necessary for its examination and the next destination. For the repair, the visitor prepares the type of equipment, the symptom observed and the place of use. For maintenance, it specifies the fleet concerned and its current organization.

Offer cards do not need to include the entire service sheet. They must make it possible to distinguish situations. An identical “Discover” button everywhere requires interpreting the context; “See fault support” announces the rest better.

Place exclusions where they influence the choice. In this fictitious case, “Domestic equipment outside the scope” would clarify the limit near the offers. Also have a “Check if my hardware is supported” route for ambiguous requests. It must lead to an explanation or a contact capable of arbitrating, not to an impasse.

Choose verifiable and situated evidence

Evidence must support a specific assertion. A workshop photo shows an environment; it does not prove either certification or an intervention time. An anonymized report extract can show what is recorded after an operation, but does not alone demonstrate the quality of all interventions.

Create a simple register: displayed statement, supporting document, validation manager, publication authorization and control date. For a testimonial, keep the approved wording and its context. For a logo, check the intended right of use and known restrictions. Do not equate a commercial relationship with an authorization to communicate.

This register is an editorial method, not a legal validation. If agreement is missing or if a person remains identifiable in an image, suspend the publication in question until appropriate verification. Don’t make a customer logo, certification, or quote to fill a mockup.

Connect each proof to the block it illuminates. It is better to explain the content of an intervention with a publishable document than to place a gallery of confidence signs without context.

Annotated reception plan: from need to the right destination

Here is the annotated plan for Atelier Repère. The titles are fictitious examples. The evidence indicated must be gathered and validated: they are not presented as existing documents.

The proofs in the table do not impose seven autonomous blocks. A coin can directly accompany an offer card. On the other hand, each destination must clearly announce its purpose and include the context transmitted, so that the visitor does not have to reformulate their entire request.

Structuring titles and journeys on mobile

Build titles based on content, not visual size. W3C indicates that headings communicate the organization of the page and can be used for internal navigation, particularly with assistive technologies^[13]. So give the sections informative titles, such as “Repair” or “Prepare for Maintenance”.

The same guide recommends nesting titles according to their level^[13]. In this plan, a main title presents the activity; large sections use H2, their possible subparts H3. A simple sentence in bold does not replace this markup.

On mobile, control the actual display order, the link titles and the space taken by the visuals. The menu must retain the essential routes without copying all the blocks. This check alone does not cover contrasts, keyboard usage or complete accessibility of the form.

Validate the welcome in the correct order

Validate in this order, before discussing graphic effects:

1. Perimeter : compare each offer with confirmed capacities and each exclusion with the work list. Decide to keep, clarify or remove ambiguous wording.
2. Evidence : reconcile each statement with its supporting document and its authorization for publication. Absent proof leads to sober reformulation or withdrawal of the assertion.
3. Roads : Open each destination. Check the continuity between the title, the incoming content and the requested information. Delete buttons that have no useful effect.
4. Mobile reading : ask someone outside the model to identify the activity, choose between breakdown and maintenance, then find the exclusions. Note his hesitations, without converting them into rates.
5. Validation : keep the reviewed version, the useful captures, the list of corrections and the name of the validator. Redo the route after correction.

For each point, use a status: accepted, to be corrected or blocking. An unconfirmed offer or an inconsistent destination blocks validation of the block concerned. The final file brings together the annotated plan, the evidence register and the mobile test report. It certifies what has been controlled, not a commercial result.

Frequently asked questions

Can an advertising campaign point to the reception?

Review what the ad promises. If it presents the company as a whole, the reception can provide a cohesive destination. If it proposes a specific intervention or requests a unique action, choose a dedicated page which takes up this context. In both cases, check the arrival on mobile and remove any wording missing from the offer actually available.

What to do if confidentiality prohibits a nominative reference?

Do not publish the default name. Check if a document can be presented without details to recognize the organization, site or people. If this possibility remains uncertain, instead present your method and the expected content of the deliverable, without attributing results to a third party. Have the selected version validated before displaying it.

How to process a request combining repair and maintenance?

Provide an entry allowing you to report both needs without sending two identical files. Ask about the current problem first, then interest in a scheduled interview. The contact responsible for qualifying the request must be able to distinguish the solutions to be proposed. The reception announces this possibility; the conditions and commitments are then specified, after examination of the material concerned.

Prepare for the next version

Start by writing your activity proposal, your main routes and the exclusions that change a decision. Then fill the plan with available evidence, then carry out the mobile check before validation. If you want to frame the architecture or its implementation with 4SYSTEM, see our web services, SEO and digital marketing to identify the support suited to your project.

Sources

• Headings | Web Accessibility Initiative (WAI) | W3C (accessed 2026-10-08)
• Creating Helpful, Reliable, People-First Content | Google Search Central | Documentation | Google for Developers (accessed 2026-10-08)