Landing page roasts vs a revenue audit
Last updated:
A public roast is a gallery. A 15-minute video teardown is a performance. A revenue audit is a private library: a site, immutable jobs, a letter grade, evidence, a ship list, and a second run on the same URL. If you pay for traffic, you need a file of record you can hand to a teammate — not a thread, not a recording. Sample · free grade.
The dated argument is A roast is not a system. This page is the evergreen comparison.
Comparison table
| Public roast / gallery | 15-minute video | SiteRevenue | |
|---|---|---|---|
| Object | A thread, a screenshot, a mood board | A recording on a call | A site (URL over time) + an immutable audit job |
| Audience | The internet | Whoever was on the Zoom | Your workspace — /audits/:id is noindex on purpose |
| Ranked tickets? | The funniest leak wins | Whatever the speaker remembered | “Fix these 3 this week” + typically 5–8 findings with effort S/M/L |
| Evidence next month | A quote-tweet | A timestamp you cannot search | Captures (fail-open), dimension lines, MD / JSON / PDF when those exports succeed |
| Comparable v2? | A new joke about the same brand | A new recording | v1 Grade D → v2 Grade B on the same site |
| Recovery | None | Inbox archaeology | Checkout email → Open with email → My Audits |
| Share | Public by default | An unlisted link if you remember | Time-bound read-only /s/:token — not a permanent public page, not a gallery |
| Incentive | Attention | A polished hour | Ship the action box, then re-audit |
Roast culture is easy to like. That is not a defect of wit. It is a defect of object. A gallery has no site identity and no obligation to look at the same URL after you ship.
Common gotchas
- Collecting other people’s folds instead of shipping yours. It feels like research. It is usually procrastination with better lighting.
- Treating a viral teardown as this week’s sprint. Severity was a vibe. Effort was not estimated. Nobody owes you v2.
- Expecting
/audits/:idto be a public catalog of strangers’ sites. Session reports are app surfaces (private, noindex). That is deliberate — a working file should not become someone else’s content farm. - Using a share link as a campaign landing page.
/s/:tokenis a contractor handoff, not how we do SEO. Indexable method lives on guides and the blog. - Re-running identical HTML “to see if the model changed its mind.” That burns a credit. See when to re-audit.
- Assuming every job has a PDF. PDF exists when the full export succeeds — not a promise on the teaser, not a chat log you scroll past.
- Inventing named customer roasts as case studies. We do not. The sample is illustrative.
How SiteRevenue differs
If you only remember two product facts, remember the objects: Site (the URL you intend to improve) and Audit job (a snapshot; it is not edited in place). A re-run is a new job. Letters stay comparable because the model and the site identity stayed put.
| Path | What you see | Cost |
|---|---|---|
| Free mini audit | Grade, leak score, executive summary, top 3 leak titles | Free |
| Page file | Dimensions, captures, before→after drafts, action box, 5–8 ranked findings, exports | $19 one-time |
| Agency | Same page object over REST; poll | Agency ($99/mo, 25 page credits) |
| Re-audit | New version on the same site; letter-grade strip | Up to 10 full re-audits on that url_key (copy) |
| Share | Read-only snapshot for a colleague | From a succeeded full job |
| Agent API | Same full jobs via REST or CLI; poll (webhooks later) | Agency |
Teaser omits full modules. Unlocking starts a new full job that captures the public page again. Dollar ranges inside findings are prioritization estimates, not a forecast and not financial advice. Public pages only — not a logged-in product crawl, not a chatbot, not a six-week slide deck.
The product spine is What is a website revenue audit?. How to operate the file: How to read a revenue audit.
Related guides
- A roast is not a system — dated argument (not this table)
- Overnight teardowns vs a file in this session — 24h PDF vs minutes
- What is a website revenue audit? — file of record; free / $19 page / API
- Path vs one-fold graders — a one-fold grader stops at the first URL
- How to read a revenue audit — live stack order
- When to re-audit your site — when a second run is worth a credit
- Copy rewrites that ship — drafts become tickets
- Comparisons · All guides
Start with a free grade
Paste the public URL people actually hit on the home page. No card. Browse the sample for the open full-report stack (illustrative — not a live customer story). Then unlock the file you can re-run — Pricing.