Webflow developer — CRO landing page + local SEO build for auto body lead gen platform
What we're building We're launching a commission-based lead generation platform connecting LA car owners with vetted auto body shops. We're starting with a single-shop pilot and need a Webflow site built to convert high-intent search traffic — people who just had an accident and are searching right now. Every element of this build must serve one goal: get a visitor to call or submit a form within seconds of landing. This is a CRO-first project, not a design showcase. What we're handing you You will not be designing from scratch. All creative assets are provided: Figma wireframes and mockups — full page layouts ready for build, including mobile breakpoints Copy — all headlines, body text, CTAs, and form labels written and finalised Branding — logo, colour palette, typography, and brand guidelines Your job is to build it accurately and make it perform — pixel-fidelity to the Figma, fast load times, and every integration working correctly on day one. Scope of work 1. Webflow homepage — CRO-optimised Built faithfully from Figma. Above-the-fold headline, trust signals (star ratings, review count), sticky click-to-call bar on mobile, lead capture form. Passes Core Web Vitals. No bloat. 2. Neighbourhood landing page template (×1, cloneable) Built as a Webflow CMS collection template we can duplicate per suburb without a developer. Example: "Auto Body Repair in Pacoima, CA." Adding a new location should be a content edit, not a build task. 3. Schema markup — LocalBusiness + Service LocalBusiness schema on every page. Service schema on each neighbourhood landing page. Correct NAP consistency throughout. Validated in Google's Rich Results Test before handover — not just installed, confirmed working. 4. LSA landing page alignment Pages structured to support a Google Local Services Ads campaign — NAP consistency, service area alignment, page experience aligned with Google Guaranteed verification requirements. You should know what this means without us explaining it. 5. CallRail dynamic number insertion Every call tracked and attributed to its source channel. We supply the CallRail account and numbers — you integrate DNI correctly in Webflow. 6. Lead form with instant notification Name, phone, zip, damage description. SMS or email alert to the shop on submission. No CRM needed at this stage. 7. Tracking stack — GTM, GA4, Meta pixel GTM container configured in Webflow. GA4 and Meta pixel firing correctly. Form submissions and calls tracked as conversion events. Google Search Console connected and verified. What we need from you Webflow — native CMS collections, custom code embeds, Figma-to-Webflow builds in portfolio CRO fundamentals You design for conversion, not aesthetics. You know what above-the-fold means and act on it. Schema markup LocalBusiness + Service schema implemented and validated, not just copy-pasted Google LSA familiarity You understand what Local Services Ads require from a landing page — no briefing needed CallRail / DNI Dynamic number insertion in Webflow — you've done this before GTM + GA4 + Meta pixel Full tracking stack configured and verified — not just installed Timeline Live within 10–14 days of project start. This is a hard deadline — it is gating a paid ad campaign. If your current workload can't accommodate that, please don't apply. To apply — three things only A Webflow site you've built for a local service business — ideally one built to generate calls or leads, not just look good. One sentence on how you'd structure the CMS collections for a cloneable neighbourhood landing page. Your realistic timeline from receiving Figma files to published site. Question 2 is a filter. If you're not sure what a CMS collection is in Webflow, this project isn't the right fit. This is a pilot build for one shop. If the model performs, we replicate the same template across 10–15 LA neighbourhoods. The right developer becomes the go-to for that rollout. Apply tot his job Apply To this Job