
WordPress to Next.js Migration SEO Checklist
Migrating from WordPress to Next.js is not just a frontend rebuild. It is an SEO migration, content migration, analytics migration, and launch operation wrapped into one project.
The technical stack can improve speed and control, but the launch can still hurt search visibility if redirects, metadata, canonicals, internal links, tracking, or indexing controls are missed.
Use this checklist before, during, and after the migration.
If you want help turning this into an actual launch plan, start with a WordPress migration audit.
Before Rebuild: Inventory the Current Site
Export or crawl:
- All indexable URLs
- Current page titles
- Meta descriptions
- H1s
- Canonical URLs
- Status codes
- Redirects already in place
- XML sitemap URLs
- Robots.txt rules
- Structured data
- Blog categories and tags
- Custom post types
- Media URLs used by important pages
- Internal links
- Top landing pages from analytics
- Search Console pages and queries
Do not rely only on the WordPress admin. Crawl the public site because the live site may include generated archive pages, media URLs, plugin routes, landing pages, or old redirects that the admin does not make obvious.
Decide Which URLs Stay the Same
Keeping URLs the same is usually the least risky path when the existing URL structure is clean.
Change URLs only when:
- The current structure is broken or duplicated.
- The migration includes a real information architecture cleanup.
- Old slugs are unreadable or no longer match the business.
- There are multiple competing versions of the same content.
For every changed URL, map old to new.
| Old URL | New URL | Status |
|---|---|---|
/old-service-page/ | /services/new-service/ | 301 |
/blog/old-post/ | /blog/updated-post/ | 301 |
/thin-duplicate-page/ | Best matching parent page | 301 or retire |
Google's migration guidance is clear that URL changes should be handled carefully to reduce search impact. Redirects are one of the core controls.
Preserve the Metadata That Still Works
Migrate:
- SEO title
- Meta description
- Open Graph title
- Open Graph description
- Social image where relevant
- Canonical URL
- Noindex rules
- Schema markup where still valid
Do not blindly copy everything. Some old metadata is keyword-stuffed, duplicated, outdated, or generated by plugins in a way that no longer fits the new page.
Use this rule:
- Preserve high-performing metadata unless there is a clear reason to improve it.
- Rewrite weak metadata for priority pages.
- Remove metadata that no longer reflects the content.
Rebuild Internal Links
Internal links often break during WordPress rebuilds because old editors used absolute URLs, page-builder blocks, plugin shortcodes, or outdated category links.
Check:
- Navigation links
- Footer links
- Blog body links
- Related posts
- CTA links
- Breadcrumbs
- Category links
- Image links
- Button links
Internal links help search engines discover pages and understand relationships. They also help users move from informational content into the service page, which is why every migration cluster should link back to the main WordPress to Next.js migration page.
Replace Plugin SEO Features Deliberately
WordPress SEO plugins often handle more than people realize.
Before launch, identify what plugin-generated behavior must be recreated:
- XML sitemap
- Robots.txt
- Canonical tags
- Redirect manager
- Breadcrumb schema
- Article schema
- Product schema
- Open Graph tags
- Twitter cards
- Noindex rules
- Pagination rules
In Next.js, these features usually move into code, CMS fields, or deployment configuration. That is good for control, but only if someone maps them before the old plugin disappears.
Check Rendering and Performance
Next.js can statically render pages, dynamically render pages, cache data, and revalidate content depending on how the route is built.
For SEO pages, confirm:
- Important content is present in rendered HTML.
- Metadata is generated server-side.
- Canonical URLs are correct.
- Images have alt text where meaningful.
- Pages are not accidentally blocked by robots rules.
- Core pages return 200 status codes.
- Redirected pages return the intended redirect status.
Google recommends good Core Web Vitals for search success and user experience, but good performance scores do not guarantee rankings. Treat performance as one part of the migration, not a magic SEO lever.
Test Forms, Tracking, and Conversion Events
SEO traffic does not matter if lead capture breaks.
Check:
- Contact forms
- Newsletter forms
- Quote forms
- Booking links
- Thank-you pages
- CRM handoffs
- Email notifications
- Spam protection
- Analytics events
- Ad pixels
- Call tracking
- UTM preservation
Do this before launch and again after launch. Form failures are common because the frontend changes while hidden backend destinations stay assumed.
Launch Checklist
Before DNS or production switch:
- Crawl staging.
- Confirm no staging URLs are canonical.
- Confirm staging is blocked from indexing if needed.
- Export final redirect map.
- Test priority redirects.
- Validate metadata on priority pages.
- Generate sitemap.
- Confirm robots.txt.
- Test forms.
- Test analytics.
- Test mobile layouts.
- Test 404 page.
- Prepare rollback steps.
- Keep the old WordPress environment accessible as a backup.
Post-Launch Checklist
After launch:
- Crawl the live site.
- Test priority old URLs.
- Submit sitemap in Search Console.
- Inspect priority URLs.
- Watch crawl errors.
- Watch indexation issues.
- Check analytics traffic.
- Check conversion events.
- Check forms and notifications.
- Monitor rankings and impressions over the next few weeks.
Some ranking fluctuation can happen during URL or infrastructure changes. The goal is not to promise zero movement. The goal is to avoid preventable mistakes and respond quickly.
What to Prioritize First
If you cannot check everything in one pass, start here:
- Top organic landing pages
- Money pages
- Pages with backlinks
- Pages with form conversions
- Redirects from old URLs
- Sitemap and robots.txt
- Analytics and conversion events
That protects the pages most likely to affect leads and revenue.
Medianeth's Migration Audit Flow
Our audit focuses on four risk groups:
- SEO: URLs, redirects, metadata, canonicals, schema, sitemap
- Content: page templates, posts, custom fields, CMS editing workflows
- Conversion: forms, CRM/email handoff, tracking, booking links
- Launch: DNS, QA, monitoring, rollback
The output is a scope map for the rebuild, not a vague recommendation to "go headless."
Book a WordPress migration audit if your WordPress site is too important to rebuild casually.