Routing
Status and destinationBroken, stale, duplicated, redirected, or soft-error routes are recorded with their final destinations.
Public launch QA · $49 founder pilot
15–20 agreed routes / one public retest
Find the launch defects your first prospects will see.
Get a credential-free review of the public routes, metadata, trust signals, and conversion messages that shape a visitor's first decision. Keep the evidence and exact retest steps.
No payment before the route list and deliverable are approved in writing. The findings are manually reviewed before delivery.
01 / What the review catches
Small public defects can break trust before the product opens.
Discovery
Metadata and indexabilityCanonicals, titles, descriptions, Open Graph, X metadata, robots, sitemaps, and structured data are compared.
Conversion
Message and CTA consistencyPricing, support, sign-up, booking, legal, download, and launch messages are checked for contradictions and dead ends.
02 / The fixed boundary
A launch snapshot with evidence, not an open-ended audit.
AreaIncludedBoundaryOutput
Routes15–20 agreed public URLsGET and HEAD onlyEvidence table
SignalsHTTP, metadata, robots, sitemapNo ranking guaranteeCorrection list
MessagesPricing, CTA, trust, launch copyNo legal interpretationPriority order
VerificationOne public retestAgreed corrections onlyRetest result
NOT INCLUDED
Private product testing needs a different agreement.
The founder pilot excludes accounts, form submission, checkout, credentials, source-code changes, production access, customer data, penetration or security testing, load testing, legal advice, and guaranteed ranking or conversion outcomes.
03 / The handoff
Know what happened, why it matters, and how to verify the fix.
- 1
Confirm the public boundary
Approve the route list, checks, exclusions, delivery target, and payment terms in writing.
- 2
Collect reproducible evidence
Each finding includes the route, observed behavior, expected behavior, impact, and retest condition.
- 3
Prioritize the correction list
Fixes are ordered by launch impact and separated from optional polish.
- 4
Retest the agreed corrections
One public retest records which expectations now pass and which remain unresolved.
04 / Transparent method
AI-assisted collection. Human-reviewed conclusions.
Inspect the work style before sharing your launch URL.
Public examples show executed checks, negative-path evidence, explicit limits, and the difference between observed facts and recommendations. They are self-directed proof, not a claim of paid-client history.
05 / Before payment
Scope, access, implementation, and timing.
Do you need an account or product credentials?
No. The founder pilot is intentionally limited to public, unauthenticated routes. A private product or logged-in workflow requires a separate written scope.
What exactly is reviewed?
The agreed public routes are checked for status, redirects, canonical and social metadata, indexability, error behavior, CTA destinations, and consistency across pricing, support, trust, and launch messages.
Does the review include fixing the site?
No. The deliverable is an evidence table, prioritized correction checklist, exact retest steps, and one public retest. Source-code changes are quoted separately.
When does the two-business-day target begin?
After the written route list, scope, payment, and any safe public context are confirmed. Missing inputs pause the delivery clock.
Founder pilot / $49 fixed
Send the public URL. Confirm the route list.
If the site fits, receive the exact boundary before payment and the evidence-backed review within two business days after the complete start conditions are met.