A domain change, CMS swap, redesign, or new URL scheme can leave Google and answer engines requesting addresses that no longer exist. Miraa runs the move as a project: list the URLs that can affect pipeline, choose what remains, and publish redirects from a written map.
Export URLs that rank, URLs with referring links, and URLs that answer engines already quote. Capture the export while the current host still responds, since the redirect map is built from it.
Each indexed URL is assigned the same intent on the new site, a merge into one page, or removal. Chains and loops are written into the map before the redirect file is exported. A new slug with no row leaves the old URL without a destination.
Old paths can return 404 on the day the new host, CMS, and design look finished. For each commercial URL, Miraa checks that the redirect lands on the mapped destination and that the destination HTML still includes the copy named in the map.
When the homepage responds, the open list is URLs that no longer return a fetch, canonicals that still name the old host, and answer-engine text that still cites a removed path. Commercial URLs on that list are corrected before template pages.
A crawler requests the old URL, follows the redirect, and stores the destination when the canonical matches. Internal links in the new templates, navigation included, should use that destination.
Once the mapped addresses have changed, crawl maintenance continues under Technical SEO.
Canonicals, the XML sitemap, and the host the site claims have to match the map. A canonical that still names the staging host leaves crawlers with two copies.
ChatGPT, Perplexity, Claude, Gemini, and AI Overviews quote pages they can fetch. A quoted URL that returns 404 drops out of the next fetch. The product description has to live on the destination.
The plain account of what the product is belongs with the answer engine work. The migration places that account on a URL those systems can request.
People use “replatform” for every item below. Each one produces a different redirect map.
Basic Growth, Growth+, and Hyper-Growth stay on the pricing page as the published retainers. A site migration is a separate project. The line for it is One-time project, $4,000.
Miraa does not guarantee that. The map gives every URL that already earns pipeline a destination, including pages answer engines describe. Individual queries can still move.
Your team, or whoever you hire for the interface. From Miraa you get the URL map, the redirects, and a check that the new templates still output the pages that have to be fetched.
Technical SEO keeps the current URLs fetchable and indexed. A migration replaces those addresses. You get the redirect map, the launch check, and the review after launch. Monitoring the replacement site can follow under its own scope.
Send the current domain, the destination if it is already chosen, the URLs sales actually uses, and the name of the person who can deploy redirects. Search Console access and the new environment need to be open. Paths that are still undecided are settled in the map, before launch.
The redirect gets a crawler to the new URL. Linking, the product explanation, and whether a model can quote that URL are handled with technical SEO, site structure, and answer-engine work.
From those two hosts, Miraa will say if the next project is the redirect map, or if the ranking issue is on the current URLs and a move would leave it in place.