Launch week has no old-to-new spreadsheet
Design is ready. DNS is booked. Equity URLs are unnamed. We stop the calendar until the map has rows: keep, 301, or 410.
Migration SEO
Migration SEO to Cut Over URLs Without a Soft-404 Hole
Migration SEO at SEOConsultants.ai is a move with a date. We inventory URLs that carry equity, write redirect and 410 rows, check staging, run launch hour, and watch for loops, soft 404s, and unmapped paths. We do not sell a recovery week. We do not treat a standing crawl queue as a cutover.
- Map
- Redirect
- Launch
- Watch
Position
The old URL must land or close on a named date.
Teams often buy a redesign and hope search follows. Hosts change. Paths change. The old URL returns a soft 404 or a homepage catch-all. Search intent on the new document still has to match what the old URL was for. A pretty new template is not a map. This page owns the cutover contract.
A standing technical queue
Crawl, render, and index tickets with no launch date belong on technical SEO. Stay here when DNS, host, or the URL pattern will change on a date. Stay there when the stack is already live and the tickets keep coming.
Open technical SEOWordPress permalink taste without a map
Post patterns, tags, and plugin fields without a cutover belong on WordPress SEO. Stay here when you treat the change as a dated move with old-to-new rows. Pretty slugs alone are not this H1.
Open WordPress SEOA URL factory redesign as theory
Programmatic SEO owns dataset, gate, and prune. The cutover still must not revive thin rows you already closed. Factory rules stay there. Launch rows stay here.
Open programmatic SEOShop catalog rules without a move
Which product URLs may exist lives on ecommerce SEO. Stay here when those paths change host or pattern on a date. A facet policy is not launch hour.
Open ecommerce SEOThe object is a dated move: inventory, redirect and 410 decisions, staging the people who sign launch can crawl, launch hour, and a watch for loops and unmapped rows. Technical SEO still owns fetch after you are living on the new stack. WordPress SEO still owns leftover archives when you are not moving. A factory that must not be resurrected still has rules on programmatic SEO. Shop paths still have catalog rules on ecommerce SEO.
We will not sell a calendar as a ranking product. We will not promise the new site will beat the old site. We will not treat a permalink taste session as launch hour. If there is no date, open technical SEO. If the only change is archive settings, open WordPress SEO. If many brands ship without a move, open enterprise SEO.
When this fits
When a go-live date exists and the old paths have no row
This page fits when you will change host, domain, CMS, or the URL pattern on a date you can name. If you needed a monthly crawl ticket, a permalink tidy, a factory gate, or a shop permit list with no move, start there instead.
Staging is a design preview only
Signers cannot crawl it. Robots will ship wrong. We make staging a go or no-go, not a screenshot.
The new homepage catches every old path
That is a soft hole. We write destinations that match the old job, or we close the object on purpose.
Someone sold a recovery calendar
We will say no. Watch finds loops and unmapped rows. It does not invoice a ranking window.
Process
Map first. Then redirects that match the row.
Four cutover jobs in this order. We do not start launch hour by hoping DNS will teach Google the new paths. The point is old URLs that land or close without a soft hole.
-
Map
We inventory URLs that carry equity or must not disappear. Search Console, analytics, and sitemaps feed the list. Keyword targeting is one job per kept path: the new URL must still do that job. A keyword dump is not inventory.
Outcome A dated inventory: keep path, equivalent, or gone.
-
Redirect
We write 301, 410, or hold for each row. Guessing the homepage is not a map. Parameter and factory leftovers that should stay dead stay dead. Topical relevance is the test for the destination: does this new URL match the old job? Keyword density on a new template is not a cutover score.
Outcome A redirect table engineering can ship and QA can sample.
-
Launch
We check staging, then we run the hour: certificate, DNS, edge redirects, sitemap swap, first live hits. Rollback criteria are named in advance. Rank drop is not an automatic rollback we invent.
Outcome A launch checklist with owners and a go or no-go.
-
Watch
We sample loops, soft 404s, unmapped equity URLs, and robots that still point at staging. This is defect detection. It is not a recovery product. Ongoing tickets after the stack is live return to technical SEO.
Outcome A watch list with a recheck window, not a ranking SLA.
Deliverables
What launch can keep after we leave
You leave with an inventory, a redirect table, a staging go or no-go, a launch checklist, and a watch list. You do not leave with a recovery calendar or a promise the new site will beat the old one.
Equity inventory
URLs that must not fall into a soft hole. Dated. Last year's sitemap export is not this list.
Redirect table
301, 410, or keep. Homepage catch-alls are named as defects until they are rows.
Staging go or no-go
What signers could crawl, what still blocked them, and what must not ship as a preview host.
Launch checklist
DNS, certificates, robots, canonicals, sitemap, first-hit samples. Rollback criteria sit next to the hour.
Watch list
Loops, soft 404s, unmapped rows. A weekly ranking report is not this list.
Benefits
What a new theme will not do on its own
Old money URLs get a row
They keep a path, they 301 to a real equivalent, or they close. They do not become a homepage sponge.
Staging stops lying
Signers crawl what will ship. Preview hosts do not leak into the live graph.
Launch hour has owners
The first hits prove the map. Spreadsheets alone do not.
Defects have a watch, not a myth
Loops and soft 404s get sampled. Nobody invoices a recovery window.
Methodology
Who can change DNS and the redirect table
This works when someone owns the go-live date, and someone can ship redirects. If both are missing, we are touring a new theme. We are not cutting over URLs.
We start with the date, the old host, the new host, and a sample of equity URLs. If any of those is missing, we name it first.
We fetch old URLs and staging URLs. We do not trust a design preview. Does this old path have a row? Will staging robots ship?
You may rename the roles below. You may not leave the date implied. An implied someday move is how a redesign ships with no map.
- Migration SEO lead SEOConsultants.ai writes the inventory, the redirect table, the staging note, the launch checklist, and the watch list. We do not become your hosting company because the date was near.
- Whoever owns go-live Names the date and can slip it. A locked calendar with no owner is a finding.
- Engineering or hosting Ships redirects, robots, and DNS. Rechecks in the first hour. They do not need a ranking target to do that.
- Whoever owns Search Console Adds the new property, swaps sitemaps, and samples coverage. They do not invent a recovery SLA.
- Leadership Accepts a slip if the map is missing. An unread table is not a failure of this page. A promise to beat prior traffic would be.
First working session
Start with the date and one old URL that has no row
The first hour is the go-live date plus one equity path with no destination. It is not a tour of technical tickets.
We write the date on the board. We pick a URL that still earns from search. We ask where it lands after launch. If the answer is the new homepage or a shrug, that is the job. If there is no date, that is technical SEO. If the only change is leftover WordPress archives, that is WordPress SEO. If many brands ship with no host change, that is enterprise SEO. If a factory must stay pruned, that is programmatic SEO plus this map.
Then we try to crawl staging as a signer would. If we cannot, launch is not ready. Search Console samples of old paths are usually the job. A Figma file is not evidence of redirects.
We leave with a first table or a stop. A table names keep, 301, or 410 for the sample and who owns DNS. A stop names what is missing: the date, staging access, or a stack that is actually a permalink tidy. Both are outcomes. A recovery invoice is not.
AI search
A cutover is not an AI Overview recovery
URLs that still resolve can help later extraction. This page cannot sell AI Overviews, a chat mention, or LLM visibility as a score.
People ask whether a clean move will land the brand in Google AI Overviews (AIO). If old URLs became soft 404s, generative search has a hole to quote, or a leftover staging host. That is ours to close as a map. If the new pages already tell the truth and models still cite the old domain, that is an AI search audit. A program across search UIs is AI SEO.
The new document has to fetch at the old job's URL or its 301
AI search needs a page it can fetch. A launch that 404s the old path does not help. We do not sell Overview presence.
Official names should still match after the host change
We check whether new HTML uses the same organization and product names. That is entity optimization as a cutover input. SameAs that still points at the old host is a defect after launch. The full identity spec stays on Entity SEO.
Measuring model answers is another URL
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. A redirect table can keep a URL real. It does not sample answers. Semantic keywords belong on the new page only when that page still does the old job.
Schema
Markup that must not still name the old host
JSON-LD helps a machine read a page the new HTML already states. This work flags canonical and sameAs leftovers after launch. It is not a schema campaign as the whole job.
Canonicals must not ship as staging hosts
If live pages point at a preview host, extractors follow the wrong graph. We name that in launch hour.
No FAQ theater to hide a missing map
We refuse question blocks added only to look complete on a new template. The redirect table is the object.
Extra types do not buy a citation
Markup will not force generative search to cite the new host. Eligibility is not a purchased mention.
Who we work with
The person who can slip the date if the map is empty
Someone has to refuse a launch with no rows. We work with that person. We do not replace them with a second hosting retainer.
Go-live owner
Names the date. Holds it when design wants to ship without a table.
Engineering or hosting
Ships redirects and DNS. Samples first-hour hits. Rechecks robots.
Whoever already runs technical SEO
Can keep going after the stack is live. If they try to run this as a standing queue with no date, two jobs collide. Standing tickets belong on technical SEO.
Questions
Frequently asked questions
How is this different from a technical SEO retainer?
Technical SEO owns standing crawl, render, and index tickets when you are not mid-move. This page owns a dated cutover: inventory of URLs that carry equity, redirect and 410 decisions, staging checks, launch hour, and a watch for loops, soft 404s, and unmapped rows. Recurring JS tickets after you live on the new stack return to technical SEO. A queue with no launch date is not this job.
Is tuning WordPress permalinks the same as migration SEO?
No. WordPress SEO owns post patterns, leftover archives, and plugin fields without a cutover. This page starts when you treat the change as a dated move: host, domain, or the whole URL pattern with an old-to-new map and a launch hour. Pretty slugs with no map stay on WordPress SEO.
Do you sell a recovery window so traffic comes back on a calendar?
No. We will not sell a week-count recovery product, a ranking SLA, or a promise that traffic will beat the old site. Watch is defect detection: loops, soft 404s, unmapped equity URLs. Rankings are not a deliverable we invent. If someone sold you a recovery package, that is not this page.
What is the difference between staging checks and launch hour?
Staging must be crawlable by the people who will sign go-live: host, robots, canonicals that will not ship as preview URLs, and templates that render. Launch hour is what staging cannot fake: DNS, certificates, the first live redirect hits, sitemap swap, Search Console coverage. A pretty staging site that stays noindex after launch is a cutover defect.
Will a clean cutover get us into AI Overviews?
No. Honest URLs that still resolve can help later extraction. A migration does not buy a place in Google AI Overviews (AIO), a generative-search mention, or an LLM visibility score. If the new HTML already tells the truth and models still cite the old host, that measurement sits on an AI search audit and on LLM SEO.
A dated cutover, then a watch
Is launch week still missing an old-to-new map?
Send the go-live date, the old host, the new host, and any spreadsheet of URLs you already have. We will name whether the map is missing, whether staging cannot be crawled, or whether the work is actually a technical queue or a WordPress permalink tidy.
- Equity URLs listed
- 301, 410, or keep
- Staging the signers can crawl
- Launch hour, then a defect watch
Map, redirect, launch, watch. Not a recovery week product.