How to Audit a Prospective Client's Website Before You Take the Project.

Why Should You Audit a Website Before Taking the Project?

Most freelance Webflow developers accept projects based on a sales call and a budget agreement. They start the discovery phase, realize halfway through that the existing site has deeper problems than the client described, and then either absorb the unpaid extra work or create an uncomfortable conversation about scope changes. Both outcomes damage the project before it even properly begins.

A pre-project website audit solves this problem. Before you commit to a timeline or price, you spend 60 to 90 minutes examining the prospect's current website for technical issues, content gaps, SEO problems, and structural concerns. The audit becomes a valuable deliverable in its own right (many prospects will pay for a standalone audit) and it calibrates your proposal to the actual state of the site rather than to what the client thinks is there.

After 70+ client projects, I have a systematic audit process that takes 90 minutes, produces a clear report, and consistently catches issues that would have created scope creep if I had not noticed them upfront. Here is how the audit works.

What Should You Check in the First 15 Minutes?

Start with the structural overview. Visit the homepage, primary service pages, About page, and Contact page. Note the platform (WordPress, Webflow, Squarespace, custom), the overall design quality, and the primary conversion paths. This orientation phase gives you the lay of the land before diving into specifics.

Run the homepage through Google PageSpeed Insights. Note the mobile and desktop Core Web Vitals scores. A site failing multiple Core Web Vitals is likely to need significant performance work, which affects your proposal. Pay special attention to INP (Interaction to Next Paint), which is the most commonly failed metric in 2026.

Check the site's mobile experience directly on a phone. Many sites that look fine on desktop are broken on mobile. Text too small, buttons too close together, navigation that does not work, images that push beyond the viewport. Mobile problems often signal that the site was built desktop-first without proper responsive consideration.

How Do You Audit the Content and SEO Foundation?

Check basic SEO hygiene. View the page source of the homepage and verify: is there a title tag? A meta description? A canonical URL? Open Graph tags with an image? Schema markup of any kind? Sites missing these fundamentals often need significant SEO work even before content improvements.

Run the homepage URL through a schema testing tool (Schema.org Markup Validator or Google's Rich Results Test). Note what schema is present and what is missing. Most sites have minimal or incorrect schema. A site with no Organization, LocalBusiness, or Article schema has significant untapped SEO potential.

Search the site name in Google. What does Google actually show? Is the homepage ranking for the brand name? Are there duplicate pages appearing? Are the meta descriptions compelling or generic? The Google results view reveals how search engines actually present the site, which differs from how it appears to the client.

Check Google Search Console if the client grants access. Coverage errors, indexing problems, and manual actions reveal issues the client might not even know about. A site with 50 pages excluded due to "soft 404" errors has structural problems that must be addressed in the project.

What Technical Issues Should You Look For?

Check the site's robots.txt file at yourdomain.com/robots.txt. Verify nothing important is blocked. Some sites accidentally block entire sections from crawlers, which kills SEO silently. Check the sitemap.xml as well. Is it present? Does it include all important pages? Are old deleted URLs still listed?

Inspect the HTML structure. Are heading tags used semantically (one H1 per page, proper H2/H3 hierarchy)? Or is the site using h1 tags for everything including navigation items? Poor heading structure is a common issue that affects both SEO and accessibility.

Run the homepage through WAVE (web accessibility evaluation tool) or Chrome Lighthouse's accessibility audit. Note the number of issues and their severity. A site with 50+ accessibility errors has significant compliance risk that should be factored into the project scope, especially for clients in healthcare, finance, education, or government-adjacent industries.

Check page load performance for 3 different page types: homepage, a service page, and a blog post. Load times and performance scores often vary significantly across page types. A fast homepage with slow service pages suggests template or content issues specific to those pages.

How Do You Evaluate the Design System?

Check design consistency across pages. Are the same fonts used everywhere? Are spacing values consistent? Do buttons look and behave the same on every page? Inconsistency signals that the site was built piecemeal without a design system, which usually means the rebuild will need to establish one from scratch.

Count the number of colors used across 5 pages. If you find 15+ different colors, the site lacks a color palette. If you find fonts that change between pages, the site lacks typography rules. These are tractable problems but they require explicit scope in the proposal.

Look at the site's interactions and animations. Are they smooth or janky? Do they work on mobile? Are there animations that fail, broken scroll effects, or modals that do not close properly? Existing interactions often need to be completely rebuilt during a redesign because they carry forward the original design debt.

How Do You Check for Conversion Issues?

Try to complete the site's primary conversion action (submit the contact form, sign up for the newsletter, request a demo). Note any friction: forms that fail to submit, confirmation pages that look broken, automatic emails that do not arrive. Conversion path breaks are the most important issues to fix because they directly affect the client's business.

Evaluate the CTAs throughout the site. Are they visually distinct? Is the copy specific ("Book a free consultation") or generic ("Learn More")? Are CTAs placed at decision points on the page? Weak CTAs are often the biggest conversion opportunity and the easiest to improve.

Check the contact form specifically. How many fields does it have? Research from Unbounce shows that every additional form field reduces conversions by 11%. Forms with 7+ fields are typically losing 50% or more of potential leads. This is low-hanging fruit for the redesign.

How Do You Present the Audit to the Prospect?

Compile your findings into a structured report with three sections: critical issues (things that must be fixed for the site to function properly), major opportunities (improvements that would significantly impact business results), and polish items (minor refinements that would improve quality). This structure helps prospects prioritize and understand where budget will produce the most return.

Include specific screenshots and examples. An abstract finding like "accessibility issues" is less impactful than a screenshot showing specific problems. Visual evidence makes the findings tangible and credible.

Present the audit as a consultation rather than a sales pitch. The goal is to demonstrate expertise and diagnose the actual state of the site. Some prospects will decide the work is bigger than their budget and not hire you. That is a win, because the project would have been a bad fit. Others will be impressed by your thoroughness and hire you based on the competence demonstrated during the audit itself.

How to Set Up Your Audit Process This Week

Create an audit template document with the categories covered here: structural overview, SEO foundation, technical issues, design system, and conversion issues. Use the template for every prospect conversation. The consistency makes your audits efficient and comprehensive.

Charge for standalone audits as a paid deliverable. A $500 to $1,500 audit report is valuable to prospects even if they ultimately do not hire you for the full project. Some will pay for the audit and hire you later. Others will pay for the audit and refer you to colleagues. Either way, you get paid for work you were doing during the sales process anyway.

For the technical SEO checks that audits include, my guide on Webflow SEO settings you are probably ignoring covers what to look for. For the conversion optimization issues that audits reveal, my article on why your Webflow contact form is losing leads covers common form failures. And for the client relationship framework that audits support, my reflection on lessons from 50 client projects covers the scoping practices that prevent future problems.

A 90-minute audit before the project starts saves 40 hours of scope creep during the project. It is the single most valuable pre-project practice I have developed in 5 years of Webflow freelancing. If you want help setting up your own audit process, I am happy to walk through it. Let's chat.