Next.js / Astro migration in Brussels

Rebuild Brussels FR NL EN sites on Astro with hreflang, x-default fallbacks, Belgian DPA cookie guidance and a documented URL ledger.

Next.js / Astro migration

Website & application migration in Brussels

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.

My WordPress.org profile

This page is for a Brussels organisation that publishes the same position paper in French, Dutch and English. A Next.js build may handle that through dynamic segments and middleware, but the public site now carries JavaScript weight on pages that are essentially PDF wrappers. I migrate those routes to Astro, keep React only where charts or filters need it, and document every language URL before cutover. All coordination is written; I work from Gdynia.

The Brussels-Capital Region concentrates EU institutions, national member federations and bilingual NGOs whose staff circulate English summaries while legal teams insist on French and Dutch source URLs. Middleware that silently rewrites locale prefixes breaks bookmarked briefings lobbyists filed with the Commission years earlier.

Belgium’s Data Protection Authority (APD) publishes cookie and tracker guidance for citizens at autoriteprotectiondonnees.be. Brussels associations under annual governance review increasingly attach network traces from staging to board packs; I document that non-essential scripts stay behind the CMP before cutover.

When a federation publishes trilingual press rooms, download filenames and BCE footer lines stay stable even if Astro collections replace Drupal nodes. Associations lose member trust faster from a 404 on a French statute PDF than from a temporary ranking fluctuation on an English summary page. I tag Statbel-style identifier blocks in the ledger so French and Dutch footers rebuild on the correct locale template without mixing KBO strings into English press copy. Commission-facing PDF wrappers move to Astro first because they change rarely yet consumed the largest shared JavaScript bundle on the old Next.js site. Walloon and Flemish member microsites keep separate breadcrumb roots so accessibility audits do not conflate unrelated IA trees during the cutover week.

#Three languages, three audiences, one domain

Brussels readers split by language community. A French PDF might be authoritative for Walloon members while Flemish members expect Dutch navigation labels. English frequently serves press and EU institution readers who will not follow French legal vocabulary.

That is not a reason to clone content machines three times. It is a reason to make URL politics explicit. My inventory tags every route with:

TagMeaning in the ledger
fr-BEFrench community primary
nl-BEDutch community primary
enInternational or press facing
pairedPart of a verified hreflang set
monoIntentionally single language

Pairs that are not true translations stay unpaired so Google does not treat them as duplicates.

#x-default when visitors do not match fr, nl, or en

Google’s localized versions guide describes hreflang="x-default" for cases where the site should offer a fallback, such as a language picker or a homepage that is not tied to one country.

Brussels sites often make English the practical fallback for EU officials, but Belgian legal footers may still need French and Dutch routes without forcing English copy into those URLs. I document the chosen x-default URL in the scope and show it in staging headers so communications teams sign once.

<link rel="alternate" hreflang="x-default" href="https://example.com/en/about-the-federation/" />
<link rel="alternate" hreflang="fr-BE" href="https://example.com/fr/a-propos/" />
<link rel="alternate" hreflang="nl-BE" href="https://example.com/nl/over-ons/" />
<link rel="alternate" hreflang="en" href="https://example.com/en/about-the-federation/" />

Return links on each HTML page must mirror the set. I generate them from a central Astro layout so manual <head> edits do not drift.

#Astro i18n without middleware roulette

Astro internationalization settings live in the i18n guide. I mirror your existing folders: common patterns are /fr/, /nl/, and /en/ under src/pages. Dynamic slugs move to content collections keyed by translation IDs.

Next.js middleware.ts locale redirects disappear unless marketing still needs a short list of campaign redirects. Those exceptions are listed with expiry dates so they do not become permanent mystery rules.

#Belgian Data Protection Authority expectations on cookies

The Belgian Data Protection Authority (APD / GBA) publishes citizen guidance on autoriteprotectiondonnees.be covering cookies, trackers, and transparency. Belgium also applies electronic communications rules related to consent for storage on terminal equipment.

When a Next.js _app or root layout imports analytics synchronously, policy pages can fire trackers before visitors interact with a banner. That contradicts how many Belgian teams interpret their cookie policy. On Astro I:

  • Keep publications and statements as static HTML.
  • Load the CMP script in the shared layout once.
  • Mount marketing tags only inside callbacks the CMP exposes.
  • Self host fonts used in French and Dutch diacritics.

I do not draft legal text. I align load order with counsel approved wording.

#Accessibility and document heavy pages

Policy sites lean on long headings and download lists. WCAG guidance from W3C still applies: headings must reflect structure, links must describe the PDF topic, and focus order on language switchers must be keyboard safe. Trilingual switchers often fail when they are client only menus. I build them as plain links in Astro with visible focus rings.

#Performance checks without invented benchmarks

Field metrics are compared only against official Core Web Vitals thresholds on web.dev: Largest Contentful Paint up to 2.5 seconds, Interaction to Next Paint up to 200 milliseconds, Cumulative Layout Shift up to 0.1. I do not promise percentage gains.

Removing full page hydration on 40 page brief libraries typically improves interaction stability because language toggles respond before a router boots. Exact numbers depend on hosting and third party scripts left after consent.

Belgian sites often list BCE or KBO numbers, registered office addresses in Brussels or Ixelles, and VAT identifiers in French and Dutch footers. During migration I keep statutory lines in the language of the page while linking to the shared legal PDF when counsel already hosts one canonical document. Mixing French body copy with Dutch legal labels in the same paragraph is avoided unless your template already survived a compliance review that way.

#WordPress and Drupal residues on older Brussels domains

Before Next.js, many associations ran WordPress or Drupal multilingual plugins. Redirects from that era sometimes linger only in nginx. I import those maps into the Astro cutover ledger so /node/ paths or old /sites/default/files/ media URLs still resolve. Missing media redirects are a common post migration surprise on document heavy sites.

#Press rooms and embargoed PDFs

Embargoed releases sometimes ship as password protected PDFs while the public listing page is crawlable. The ledger marks which listings must stay noindex until publishing time. Astro preview builds can use environment flags so translators review French and Dutch copies on staging without leaking titles to production sitemaps.

#EU institution readers versus Belgian members

English pages often explain positions to EU institution readers while French and Dutch pages speak to member companies. Hreflang still pairs them when the underlying facts match. When English is an executive summary only, I mark the row as partial translation so hreflang does not claim identical coverage.

#EU-only hosting and named subprocessors

If you need EU-only hosting, I list subprocessors and regions in the handover note. Astro static output can sit on any object storage compatible with your DPA. Dynamic islands that call APIs may still leave Belgium depending on backend design; those endpoints are named explicitly rather than hidden inside a shared bundle.

#Search Console property strategy

If you maintain separate Search Console properties per language path prefix, tell me before launch so verification meta tags or DNS tokens move with the Astro layout. Mixed property setups cause false alarm emails after cutover when hreflang is correct but verification files were left on the old Next deployment.

#What to send for a useful first reply

Include your live sitemap URL, a screenshot of the language switcher behaviour today, and whether cookies currently fire on a French policy page before interaction. That trio usually exposes whether the problem is middleware, layout level React, or tag manager placement.

#Cutover ledger for Brussels teams

StepDeliverableOwner on your side
InventoryCSV of routes with language tagsCommunications or web editor
Translation mapKeys linking fr, nl, en slugsContent lead
StagingPassword protected Astro buildEngineering approves access
Redirect rehearsalEdge rules for retired sectionsHosting partner
Post launchSearch Console checks per localeSEO or agency

Rollback keeps the prior Next.js artifact deployable until each locale shows stable redirect errors below your internal threshold.

#React islands for charts, not for press releases

When a page needs a live vote tracker or membership statistics, I wrap the React chart as an island with client:visible. The surrounding narrative stays static for citation friendly URLs. If the data is annual PDF only, the island is dropped to avoid unnecessary JavaScript.

#Translators and slug ownership

French and Dutch editors often want different headline rhythm even when facts match. I store a shared translationKey in the CMS or collection schema so hreflang pairs stay machine checkable while slugs remain human readable per locale. English summaries can share the key without sharing the French slug text.

#Security headers and third party embeds

Institutional pages sometimes embed videos or social timelines. Each embed is listed with its cookie impact so counsel can decide whether it belongs behind a click to load wall. Astro makes that pattern straightforward: static placeholder HTML, script injected only after consent or explicit user gesture.

#Measuring success after launch

I compare redirect errors, hreflang validation in Search Console, and consent log samples for one week post cutover. Rankings may fluctuate while Google recrawls; lasting damage usually traces to missing 301s or changed titles, which the ledger is meant to prevent. I document the baseline screenshots you provide so comparisons stay factual rather than anecdotal.

#Written enquiry

Reach me through the contact page with your domain, which languages are live today, and whether x-default already exists in your templates. I will answer in writing with a hreflang matrix, cookie load plan, and phased Astro build order before code changes land in your repository.

List any PDF that parliamentary assistants cite by fixed URL. Those permalinks receive priority in the first redirect rehearsal so a framework upgrade does not become a political communications incident during plenary week.

If your communications team maintains separate newsletter domains, mention whether UTM conventions must stay byte identical after migration so attribution dashboards do not break on the first send after launch. Include one example campaign link from each language if available so I can verify query strings survive the Astro router unchanged.

See also in Belgium

Need this service: Next.js / Astro migration in Brussels?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Explore other WordPress services and knowledge base