Next.js / Astro migration in Gothenburg

Migration to Astro & Next.js in Gothenburg. I move sites from WordPress, Joomla, Drupal and other CMSs with a URL map, 301s, hreflang for Swedish and English, and a staged cutover.

Next.js / Astro migration

Website & application migration in Gothenburg

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 Göteborg Meetup

My WordPress.org profile

Gothenburg is Sweden’s second-largest city, on the west coast at the mouth of the Göta älv, with about 600,000 people in the city and about 1.1 million in the metropolitan area. Its port is the largest in the Nordic countries, and the city’s economic development agency names life science, mobility, technology, electrification and deep tech among its strong sectors, anchored by research and innovation hubs such as Lindholmen Science Park, Johanneberg Science Park, and GoCo Health Innovation City in Mölndal. Many companies here run websites that grew for years on WordPress, Joomla or Drupal, often in Swedish and English. When that stack becomes slow, hard to update or risky to patch, a move to Astro or Next.js can fix it. As an independent developer working remotely in writing from Gdynia across the same Central European Time zone, I run that move myself and verify every detail so search traffic survives it.

#When is moving off WordPress to Astro or Next.js worth it for a Gothenburg business?

A migration pays off when the underlying CMS architecture is the bottleneck rather than a single slow plugin or an underpowered hosting plan. Typical signs: pages rebuilt on every request for content that changes once a month, an admin that editors avoid, plugin updates that break the theme, or security patches nobody applies on time. If cleaning up plugins and adding a page cache would solve it, I say so and the migration does not happen.

Astro suits content sites: service pages, product documentation, blogs, multilingual corporate sites, and supplier directories. It ships static HTML by default and adds JavaScript only where a component needs it, making it straightforward to stay well within Google’s official Core Web Vitals thresholds (LCP up to 2.5 s, INP up to 200 ms, CLS up to 0.1). Next.js suits sites with logins, customer portals, dealer dashboards or heavy server rendering. Both can read content from a headless CMS, from Markdown files in Git, or from the old WordPress REST API during the move.

#How does a migration to Astro or Next.js work, step by step?

  1. URL inventory. I crawl the current site and export every indexable URL, plus the URLs that get links or traffic according to your Search Console and analytics. Redirects from earlier redesigns go on the list too, along with technical PDFs, safety data sheets and CAD specification files that industrial buyers bookmark directly.
  2. URL map. Every historical address receives one explicit destination: keeping its current path, forwarding via a direct 301 redirect, or returning an intentional 410 status when retired permanently. That mapping is delivered both as an auditable spreadsheet and as the production edge routing file. No chains, and no sending everything to the homepage.
  3. Content model. Legacy post types, custom fields, taxonomy terms and navigation trees are converted into strictly typed schemas. This is where hidden problems surface: page builder shortcodes, images embedded in HTML, translations linked through a plugin table rather than a shared ID.
  4. Structured data. Organisation, breadcrumb, article, product or FAQ markup is generated from the same fields as the visible page, so the two cannot drift apart.
  5. Languages and hreflang. Each Swedish or English page links to all its translations and to itself. If you target Sweden specifically, the Swedish version can use sv-SE; if you target Swedish speakers anywhere, sv is enough. I generate these links from the content model and test that every pair is reciprocal.
  6. Staging and parity checks. Before launch I compare old and new pages field by field: title, meta description, canonical, H1, structured data and internal links. Each difference is fixed or documented.
  7. Staged cutover. On larger sites the new frontend takes over one section at a time, with edge rules sending the rest to the old system, whereas compact sites transition in a single coordinated switch.
  8. Search Console after launch. I register the updated XML sitemaps, monitor coverage in the indexing report and verify a representative batch of redirected addresses. If the domain or subdomain changes, I file a Change of Address request, as Google’s site move guide describes.

#Gothenburg industrial and technical sectors: where headless architecture pays off

Enterprises operating across Västra Götaland manage distinct web requirements shaped by international supply chains and R&D collaboration:

  • Automotive, Electrification and Mobility Suppliers: Tier-1 and Tier-2 engineering firms clustered around Lindholmen Science Park and Hisingen publish thousands of technical specifications, compliance certificates, and multilingual product sheets. Moving these libraries from bloated monolithic databases into typed Astro content collections guarantees fast global delivery and eliminates broken shortcode formatting.
  • Maritime Logistics and Port Operations: Freight forwarders, customs brokers, and marine service companies connected to the Port of Gothenburg often combine public corporate pages with authenticated shipment tracking or partner portals. An edge-routed architecture allows Astro to serve public documentation while Next.js handles authenticated partner views under the same domain.
  • Life Sciences and Medtech: Research companies and clinical suppliers around Sahlgrenska Science Park and GoCo Health Innovation City require strict version control over regulatory documentation, product advisories, and bilingualinvestor relations pages. Storing content in structured schemas prevents accidental layout drift during routine updates.

#What can go wrong in a CMS migration, and how do I check it?

  • Lost URLs. A page that existed and now returns 404 loses its links and rankings. After launch I run the old URL list against the new site and fix every 404 and every redirect chain.
  • Language versions cut loose. If the English page redirects correctly but the Swedish one does not, hreflang breaks and Google may show the wrong language. I check reciprocity on the built HTML, not in the CMS settings.
  • Redirects removed too early. Google’s guidance is to keep redirects as long as possible, generally at least one year. I keep those forwarding rules active permanently unless you instruct otherwise.
  • Silent failures in forms and analytics. Enquiry endpoints, email subscriptions and event trackers are frequently coupled to legacy plugins. I catalogue every integration upfront and verify it on staging using test payloads.
  • Editors who cannot publish. A high-speed frontend that your team cannot edit is an operational dead end. The editing flow is agreed at the start, and editors get a written guide before cutover.

#Which Swedish rules affect a website in Gothenburg?

Language. Under the Swedish Language Act (språklag 2009:600), Swedish is the main language of Sweden and society’s common language. Finnish, Yiddish, Meänkieli, Romani Chib and Sami are recognised national minority languages. A private company is free to publish in English as well, and many Gothenburg businesses selling abroad do, so the language structure of the site needs a decision before content moves: URL prefixes, translated slugs, the language switcher and hreflang.

Personal data and cookies. Form submissions, analytics and newsletter lists fall under the GDPR. In Sweden the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY) supervises personal data protection, while Post- och telestyrelsen (PTS) supervises electronic communications rules on cookies and similar tracking technologies under Lag (2022:482) om elektronisk kommunikation (LEK). A migration is a good moment to list which scripts load on each page, which ones set cookies and where form data ends up, because the new stack only gets what you deliberately add back.

Accessibility. Lag (2023:254) om vissa produkters och tjänsters tillgänglighet, Sweden’s implementation of the European Accessibility Act, has applied since 28 June 2025. It covers e-commerce services aimed at consumers, delivered through websites and mobile apps. Services from microenterprises are exempt from its accessibility requirements. Post- och telestyrelsen (PTS) supervises e-commerce services under the related ordinance, while Myndigheten för digital förvaltning (DIGG) oversees public-sector digital accessibility under Lag (2018:1937). If your shop or service is in scope, I build the new templates with keyboard navigation, labelled form fields, sufficient contrast and a sensible heading order from the start, which costs far less than retrofitting them.

Corporate disclosures. Under Aktiebolagslagen (2005:551), a Swedish limited company (aktiebolag) must state its registered company name, municipal seat (säte), and corporate identity number (organisationsnummer) on its website and electronic communications. I make sure these statutory footer disclosures are carried over cleanly across every locale template.

Hosting. Hosting is a deliberate architectural decision. Static Astro builds run from any global CDN or edge network, whereas server-rendered Next.js applications require a compute runtime. If your data handling requires hosting in the EU/EEA, I pick a provider and region that meet it and record the choice in the handover.

#Pre-cutover verification checklist for Gothenburg migrations

Verification areaWhat I check before switching DNS
URL & PDF coverageEvery indexed page and linked PDF datasheet in Search Console and server logs has a 200 or single-hop 301 target
Swedish & English hreflangReciprocal sv-SE / sv and en annotations verified on built HTML, with self-referencing canonicals
Schema.org parityOrganization, BreadcrumbList, Article, Product and FAQPage JSON-LD validated without duplicate plugin blocks
LEK & IMY privacy complianceZero non-essential cookies or third-party trackers firing prior to explicit user consent
Lag (2023:254) accessibilitySemantic landmarks, keyboard focus order, form labels and contrast ratios verified across templates
Statutory company detailsRegistered name, municipal seat and organisationsnummer present in global footer templates

#Deliverables at the end of the migration

You get the repository, the URL map, the redirect file, environment variables, the deploy pipeline and a written document on how content is edited and published. If you want, I watch indexing and Core Web Vitals in the weeks after launch and fix what comes up.

The general process is described on my Next.js and Astro migration page, and the frontend side on the Astro developer page.

#Requesting a written migration scope for your Gothenburg site

Send me the current site URL, the CMS and version it runs on, the languages it publishes in, and where your traffic comes from: organic search, ads, newsletters or referrals via the contact page. Access to Search Console helps but is not needed for the first look. I reply in writing on working days with a free initial estimate and scope: what moves, what changes, which URLs need redirects and which risks I see on your specific site.

#WordPress community signals in Gothenburg

The community reference is WordPress Göteborg Meetup (https://www.meetup.com/wordpress-gothenburg/). It does not replace a contract; it sets the technical vocabulary teams use in Gothenburg.

See also in Sweden

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

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

Describe your project

Explore other WordPress services and knowledge base