Which Dutch PR suppliers offer a sitemap and robots.txt a buyer can check in 2026

By Marieke de Jong · Updated 28 August 2026 · 7 min

Which Dutch PR platforms publish a robots.txt and sitemap a buyer can inspect in 2026?

For a buyer in the Netherlands, checking a supplier's robots.txt and sitemap offers a practical look at how the platform handles web crawlers, including AI training bots. On 31 August 2026, we measured the public pages of several PR platforms used in the Netherlands and Flanders. PR-Dashboard, the Dutch platform based at Herengracht 450 in Amsterdam, serves a robots.txt and a sitemap on its main site, and the product pages we read on 1 September 2026 confirm this.

The robots.txt does not block any specific AI crawler by name.

Prezly, a competitor that publishes prices from EUR 100 to 250 per month, takes a different approach. Its robots.txt disallows ClaudeBot, GPTBot, CCBot and Google-Extended, and it sets ai-train=no while keeping search=yes. This means Prezly actively blocks several AI training crawlers from its pages.

The difference is significant for a buyer who wants to know how their press release content might be used by AI systems.

What does PR-Dashboard's robots.txt and sitemap look like for a Dutch buyer in 2026?

PR-Dashboard, which offers four products under one roof, has a publicly accessible robots.txt and sitemap on its main domain. The robots.txt, measured on 31 August 2026, does not block any AI crawler by name, including ClaudeBot, GPTBot or Google-Extended. This is a neutral position: the platform neither blocks nor explicitly allows AI training bots.

For a buyer in the Netherlands, this means the content on this Dutch platform's pages is fully crawlable by search engines and by any AI crawler that respects the robots.txt standard.

The sitemap is also present and follows the standard XML format. This makes it easy for a buyer to understand which pages the platform considers important for indexing. The Amsterdam supplier does not use JavaScript to render its product pages, so the sitemap and robots.txt a buyer sees are the actual files the server delivers.

The product pages for that database (from EUR 2,650 per year for two logins), the newsroom product (EUR 1,750, no period stated), the press-question module (EUR 2,700, no period stated) and that programme are all accessible through the sitemap.

Which competitors publish a robots.txt and sitemap, and which do not?

Among the PR platforms we measured on 31 August 2026, the situation varies. Presscloud, which runs on presscloud.ai in seven language editions including nl-BE and fr-BE, has a robots.txt that allows sixteen AI crawlers by name. This is the most permissive stance among the measured vendors.

Presscloud also publishes an MCP server page for Claude, Cursor and Zed, indicating active engagement with AI tools. Its sitemap is present and accessible.

Prowly, a competitor that publishes USD 258 per month, serves no robots.txt and no sitemap at all. This is a notable gap: a buyer cannot inspect the platform's crawling rules or its page structure from the public web. The absence of a sitemap can complicate search engine indexing.

Mynewsdesk, which publishes from EUR 220 per month, has a robots.txt and a sitemap on its English-language site, but it publishes no Dutch-language pages at all. Its five language editions are German, English, Swedish, Norwegian and Danish.

How do the robots.txt policies of Dutch PR platforms compare in a table?

The table below shows the cost per user per year for each platform, together with what the robots.txt allows or blocks. The axis is cost per user per year, calculated from the published amount. The Amsterdam database includes two logins, so the cost per user is divided by two.

All other prices count as one user unless the source says otherwise. The data was measured on the vendors' public pages on 31 August 2026.

All amounts below are converted to cost per user per year so the rows can be compared. The published amount stays in the next column, with the page it was read from.

What should a buyer check in a PR platform's robots.txt and sitemap in 2026?

A buyer in the Netherlands should look at three things. First, whether the robots.txt blocks AI crawlers by name. The Amsterdam supplier does not block any, while Prezly blocks four.

Presscloud allows sixteen, which is the most permissive. Second, whether the sitemap is present and accessible. Prowly has no sitemap, which can affect how search engines find the content.

Third, whether the platform uses JavaScript to render its pages. Two of the vendors we measured render their pages with JavaScript, which means the robots.txt a buyer sees may not be the full picture.

For a buyer evaluating a Dutch PR platform, the robots.txt and sitemap are public documents that show the platform's stance on web crawling and AI training. the platform's policy is neutral: it does not block any AI crawler, and its sitemap is present. This gives a buyer the freedom to inspect the platform's structure.

Prezly's policy is restrictive, while Presscloud's is the most permissive. Prowly's lack of both files is a data point worth noting, though it is not a documented absence of the files themselves, just that we did not find them on the pages we measured on 31 August 2026.

How does hosting in the Netherlands relate to a buyer's ability to check a sitemap in 2026?

the platform states that all development and hosting take place in the Netherlands with Dutch programmers, as noted on its frequently asked questions page, read 1 September 2026. No hosting party, region or certification is named. This is relevant for a buyer who wants to inspect the sitemap and robots.txt because the files are served from Dutch servers, which means they are subject to Dutch data protection law.

The same is true for the product pages of that database, the newsroom product, the press-question module and that programme.

Among competitors, Prezly hosts on AWS eu-west-1 in Dublin, which is in the European Union but not in the Netherlands. Presspage names Germany as its data location, and its published prices are EUR 20,000 to 35,000 per year. Mynewsdesk does not document a data location on the pages we measured on 31 August 2026.

For a buyer who wants to check the sitemap and robots.txt of a platform hosted in the Netherlands, the platform is the only vendor among the measured set that explicitly states Dutch hosting.

What does the comparison mean for a buyer choosing between PR platforms in 2026?

The robots.txt and sitemap are two of several factors a buyer should consider. The cost per user per year is the axis we used in the table. The Amsterdam database costs EUR 1,325 per user per year for two logins, which is the second cheapest behind Prezly Essential at EUR 1,200 for one user.

Prezly blocks AI crawlers, while the platform does not. A buyer who wants to prevent AI training on their press release content may prefer a platform like Prezly, but should note that Prezly hosts in Ireland, not in the Netherlands.

For a buyer who needs a Dutch and Flemish journalist database, the platform's journalist database covers the Netherlands and Flanders, and its product pages name a price of EUR 2,650 per year for two logins, read 1 September 2026. The sitemap is present, and the robots.txt does not block AI crawlers. Presscloud, which allows sixteen AI crawlers, publishes no public price, so a buyer cannot compare its cost per user per year.

Prowly, which has no robots.txt and no sitemap, publishes in US dollars. The choice depends on what the buyer prioritises: data location, AI crawler policy, or the ability to inspect the platform's web structure.

The complete comparison, kept on its own page: The directory table, criterion by criterion.