See what your website would take to migrate.
Scan your current website to see how large the migration really is, what moves across as structured content, which setup we would recommend, and whether it fits one of our fixed-price migration packages.
Scanning
- Checking your website
- Mapping pages and content
- Finding reusable page patterns
- Checking technology and functionality
- Reviewing SEO and performance
- Building your migration assessment
Performance testing is taking a little longer. You can wait for it to finish or complete the report without performance data.
How your website is structured
What we found
Where migration can improve things
Recommended setup
What we would preserve
What stays
What changes
SEO signals we carry over
What needs a closer look
Next step
Book a call and we'll go through this assessment with you.
PageSpeed score on mobile, out of 100
until the main content appeared on mobile
2.5 s
Google counts under 2.5 s as good.
More than a page count.
The scanner maps the parts of your website that decide how big a migration really is.
Website structure
We separate genuinely different pages from reusable templates and structured content.
Content and CMS
Articles, case studies, products, locations and other repeatable content are identified as collections, not counted as individually built pages.
Technology and functionality
We look for the platform, CMS, forms, search, integrations, multilingual setup and other functionality that can affect the migration.
SEO and performance
We check the technical SEO signals that have to survive the move, and look for performance or implementation issues that can be improved during the migration.
Migration fit
Based on the public website, we recommend a target setup and tell you whether the project fits a fixed-price package or needs a closer review.
1,346 URLs doesn't always mean 1,346 pages to rebuild.
A large website can hold hundreds or thousands of articles, case studies or products that all share one underlying structure. The scanner looks for those patterns and, wherever the evidence supports it, counts them as reusable page families with structured content rather than as separately designed pages.
A page in three languages is still one page to rebuild; the translations move across as content.
We price the migration around the structure that has to be rebuilt, not the number of URLs a sitemap happens to contain.
- 42 website pages to rebuild
- 1,280 CMS entries in 5 collections
- 24 archive and system pages
Sometimes the right answer is: we need to look closer.
Parts of a website can sit behind a login, a password, bot protection or a private backend. Some sites build their pages in the browser, which leaves a scanner little to read. Shops, gated downloads and member areas can also behave differently once someone signs in.
When there isn't enough evidence for a reliable fixed price, the scanner says so instead of guessing. You still get everything it could verify, and the areas that need a manual review.
That isn't a failed scan. It means we found something worth checking before we give you a price.
Straight answers.
Is the Website Migration Scanner free?
Yes. You can scan any public website and see the assessment without creating an account or booking a call.
How accurate is the migration estimate?
The scanner works from the publicly accessible website: its pages, reusable content, technology and functionality.
Straightforward websites can often be placed in a fixed-price package straight away. When something important can't be verified publicly, the result asks for a manual review instead of making assumptions. We confirm the final scope before work begins.
Why is the page count different from the number of URLs on my website?
Because for a migration, URLs and pages aren't the same thing.
Hundreds of blog posts, case studies or products can share one reusable template, and a page in several languages is still one page. The scanner separates structured content from genuinely different page structures, so the estimate reflects the work of rebuilding the site.
Why didn't I get an instant price?
The scanner only shows a fixed-price package when it has enough information to place the migration confidently.
Login, ecommerce, unusual backend functionality, a very large website or sections it can't reach may need a review from us before we confirm the scope.
Can the scanner see pages behind a login or password?
No. It reads only what's publicly accessible and never tries to get past a login, a password or other access controls.
It also follows your robots.txt: if that asks crawlers to stay out, the scanner stays out. If protected functionality looks relevant to the migration, it's flagged for review.
Which platforms does the scanner recognize?
Any public website can be scanned. The scanner recognizes common platforms, including WordPress, Webflow, Wix, Squarespace, Framer, Shopify and HubSpot.
On WordPress it also reads the public content API where it's available, which makes the page count more precise.
Why does a new scan show the same result?
Results are saved for 24 hours. Scanning the same website again within a day shows the saved report, so a change you've just made shows up in a scan the next day.
How long does my report link stay available?
30 days. Anyone with the link can open it, and it isn't listed anywhere or indexed by search engines.
We keep a fuller copy of the scan for 90 days, which becomes the starting brief if you go ahead with a migration.
Popular migrations.
What moving off a specific platform involves: what comes across, what gets rebuilt and where the work is.
Want to talk it through?
If you have questions about your scan, want to confirm the scope or are ready to move the website, we can go through the next step together.