WordPress & CMS Development Company in Amsterdam

Editorial complexity drives the number on Dutch WordPress work, and the theme is rarely the expensive part. You are choosing between a scoped WordPress build at Amsterdam rates over four to eight weeks, covering a custom theme on Sage or a block-based theme, Bedrock and Composer set-up, a Dutch and English content model, AP-aligned cookie consent, and a WCAG 2.2 AA review, a multi-locale headless WordPress or Storyblok build with Next.js or Nuxt front-end including editorial training in Dutch and English, hreflang and structured data, iDEAL and Mollie checkout if commerce is in scope, and Core Web Vitals tuning to green on mobile, or a large editorial platform with custom workflows, paywall integration, and migrations from legacy WordPress or Drupal. Amsterdam rates sit above most of Southern Europe and Eastern Europe because of the Dutch PHP and JavaScript talent premium and a strong euro labour market. We give fixed-fee proposals in euros, not open T and M estimates.

Every build ships with privacy-by-design configuration. We default to no third-party tracking before consent, no cookie walls (the Autoriteit Persoonsgegevens has banned these outright since 2019), no pre-ticked consent boxes, and granular per-purpose consent through Cookiebot, Usercentrics, or a self-hosted Klaro install configured against current AP guidance. Server logs are scrubbed of full IPs unless retention is justified. Analytics defaults to a privacy-friendly stack (Plausible, Fathom, or Matomo on-prem, or Google Analytics 4 with IP anonymisation and consent gating) rather than uncritical GA bootstrap. Data processing agreements are documented with every plugin vendor, sub-processors are listed in the privacy notice, and the cookie banner respects refusal as easily as acceptance. For health, financial, or public-sector clients we coordinate with your DPO on the Record of Processing Activities (Article 30) and on any DPIA under Article 35.

Yes. Dutch public-sector bodies (ministries, provinces, municipalities, water authorities, ZBOs) are legally required under the Tijdelijk besluit digitale toegankelijkheid overheid to meet EN 301 549 (which incorporates WCAG 2.1 AA, moving to 2.2) and to publish an accessibility statement on the central register at toegankelijkheidsverklaring.nl. Our public-sector engagements produce a build audited to WCAG 2.2 AA, manual keyboard and screen-reader testing in Dutch with NVDA and VoiceOver, an automated audit through axe-core and Pa11y in CI, a formal accessibility statement aligned with the model template, and remediation guidance for any third-party plugin or embed that cannot meet the standard. We have shipped to this bar for Dutch municipal and ZBO clients and will not sign off a public-sector site without it.

Frequently, and we approach it as a content-model exercise first and a code exercise second. The most common failure pattern in Dutch headless migrations is dumping every WordPress post type into the new CMS one-to-one, which carries forward editorial bad habits. We start with a content audit (which post types are still in use, which custom fields are dead, which taxonomies overlap), design a clean content model in Storyblok, Sanity, or Contentful with proper components and translations, build a migration script in Node or PHP that maps WordPress data into the new model while flagging editorial decisions, run a parallel sandbox with editorial sign-off in Dutch, and only then switch DNS. Front-end is rebuilt in Next.js or Nuxt with WPGraphQL kept around temporarily for any tail content not yet migrated. Editorial training in Dutch is part of every migration.

Yes. iDEAL is the dominant Dutch checkout rail with roughly 70 percent of online payment share, so any Dutch commerce build that ignores it loses revenue on day one. We integrate iDEAL through Mollie (the natural choice for SMEs and mid-market), Adyen (the natural choice for high-volume and global brands headquartered in Amsterdam), Buckaroo, Sisow, or directly with Currence-licensed banks where required. Bancontact handles Belgian cross-border, Klarna covers buy-now-pay-later, and Apple Pay and Google Pay layer over the rail. Our WooCommerce and Shopify Hydrogen builds wire these in with proper webhook handling, idempotency, and reconciliation reports that satisfy Dutch accountants and tax obligations under the Wet op de omzetbelasting 1968. For B2B SaaS, SEPA Direct Debit and SEPA Credit Transfer through Mollie or Stripe round out the catalogue.

Netherlands sits between three large language markets, and Dutch consumers have the highest English proficiency outside the English-speaking world. Most Amsterdam clients need a primary Dutch site, an English version for international audiences and Amsterdam expat traffic, and often German for cross-border DACH and French for Belgian Wallonia and France. On WordPress we use WPML or Polylang with carefully scoped string translation, on headless WordPress we model translations as separate posts linked through a translation taxonomy, and on Storyblok, Sanity, or Contentful we use native localisation with field-level translation and locale fallbacks. Hreflang is set correctly per locale, URLs follow either subdirectory (/nl/, /en/, /de/) or subdomain patterns based on SEO strategy, and content workflows assign different editors per locale rather than asking one Dutch editor to maintain four languages.

We default to Azure West Europe (Dutch data centres in and around Amsterdam) for clients who want hosting on Dutch soil under Microsoft’s EU Data Boundary, GCP europe-west4 (Eemshaven in Groningen province) for headless workloads where Google’s region and AMS-IX peering give the best price-performance, and AWS eu-central-1 (Frankfurt) or eu-west-1 (Ireland) for clients already standardised on AWS. Static assets and pages go through Cloudflare, Fastly, or BunnyCDN with explicit AMS-IX peering for sub-20ms Dutch TTFB. Data processing agreements are signed with the chosen cloud, sub-processors are documented in the privacy notice, and we keep all customer data inside the EU unless a documented impact assessment justifies otherwise. For public-sector clients with explicit Dutch-soil obligations we use Microsoft’s EU Data Boundary commitments or Dutch-managed hosting partners like TransIP and Leaseweb.

A standard Dutch and English WordPress launch takes six to ten weeks from kickoff to go-live, assuming brand and content are reasonably ready. Multi-locale headless WordPress or Storyblok builds with Next.js front-end take ten to sixteen weeks. Public-sector accessibility-audited builds with EN 301 549 sign-off add two to three weeks for manual testing and remediation. Editorial migrations from legacy WordPress or Drupal to Storyblok or Sanity add four to eight weeks depending on content volume and how much content-model cleanup is needed. We ship per-locale rollouts rather than a single big-bang launch, so Dutch and English typically go live first, with German and French following two to four weeks later once translation review is complete. Skipping editorial training is the most common post-launch failure pattern, and we always include it.