Next.js / Astro migration in Aalborg

Rebuild Aalborg B2B and industrial sites on Astro or Next.js with Danish accessibility law, WCAG aligned templates, da en URLs and a written migration scope.

Next.js / Astro migration

Website & application migration in Aalborg

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 Aalborg

My WordPress.org profile

North Jutland companies that publish long technical pages for offshore wind, district energy, maritime suppliers, or AAU-linked hardware often built the public site on Next.js while WordPress, Umbraco, or a headless CMS still feeds the content. The combination works until marketing asks for faster LCP on mobile networks, until a Danish customer sends an accessibility questionnaire, or until Datatilsynet questions analytics that load before cookie consent. I plan and execute migrations to Astro or, where authenticated areas need it, a split with Next.js on the same domain, from Gdynia, in writing only.

The clusters around NOVI Science Park, Port of Aalborg, and Aalborg University are typical buyers: English datasheets for export, Danish compliance pages for home authorities, and specification tables that must not break when QR codes on equipment still point at legacy paths.

Port of Aalborg describes itself as Northern Jutland’s largest logistics hub and ties its strategy to Aalborg Municipality business and sustainability goals on the waterfront.

#What Danish accessibility law expects from a B2B web surface

Denmark transposed the European Accessibility Act through the Act on accessibility requirements for products and services (Act No. 801 of 7 June 2022), published on retsinformation.dk. The act targets defined product and service categories rather than every corporate blog post. For many Aalborg firms the relevant question is whether the website is the customer facing channel for a covered service, for example certain e-commerce flows, consumer facing terminals, or digital services within the act’s annexes.

I do not guess your legal category. In the written scope I list the pages that act as sales, ordering, support, or account entry points versus pure investor relations. For pages inside the duty, technical work aligns with EN 301 549 style expectations, which trace back to WCAG 2.x principles documented by W3C. That means real headings instead of styled divs, visible focus states, text alternatives for informative images, and forms that label mandatory fields in both Danish and English where both locales exist.

Public sector sites in Denmark follow separate digital accessibility standards overseen by Agency for Digital Government (Digitaliseringsstyrelsen) under the Ministry of Digitisation. Private B2B sites do not copy public sector manuals blindly, but the same WCAG vocabulary is what procurement officers and OEM partners increasingly paste into vendor checklists.

#Why a global Next.js hydration layer works against those audits

Next.js can render HTML on the server, yet many App Router projects still ship a large client bundle so navigation, analytics hooks, and design system providers hydrate on every route. For a datasheet that is mostly tables and downloads, that work buys little function.

Screen reader and keyboard audits then surface repeating problems: focus traps inside client only menus, buttons that exist only after hydration, route changes that skip a proper page title update, and color contrast bugs inside CSS in JS bundles. Google’s field metrics add commercial pressure: official Core Web Vitals thresholds on web.dev treat Largest Contentful Paint up to 2.5 seconds, Interaction to Next Paint up to 200 milliseconds, and Cumulative Layout Shift up to 0.1 as the “good” band. Hydration on a 200 row parameter table works against the interaction budget even when the copy is technically correct.

Astro compiles each route to HTML first. Interactive pieces stay optional islands. Astro’s accessibility guide documents built in checks such as enforcing alt text on images handled through Astro assets. That does not replace manual keyboard review, but it stops the easiest regressions from reaching staging unnoticed.

#Rebuilding the Aalborg public layer without losing Nordic URLs

Industrial sites in North Jutland rarely publish in Danish alone. Export facing English paths often sit beside Danish originals. Losing parity during a framework change hurts both search and partner trust.

My first deliverable is a URL ledger built from four inputs: the Next.js repository routes and redirects, XML sitemaps, server access logs for PDF and API paths, and Search Console coverage exports. Each legacy address gets a decision row: keep path identical on Astro, merge into a new canonical with one 301, or retire with a documented reason.

For language pairs I emit reciprocal hreflang links on staging and verify return links. I do not promise unchanged rankings; I do promise that crawlable HTML, canonical tags, and redirect targets are intentionally mapped before DNS moves.

When WordPress remains the CMS, content APIs stay stable while the theme layer moves. The WordPress REST API handbook defines the fields I type in Astro content collections so editors keep familiar admin screens.

#Cookies, fonts, and scripts under Danish supervision

Personal data on Danish sites sits under GDPR and the Danish Data Protection Act enforced by Datatilsynet. Storage of and access to information on a user’s device through cookies or similar technologies is additionally governed by the Cookie Executive Order and sector guidance from Erhvervsstyrelsen and the consumer ombudsman. These tracks interact: a migration is a good moment to remove next/font Google CDN calls and self host subsets that include Danish letters, and to ensure analytics stays behind the same consent callback your legal team already approved.

I do not install a new consent manager unless you ask. I do make sure global React effects cannot fire tags before the CMP allows it, because that issue is structural in many Next.js layout files.

#Staged cutover pattern for an Aalborg build

PhaseWhat you see on stagingWhat I verify before the next phase
InventorySpreadsheet of every live URL, locale, and assetNo mystery 404s on PDF or CAD paths
Template parityDanish and English layouts with real CMS dataKeyboard path through nav, search, and primary forms
Performance snapshotCrUX linked field where availableLCP, INP, and CLS against web.dev thresholds
Redirect rehearsalEdge rules for renamed sections onlySingle hop 301, no chains
Go live windowDNS or proxy switch with rollback stepsSearch Console fetch on critical URLs

Rollback means keeping the previous Next.js build deployable until the measurement window finishes, not a vague promise.

North Jutland product pages often push visitors toward large PDF datasheets, STEP files, or conformity declarations. Accessibility law still matters on the HTML wrapper: the download control needs a descriptive link name in Danish and English, icons need text equivalents, and filterable specification tables need header cells that screen readers can associate with data cells. During migration I rebuild those tables as semantic HTML in Astro rather than spreadsheet exports pasted into client components.

Binary files usually keep their existing URLs on object storage or CDN paths. The URL ledger marks each asset host separately so a theme change does not break signed URLs or cache keys.

#Mandatory business identifiers on Danish sites

The Danish Commerce and Companies Act and the E-Commerce Act require identifiable trader information on commercial websites. For an ApS or A/S in Aalborg that typically means registered name, North Jutland address, CVR number, and contact channel visible without opening a modal. I render those fields in the global footer at compile time so they appear on every locale and are not hidden inside client only drawers.

If your legal template already lists terms in Danish with an English summary, the migration preserves both versions and records which URL is canonical for each language.

#Astro versus Next.js on the same Aalborg domain

Marketing, documentation, and compliance libraries usually belong on Astro with zero client JavaScript by default. Authenticated distributor areas, MitID broker handshakes, or live ERP stock calls may still need Next.js server routes or another backend app. The written scope names which host serves which path prefix so cookies and content security policies stay coherent.

Graphic design stays with your team or agency; I implement Figma or existing CSS inside Astro components. I do not run workshops on site in Aalborg; reviews happen through staging URLs and annotated screenshots.

#What to prepare before I start the URL audit

You can speed up the first written reply by sending a spreadsheet of priority URLs (top products, compliance statements, careers, investor pages), the name of your consent management platform, and whether Danish or English is the editorial master. If an accessibility audit report already exists, attach the failing URLs so I can tie fixes to concrete templates rather than generic advice.

After cutover I keep a short monitoring checklist: Search Console coverage for both languages, redirect error reports from your CDN, consent logs for a sample week, and manual keyboard retest on the templates that changed most. That window is when I answer questions about regressions in writing, still without scheduling calls.

If your team already publishes through a design system in Figma, I map components to Astro partials once so later CMS entries inherit accessible defaults instead of one off page fixes. The first estimate for that mapping is free once I have read access to the repository or a static export of the current Next.js site.

#Written enquiry

Send a message through the contact page with your live URL, current CMS, whether you publish in Danish, English, or both, and any accessibility review deadline from a customer or authority. I will reply in writing with a migration outline: URL counts, framework split, consent and font changes, and the verification gates I run before cutover.

WordPress support & development in Aalborg

See also in Denmark

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

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

Describe your project

Explore other WordPress services and knowledge base