GEO Consultant, Netherlands

What makes a Dutch page worth citing

Assistants such as ChatGPT search, Perplexity, Copilot and Google's AI features build answers from retrieved pages. How they pick those pages is not published, but cited pages tend to share visible traits: they make a specific statement, they make it early, and the statement can be checked. In a Dutch company, the material that fits that description often sits where no crawler can read it, in quotations, project files, installation manuals and the heads of experienced staff.

GEO work begins by finding that material. Useful questions include:

• Which questions do your sales engineers answer again and again on calls?
• Which calculations do you run for customers that could be explained as a method, without publishing customer figures?
• Which terms do buyers misunderstand, in Dutch or in English?
• Where do customers weigh you against a different approach, not just a rival supplier?

Original data counts only if you genuinely hold it and are willing to publish it. Survey results, aggregated service observations or test outcomes can make strong reference pages, but they must be real, current and approved internally. I will not invent data or present opinion as research. If there is nothing original to publish yet, clear definitions and honest method pages are a sound place to start.

Citation-friendly structure for reference pages

A model quotes passages, not whole pages. A passage survives quotation when it makes sense on its own, so I write and edit reference pages with that in mind:

• Statement first. Each section opens with the definition, rule or conclusion, followed by conditions and exceptions.
• One idea per section. Headings name the question or concept, so a retrieval system can match a query to the right part of the page.
• Tables for comparisons. Criteria in rows, options in columns, with the same criteria applied to every option.
• Numbered steps for methods. Each step names an action and its result.
• Named authors and review notes. A visible author with relevant expertise and a note of when the page was last checked.

Schema reinforces this structure; it cannot substitute for it. Article, Organization and, where accurate, FAQ or HowTo markup should describe what is visible on the page and nothing more. Whether a search engine shows any rich result for it is a separate matter I do not promise.

Dutch writing has a specific trap here: long compound nouns and passive constructions can make a sentence correct yet awkward to quote. Native editors on your side keep the Dutch natural while still putting the key statement first. For the wider picture of how assistants describe your company, see the AI search optimization page for the Netherlands.

Outside sources Dutch assistants tend to draw on

Your own site is only part of an answer. For Dutch business questions, assistants often cite pages from outside the company: sector association guidance, trade magazines, regional news sites, comparison and directory platforms, public registers and knowledge pages from semi-public bodies. The mix differs by sector and by tool, which is why the citation log records it instead of assuming it.

GEO does not mean trying to appear in every one of those sources. It means understanding which ones shape answers on your topics and asking where you have a legitimate reason to contribute:

• An association knowledge base that accepts technical explanations from members.
• A trade publication interested in a practical article from your specialist.
• A directory or comparison listing that describes your service incorrectly and can be corrected.
• A supplier or customer willing to publish a joint project description with accurate facts.

Paid placements dressed as editorial content, link schemes and fabricated reviews are excluded. Beyond the ethical problem, such tactics can be discounted by the systems they aim to influence, and they erode trust with Dutch buyers who check where a claim came from. Where your sector has a standard-setting body or inspection regime, the strongest move is usually to explain clearly, on your own pages, how you work within it, and leave any endorsement to that body.

Dutch and English sources that say the same thing

Many Dutch companies publish in both languages, and the versions drift apart. The Dutch page gets the new delivery terms while the English page keeps the old ones, or an English product sheet still lists a service that was discontinued. An assistant asked in English may cite that English page and repeat outdated facts, while the same question in Dutch gets a correct answer. Assistants also read across languages, so a Dutch answer can quote an English source, or a Flemish page from a distributor.

I check parity on the pages that matter for citations:

• The same core statements, definitions and limits in both versions, written naturally rather than translated word for word.
• Matching tables and specifications, with units and terms each audience expects.
• Hreflang pairs and canonicals that point each version to its counterpart, so neither looks like a duplicate.
• An agreed source of truth, often the Dutch page, with a rule that the English version is updated at the same time.

If you also serve Flanders, Belgian wording and context may need their own version; the GEO page for Belgium looks at that side of the border. Your Dutch writers, in-house or external, own the Dutch wording, while the research, structure and parity checks come from me.

Fresh facts, a citation log and the limits of GEO

A page that was accurate when published can become a liability once it is cited. Prices, lead times, regulations, subsidy schemes and product ranges change, and assistants may keep quoting the old version until they retrieve the page again. I set up a simple expiry register: each reference page lists the facts likely to change, who owns them and which event triggers a review, such as a price update or a change in Dutch rules. Where regulation, tax or GDPR questions are involved, your advisor should check the content before publication.

Progress is tracked with a citation log. A fixed set of Dutch and English prompts is rerun on a schedule in the tools your buyers use. Each run records whether your pages are cited, which outside sources appear and whether the statement attributed to you is still correct. Answers vary between runs, so the log shows direction over time, not a score. An inquiry source field on forms and in your CRM makes AI-influenced leads visible as well.

GEO has clear limits. It cannot force any tool to cite you, cannot rewrite what a model absorbed during training and cannot make up for a weak offer or thin expertise. It can make genuine knowledge easy to find, quote and verify. For the question-and-answer side of the same work, see answer engine optimization in the Netherlands; the Netherlands overview lists my other remote services there.