PILLAR

What is a page (one-URL) audit?

Last updated: 2026-09-16

A conversion path audit starts on the public landing page after the click. One URL is enough. Add checkout if it is a public page. Optional: the ad or email they saw. SiteRevenue names where the promise dies. The cash path is the $19 page file — free grade, then unlock. Public pages you paste. Not Google Analytics. Not a logged-in crawl. Not a Google Ads login.

The sample shows the page-file shape. Landing-page audit stays on the home page. How to operate a path-shaped file: How to read a funnel audit. Side-by-side: Path vs one-fold graders.

Path file vs page grade

Page file ($19) — cash path	Path concept (educational)
One public URL	Ordered public steps after the click
Eight leak classes on that fold	Six path classes — not a ninth landing-page module
“Fix these 3 this week” on that URL	This-week actions tied to the break
Object: a site (one URL)	Object: where conversion dies across steps
Home form	Grade each public URL on the home form

Five landing-page grades stapled together still stop at the first URL. If the file does not name where the path breaks, it is a one-fold grader with extra tabs.

Who it is for

Teams who already paid for a click and lose the visitor after the fold — signup, pricing, checkout, thank-you
Operators who can paste the real public URLs (mixed hosts are fine: Stripe, Calendly, Typeform)
Agencies who re-run the same path after shipping the break

It is not an analytics ingest, a session replay, or a scanner of private logged-in areas. Only public HTML on the steps you submit.

What you paste

1–7 public http(s) URLs (landing required), in the order a visitor actually walks. One landing page is enough. Add checkout if it is a public URL. Optional: the ad or email they saw.
Typical chain: landing → signup or pricing → checkout or form → thank-you.
You supply the steps. We do not crawl. We do not invent the next URL from a button.
A login wall or bot challenge mid-path is a finding (step completeness), not a bypass.

NN/g’s 3-step CTA is verb + what happens next + why it is worth the tap. Across a path, that verb has to land on the submitted next URL. Google Ads landing page experience is the paid version of the same continuity test — the arriving promise should still be true on step 3.

What good looks like

Every submitted step is reachable public HTML — not a 404, empty body, or “session expired.”
The job sold on step 1 is still true later. Price, audience, and mechanism do not silently change.
The primary CTA from step N lands on step N+1. “Start trial” does not dump onto a blog or a calendar the click did not buy.
Friction does not stack by surprise — each step adds only what that step needs (Baymard guest-first checkout applied along the path, not only on page one).
One filled primary between steps. Sales or “learn more” is a text link, not a rival button after pay.
Phone fold works on later steps, not only the campaign lander.

Classic break pattern: pricing sells “Start free trial,” Stripe takes the card, then /welcome asks for a product tour. The break is welcome — illustrative, not a customer story, not a promised lift.

Common gotchas

Paying $19 and expecting the whole path. The page file is one URL. Paste each later public URL on the home form for its own grade.
Calling it “pages crawled.” We do not crawl. You supply the public URLs.
Pasting a logged-in app. Public HTML only. A login wall is a finding, not a bypass.
Using GA4 drop-off as the input. We do not ingest analytics. Empirical drop-off is a different product.
Concatenating five page grades. The synthesis is one path job. Generic “Improve CTA / Hero / Trust” with no host is not the file.
Treating the sample as a case study. It is a labeled composite. We do not invent conversion lifts.

How SiteRevenue scores it

Path jobs use a second rubric (funnel kind). They do not add a ninth class to the eight-module page scorecard.

Public path labels (0–10, higher = healthier on that slice):

Label	What it asks
Step completeness	Dead end, 404, login wall, empty capture
Promise continuity	Hero job still true on later steps
CTA destination match	Button verb vs landed page
Friction accumulation	Fields, surprise price, extra pitch
Competing actions	Second primary between steps
Mobile path	Phone fold across steps, not one page

Polarity is the same as the page file: letter A is healthier than F; leak score higher = more leaks. Dollar ranges inside findings are prioritization estimates, not a forecast.

The engine must name an in-range break (where conversion dies), write path findings that cite a host or step, and tie this-week actions to that break. Titles that could apply to any website fail the job.

Teaser omits full modules. Unlocking starts a new full job that recaptures the public steps — it does not reuse the teaser scrape.

Free teaser, page file, credits, API

Path	What you see	Cost
Free mini	Grade, leak score, top 3 titles	Free
Page file	Eight-class conversion file for one URL + up to 10 full re-audits	$19 one-time
Re-audit	New immutable version on the same URL	$19 page tune loop or Agency ($99/mo, 25 page credits)
Agency	Same page object over REST; poll until complete	Agency ($99/mo, 25 page credits)

Screenshot capture is fail-open. Job webhooks are not shipped — poll.

See the sample for the page-file shape. Cash path vs Agency: Pricing.

How it works

Paste a public landing URL on the home form (optional desired outcome; optional competitor URLs).
Free mini grade runs in about a minute — letter, leak score, three titles.
Unlock the $19 page file when the titles hit. Unlock recaptures the public page.
Ship the leak, then re-audit the same URL from /audits/:id to see whether the letter moved.
Agency ($99/mo, 25 page credits), optional — REST Agent API. Poll. No webhooks.

What a full path report includes

Live render order on /audits/:id (empty modules omitted):

Grade card — letter + leak score + This page is asking for (live heading, including on funnel jobs)
History — when this path already has a prior full run (before the strip)
Conversion path — ordered hosts; the break is marked
Fix these 3 this week — actions tied to the break, effort S/M/L
Ranked path findings — host or step in the title; evidence and a fix
Captures — fail-open shots of the public page (live full jobs; sample is illustrative)
Path dimensions — the six labels above
Rewrites — drafts for the breaking step
Per-step scorecards — each page on the path. The product is where it breaks, not a landing-page grade of every URL
Exports — PDF / Markdown / JSON in the masthead on a succeeded full job

Walk that stack: How to read a funnel audit.

What this is not

Not a landing-page grade of the first URL
Not GA4, heatmaps, or session replay
Not a logged-in or authenticated crawl
Not auto-discovered steps
Not Google Ads bid management (no Ads OAuth)
Not a conversion-rate guarantee or a named customer lift
Not live job-completion webhooks (Agent API users poll)
Not CLI --funnel or audit submit --url as a path creator — REST kind=funnel submits the path

How to read a funnel audit — live stack order; break vs titles
Path vs one-fold graders — a one-fold grader stops at the first URL
What is a website revenue audit? — page file of record
How to read a revenue audit — page stack
When to re-audit your site — v1 letter → v2 letter
Module guides — hero, CTA, match, offer, proof, form, trust, mobile
Comparisons · All guides

Start with a free grade

Paste a public URL on the home form. No card. Browse the sample. Unlock the $19 page file when the titles hit. Pricing.