A business that works within a thirty kilometre radius does not compete with the entire market online. It competes with a manageable number of providers from the same region. That is precisely why local enquiries are often won or lost on small details: who appears at all when someone searches for a service plus a place, whose contact details turn out to be correct, whose opening hours hold up in practice. This article describes the building blocks that have to come together, in the order in which they typically start to pay off: consistent business details, dedicated pages per location and per service, maintained opening hours and contact routes, structured data for local results, and a clean legal footing for customer reviews.
Why local search follows its own rules
The starting position is well documented. In Germany, around 93 percent (Federal Statistical Office, ICT usage in private households) of people aged ten and over recently used the internet, and access happens predominantly on mobile devices and on the move. At the same time the supply side is highly fragmented: the skilled trades alone comprise roughly 1 million businesses (German Confederation of Skilled Crafts) employing about 5.6 million people (German Confederation of Skilled Crafts). For an individual business this means the number of potential competitors in its own catchment area is small enough to become visible with reasonable effort, and large enough that an incomplete website noticeably costs enquiries. Which components a company website needs for this is summarised in the overview of what XICflow delivers.
Local searches differ from general research in one fundamental respect: they are usually tied to a concrete action that is about to happen. Someone looking for an emergency service because the heating has failed wants to be on the phone within minutes. Someone looking for lunch wants to know whether the place is open today and what is on the menu. Someone looking for a practice or a law firm checks availability, area of responsibility and appointment options. The website therefore has to answer these questions quickly and without detours, not merely somewhere on the page. How a complete company website with all the pages required for this can be produced from a single briefing is described in the article on AI-assisted website creation.
Three questions every local page has to answer
Consistent business details are the foundation
Across the EU, around 78 percent (Eurostat, ICT usage in enterprises) of companies with at least ten employees recently had a website of their own. Having a website is therefore no longer a differentiator; the quality of the details on it still is. The most important and least spectacular lever is consistency: company name, address and phone number should appear in identical spelling everywhere, meaning on the website itself, in the legal notice, in business directories, in social profiles and in every printed piece. Discrepancies rarely arise deliberately; they accumulate over time as a number is added, a legal form changes or a suffix is dropped. Which details are legally required in any case is explained in the article on imprint and privacy policy.
- Full company name including legal form, spelled exactly as in the commercial register and the legal notice
- Address with the street term written out, house number, postal code and town, without changing abbreviations
- Phone number in a single consistent format, ideally written internationally and stored as a tap-to-call link
- An email address that is actually read, plus a form as a second route
- Opening or service hours per location, including deviating hours on public holidays
- Catchment area in plain words: the towns, districts or counties where the business genuinely operates
- A named contact person per location if the business runs more than one branch
| Detail | Typical drift | Recommended handling |
|---|---|---|
| Company name | Sometimes with, sometimes without legal form; suffixes come and go | Define one binding spelling and carry it through everywhere |
| Address | Street, St. and Str. mixed; a PO box instead of the trading address | Write the term out and keep the same order of components |
| Phone | Different separators, extensions, disconnected old lines | One format per location, stored as a link, old numbers actively retired |
| Opening hours | Only on the contact page, holidays left unmaintained | Stored per location, with special days entered before they arrive |
| Catchment area | Described vaguely as a region | Name the actual towns and counties where work is carried out |
The practical trick is not to maintain these details in several places, but to store them once and generate every occurrence from that single record. As soon as contact details are maintained separately in the footer, the contact page, the location pages, the legal texts and the structured data, they tend to drift apart within a few months. In XICflow, business details therefore live in the site configuration and are inserted into every output; changing a phone number takes one edit and reaches every page as well as the markup for search engines. How this path from configuration to statically delivered page works is shown in the description of how XICflow works.
A dedicated, complete page for every location
Businesses with several branches often list their locations as address blocks on a single contact page. For local visibility this is the weaker option, because one page can hardly be relevant for several places at once: title, description, heading and URL can only be assigned once. A dedicated page per location solves that without inflating the structure. It carries a descriptive URL, its own description, the address of that branch, the team working there, the services offered there and the hours that apply there. That makes it more useful for visitors and unambiguous for search engines.
Place at the core
Address, directions, parking and catchment area appear in the text, not only inside an embedded map. The page title names the place as well.
Hours and reachability
Opening or service hours for this branch, deviating hours on public holidays, and a route to a person who actually replies.
Substance of its own
Team, equipment, typical projects and local contacts. Only this original content turns a duplicated address into a page that stands on its own.
To keep several location pages from becoming text duplicates, one simple rule helps: the frame may be identical, the substance may not. Service descriptions can share a basic structure, yet examples, contact people, catchment areas and directions differ per location anyway. If a branch closes or is renamed, the old address should not simply be deleted but permanently redirected to the new page so that external links do not run into a dead end. How the different page types feel in combination can be explored in the XICflow example sites.
Thin location pages are a risk
Service pages instead of one long service list
The second major lever is how the offering is split up. Many businesses squeeze their entire range onto a single page, often as a bulleted list with one sentence per item. For visitors that is a burden, because they have to find their own task among twenty others, and for discoverability it achieves little, because one page can hardly be the right answer to twenty different search queries. A dedicated page per relevant service reverses that: it can answer the typical questions about this one task, explain price ranges and process, name prerequisites and offer a concrete next step at the end.
- A heading that names the service in the customer's language rather than in internal jargon
- A short paragraph describing the task and picking up the typical starting situation
- The process in steps: enquiry, appointment, assessment, quotation, execution, handover
- Framework conditions: duration, required preparation, cost drivers, possible funding schemes
- Boundaries: what is not included and who is responsible in that case
- The catchment area for this service if it differs from the rest of the offering
- Frequent questions from the day-to-day work of the business, answered in full sentences
- A clear next step with phone number and form, without a detour via the home page
As soon as several locations meet several services, the temptation arises to create every combination as a separate page. With three locations and twelve services that would be 36 additional pages, most of which would have nothing of their own to say. The combination is worthwhile only where it genuinely carries substance: for services with a clear local dimension, for tasks in high demand, or for branches with special equipment. For everything else a good service page plus a note on the locations where it is delivered is enough. Which scope suits which business can be gauged from the pricing overview.
| Structure | When it fits | What to watch |
|---|---|---|
| One collective page for all services | A very small offering with two or three services | Becomes cluttered quickly and answers specific queries only roughly |
| One page per service | The normal case for businesses with clearly distinguishable offerings | Each page needs its own content, its own description and its own next step |
| One page per location | Several branches with their own address and their own team | Without a real branch, empty place pages appear and risk being devalued |
| Location and service combined | Services in high demand with a distinct local dimension | Create only where original content exists, otherwise maintenance load grows |
Opening hours, reachability and contact routes
Hardly any detail is found outdated as often as opening hours, and hardly any has more direct consequences in local search: someone standing in front of a locked door because the website stated different hours rarely comes back. Well maintained hours therefore involve more than a weekly table. They account for company holidays, public holidays, shortened days before holidays and, where applicable, emergency service times. In addition, every page should offer a contact route that fits the situation. A tap-to-call link is often the fastest route on the move, a form suits enquiries with details and attachments, and a promised call-back takes pressure out of the first contact. How to design forms so that enquiries arrive complete instead of disappearing in a busy inbox is described in the article on contact forms and enquiry handling. Anyone additionally embedding a map from an external mapping provider should keep in mind that this usually transfers data to third parties and may require consent; the basics are explained in the article on GDPR and cookie consent.
Phone in one tap
The number is stored as a link and reachable in the header of every page. Next to it stands the time when someone actually picks up.
A form with context
Few mandatory fields, clear labels, a stated response time. Enquiries land in an overview instead of a crowded mailbox.
Directions without guesswork
The address as text, notes on parking, access and step-free entry, plus a map integration that only loads after consent.
Local visibility rarely comes from one big move. It comes from the small details being correct year after year.
Structured data for local results
Structured data are machine-readable additions in the source code of a page. They change nothing about how visitors see the page, but they make explicit what the text says anyway: that this is a business at a specific address, with this phone number, these hours and this catchment area. For local results that helps, because search systems reconcile details from several sources and tend to treat contradictions cautiously. The open schema.org vocabulary is the common choice, embedded as JSON-LD in the head of the page. What matters is emitting the markup per location rather than globally for the whole company, otherwise every page carries the same address.
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Example Building Services Ltd, North branch",
"url": "https://example.com/locations/north/",
"telephone": "+49 5121 1234560",
"email": "north@example.com",
"address": {
"@type": "PostalAddress",
"streetAddress": "Sample Road 12",
"postalCode": "31234",
"addressLocality": "Sampletown",
"addressCountry": "DE"
},
"areaServed": ["Sampletown", "Sampleshire district"],
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
"opens": "07:00",
"closes": "17:00"
}
]
}Two limits deserve attention. First, markup does not replace content: details that do not appear in the visible text should not be marked up either. Second, an enhanced presentation in search results is a possibility rather than an entitlement; search engines decide case by case. The effort-to-benefit ratio is nonetheless favourable, because the markup can be generated from fields that already exist and creates no additional editorial work. Which markup makes sense for which page type and how to verify it is covered in depth in the article on structured data in search results.
Using reviews within the legal framework
Reviews carry weight locally because they answer a question no marketing copy can answer: what was it like for other people. The legal framework is tighter than many assume. Under section 5b paragraph 3 UWG (German Act Against Unfair Competition) a provider who makes consumer reviews accessible must state whether and how it ensures that those reviews originate from consumers who actually used the service. The annex to section 3 paragraph 3 UWG additionally classifies it as unlawful to publish or commission fake reviews, or to claim that reviews have been checked without having taken reasonable measures to do so. Anyone showing reviews on their own website should therefore name their origin and avoid a selective presentation.
- Show only reviews that were genuinely submitted, stating the source and the period they cover
- Make the distribution visible alongside the average instead of selecting top marks exclusively
- State whether and how authenticity is verified, in plain language and close to the reviews themselves
- Offer no incentives for positive reviews; a factual request for feedback after completion is permissible
- Respond to criticism publicly and calmly, without disclosing personal details from the assignment
- Do not invent awards from reviews; present only what can be substantiated
Technical foundations that matter locally
Local visits happen predominantly on mobile devices, frequently on the move and often on a weak connection. That is exactly where technology translates into revenue. According to the Core Web Vitals Technology Report, only around 48 percent (HTTP Archive, Core Web Vitals Technology Report) of mobile origins achieve good values across all three metrics. A statically delivered page without heavyweight scripts has structural advantages here, as the article on PageSpeed and static delivery shows in detail. Accessibility comes on top: since June 2025 many services in electronic commerce fall under the requirements of the German Accessibility Strengthening Act, which follows WCAG 2.2 at level AA and has practical consequences precisely for contact details, forms and opening hours; the article on the Accessibility Act and business websites puts this into context. Both aim at the same goal: the information has to arrive reliably on every device and with every form of operation.
The short version