Website & application migration in Amsterdam
I migrate sites from WordPress, Joomla, Drupal, Angular, Vue and other technologies to Astro and Next.js. I plan each migration to keep SEO, content and features intact and switch over in an agreed window. I work alone and have years of experience with both legacy and modern stacks.
- I have had a wordpress.org account since 2006.
- I contributed to WordPress core for versions 7.0 and 7.1.
- I maintain 30 plugins on wordpress.org.
- I organise and speak at WordCamps.
- I have attended every WordCamp Europe from 2017 to 2026.
- Local WordPress meetup: WordPress Amsterdam
This page is for an Amsterdam company that publishes investor and partner content in English while campaigns and compliance pages stay Dutch. Next.js may have made sense when the product dashboard was already React, but the marketing layer now pays a hydration cost on every static blog post. I rebuild those public routes on Astro, or split Astro and Next.js by path, from Poland, with project communication in writing only.
Amsterdam Trade & Invest, on iamsterdam.com/en/business/setting-up, reports that more than 3,500 international companies have invested in the Amsterdam metropolitan area. Dutch filings and English investor decks often share one hostname, so I lock /nl/ compliance URLs in the scope spreadsheet before any Astro route generator runs.
Randstad teams also accumulate decade-old campaign paths embedded in printed annual reports. Those rows stay keep unless counsel approves a 301, because Dutch regulators and ad buyers reopen the same URLs long after middleware experiments end. Staging checks fail if an English investor path redirects twice before resolving.
Dutch and English URLs without middleware guesswork
Locale detection in Next.js middleware is convenient until Marketing needs a fixed Dutch URL for a regulator filing while Growth wants an English landing page for the same product. Middleware redirects hide the true address from editors and break UTM tracking when the default locale changes.
Astro documents internationalization in the i18n guide. I set defaultLocale and locales in astro.config.mjs, then place routes where your sitemap already expects them. If the live site uses /en/ and /nl/ prefixes, I keep that shape so external links survive.
| Decision | What I document in the scope | Why it matters for Amsterdam teams |
|---|---|---|
| Prefix vs subdomain | Final hostname pattern | Ads and press releases embed URLs years later |
| Default locale | Which folder omits a prefix if any | Affects canonical and x-default |
| Fallback page | Which URL carries x-default | Google uses it for unmatched languages |
| Retired locales | 301 targets for old /de/ tests | Prevents silent 404s on former experiments |
Google’s localized versions documentation requires reciprocal hreflang links. During staging I crawl both language trees and fail the build if a Dutch page points to English without a return link.
Article 11.7a and the Autoriteit Persoonsgegevens
The Netherlands implements EU privacy rules through the GDPR implementation act (UAVG) supervised by the Autoriteit Persoonsgegevens. Cookie and similar technologies additionally fall under Article 11.7a of the Telecommunications Act on wetten.overheid.nl. Paragraph one requires clear information and consent before storing or reading information on a user’s device.
Many Amsterdam Next.js sites load Tag Manager or analytics inside a root layout useEffect. That pattern often fires before a consent banner records a choice, which creates complaints risk under AP enforcement. During migration I:
- Move marketing routes to static HTML with no default client bundle.
- Load non essential scripts only through the CMP hooks your legal team already approved.
- Self host fonts instead of pulling them from a third party CDN on first paint.
I do not replace your Data Protection Officer’s policy text. I do make the technical load order match the policy.
When Astro fits Amsterdam marketing and when Next.js stays
Content libraries, pricing explainers, API guides, and event pages are ideal Astro candidates because they are read mostly linearly. They benefit from compile time data fetching from Sanity, Contentful, Storyblok, or headless WordPress without shipping a router to every visitor.
Keep Next.js where there is real session state: logged in client portals, interactive pricing for complex SKUs, or onboarding wizards. The scope diagram lists path prefixes so cookies and security headers stay consistent across both runtimes on one domain.
Official Core Web Vitals thresholds on web.dev remain the neutral performance language I use in acceptance: Largest Contentful Paint up to 2.5 seconds, Interaction to Next Paint up to 200 milliseconds, Cumulative Layout Shift up to 0.1 in field data where you already measure it.
Inventory before any template rewrite
Randstad teams often accumulate locale experiments: /en-eu/ microsites, /nl-nl/ duplicates, or next.config.js redirects from old WordPress slugs. My inventory merges:
- Git routes and dynamic segments from the Next.js tree (Next.js docs for reference when reading your repo).
- Live sitemap URLs and lastmod dates.
- Search Console performance exports filtered by page.
- A sample of paid search final URLs your agency still buys.
Each row gets: keep, merge with 301, or deprecate. Only then do I scaffold Astro layouts so editors still recognize preview URLs.
Hreflang and structured data on bilingual launches
I generate <link rel="alternate" hreflang="..."> elements in a shared layout component so translators cannot forget return links. For pages that exist in Dutch only, I either add hreflang="nl-NL" without a fake English twin or mark the page as intentionally monolingual in the ledger so SEO stakeholders sign off.
Schema.org Organization and WebSite JSON-LD is rendered server side in Astro, matching your legal entity data in Dutch and English footers. I do not duplicate FAQ schema in MDX; the inline FAQ at the bottom of this page is the source for visible answers.
Payment and commerce adjacent routes
Amsterdam fintech and SaaS sites sometimes embed iDEAL or card flows inside React islands. Those components can remain islands while surrounding copy is static. The scope states which pages carry payment data so PCI and consent boundaries stay with your compliance team.
Example Astro layout for nl and en press releases
The snippet below is illustrative for a bilingual news template. Paths follow the folder structure agreed in the scope, not a generic starter:
---
// src/pages/nl/pers/[slug].astro
import Base from '../../../layouts/Base.astro';
import { getNews } from '../../../lib/cms';
const { slug } = Astro.params;
const item = await getNews(slug, 'nl');
const enPath = item.translationEnPath;
---
<Base lang="nl-NL" alternates={{ en: enPath, nl: Astro.url.pathname }}>
<article>
<h1>{item.title}</h1>
<p>{item.dek}</p>
</article>
</Base>Base.astro centralizes hreflang link elements so translators cannot ship a Dutch page without its English return path.
Legacy redirect rules hidden in config
An older domain may still carry redirect maps from a previous CMS. Those rules hide inside next.config.js, nginx, or Cloudflare. I extract them before building Astro output because a framework migration is when duplicate redirect tables usually surface. Conflicting 301 chains hurt crawl budget on bilingual sites more than monolingual ones because Googlebot fetches both locales.
Hosting and processor list for AP questionnaires
Autoriteit Persoonsgegevens questionnaires often ask which processors touch IP addresses on page load. Static Astro hosting on an EU region with self hosted assets gives a shorter subprocessors table than a layout that pulls fonts, tags, and A/B frameworks from mixed regions. I list CDN nodes, form endpoints, and preview hosts separately in the handover document so your privacy team can paste answers without reverse engineering the repo.
Staging reviews your growth team can run without a call
I publish staging behind basic auth or VPN as you prefer. Marketing can click Dutch and English pairs side by side, verify language switchers land on the correct canonical, and confirm UTM parameters survive. Growth can run their own tag assistant walkthrough against the CMP flow. Engineering receives a redirect CSV to diff against production.
Rollback and launch sequencing
Launch uses a rehearsed order: freeze redirect edits, deploy Astro build, switch proxy target, run automated link checker, then watch Search Console for both locales. If critical paid URLs fail, rollback means pointing the proxy back to the previous Next.js deployment within the agreed window, not rebuilding from scratch. The scope names who holds DNS access and where the previous build artifact lives.
Why not only optimize the existing Next.js bundle
Tree shaking and image tuning help, but they do not remove the root layout client graph. When INP complaints come from content editors testing on laptops rather than from app users, the issue is usually global providers on pages that do not need them. Splitting Astro for marketing and Next.js for the product area addresses that structural split directly.
Dutch copy quirks that affect slugs and metadata
Compound words in Dutch titles can produce long slugs if editors auto generate them from headlines. During migration I align slug rules with your analytics naming so /nl/ paths stay short enough for sales decks. English slugs sometimes stay Latin while Dutch navigation labels remain fully localized; both versions still participate in hreflang as long as the content is a true translation pair.
Legal footers in the Netherlands often reference KVK numbers and BTW identifiers. I keep those visible in Dutch footers and mirror the essentials in English footers without mixing languages inside one paragraph unless your counsel already approved that pattern.
Seasonal campaigns around Amsterdam events sometimes spawn temporary /en/ landing pages. I tag them in the URL ledger as time boxed so hreflang pairs return to the evergreen product page when the event ends, avoiding orphan English URLs without Dutch siblings.
Collaboration model
Graphic design and wireframes come from your studio. I implement them in Astro components and keep spacing tokens aligned with your Figma file. I do not offer video calls or on site days; feedback flows through email or your ticket system with staging links attached.
Written enquiry
Use the contact page with your domain, how Dutch and English are split today, which CMP you use, and whether middleware currently auto redirects browsers. I will reply with a bilingual URL map, hreflang plan, and the Astro i18n configuration I propose before any code merge.
Attach two example URLs in each language if you already know which pages matter most for organic traffic or regulatory disclosure. That lets me prioritize hreflang pairs in the first staging build instead of migrating low traffic experiments first.
If you run separate properties in Google Search Console for example.nl and example.com, tell me which hostname stays canonical after migration so Analytics and Search Console tags move in the same pull request as the hreflang layout. The first written reply after that review is free once I can crawl staging or production without breaching your access policy, NDA limits, vendor pen test restrictions, or client confidentiality markings on PDFs.
Selected projects
Examples of my work.
E-commerce Development: pluginfinance.com
pluginfinance.com is a modern, highly scalable WordPress-based service dedicated to showcasing and distributing financial plugins. The project was designed w...
E-commerce Development: radio.friko.pl
Radio.friko.pl is an internet radio station that operated between 2005 and 2010 as part of the Friko.pl platform, offering users access to music streaming, l...
E-commerce Development: terazjemy.pl
Terazjemy.pl is an online platform designed to promote a healthy lifestyle by providing users with practical information, recipes, and tips on balanced nutri...
WordPress support & development in Amsterdam
See also in Netherlands
Need this service: Next.js / Astro migration in Amsterdam?
Describe your project by e-mail. I reply within 48 hours.
Describe your projectExplore other WordPress services and knowledge base
Migration to Astro, Next.js, and headless WordPress.
WooCommerce sync with ERP and wholesale systems.
Business process automation around WordPress and company systems.
Library of concrete automation use cases.
Headless WordPress, Sanity, Strapi, and Contentful with Astro or Next.js.
Astro, MDX, edge delivery, and Core Web Vitals measured on real traffic.
Custom WordPress engineering and architecture.
Scalable headless, ERP, and AI architecture for enterprise.
Related categories
Supporting articles

Six to sixteen weeks for typical engagements, with a four-phase shape: discovery, scoping, build and cutover, tuning. The variables are catalogue size, integration count, URL preservation, and editorial team readiness, not framework choice.

A definitive 4-year Total Cost of Ownership (TCO) analysis, real-world Core Web Vitals benchmarks, Astro 7 GraphQL APQ architecture, and a 10-point executive decision matrix for choosing between decoupled and traditional WordPress.

The Shopify Plus vs WooCommerce headless decision in 2026 is no longer a binary "platform vs custom" trade-off. Both can run headless, both integrate AI, both ship at the edge. The real axes are control, total cost over five years, and exit strategy. This article walks the matrix with confirmed platform facts.