SEO checklist after migrating an AI website to WordPress
Keep your rankings after moving from an AI website builder to WordPress: redirects, canonicals, sitemaps and Search Console.
Convert2WP – convert your AI website to WordPressClick here
1. Keep URLs identical where possible
The safest migration keeps every URL the same. Where a URL must change, add a single permanent 301 redirect from old to new – no redirect chains.
2. One canonical per page
Every page should have a self-referencing canonical tag in the server HTML. Check it with 'view source', not only in the browser inspector.
3. Multilingual sites
Only list language versions in hreflang and the sitemap when the page is really translated in the server HTML, including the html lang attribute.
4. Sitemap and Search Console
Submit one sitemap for the exact property (with or without www). Expect rankings to move for a few weeks after a large change – that is normal re-evaluation.
Raw HTML versus rendered DOM
Google processes pages in two waves: first the raw HTML response, later a rendered version when rendering resources become available. Many AI-built sites put titles, canonicals and hreflang tags in place with JavaScript, so the first wave sees an empty or identical document on every URL. WordPress outputs these tags on the server, which removes that risk entirely. Verify it with curl -s URL | grep -i canonical, not with the element inspector, which shows the DOM after scripts have run.
Writing redirect rules that scale
For a handful of changed URLs a redirect plugin is fine. For hundreds, rules at the web server are faster and easier to audit. On Nginx a map block from old path to new path with a single return 301 handles thousands of entries efficiently; on Apache a RewriteMap or a list of Redirect 301 lines in .htaccess does the same. Test a sample with curl -I to confirm a single hop and a 301 status, never 302, and no chains through an intermediate URL.
Monitoring the first eight weeks
After launch, watch three reports in Search Console: Pages for indexing status, Sitemaps for the number of discovered URLs, and Performance filtered by page. A temporary dip followed by recovery within four to eight weeks is the normal pattern. Server logs are the most honest signal: if Googlebot requests your important URLs and receives 200 responses with correct canonicals, indexing follows. Persistent 'Duplicate without user-selected canonical' messages almost always point to a canonical or language tag that is missing in the raw HTML.
Field notes: the redirect map as a living document
The redirect map is the most underrated artefact of a migration. I keep it as a simple spreadsheet with three columns: old URL, new URL and status code. Every row is tested with a crawler after launch, and any 404 found in Search Console in the following weeks is added as a new row. A redirect plugin or server rules then import the sheet directly.
Avoid chains. If an old URL already redirected once on the AI platform, point it straight to the final WordPress URL. Every extra hop costs crawl budget and dilutes signals.