What does an SEO migration timeline look like?

An SEO migration timeline has five phases, and getting the order right matters more than hitting exact dates. The phases are audit and inventory, mapping and planning, build and staging QA, launch, and post-launch monitoring. Two things about the shape are non-negotiable: the audit and URL inventory come first, because the redirect map, the build, and the verification all depend on knowing what exists, and the monitoring phase runs for weeks after launch, not the day or two teams often allow. Everything else flexes with the size of the site. WPBuildAI’s scan produces the URL inventory and complexity view the timeline is built from, so the plan rests on the real shape of the site rather than an optimistic guess.

Give the timeline a tail rather than ending it at launch: Google’s guidance is to keep redirects live for at least a year after the move is complete, which means the plan needs an owner for a period considerably longer than most migration projects are funded for.

The five phases of an SEO-safe migration

Think of the timeline as a sequence where each phase produces what the next one needs. Phase one inventories the site, which phase two turns into a redirect map and plan, which phase three builds and tests on staging, which phase four launches, which phase five monitors and corrects. The durations below are planning ranges, not promises, and they scale with site size, but the order is fixed. Skipping or shortening phase one is the most common scheduling mistake, because it makes every later phase rest on incomplete information, and the cost surfaces only after launch when it is expensive to fix. The full process detail lives in migrating WordPress without losing SEO.

Phase 1: audit and inventory

Plan roughly one to two weeks. This phase produces the complete URL inventory and a picture of what the site contains: every URL from the sitemap, internal links, and Search Console, plus the metadata, media, templates, and any languages, the groundwork covered in finding all URLs. It also surfaces the high-value pages, because traffic is uneven: the Ahrefs search traffic study found a small share of pages earns most visits, and those pages set the priorities for everything downstream. The output is the inventory the rest of the project depends on, which is why it comes first and is not rushed.

Phase 2: mapping and planning

Plan around one week. Here the inventory becomes a plan. You design the new URL structure to reuse old paths where possible, build the old-to-new redirect map with each pair single-hop and exact, and decide what content carries over and what is consolidated. This is also where the risks are assessed and the launch is scheduled, informed by the risks of migrating to a new CMS. The redirect map is the central deliverable, and its completeness is what Google’s site move guidance treats as the heart of a safe move. A good map here makes launch uneventful later.

Phase 3: build and staging QA

Plan two to six weeks, the phase that varies most with site size and complexity. The new site is built, content is imported, metadata is set from the export, and internal links are recreated. Crucially, the staging site stays noindex so it is not indexed before launch. QA on staging checks URL parity, titles, H1s, canonicals, and that redirects resolve in single hops. A large or multilingual site sits at the long end of this range; a small brochure site at the short end. This phase is long because it is where most of the actual work happens, and where catching problems is still cheap.

Phase 4: launch

Plan a single low-traffic window, often a day. Launch is a sequence of careful switches: remove the staging noindex, apply the redirects, point DNS, confirm the live canonical, and resubmit the sitemap, the steps in a redesign launch checklist. Use permanent 301s so the move reads as permanent, per Google’s redirects guidance. The single most damaging launch error is shipping the live site with the staging noindex still applied, which deindexes everything, so it gets its own explicit check. Schedule launch away from peak traffic and your busiest season, and keep the ability to roll back.

Phase 5: post-launch monitoring

Plan four to eight weeks, and resist the urge to call the project done at launch. Google has to recrawl the new URLs and process the redirects, which takes weeks, and some ranking wobble during that window is normal. Watch two numbers in Search Console: the 404 count, fixing URLs the inventory missed as they surface, and the indexed-page count, which should recover toward the old total. If 404s climb and impressions fall and stay down, a batch of URLs is missing a redirect. This phase is where a migration is confirmed successful or quietly rescued, and skipping it is how recoverable problems become permanent losses.

How to size the timeline for your site

The phases scale with three things: the number of URLs, the number of distinct templates, and the number of languages. A 50-page single-language site can run the whole timeline in a few weeks; a 5,000-page multilingual site with many templates can take months, mostly in phases three and five. The platform you move to does not change the SEO timeline much, because the CMS is not a ranking factor, as Backlinko’s analysis of 11.8 million results found. What changes the timeline is scale and complexity, which is exactly what a scan measures up front, turning a guessed schedule into a sized one.

A worked example: a mid-size site timeline

A 600-page site with three templates and one language planned a migration. Phase one took ten days to inventory 600 pages plus 200 archive and tag URLs and flag the 70 that drove most traffic. Phase two took a week to design the new URLs, hand-map the top 70 and rule-map the rest, and build the redirect map. Phase three took four weeks to build, import, and QA on staging with noindex on. Phase four was a Tuesday-morning launch: noindex off, redirects on, sitemap resubmitted. Phase five ran six weeks of monitoring, during which a dozen missed URLs surfaced as 404s and were redirected, and rankings recovered to baseline. Total: about twelve weeks, sized from the phase-one scan rather than guessed.

Common mistakes in migration scheduling

• Shortening phase one, so the redirect map is built on an incomplete inventory.
• Allowing only a day or two of post-launch monitoring instead of weeks.
• Scheduling launch right before a peak season or sales period.
• Treating the build phase as fixed when it varies most with site size.
• Setting dates before scanning the site, so the schedule is a guess, not an estimate.

Key points to remember

An SEO migration timeline runs in five phases: audit and inventory, mapping and planning, build and staging QA, launch, and post-launch monitoring. The order is fixed, the inventory comes first because everything depends on it, and monitoring lasts weeks, not days. Size the schedule by URL count, templates, and languages, not by the platform, since the CMS is not a ranking factor. Build the redirect map in phase two so launch is uneventful, and keep staging noindex until you go live. Treat the dates as ranges and the sequence as the rule. WPBuildAI’s scan produces the inventory and complexity view the timeline is built from, so the plan reflects the real site. Send your site URL for a free migration assessment.

Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.