I Paste a Live URL Into Claude, Then It Audits and Fixes My Entire Webflow Site

I've been building in Webflow for a while. But the part of the job I've always hated is the audit. Dead links, OG images missing from CMS items, redirect chains, alt text that doesn't exist, forms going nowhere. It's tedious, it's manual, and clients don't pay for it — they pay for the site working.

The audit is the thing you do so the site doesn't embarrass you later. And until recently, it was my least favorite hour of any project. Now it takes me the time it takes to paste a URL.

Here's the full workflow — no fluff, no theory, just exactly what I do.

The first part is the simplest. I open a Claude conversation and paste something like this:

"Here's my live Webflow site: https://example.com. Audit it for broken links, missing OG images, SEO issues, accessibility gaps, CMS inconsistencies, and any layout problems."

That's it. No MCP connection. No API keys. No setup. Just the URL.

Claude crawls the live site and within a couple of minutes, I get back a full report. Here's what a typical audit looks like:

• Dead links — 3 internal links pointing to old slugs that were moved during dev
• OG images — 14 CMS blog items missing custom OG images, defaulting to the site-wide fallback
• Alt text — 7 images with empty or generic alt attributes
• Broken form redirects — contact form redirecting to a staging URL that went stale after launch
• Layout issue — one card component breaking at 375px width on mobile

None of these are catastrophic individually. But together? They're the kind of thing that makes a site feel unfinished — and they're exactly the kind of thing clients don't notice until their marketing team points it out.

The audit is the thing you do so the site doesn't embarrass you later. Not a single one of these issues would break a site — but together, they make it feel careless.

Once I have the audit report, I connect Claude to the Webflow site using MCP. This is the only technical step, and it takes about a minute.

MCP — Model Context Protocol — is what lets Claude actually interact with a platform instead of just talking about it. Once connected, Claude has access to the Webflow Designer: CMS collections, page settings, SEO fields, interactions, the works.

I hand Claude the audit report and say something like:

"Here's the audit report from step one. Connect to the Webflow site and fix everything on this list. For the OG images, use the CMS item titles and site branding to generate proper images. Fix dead links to their correct URLs. Add proper alt text. Fix the card at 375px."

And then I watch.

Here's what Claude does inside Webflow, item by item:

• Opens each CMS collection item and updates the OG image field with properly branded images
• Goes through every broken link, finds the correct destination, and updates the href
• Adds descriptive alt text to every image that was missing it
• Updates the contact form's success redirect from the old staging URL to the production one
• Adjusts the card component's flex properties so it stops breaking at 375px

It works through the list systematically. Some fixes take a few seconds. Complex ones — like the card layout bug — take a bit longer because Claude has to inspect the component structure first.

The whole process, from pasting the URL to having every fix applied, takes about 20 minutes. The same process manually used to take me two to three hours across multiple tabs — Webflow Designer, browser devtools, various testing tools, and a Notion checklist.

Twenty minutes end to end. Same process manually took two to three hours across Webflow, devtools, testing tools, and a scattered to-do list.

Here's the key thing: Claude isn't replacing my judgment. It's replacing the clicking. I still decide what gets fixed and how. Claude just does the actual work of navigating the Webflow UI, opening panels, editing fields, and saving. I review, approve, and move on.

Most freelancer blog posts about AI are either "AI will replace us all" panic or "AI is a toy, learn to code" gatekeeping. The reality is somewhere in between and way more useful.

Here's what this workflow gave me:

• Site audits went from "something I dread" to "something I do during coffee." The psychological difference between dreading an audit and knowing it'll take 20 minutes is bigger than the actual time saved.
• I ship cleaner sites. When audits are fast, I do them more often. More audits mean fewer embarrassing bugs that clients find first.
• Clients notice the polish. When OG images are present on every CMS item and every link goes somewhere real, the site feels intentional. That's hard to quantify, but it's what separates professional work from good-enough work.
• I can charge more for maintenance. Not because I'm doing more work — because I'm delivering better work in less time. And clients pay for outcomes, not hours.

I want to be clear about the limits because I hate blog posts that pretend AI is magic:

• Claude cannot make design decisions. It can fix a layout bug, but it can't tell you whether that card should be two columns or three. That's still your job.
• Claude cannot understand brand nuance. It'll write alt text, but it won't capture your client's voice unless you give it very specific instructions.
• Claude can miss things. It's good, but it's not perfect. I always spot-check the fixes before shipping.

This workflow doesn't replace me. It replaces the part of the job I never liked doing anyway. The audit, the grunt work, the CMS clicking marathon. The part where I'm not being creative — I'm just being thorough.

This doesn't replace me. It replaces the part of the job I never liked doing anyway: the audit, the grunt work, the CMS clicking marathon. The part where I'm being thorough, not creative.

If you're a Webflow developer — especially a freelancer handling multiple client sites — try this tomorrow:

1. Open Claude and paste a live URL from one of your client sites. 2. Ask for a full site audit — dead links, OG images, SEO, accessibility, layout. 3. Read the report. You'll probably find at least one thing you missed. 4. If you have MCP set up, connect Claude to Webflow and let it apply the fixes. 5. Spot-check everything. Then ship.

The first time you do this, you'll feel a little weird watching an AI click through your Webflow dashboard. By the third time, you'll wonder why you ever did audits any other way.