Rebuilds, however they're built
Lovable, v0, Bolt, a hand-rolled Next.js app - the build tool doesn't matter. Run the scorecard before the client sees the site.
We do the heavy lifting.
Nothing gets left behind.
Moving a site is like moving a house: the new place is only good if everything actually arrives. Put your address in. In 20 seconds you will know what your site is built with, and every part of it a move can silently break: your forms, your search rankings, your shop, your images.
Free, no account. We read the page and tell you what is at risk.
20 seconds, not 20 minutes
Nothing installed on your site
No email required
Tell us the two platforms. We know what breaks in that move.
The failures are not random. Wix-to-WordPress loses something different from Squarespace-to-Shopify. Pick your move and the scan starts from the things that actually go missing in it.
Moving from Wix
to WordPress
- Wix SEO defaults that WordPress does not recreate
- Image URLs that change and break old links
- Pages that need redirects or they 404
Moving from Squarespace
to WordPress
- Squarespace URL structure, rebuilt differently
- Every saved link breaking on day one
- Lost meta descriptions on every page
Moving from Squarespace
to Next.js
- Structured data and Open Graph tags that do not survive
- Blog URLs and their rankings
- A contact form with nothing behind it
Moving a store
to Shopify
- Products, prices and pictures that did not all arrive
- Old product links that no longer resolve
- Search listings going blank
Moving from GoDaddy
to Webflow
- Title tags replaced by Webflow defaults
- URLs changed without redirects
- Alt text lost on every image
Moving from WordPress
to a headless build
- Years of Yoast and Rank Math settings dropped
- Custom fields never ported
- RSS feeds that stop existing
Moving from Shopify
to a custom storefront
- Product and Offer schema no longer generated
- Collection and product handle URLs
- Canonical tags on variant pages
Somewhere else
anything with a URL
- Run the free scan and see what your site depends on
- Works on any platform, on either side
- No account, no install, 20 seconds
A real rebuild, verified: six iterations to green
6
Iterations to fix
7/7
Checks passing
4
Issues caught pre-launch
New websites break things nobody notices right away
Every agency has lived some version of it. The new site goes live, the client is thrilled, and three weeks later the calls start: a form that never submitted, a page that lost its meta data, traffic sliding because structured data quietly disappeared in the move.
Building the new site got faster. Checking it still looks like 2019: eyeball a few pages at a couple of widths, spot-check some titles, and hope the parts you didn't look at held. The pages nobody opens are the ones that cost you the client.
It's a move with no inventory: everything arrives, and nobody checked the list.
Seven checks, old site against new
MigrateKit scores the difference between the old site and the new one. The baseline is what the client already had.
| Check | What it answers |
|---|---|
| SEO preservation | Did titles, meta descriptions, canonicals, Open Graph tags, headings, and structured data survive the rebuild? |
| Content completeness | Is every text block, link, image, and heading from the old site accounted for on the new one? |
| Visual fidelity | Does it match at desktop, laptop, tablet, and mobile widths? Pixel-level comparison at four breakpoints. |
| Performance | Are Core Web Vitals (LCP, CLS, TBT, TTFB) and page weight as good or better than before? |
| Accessibility | Did the rebuild introduce new WCAG 2.1 A/AA violations the old site didn't have? |
| Images | Do all images load on the new site, at their original resolution, with no upscaling or format downgrades? |
| Functionality | Do the links resolve, forms submit, mobile menu open, and anchors scroll? |
Every check has a target and a pass/fail gate. The output is a client-ready summary and machine-readable JSON, so it drops into a CI pipeline or an agent workflow as easily as into a client email.
Two URLs in, a scorecard out
Point it at both sites.
The old site live, the new one on staging. Any platform, any stack: Wix, Squarespace, Duda, WordPress, Webflow, Next.js, anything with a URL.
The suite runs.
Seven checks, every breakpoint, before/after metrics. A full pass takes minutes.
Read the Scorecard.
Pass/fail per check, with the exact failing pages, tags, and elements listed. Fix, re-run, ship when it's green.
Where it fits
Platform migrations
Moving a client off Wix, Squarespace, Duda, or old WordPress. Prove nothing was lost in the move.
Redesigns and replatforms
When the design is meant to change, skip the visual check and keep the other six: content, SEO, accessibility, and function still have to survive.
Questions we get
By hand, at four breakpoints, on every page, including the structured data and the Open Graph tags? The Scorecard does that in minutes and produces evidence you can attach to the invoice.
Those tools compare your site to its own last commit, on one codebase. They are excellent at that. MigrateKit compares two different sites on two different stacks, which is what a rebuild actually is. No CI integration on the old site required, because you usually don't have one.
No tool can promise rankings. The Scorecard proves the on-site signals search engines read (tags, content, structure, speed) survived intact. That is the part of SEO a rebuild can destroy and the part you control.
Run the checks that should hold and skip the ones that shouldn't. A redesign keeps content, SEO, accessibility, and functionality checks; the pixel comparison is for like-for-like rebuilds.
If both sites load in a browser, MigrateKit can score them. It reads the rendered pages, not your framework.
Either way works. MigrateKit scans your old site against your new one and proves what did not come across, so you or your builder can fix it before launch. If you would rather not run the move yourself, we also take on managed moves by request: we rebuild the new site, move the content, set up the redirects, and hand you a passing scorecard before anything goes live. Either way, what we verify is the public-facing layer - pixels, SEO, content, speed, accessibility, and rendered functionality like links, forms, and menus. Server-side business logic behind your app is not in scope; that needs its own tests.
Free scan. Free report. We charge for the move.
The free scan reads one page in about 20 seconds, no account. The full Verification Report is free too: your old site against the new one across all seven checks, with the failing pages, tags and links listed, re-run until it passes. The store catalog and old links are covered when the new store is Shopify.
If you would rather not run the move yourself, we do it: managed migration from $2,500, quoted per site.
See full pricingWhat is it built with? That decides how you confirm it.
A full comparison reads both sites, so before it runs you confirm you control them - the same way Google Search Console does it. The platform you are on decides which method is easiest. Not sure? Upload a file.
WordPress
Add a line of codeA code snippet plugin, or the theme's header. No file access needed.
Wix
Add a line of codeSite Verification, or Custom Code placed in the head. Needs a paid plan.
Shopify
Add a DNS recordSettings, Domains, DNS settings. No theme editing, so no code to break.
Squarespace
Add a DNS recordWorks on every plan. Code injection needs a Core plan or above.
Webflow
Add a line of codeHead code in site settings, then publish. Custom code needs a paid plan.
GoDaddy Website Builder
Add a DNS recordThe only route on this product - it has no site-wide code field.
Not sure / something else
Upload a fileOne small text file in your web root, wherever that is hosted.
You only do one of the three. The dashboard shows the exact tag, file name or record to add for your platform and checks all three when you press the button. Step-by-step for each: how to confirm a site is yours.
We can move it for you.
You do not have to run the move yourself. Give us both addresses and the access we need, and we handle it end to end: we rebuild the new site, move the content, set up the redirects, and verify every check is green before anything goes live.
What a managed move includes
We do the packing. Content, images, SEO tags and structured data are carried across and checked item by item, not by eye.
We do the driving. Redirects for every old address, forms wired up, the mobile menu tested, and the new site checked at four screen widths.
You get the inventory list. The full pass/fail scorecard for the finished move, which you can keep, or forward to whoever is paying for it.
Nothing goes live until it passes. If a check fails, it gets fixed before the domain is pointed at the new site.
Managed moves start at $2,500 and are quoted per site, so we will ask about the page count, the platform and the catalog size before quoting. Start with the free scan below and tell us you want us to handle it, or email [email protected].
Now check the whole move.
The free check reads one page. When your new site is up, the full Verification Report runs your old site against it across all seven checks - the failing pages, links, images, forms, and search signals listed by name - free, and you can re-run it until it passes.