Web Development Company in Amsterdam

Checkout and supervision separate one Amsterdam web budget from another far more reliably than design ambition does. Projects land as a scoped marketing site at Amsterdam rates over six to ten weeks, covering Next.js or Astro, headless CMS (Storyblok, Sanity, Contentful), Dutch and English localisation, AP-compliant analytics, and Core Web Vitals targets, a mid-sized commerce site with iDEAL plus Apple Pay plus Google Pay checkout, search, and product content, or a production-grade web application with custom backends, multi-tenant logic, EU DORA controls, and DNB-supervised payment functionality. Amsterdam rates sit above Rotterdam and Eindhoven because of the Booking.com, Adyen, and Bol.com talent premium. We give fixed-fee proposals rather than open T and M estimates, billed in EUR with Dutch BTW (21 percent) applied where required.

The Autoriteit Persoonsgegevens (AP) ruled in March 2019 that cookie walls (where access to a site is conditional on accepting tracking cookies) are unlawful under GDPR, because consent cannot be freely given. This is one of the strictest interpretations in the EU and shaped how Dutch sites design consent. Our default pattern is cookieless analytics through Plausible or PostHog (EU-hosted) for first-party measurement, with Google Analytics 4 or Meta Pixel only loaded after explicit opt-in through a Cookiebot, OneTrust, or Iubenda CMP. We design clear reject-equals-accept UX, ship a publicly accessible cookie register, and keep consent logs to defend against AP complaints. Functional cookies (cart, language, session) run under legitimate interest without consent prompts.

Yes. iDEAL settles the majority of Dutch online retail transactions and the new iDEAL 2.0 / Wero rollout under the European Payments Initiative is extending it across the EU. We integrate through Adyen Web Drop-in or Components (the reference Amsterdam standard, patterned after Adyen’s own enterprise clients), Mollie when SMB-friendly hosted checkout fits, or Buckaroo and Worldline for higher-volume contracts. Apple Pay on the web uses Apple Merchant ID and merchant validation, Google Pay uses the Google Pay JavaScript API, Bancontact is wired for Belgian users, and Klarna or Riverty (formerly Afterpay) is layered for buy-now-pay-later. PSD2 / PSD3 strong customer authentication is enforced through the bank-side flow.

The EU Accessibility Act (EAA) came into force on 28 June 2025 and is transposed in the Netherlands through the Tijdelijk besluit digitale toegankelijkheid and related frameworks. It applies to consumer-facing digital services including e-commerce, banking, telecoms, transport ticketing, and e-books, on top of the existing Dutch public sector accessibility regime that has been in force since 2018. Our builds target WCAG 2.1 AA as baseline, with keyboard navigation, screen reader testing (NVDA, JAWS, VoiceOver), sufficient colour contrast, scalable typography, captions on video, and form-error clarity. We deliver an accessibility statement (verklaring), a conformance report, and a remediation roadmap. Dutch market surveillance authorities can enforce non-conformance, and we have built remediation programmes for clients caught flat-footed by the 2025 deadline.

Yes. The EU Digital Services Act (DSA) applies to all platforms accessible in the EU, with stricter rules for very large online platforms (VLOPs) and very large online search engines (VLOSEs). Bol.com, Booking.com, and similar Dutch operators sit in or near VLOP scope. We build DSA-compliant features: notice-and-action mechanisms, internal complaint handling, trader traceability under the trader transparency obligations (effective from February 2024 for all platforms allowing distance contracts), ranking transparency, and content moderation logs. For Big Tech marketplaces under the EU Digital Markets Act (DMA), we build to the gatekeeper interoperability and self-preferencing prohibitions where relevant. AP and the European Commission share enforcement reach.

Next.js is the default choice for most Amsterdam web projects because the App Router with React Server Components ships sub-second TTFB on Dutch broadband and most teams hire fluently against the React ecosystem; Booking.com and Adyen run substantial React. Remix fits when nested routing maps cleanly to the data model and the team is React-fluent. Astro is the right call for content-heavy marketing sites where partial hydration keeps JavaScript payloads minimal and Core Web Vitals targets are aggressive. SvelteKit is a sharp choice when the team has Svelte taste and bundle size is critical. We will recommend honestly based on the team you actually have and the content vs interactivity mix, not based on which framework we want to bill more hours against.

Most Dutch sites need parallel Dutch and English content for domestic plus expat and international audiences. We default to subdirectory localisation (/nl and /en) over subdomains, with hreflang tags wired correctly and Dutch-first canonical URLs for the .nl ccTLD where the brand has one. Keyword research uses Google.nl (which dominates Dutch search at over 95 percent share, well above the global Google average) plus Ahrefs and Semrush. Technical SEO includes XML sitemaps with hreflang, schema.org Organization and Product markup, BreadcrumbList JSON-LD, Open Graph and Twitter Cards for social, and AMS-IX-proximate edge caching to keep TTFB under 200ms for Dutch users. We also handle Google Merchant Centre feeds for Dutch e-commerce and review schema for the Trustpilot and Kiyoh ecosystem.

Default hosting is AWS eu-west-1 (Ireland) or eu-central-1 (Frankfurt), Azure West Europe (Amsterdam data centres, which we pitch when clients want literal Amsterdam-local hosting), or GCP europe-west4 (Eemshaven, NL, on Dutch grid green energy and a notable sustainability story). For edge serving we use Cloudflare with its Amsterdam POP, Vercel Edge, or AWS CloudFront with its AMS-IX-proximate edge locations. For DNB-regulated payment workloads we stay strictly EU and document the choice in the DPIA. For public sector work we follow Rijksoverheid cloud guidance and the recent Dutch government policy direction on cloud risk assessment. Schrems II Transfer Impact Assessments are completed for any US-headquartered provider, even when EU-region.