Website Growth Grader methodology

The grader combines one public page fetch with the business context you enter. Context steers how opportunities are framed (e.g. lead gen vs demo requests) it does not pull CRM or analytics data.

• Required: website URL, business type, main growth goal, and target market.
• Fetched: HTML for the submitted URL (SSRF-hardened), including visible copy, metadata, schema blocks, and CTA/proof language signals.
• Optional later: qualification fields appear only after free value (score + top opportunities) is shown.

Homepage URLs are the common case. Product or service landing pages can be stronger tests when that URL is the primary growth surface.

Each dimension asks: given public HTML and stated goals, how clearly does this page support discovery, trust, conversion, and expansion signals a growth team can act on? We score readiness patterns not last month’s sessions.

• Clarity of offer and audience fit
• Proof and trust density
• Conversion path and CTA quality
• SEO / on-page discoverability proxies
• AI / answer extractability readiness
• Content depth and architecture cues on the page
• Measurement and next-step hygiene where visible

Weights reflect relative contribution to an overall growth-readiness composite in this product model. They are not Google’s ranking weights.

Each dimension reports score, confidence, evidence found, evidence missing, business consequence, and a recommended next action. Confidence drops when signals are sparse missing data does not always mean failure.

• Based on: public HTML, visible copy, metadata, schema, CTA/proof language, SEO checker pillars.
• Not included: backlinks, rankings, CRM data, private analytics, field Core Web Vitals, actual answer-engine prompt monitoring.

Example: a founder-led B2B SaaS homepage scores 58 overallwith strong offer clarity (B) but weak proof (D) and mediocre conversion path (C). SEO dimension is mid-band; AI extractability is low because benefits are buried in marketing adjectives without concrete entities or FAQ structure.

• Top opportunity first: add customer proof near the primary CTA before rewriting every paragraph. Proof deficits often block demos more than missing meta descriptions.
• Goal alignment: if the stated goal is “book demos,” a vague “Learn more” path should outrank pure brand storytelling in your fix list even if brand copy feels “on voice.”
• Confidence matters: a low-confidence SEO score means “we could not see enough,” not “you failed SEO forever.” Pair with the dedicated SEO Checker when technical detail is the bottleneck.
• Single page bound: a strong homepage can still hide a weak pricing or case-study architecture use Content Architecture Gap Checker for multi-page structure.

1. Submit website and basic context.
2. See progress across dimensions being checked.
3. Reveal overall score and category scores.
4. Reveal top three opportunities.
5. Email unlocks the complete report and roadmap copy.
6. Optional qualification after value is demonstrated.
7. Service and related-tool CTAs.