How Nebula Audits a Landing Page

The 9-Step Diagnostic

Every audit runs these checks in order. A run produces a pass or fail on each signal with the specific page evidence behind the verdict.

1. 01

   Message Match

   Does the page promise match the expectation created by the ad or referring source?

   The primary headline and first supporting line must restate the same offer, audience, and outcome as the ad or referral context that produced the visit. A run flags this signal when the rendered headline contradicts, generalizes away from, or omits the promised offer.

   Inspected: H1 text, first subheadline, title tag, referring campaign parameters when present.

2. 02

   Trust Signals

   Does the page support its claims before asking for commitment?

   At least one verifiable proof element must appear near the conversion ask: named results, sourced review counts, case studies, or identifiable company and author information. A run flags pages that make strong claims with no adjacent, checkable support.

   Inspected: testimonial and logo blocks, review widgets, case study links, author and company identity markup.

3. 03

   Mobile CTA

   Is the primary action visible and usable on a small viewport?

   The primary call-to-action must be fully visible inside the initial 390px-wide viewport without scrolling, and must meet minimum tap-target size. A run flags CTAs pushed below the fold, overlapped by other elements, or smaller than usable touch targets at mobile width.

   Inspected: CTA bounding box position and size at 390px, overlap checks against header, banners, and sticky elements, tap target dimensions.

4. 04

   Load Speed

   Does the page become useful quickly enough to keep paid visitors from bouncing?

   Main content must reach usable state fast enough on a constrained connection. A run inspects render-blocking behavior, oversized hero media, and late-loading primary content, then reports measured values against the required threshold for the specific finding.

   Inspected: render-blocking resource count, hero image weight and format, when primary content becomes visible.

5. 05

   CTA Clarity

   Is the next step obvious and proportionate to visitor intent?

   One primary action must dominate. A run flags pages offering several competing equal-weight actions, vague action labels, or asks disproportionate to intent (for example demanding account creation before delivering any value).

   Inspected: button label text, count and relative weight of distinct actions, ask placement relative to value shown.

6. 06

   Above-Fold Clarity

   Can a visitor understand the offer and next action in the first viewport?

   Within the initial viewport a first-time visitor must be able to answer three questions: what is offered, who it is for, and what to do next. A run flags pages where any of these answers requires scrolling or inference.

   Inspected: viewport-height slice of rendered DOM, headline, subhead, CTA presence in that slice.

7. 07

   Ad Signal Continuity

   Can paid clicks be connected to outcomes without guessing?

   Paid traffic infrastructure must preserve click identity through to conversion events. A run checks for broken or missing tracking continuity between entry and conversion surfaces and flags gaps that would force attribution guesses.

   Inspected: tracking parameter handling across navigation, conversion event wiring, attribution break points.

8. 08

   SEO Foundations

   Can search systems retrieve and interpret the page foundations?

   Core retrieval elements must be present, unique, and consistent: crawlable status, canonical URL, title, meta description, heading hierarchy, and indexability directives. A run flags missing, duplicated, or contradictory foundations.

   Inspected: HTTP status and robots directives, canonical tag, title and meta description, heading structure.

9. 09

   AI Readiness

   Can answer engines identify, verify, and cite the page accurately?

   Machine-facing surfaces must let AI systems resolve who you are, what you offer, and what claims are supportable: structured data matching visible content, explicit factual statements, stable entity references, and crawler policy that permits answer engines you want citing you.

   Inspected: JSON-LD presence and accuracy, entity consistency, claim specificity, crawler access rules for AI agents.

About the tool

The audit engine is a browser-based application built by Nebula Components. It operates on publicly accessible HTML and does not require login credentials, site access, or a CMS integration. It does not submit forms, traverse checkout flows, or retain raw page screenshots beyond the analysis window. The full set of checks and pass/fail criteria is published in the Landing Page Diagnostic Specification v1.

Application type

Web-based diagnostic tool

Category

Conversion Rate Optimization

Operating system

Any (browser-based)

Price

Free

Signals checked

9 deterministic conversion signals

Runtime

Under 2 minutes per page

Account required

No - results are visible without signup

Platforms supported

Any publicly accessible URL