Growth tool

Landing Page Scorecard

Review a public landing page URL across SEO basics, message, offer, proof, and conversion friction.

$ review url

Review a live landing page URL.

Paste a public page. The tool reviews the public HTML, identifies the action the page appears to ask for, and points to checks that can affect search visibility or conversion quality.

Enter a public URL to get a first-pass review.

How I read the score

25-30The public page is in good shape. Check analytics and lead quality before scaling.
20-24Good enough for a controlled test. Review the weakest visible section first.
15-19Do not judge the channel yet. The page still has visible leaks.
0-14Too much is unclear. Rework the page before sending paid traffic.

The scanner fetches public HTML only. It cannot see private pages, ad account data, heatmaps, session recordings, CRM routing, lead quality, or actual sales follow-up.

What this tool is for

I use this kind of review when a page has traffic and the team is debating the wrong number. Sometimes CPL is blamed when the page is asking for the wrong action. Sometimes the form is blamed when the proof does not support the claim. Sometimes the page converts, but the source and offer context disappear before sales can use it.

What the scanner checks

SEO basics

  • The page has a useful title and meta description.Searchers and search engines can understand the page before opening it.
  • The page has one clear H1.The main heading matches the page topic and does not compete with other H1s.
  • The page is indexable and canonicalized.The public HTML does not contain a noindex directive, and the canonical URL points to the intended page.

Message

  • The page says who it is for.A visitor can tell whether the page is meant for their company, role, problem, or use case.
  • The first screen names the problem clearly.The headline and opening copy do not ask the visitor to infer the main issue being solved.
  • The primary next step is obvious.There is one main action, and it matches the intent of the traffic source.

Offer

  • The offer is specific enough to evaluate.The page explains what the visitor gets, not only a broad promise or category.
  • The page lowers the risk of taking action.It handles price, effort, time, fit, implementation, or commitment concerns.
  • The offer matches the visitor's stage.Cold traffic, comparison traffic, and retargeting traffic are not asked to make the same decision.

Proof

  • Proof is tied to the promise.Testimonials, case notes, numbers, logos, or examples support the actual claim on the page.
  • The proof has enough detail to be credible.It includes context such as audience, starting point, constraint, result, or method.
  • The page answers one real objection.It addresses why someone may hesitate, not just why the offer is good.

Friction

  • The form asks only for needed information.Every required field has a reason at this stage of the buyer journey.
  • The mobile page is easy to complete.Copy, form fields, buttons, and page speed do not make the action harder on mobile.
  • The page avoids competing actions.Navigation, secondary CTAs, widgets, and popups do not pull visitors away from the main job.

What still needs a manual check

Public HTML can show hints of analytics and CRM tooling, but it cannot prove the lead was recorded correctly or worked well. I keep these checks outside the score so the tool does not pretend to know what happens after submission.

Tracking checks

  • The main action appears in analytics.Form submissions, booked meetings, downloads, errors, and qualified outcomes can be reported.
  • Source and campaign context remain available.Traffic source, campaign, keyword/ad, landing page URL, and offer are attached to the submission.

Sales handoff checks

  • The right team receives the lead.Routing, owner, alert, calendar, and response-time rules match the promise made on the page.
  • The responder can see why the person converted.The CRM record includes the page, offer, source, and important form answers.

How the URL review works

The tool fetches the public HTML, reads the title, meta description, headings, canonical URL, robots directives, structured data, extracted text, buttons, forms, images, link types, and common script hints. For forms, it estimates the primary conversion form and excludes hidden tracking fields, search boxes, submit buttons, honeypots, and conditional fields from the visitor-field count. The score uses public-page signals only. Tracking and sales handoff are shown as manual checks because the scanner cannot prove them from public HTML.

Why landing page reviews go wrong

Many reviews stop at the visible page: headline, button, hero section, form length. Those are easy to see, so they get over-discussed. The harder question is whether the page matches the visitor's intent and whether the lead can be worked after conversion. A page can look clean and still fail because the offer is vague, the proof is unrelated, or the CRM receives a raw submission with no useful context.

How to use the result

Start with the weakest section and check whether the finding is true in the real funnel. If message is weak, compare the ad promise, keyword intent, H1, and first CTA. If proof is weak, add evidence that supports the exact claim. Treat tracking and handoff as manual checks, not as proof that the analytics or CRM setup is working.

A practical example

A paid search page for "B2B SEO consultant" can have a direct headline and a short form, but still be hard to evaluate. If the page does not say what kind of SEO problem is being handled, what happens after the enquiry, or what evidence backs the claim, lower CPL will not make the channel easier to judge.

What I would check next

  • If message is weak, compare the ad promise, keyword intent, page headline, and first CTA.
  • If offer is weak, rewrite what the visitor gets and what happens after they submit.
  • If proof is weak, add evidence that supports the specific claim, not generic trust signals.
  • If friction is weak, remove fields or steps that do not help qualification at this stage.
  • If tracking or handoff is weak, fix the CRM path before judging channel quality.

Methodology and limitations

The scanner can only review what is visible in public HTML. It cannot confirm whether events fire correctly, whether hidden CRM fields are populated, whether lead scoring works, or whether sales follows up quickly. Treat it as a structured first pass before a deeper review with analytics, recordings, CRM records, and sales notes.