Click Here
Before we scope

How we audit Webflow sites before we scope a project

Two internal tools give us the facts before we write a proposal: a Migration X-ray for sites moving to Webflow, and a Site Health Check for live Webflow sites.

Request a site audit
Chrome magnifying glass inspecting a glowing blue wireframe of a website page
Layer Image

Why we audit before we scope

A proposal is only as good as what we know about the site. Before we estimate a migration, a rebuild or a maintenance plan, we run one or both of these tools and use what they find to shape the scope with you.

They are internal tools, not a public scanner. We run them on request, for sites you own or are authorised to share, as part of a scoping conversation or an engagement.

See what each tool checks

Our audit tools

Two tools we run before we scope

Bg layer
For migrations
Migration X-ray
For sites moving to Webflow. It reads the current site's sitemaps and any exports you share, then drafts the redirect plan we scope against.
What it produces:
A URL inventory of every URL found in the sitemaps and exports, with status, title and canonical for a sample
Template clusters such as /blog/{slug}, with a low-to-high estimate of how many pages are CMS-driven
A redirect-map draft that marks each old URL keep, redirect or decide, with a confidence level
A Webflow 301 CSV, checked by our validator for format, wildcards, duplicates, loops and chains
Risk flags ranked high, medium or low, such as URLs cited in AI answers whose path would change
Bg layer
For live Webflow sites
Webflow Site Health Check
For Webflow sites we manage, or that the owner asks us to review. It runs 33 read-only checks and writes a one-page report with a traffic-light result for each.
What it checks:
Domain: HTTPS, one canonical host, HSTS, DNS against Webflow's current records, and CAA
Crawling: robots.txt, search and AI search crawler access, the sitemap, homepage indexing and staging visibility
A sample of pages: status, noindex, canonicals, titles, descriptions, H1s, heading order, alt text and Open Graph images
Structured data, HTML size, scripts, images and autoplay video, plus Chrome UX Report speed data when it is available
Webflow details such as the last published date, and whether privacy and terms links are present
Bg Layer Image
Before scoping
How it fits an engagement
We run these tools as part of a scoping conversation or an engagement. Each run starts with your go-ahead.
How a run works:
You confirm that you own the site or are authorised to share it
We run the tool that fits: the X-ray for a migration, the Health Check for a live Webflow site
We review each report before we share it and correct any finding that is wrong
The findings feed the scope and the proposal we discuss with you
Run folders and reports are deleted 90 days after the run unless a project starts

What the output looks like

  • Migration X-ray: a run folder with inventory.csv, clusters.csv, redirect-map-draft.csv, a validated webflow-301-draft.csv with its import notes, risk-flags.csv and a summary labelled “Pre-migration estimate”.
  • Site Health Check: a one-page HTML report for each site that can be printed to PDF. Each check is marked Fix, Attention or OK, or Unable to determine when the answer can't be seen from outside, with a plain-English fix. Hard blockers are listed at the top.
  • What the tools keep: derived facts only, such as status codes, titles and counts. Page bodies are not stored, and email addresses are removed from what is kept.
  • What the tools never do: log in, submit forms, get past bot challenges or change anything on the site. They follow robots.txt and send about one request per second, with a cap on requests per run.
  • Limits: page checks use a sample of 50 pages by default, so a clean sample does not prove every page is clean. Lab speed tests are a separate step.
Website audit checklist with items marked Pass and two flagged for Attention
Request a site audit
FAQ’s

Frequently Asked Questions

(01)
Is there a public version I can run myself?

No. Both tools are internal. We run them on request for sites you own or are authorised to share, as part of a scoping conversation or an engagement.

(02)
What do you need from us?

The site URL and your confirmation that you can authorise the check. For a migration, exports help: a Search Console pages export, a crawl export, or a list of URLs cited in AI answers. We can also work from saved sitemaps.

(03)
Will the audit change or slow down our site?

The tools make no changes. They only send GET and HEAD requests, follow robots.txt, pace themselves at about one request per second and stop at a fixed request cap.

(04)
Does a clean report mean the site has no problems?

No. Page checks use a sample, and some answers can't be seen from outside, for example when the site sits behind a proxy. In that case the report says Unable to determine instead of guessing.

(05)
Is the redirect-map draft a finished migration plan?

No. It is a draft labelled Pre-migration estimate. Rows that need a human decision are marked decide and left out of the import file, and we agree them with you during the project.

(06)
How long do you keep the results?

Run folders and reports are deleted 90 days after the run, unless a project starts.

(07)
Do you share client data in sample reports?

No. The sample output described on this page uses no client data. Reports for your site are shared only with you.

Layer
Want us to look at your site?
Tell us what you are planning and we will confirm which checks fit.
Request a site audit