Skip to content

Fix product identity mismatch: footer and free-tools page language - #477

Open
manazoid4 wants to merge 3 commits into
mainfrom
claude/ecstatic-volta-gvaah5
Open

Fix product identity mismatch: footer and free-tools page language#477
manazoid4 wants to merge 3 commits into
mainfrom
claude/ecstatic-volta-gvaah5

Conversation

@manazoid4

Copy link
Copy Markdown
Owner

Summary

  • Footer CTA language was using old domestic lead-gen copy ("SCAN MY AREA FREE", "LOCK YOUR PATCH") that directly contradicted the FTS public tender qualification product — especially damaging because it appears on every page. Updated to "CHECK FTS FREE →" and "SEE PILOT PRICING →". Headline updated to "CHECK THE CURRENT FTS FEED. FREE. NO CARD NEEDED."
  • Footer nav links fixed: "Scan My Area" → "Find Opportunities" (now matches TopNav), "How It Works" link changed from /blueprint/methodology (now matches TopNav). Removed stale "Retrofit Leads" and "By Trade" links that don't belong in the current FTS product nav.
  • Footer trust copy updated: removed "Local knowledge baked into every signal score" (domestic framing) and replaced with "Public Works Qualification — not a domestic lead directory" to set clear expectations.
  • Free-tools page hero was comparing JobFilter to "Checkatrade, Bark, and MyBuilder" and stated "Leads are the paid part." Both are wrong for the FTS product. Updated to: "The public tender qualification is the paid part."
  • Free-tools comparison table removed stale features (Vantage bid decks, Vicinity proof generator, WhatsApp lead alerts) and replaced with accurate current features (FTS opportunity scan, firm-aware qualification, evidence/requirement gaps, outcome tracking).
  • "LOCK MY PATCH" CTAs throughout free-tools page changed to "SEE PILOT PRICING" — territorial language contradicts "PUBLIC OPPORTUNITIES — ACCESS IS NOT EXCLUSIVE" guarantee shown on homepage.

What changed

File Change
src/components/Footer.tsx Footer CTA headline + buttons, nav links, trust copy
src/pages/FreeToolsPage.tsx Hero copy, comparison table, CTA buttons

Why this matters

A UK tradesman landing on any page scrolls to the footer and reads "LOCK YOUR PATCH" — which implies territory exclusivity (the Checkatrade model). The homepage explicitly says the opposite. This inconsistency destroys trust before the £39 decision. Every fix here reduces friction on the path to paid activation.

Validation

  • TypeScript: passes (npx tsc --noEmit — clean)
  • No logic changes — copy and link targets only
  • Mobile layout unaffected (structural markup unchanged)

Generated by Claude Code

Footer was using domestic lead-gen language ("SCAN MY AREA FREE",
"LOCK YOUR PATCH") that contradicted the FTS public tender qualification
product. Fixed footer CTA to use FTS-aligned copy ("CHECK FTS FREE",
"SEE PILOT PRICING"). Fixed footer nav to use "Find Opportunities"
(matching TopNav) and /methodology (matching TopNav link) instead of
stale aliases. Trust copy updated to clarify this is Public Works
Qualification, not a domestic lead directory.

Free-tools page hero compared the product to Checkatrade/Bark/MyBuilder
and stated "Leads are the paid part" — wrong for the FTS product. Updated
to "The public tender qualification is the paid part." Comparison table
removed old feature references (Vantage, Vicinity, WhatsApp alerts) and
replaced with accurate FTS qualification features. Replaced all "LOCK MY
PATCH" CTAs with "SEE PILOT PRICING" throughout the free-tools page.

Co-Authored-By: Claude <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

@vercel

vercel Bot commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
job-filter-v1 Ready Ready Preview Aug 17, 2026 10:49am

@supabase

supabase Bot commented Aug 17, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project nfjwuwsuaapufmkppoeo because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

claude added 2 commits August 17, 2026 10:46
Removes stale libc fields from optional dependency entries — artifact
of running npm install with a newer npm version. No dependency changes.

Co-Authored-By: Claude <noreply@anthropic.com>
Resolves nanoid < 3.3.18 (high: custom generators looping indefinitely
at size zero) and postcss <= 8.5.22 (moderate: incomplete GHSA-6g55
fix). Pre-existing on main branch; fixes CI dependency audit step.

Co-Authored-By: Claude <noreply@anthropic.com>
@alwaysmeticulous

alwaysmeticulous Bot commented Aug 17, 2026

Copy link
Copy Markdown

✅ Meticulous spotted 0 visual differences across 169 screens tested: view results.

Meticulous evaluated ~4 hours of user flows against your PR.

Expected differences? Click here. Last updated for commit f1d7726 Fix high-severity dependency vulnerabilities via npm audit fix. This comment will update as new commits are pushed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants