How to Migrate WordPress to Next.js Without Losing Your SEO

Most “WordPress to Next.js” tutorials show you how to fetch posts from the WP REST API and render them in the App Router. That’s the easy 20%. The 80% that actually decides whether your organic traffic survives is everything around the content: your URLs, your redirects, your metadata, your sitemap, and your images. Get those wrong and you’ll watch impressions fall off a cliff two weeks after launch, right when everyone assumes the migration “went fine.”

This guide is the checklist I wish every team ran before flipping DNS. It’s framework-accurate for the Next.js App Router, and it works whether your new backend is headless WordPress, a headless CMS, or flat files.

The one rule that saves rankings

Every decision in a migration comes back to a single principle:

Nothing about how Google already sees your pages should change, except the parts you deliberately improve.

Google ranks specific URLs based on their content, their metadata, and the links pointing to them. A migration is dangerous precisely because it’s tempting to change all three at once: new URLs, a “cleaner” content structure, redesigned templates. Do that and you’ve thrown away the signals every ranking is built on. The safe path is boring: same URLs, same content, same meta, just a faster, modern frontend underneath.

Step 1: Inventory everything before you touch anything

You cannot preserve what you haven’t captured. Before writing a line of Next.js, you need a complete, structured snapshot of the live site: every published URL, its rendered content, its SEO metadata, its images, and its internal links. This inventory becomes the source of truth for your redirect map, your generateMetadata, and your sitemap.

This is the step most guides wave away with “export your content from WordPress.” In reality it’s where migrations break, because the default WordPress export (WXR) gives you raw post content, not the rendered HTML your page builder actually outputs, and it drops most of the SEO fields you need. If your site runs Elementor, WPBakery, Divi, Bricks, or Oxygen, a raw export is close to useless: the shortcodes never render.

This is exactly what Migratik was built for (Migratik packs an entire WordPress site into one clean JSON file) the fully rendered content_html (builder shortcodes executed), the theme-rendered document_title, the permalink of every item, SEO meta from Yoast / Rank Math / AIOSEO, featured & in-content images, internal links, taxonomies, and custom fields. It’s builder-agnostic and read-only, so it changes nothing on your live site. That single file is the inventory this entire guide runs on. packs your whole site into one file that powers your routes, metadata and redirects.

Start with a clean inventory (Migratik exports your whole WordPress site) rendered content, SEO metadata, permalinks, images, and links, into one file that powers your redirects, metadata, and sitemap. Free to install, read-only, and safe on a live site. Install Migratik free on WordPress.org

Vollständiger Original-Bericht

Ausführliche Details, Code-Beispiele & Hersteller-Stellungnahme auf dev.to.

↗ Original-Artikel auf dev.to lesen