Local SEO Consultant, Netherlands

KvK establishments, trade names and the name on your profile

Every Dutch company is registered with the Chamber of Commerce (KvK), and each physical place where it operates can be recorded there as a separate establishment with its own establishment number. That structure is useful for local search. I use the KvK extract as the starting list of locations, so the profile set matches what is officially registered rather than what an old spreadsheet says.

A Google Business Profile ought to carry the name printed on the door, the van and the invoice. For many Dutch businesses that is a registered trade name, not the statutory name of the BV behind it. Problems start when the two are mixed: one branch listed under the BV name, another under the trade name with a city added, a third with a slogan. Google treats added keywords in the name as a guideline breach, and customers simply get confused.

Getting verified comes next. The method is Google's choice, and for many new or edited profiles it now means filming a short clip that moves from the street and your signage to something only the operator can access, such as a staff-only room or the till. Shared buildings, unsigned units and home offices are where verification often fails. I prepare each location before the request, so the video shows what Google needs to see and the address on the profile matches the address on the KvK record.

Ownership deserves attention too. Profiles created years ago by a former employee or a web agency are common, and recovering them takes time. A clean list of owners and managers per location is one of the first deliverables.

Postcodes, house-number additions and business parks

Dutch addresses look tidy, but small details cause map errors. House-number additions such as a letter or a unit suffix are often dropped or written in the wrong field, which can place a clinic in the apartment upstairs or merge two businesses at one entrance. I compare each address with the official address and buildings register (BAG) and with the postcode, then check where the pin actually lands.

Common Dutch issues I look for:

• Business parks. Units on an industrial estate often share one street and a long run of numbers. Pins drift to the estate entrance or a neighboring hall, so customers end up at the wrong gate.
• Village versus municipality. After municipal mergers, the town in a postal address can differ from the municipality name. Profiles and location pages should use the place name local customers use in searches.
• PO boxes. A Postbus address cannot serve as a profile address. Where customers do not visit, a service-area profile is the honest setup.
• Home-based trades. Many self-employed tradespeople work from home. Their profiles should hide the home address and show the towns or regions they actually serve.

Service areas in the Netherlands overlap quickly because towns sit close together. I keep them to places the team really travels to, rather than drawing a large radius that promises visits nobody will make. Map data also needs checking on other platforms, including Apple and Microsoft maps, since a wrong pin there sends the same customer to the same wrong gate.

Branches, franchise formulas and location pages

Dutch retail, hospitality, fitness, childcare and home services often run as franchise formulas or regional chains. Local search in those networks depends less on clever optimization and more on clear rules. Who owns each profile: head office, the franchisee or both? Who may change opening hours, photos and services? What happens when a franchisee leaves or a branch moves to a new address?

I set this up as a location master: one record per KvK establishment with the approved name, address, phone number, opening hours, categories, services and profile ownership. Head office keeps owner access to every profile and franchisees manage day-to-day details. A short playbook deals with new branches, moves, temporary closures and final closures, including holiday hours and the bridge days many Dutch businesses close on.

Each real location also deserves a page on your website that the profile links to. A good location page shows the address, how to get there by car, bike or public transport, parking, the team, services offered at that branch and its own reviews. Pages for towns where you have no branch are only worth writing when you genuinely serve them and have something specific to say, such as projects completed nearby or a local service schedule. Dozens of near-identical city pages are doorway pages; they rarely help and can hurt the whole site.

If you also run branches in Flanders, Belgian Dutch wording and Belgian addresses need their own handling, which my local SEO work in Belgium covers. For larger networks, larger networks can follow the approach on my multi-location local SEO page.

Reviews under Dutch consumer rules

Reviews influence which local business gets the call, and they are also an area where rules have tightened. EU consumer law, applied in the Netherlands and supervised by the Authority for Consumers and Markets (ACM), treats fake reviews and reviews presented in a misleading way as prohibited commercial practices. Businesses that show reviews on their own site are also have to explain if, and how, they verify that reviewers actually bought or used what they review. Your legal advisor can say how these rules apply to you; I design the review routine so that honesty is built in from the start.

In practice:

• All customers get an identical review request, by email, text message or a card at the counter, without first filtering for happy customers.
• No buying reviews, no reviews from staff or family, and no rewards that depend on a positive rating. Google's own policies prohibit incentives for reviews, regardless of local law.
• Replies come from a named person at the location, in clear Dutch, within a reasonable time, including to critical reviews.
• Review widgets on your site show the source and do not hide negative reviews.

Dutch customers also read reviews on independent review platforms and on trade marketplaces where they book tradespeople. I check which of these show up for your important searches and make sure your business details there match your profiles. Replies on every platform are drafted or approved by a native Dutch speaker in your business, so they read as a direct, polite answer rather than translated text.

Calls, WhatsApp and route requests per location

Local search only matters if it produces customers, so measurement has to show which location received which call, chat or visit. Many Dutch customers prefer to message a business on WhatsApp rather than call, and a profile or location page that offers a chat button needs tracking just as much as the phone number.

The setup I put in place, delivered remotely through your web team or agency:

• Website links on each profile tagged with campaign parameters, so map visits can be told apart from ordinary organic sessions.
• Call tracking where the tracked number is listed first on the profile while your normal number stays on as a secondary number, keeping contact data consistent in directories.
• WhatsApp chat clicks measured on profiles and branch pages, plus a prefilled opening message that names the branch.
• Profile performance data per location for calls, route requests and website clicks.
• CRM fields that store the location, source and first contact channel for every inquiry; my CRM consulting covers that configuration.

On Dutch sites, analytics normally runs in full only after a visitor accepts cookies, and the Autoriteit Persoonsgegevens has issued guidance on analytics cookies. Whether your consent banner and tracking setup are compliant should be confirmed by your privacy advisor. Reports separate complete sources, such as profile and call data, from partial ones. I do not promise map positions; distance, competition and Google's own choices decide much of the outcome. My SEO consultant Netherlands page covers the full search strategy; see also the AI search optimization page for the Netherlands or the Netherlands overview.