Next.js / Astro migration in Frankfurt am Main

Moving a Frankfurt am Main site from WordPress, Joomla or Drupal to Astro or Next.js is mostly not a design job. It is keeping every address, every structured data block and every language version working while the system underneath is replaced.

#What does a CMS to Astro or Next.js migration involve?

The work has six parts, in this order.

1. URL inventory. I collect every old URL from the XML sitemaps, the CMS database, server logs and analytics exports, then add the URLs that external sites link to.
2. URL map and redirects. Each old URL gets a target: the same path where possible, a new path with a permanent redirect where not. Google’s site move guide asks for server-side 301 or 308 redirects, straight to the final address, and warns against sending many old URLs to the home page, which can be treated as a soft 404.
3. Content model. Posts, pages, custom post types, Drupal nodes or Joomla articles become typed content collections in Astro, or a headless CMS feeding Next.js. Fields that only existed for one plugin get a decision: keep, merge or drop.
4. Structured data and meta. Titles, descriptions, canonicals, Open Graph tags and JSON-LD are compared old against new, page by page, on the built output.
5. Staged cutover. The new site runs on a staging domain, blocked from indexing, until the redirect map passes a full crawl. Large sites switch section by section; small ones can switch at once.
6. Monitoring. After launch I watch Search Console, server logs and analytics. The indexed count for old URLs should fall while the new one rises; a page that loses traffic and does not recover is a bug to find.

#Astro or Next.js for a Frankfurt company site?

Astro fits sites that are mostly content: company pages, blogs, documentation, landing pages for trade fair campaigns. Pages are built as static HTML and ship JavaScript only where a component needs it. Next.js fits when the site has logins, personalised dashboards, server-side rendering per request or a React team that will maintain it. I recommend one after seeing the current site and the team that will own it. More detail is on my Next.js and Astro migration page and the Astro developer page.

#How do I keep rankings when the URLs change?

By treating redirects as part of the release, not as a cleanup afterwards. Before cutover I crawl the old URL list against staging and expect one hop to a 200 page for every entry. Google recommends keeping redirect chains short and keeping redirects in place generally at least one year.

The hosting limits matter here. On Cloudflare Pages, for example, a _redirects file holds at most 2,000 static and 100 dynamic redirects; a larger map needs Bulk Redirects configured through the dashboard or API. I check the size of the map against the target platform before choosing it, not after the build fails.

If the domain changes too, Search Console’s Change of Address tool comes in. Google states it is only needed for a move to another domain or subdomain, not for path changes or an HTTP to HTTPS switch.

#What changes for a German and English site in Frankfurt?

Frankfurt is the most populous city in Hesse, on the river Main, and the fifth most populous city in Germany. About a quarter of its residents are foreign nationals, according to Wikipedia. A site that speaks to that audience in German and English needs both versions to survive the move.

For a multilingual migration, hreflang is where things break quietly. Google’s documentation is clear that each language version must list itself and every other version; if two pages do not point to each other, the tags are ignored. WordPress multilingual plugins often generate these tags at runtime, so after a migration they simply disappear unless the new build creates them. I generate them from the content model and check reciprocity on the built HTML, with an x-default where a language selector page exists.

#Which sectors and rules shape a migration here?

Frankfurt’s economic development office lists finance, trade, hospitality, crafts, real estate, industry, IT and telecommunications, creative industries and logistics as its sectors. The city is home to the European Central Bank, the Deutsche Bundesbank, the Frankfurt Stock Exchange, Messe Frankfurt and Frankfurt Airport, the busiest airport in Germany.

Three practical consequences for a website move:

• Data protection. The Hessian Commissioner for Data Protection and Freedom of Information (Der Hessische Beauftragte für Datenschutz und Informationsfreiheit), in Wiesbaden, has supervised non-public bodies in Hesse, including companies, since 1 July 2011. A migration is the point where I list every third-party script, font and embed the old site loaded, and decide with you which ones the new frontend still needs and whether they wait for consent.
• Accessibility. The European Accessibility Act covers e-commerce and banking services among other products and services; the European Commission notes that Member States had to bring it into national law by June 2022. I check heading structure, form labels, contrast and keyboard use on the new templates.
• Hosting location. DE-CIX describes its Frankfurt exchange as the world’s leading internet exchange, with more than 1,000 networks reachable. I document where the build output, the CMS and any form backend actually run, so your data protection documentation matches the real setup.

#What can go wrong, and how do I check it?

• Lost URLs. Pages that were never in the sitemap. I compare the crawl, logs and analytics landing pages before cutover.
• Changed canonicals or meta. I diff them between old and new builds for every mapped URL.
• Missing structured data. JSON-LD injected by plugins disappears with the CMS; I confirm each old schema type exists on the new site.
• Broken forms and tracking. Contact forms, newsletter sign-ups and conversion tags are tested on staging with real submissions.
• Hreflang gaps. Checked as described above, on the built pages.

#Do I need the Change of Address tool in Search Console?

Only if the domain or subdomain changes. Most CMS to Astro migrations keep the domain, so the work is the URL map and the redirects.

#How long do the old redirects have to stay?

Google recommends generally at least one year. I plan the redirect file so it can stay much longer.

#Will a German and an English version need hreflang?

Yes, if both versions exist, and each version must reference the other, or Google ignores the tags.

#Who supervises data protection for a Frankfurt company?

The Hessian Commissioner for Data Protection and Freedom of Information in Wiesbaden, which supervises non-public bodies based in Hesse.

#What is the next step?

Send me the current site URL, the CMS and its version, the languages you publish in, and where your traffic comes from (organic search, ads, newsletters, partner links). I reply with a written scope: what moves, what gets dropped, how many URLs need redirects, Astro or Next.js and why, and the order of the cutover. You can start through the headless CMS developer page or the contact form on this site.

#WordPress community signals in Frankfurt am Main

The community reference is WordPress Frankfurt (https://www.meetup.com/wordpress-frankfurt/). It does not replace a contract; it sets the technical vocabulary teams use in Frankfurt am Main.

We build secure, high-performance WordPress solutions for businesses in Frankfurt am Main, tailored to local market realities. In the Banking & Financial Services segment, questions usually turn on WordPress, WooCommerce, Astro, Next.js versus legacy.

Scope and assumptions arrive in writing after a short brief. Banking compliance (BaFin), financial sector security standards, and fintech integration platforms.

#FAQ

#Why are Frankfurt financial institutions and enterprises adopting Astro?

Frankfurt am Main is continental Europe’s primary financial capital, hosting the European Central Bank, Deutsche Bundesbank, Frankfurt Stock Exchange, and over 200 international credit institutions. Websites built on outdated CMS monoliths struggle with security surface vulnerability, slow TTFB, and complex maintenance cycles under DORA and NIS-2 mandates. Astro eliminates server-side PHP dependencies and public databases by pre-compiling content into static HTML, providing ironclad security against cyber threats and instant edge delivery.

#How do you preserve German and English search engine rankings during migration?

Before migrating any content, I construct an exhaustive URL manifest combining live crawl results, historical sitemaps, and Search Console data. Every legacy address is either preserved identically or mapped to a permanent HTTP 301 redirect served directly at the edge. Reciprocal hreflang tags (such as de-DE and en) are compiled directly into the static document headers to guarantee that international audiences are routed seamlessly to their corresponding language versions.

#What German data protection regulations are enforced during the rebuild?

In Hesse, non-public commercial entities are supervised by the Hessian Commissioner for Data Protection and Freedom of Information (HBDI). All tracking scripts, marketing beacons, and third-party embeds are blocked until explicit consent is recorded via compliant consent banners. Fonts and assets are self-hosted locally on secure European servers, preventing unvetted telemetry transmissions to overseas cloud networks.

#How do Frankfurt editorial teams publish new content following the migration?

Yes. Your marketing team can retain their established authoring workflows by decoupling the CMS into a headless content repository (such as WordPress, Strapi, or Sanity). Editors publish articles and press releases in the familiar administrative backend, while Astro queries published records via REST or GraphQL APIs to build static, zero-JS pages automatically upon saving.

#What is the expected delivery timeframe for an enterprise migration in Frankfurt?

A typical corporate replatforming covering 20 to 50 unique page templates, multilingual translations, and custom forms spans approximately 3 to 5 working weeks from initial crawl analysis to production cutover.