Run a B2B landing page conversion teardown and fix queue

Start with the live landing page URL, target audience, traffic source, offer, primary CTA, and conversion goal. Use Firecrawl to extract the page copy, headings, links, forms, and visible structure. Add screenshots manually if visual layout matters, because page text alone will miss design friction.

Open Google Analytics 4 and capture sessions, source mix, conversion rate, form starts if tracked, device split, top referrers, and drop-off points. If Hotjar is available, review 5-10 session recordings or heatmaps to identify rage clicks, ignored sections, scroll depth issues, and form hesitation.

Use Claude to evaluate the page against a structured rubric: who it is for, what problem it solves, why now, why this company, proof quality, CTA clarity, friction, trust, objection handling, and mobile readability. Ask for scores and evidence from the actual page, not vibes.

Audit this B2B landing page using a conversion-focused rubric.

Page URL:
{{page_url}}

Extracted page content:
{{page_content}}

Campaign context:
{{campaign_context}}

Analytics summary:
{{analytics_summary}}

Score each area from 1-5:
1. Audience clarity
2. Problem clarity
3. Offer clarity
4. Differentiation
5. Proof and credibility
6. CTA strength
7. Form friction
8. Objection handling
9. Mobile scannability
10. Message match with traffic source

For each score, include evidence from the page or analytics. Then list the 10 highest-impact fixes.

Take the lowest-scoring sections and use Claude to create rewrite options. Prioritize the hero, subhead, CTA, proof block, and form intro before rewriting the entire page. For each rewrite, keep one conservative version and one sharper version so the team can choose based on brand risk.

Rewrite the weakest landing page sections based on this audit.

Audit findings:
{{audit_findings}}

Current copy blocks:
{{current_copy_blocks}}

Audience:
{{target_audience}}

Offer:
{{offer}}

Brand voice:
{{brand_voice}}

For each weak section, provide:
1. Problem with current copy
2. Conservative rewrite
3. Sharper rewrite
4. Why the rewrite should improve clarity or conversion

Focus on hero, subhead, CTA, proof, and form intro first.

Create an Airtable backlog with every recommended fix. Add fields for page section, issue, proposed fix, impact, effort, owner, status, and test method. Classify fixes as copy, design, form, proof, analytics, or technical. This turns the teardown into work that can be assigned.

Convert this landing page audit into a fix backlog.

Audit findings:
{{audit_findings}}

Rewrite options:
{{rewrite_options}}

Team constraints:
{{team_constraints}}

Create backlog rows with:
- Section
- Issue
- Recommended fix
- Fix type
- Impact: high, medium, low
- Effort: high, medium, low
- Owner
- Test method
- Notes

Sort by high impact and low effort first.

Implement the highest-impact low-effort fixes in Webflow. Typical first-pass changes include hero rewrite, clearer CTA, proof block repositioning, shorter form intro, trust badges, and message-match edits for paid traffic. Do not redesign the entire page unless the audit proves the structure is the actual problem.

After the changes go live, track conversion rate, CTA clicks, form starts, form completions, scroll depth, and source-specific performance. Compare against the previous period with similar traffic quality. Log results in Airtable and mark each fix as validated, inconclusive, or rolled back.