Competitor website monitor
After a fix or a rebuild, will watch what rivals change, so the comparison stays current.
Solutions · by problem
Should we rebuild the website, or fix what we have?
The agency quoted a full rebuild. In the sample report, run on a constructed test firm, priority action one is a single page: a five-step "How we work" page. The free report lists the gaps that lose buyers and ranks the fixes by effort, before you brief anyone.
Answered today
The problem
What owners say.
- The site looks dated. Is that why it doesn't bring in work?
- An agency quoted us for a full rebuild. Do we need one?
- We had a new site two years ago and nothing changed.
- I don't know if the problem is the design, the words or the speed.
Composite phrasings of a common problem, not quotes from named customers.
Why it is hard
Why checking by hand fails.
Owners judge a site by how it looks. Buyers judge it by whether it answers their questions: what you do, for whom, at roughly what cost, with what proof, and how to start. A handsome site that skips those loses the same buyers the old one did.
Most gaps fix in place: a missing fee page, proof buried on one page, a contact form that asks too much, slow pages on a phone, text locked inside images where machines cannot read it. A rebuild is the right call when the structure blocks the fixes.
The sample report shows the shape of the output. The constructed firm's hero is a stock courthouse photo. Its SRA registration appears only in the footer. Its testimonials carry first names only. Its process is missing, while the top-scoring rival puts five steps on the homepage. None of those needs a new website.
The limits. This reads content and route. It is not a design review. Page speed comes from Google's PageSpeed endpoint and sits beside the content reading. We do not build websites, so the report has no rebuild to sell.
What we read
Each source, and the code that reads it.
Every source names the module in our code that reads it. A source marked in build does not run for customers yet.
- Your pages as textWhat a machine and a skim-reader get from each page, with images and video stripped.
src/lib/firecrawl.ts - Five buyer archetypesWhere each buyer type stalls, scored against a fixed rubric.
src/lib/prompt/evaluate.ts - Page speedGoogle PageSpeed measurements for your pages, as reported by Google's own endpoint.
src/lib/connectors/pagespeed.ts - Rivals' sitesThe same reading on the competitors you name, so a gap is judged against your market.
src/lib/firecrawl.ts
What you get
What you get back.
- The gaps that cost buyers, each with the page and the evidence
- Actions ranked by effort, so fix-in-place work is visible before any rebuild
- Your site scored beside your rivals' sites on the same rubric
- A brief to hand to whoever does the work, fix or rebuild
Today and in build
What runs today, and what is in build.
Live tools run now. Loops in build will answer it again on a cadence you choose. They are not on sale.
Where it comes up
Industries that ask this.
Each industry page puts the problem in that trade's terms.
FAQ
Questions about “Rebuild, or fix what we have”
Will you tell me to rebuild?
Only if the reading shows the structure blocks the fixes. We do not build websites, so we have no rebuild to sell you.
Is this a design review?
No. It reads what the site says and whether it answers a buyer's questions, beside your rivals. Most lost buyers are lost on content and route, not colour.
Can I give the report to my web designer or agency?
Yes. Each action is written to be handed over, with the page and the evidence.
Does page speed matter for this?
It is one input. The speed figures come from Google's PageSpeed endpoint and sit beside the content reading.
Name the rivals you lose to.
The free report reads your site beside theirs, five buyer types on one rubric. No account and no card to start.