A Webflow-native audit engine that turns website issues into qualified leads

SoFlow built a Cloudflare Worker audit backend with D1 storage so a submitted website turns into a structured technical report, a reusable sales asset, and a qualified lead — all inside a Webflow-branded flow.
SoFlow Audit Engine
Client
SoFlow Audit Engine
Timeline
Case study draft
Services
No items found.
About

A branded audit product that turns a submitted URL into a sales asset

This implementation shows how SoFlow turns technical SEO, accessibility, performance, and Webflow implementation checks into a branded product experience. The public page stays in Webflow, while Cloudflare Workers handle crawling, scoring, storage, report rendering, and notifications.
Challenge

Proving capability before the sales call

A normal contact form can capture a lead, but it doesn't prove technical capability or give a prospect an immediate reason to trust the agency.

The site needed a way to translate invisible technical issues — the kind a business owner or marketing team can't see on their own — into a report they could actually understand and act on.

Goal

A backend serious enough to earn trust in one submission

The goal was a Cloudflare Worker audit backend with D1 storage, public audit routes, generated report assets, export endpoints, and optional integrations for Browser Rendering, PageSpeed data, OpenAI summary polishing, and webhook notifications.

Webflow stays the marketing surface throughout; the Worker owns the entire dynamic report workflow behind it.

Result

A Webflow-native product that turns a URL into a report and a lead

The audit engine turns a website submission into a structured report with prioritized findings, methodology notes, and Webflow-aware recommendations — and creates a repeatable product story for SoFlow's technical SEO and Webflow services in the process.

Stack
Webflow, Cloudflare Workers, Cloudflare D1, Browser Rendering, PageSpeed Insights, JavaScript
Systems
Webflow, Cloudflare, Google PageSpeed Insights, Google Apps Script webhook
Category
SEO / AI Search
This is some text inside of a div block.

The brief was to create a branded website audit experience for SoFlow that lives naturally on its own Webflow site while producing genuinely useful technical reports for prospects.

The tool needed to feel like a public marketing product, not a disconnected developer utility bolted onto the site.

This is some text inside of a div block.

A normal contact form can capture a lead, but it doesn't prove technical capability or give the prospect an immediate reason to trust the agency.

The site needed a way to translate invisible technical issues into a report a business owner or marketing team could actually understand.

This is some text inside of a div block.

The implementation had to fit inside an existing Webflow site, avoid exposing private generated reports to search engines, store audit results reliably, and support external services like PageSpeed, browser rendering, and webhook notifications.

It also had to stay bounded, so a free audit could complete quickly rather than behaving like a full enterprise crawler.

This is some text inside of a div block.

SoFlow implemented a Cloudflare Worker audit backend with D1 storage, public audit routes, generated report assets, export endpoints, and optional integrations for Browser Rendering, PageSpeed data, OpenAI summary polishing, and webhook notifications.

The Webflow page remains the marketing surface throughout — form, branding, and layout — while the Worker owns the entire dynamic report workflow behind it.

This is some text inside of a div block.

Webflow renders the public audit form and report shell. A submitted URL goes to the Cloudflare Worker, which normalizes the target, runs a bounded set of crawl checks, stores the result in D1, optionally enriches it with Browser Rendering, PageSpeed, and OpenAI summary passes, and serves the finished report data and assets back to the public Webflow pages.

This is some text inside of a div block.
  • Lead capture through a branded, Webflow-hosted audit form
  • D1-backed audit status and report storage
  • Bounded crawl checks for metadata, redirects, robots, sitemap, links, and page structure
  • Optional rendered DOM, accessibility (axe), and visual QA evidence when browser rendering is available
  • Private-route SEO handling so generated report URLs stay out of public search results
This is some text inside of a div block.

The audit engine turns a website submission into a structured report with prioritized findings, methodology notes, and Webflow-aware recommendations — and creates a repeatable product story for SoFlow's own technical SEO and Webflow services.

This is some text inside of a div block.
  • Stores the full audit lifecycle and report payloads in Cloudflare D1
  • Serves separate public audit, report, and audit-derived quote routes
  • Falls back gracefully when optional integrations like PageSpeed or OpenAI are unavailable
  • Keeps public Webflow pages fully separate from private backend execution and credentials
This is some text inside of a div block.

Why build a full audit backend instead of just a contact form?

A contact form captures a lead but gives a prospect no reason to trust the agency yet. This engine trades that gap for proof: submit a URL, get a structured report on real, specific issues — metadata, redirects, crawlability, structure, and optionally rendered and accessibility checks — before a sales conversation even starts.

Can this audit engine replace a full manual audit?

No. It's designed as a fast technical and strategic starting point. A deeper professional audit expands the findings, confirms edge cases the bounded crawl can't reach, and turns the report into an implementation plan.

Can this pattern be adapted for other lead tools?

Yes. The same Webflow-front, Worker-backend architecture can power calculators, diagnostics, eligibility checks, product selectors, or any other Webflow-native lead tool that needs real backend logic behind a simple public form.

This is some text inside of a div block.

This build proves SoFlow can turn Webflow into a genuine product interface, using Cloudflare Workers for the secure backend logic, storage, and report generation that Webflow was never meant to own directly.

This is some text inside of a div block.

Why build a full audit backend instead of just a contact form?

A contact form captures a lead but gives a prospect no reason to trust the agency yet. This engine trades that gap for proof: submit a URL, get a structured report on real, specific issues — metadata, redirects, crawlability, structure, and optionally rendered and accessibility checks — before a sales conversation even starts.

Can this audit engine replace a full manual audit?

This is some text inside of a div block.

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

This is some text inside of a div block.

Heading 1

Heading 2

Heading 3

Heading 4

Heading 5
Heading 6

Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.

Block quote

Ordered list

  1. Item 1
  2. Item 2
  3. Item 3

Unordered list

  • Item A
  • Item B
  • Item C

Text link

Bold text

Emphasis

Superscript

Subscript

This is some text inside of a div block.
This is some text inside of a div block.
Before

Before the implementation, technical website issues were mostly discussed manually after a prospect had already contacted SoFlow.

There was no reusable product surface connecting audit expertise, report proof, and lead capture into a single flow.

After

After the implementation, SoFlow has a public audit funnel, generated report pages, reusable report assets, and a stronger way to open technical SEO conversations from real, specific evidence.

This is some text inside of a div block.

Webflow is excellent for the public page and conversion flow, but audit logic needs backend execution, API keys, storage, generated report URLs, and crawler safeguards that page-level custom code can't safely hold.

Putting that logic into browser-facing custom code would expose credentials, limit reliability, and make report storage effectively impossible.

Let's talk

Ready to elevate your business?