# Launch Ready

> Launch Ready is a website preflight for founders. It checks public launch signals and returns a public, evidence-backed report.

## Documentation
- [Documentation home](https://launchready.cc/docs): Focused human documentation with a Markdown representation for every page.
- [Documentation map](https://launchready.cc/docs/llms.txt): Concise, documentation-only map for agents.
- [Run a light check](https://launchready.cc/docs/getting-started/run-a-light-check): Submit a public website and safely use the free launch-readiness check. Markdown: https://launchready.cc/docs/getting-started/run-a-light-check.md
- [Understand a report](https://launchready.cc/docs/getting-started/understand-a-report): Read scores, evidence, findings, and limits without overclaiming what a scan proves. Markdown: https://launchready.cc/docs/getting-started/understand-a-report.md
- [Light-scan methodology](https://launchready.cc/docs/methodology/light-scan): What the passive scan observes, how it scores, and what it deliberately does not do. Markdown: https://launchready.cc/docs/methodology/light-scan.md
- [Safety and limitations](https://launchready.cc/docs/methodology/safety-and-limitations): The passive-request boundary, public-report visibility, and the questions a light scan cannot answer. Markdown: https://launchready.cc/docs/methodology/safety-and-limitations.md
- [API overview](https://launchready.cc/docs/api/overview): Use the low-volume preview API to run a public scan and retrieve its structured result. Markdown: https://launchready.cc/docs/api/overview.md
- [Agent quickstart](https://launchready.cc/docs/agents/quickstart): Start from machine-readable discovery, respect the scan boundary, and handle public results safely. Markdown: https://launchready.cc/docs/agents/quickstart.md
- [OpenAPI contract](https://launchready.cc/openapi.json): Machine-readable contract for low-volume agent and API usage.

## Canonical pages
- [Homepage](https://launchready.cc/): Run a free light check.
- [About](https://launchready.cc/about): Product purpose and intended users.
- [Blog](https://launchready.cc/blog): Founder guides to launch readiness, trust, SEO, and AI discovery.
- [Public scans](https://launchready.cc/scans): Recent public website reports.
- [Launch readiness guides](https://launchready.cc/blog/topics/launch-readiness): Public journeys, failure states, recovery, operations, and post-launch triage.
- [Vibe coding guides](https://launchready.cc/blog/topics/vibe-coding): Use AI development speed without surrendering judgment around consequential code paths.
- [Users and traction guides](https://launchready.cc/blog/topics/traction): Find early users, interview them, choose channels, price the product, and measure pull.
- [Search and trust guides](https://launchready.cc/blog/topics/search-and-trust): Publish clear, consistent facts people, search engines, and agents can verify.
- [Turn a startup waitlist into active users](https://launchready.cc/blog/startup-waitlist-not-converting): Convert a startup waitlist into active users through qualified cohorts, direct invitations, founder onboarding, activation measures, and one change at a time.
- [Write honest startup comparison pages](https://launchready.cc/blog/startup-comparison-pages-seo): Research, write, and maintain useful startup comparison and alternative pages with first-hand tests, sourced claims, honest fit, and publication gates.
- [Fix Stripe payment and entitlement mismatch](https://launchready.cc/blog/stripe-payment-succeeded-app-says-unpaid): Trace Checkout, webhook delivery, signature verification, idempotent fulfillment, event ordering, delayed payment, and application entitlement state.
- [Rewrite or launch a vibe-coded app?](https://launchready.cc/blog/rewrite-vibe-coded-app-before-launch): Decide which prototype code to keep, isolate, replace before launch, or rewrite later using consequence, invariants, tests, and customer evidence.
- [Fix an AI app cost spike after launch](https://launchready.cc/blog/ai-app-cost-spike-after-launch): Contain unexpected AI and cloud spend, trace cost per completed job, stop duplicate work and agent loops, and enforce useful production limits.
- [Fix a custom domain after launch](https://launchready.cc/blog/custom-domain-not-working-after-launch): Diagnose authoritative DNS, stale A and AAAA records, DNSSEC, hostname verification, TLS, redirects, cookies, OAuth, and search signals in order.
- [Free trial vs freemium for startups](https://launchready.cc/blog/free-trial-vs-freemium-startup): Choose a free trial, freemium plan, or paid pilot from time-to-value, usage cost, abuse risk, buying motion, and the reason customers pay.
- [Why startup users do not come back](https://launchready.cc/blog/startup-users-not-coming-back): Separate measurement, activation, product value, audience, and return-loop failures before spending more money to acquire users.
- [Write your first startup case study](https://launchready.cc/blog/startup-case-study-first-customer): Turn one early customer result into a credible case study with consent, a real baseline, a clear method, honest limits, and factual sign-off.
- [Programmatic SEO for startups](https://launchready.cc/blog/programmatic-seo-startups): Turn repeated user questions and verified data into useful scalable pages without publishing thin content, doorway pages, or invented claims.
- [Authentication vs authorization](https://launchready.cc/blog/authentication-vs-authorization-vibe-coded-app): Test whether two valid users, team roles, files, exports, jobs, and support tools remain inside their intended permission boundaries.
- [Closed beta vs open beta](https://launchready.cc/blog/closed-beta-vs-open-beta-launch): Choose between alpha, closed beta, invite-only access, open beta, and public launch using consequence, support capacity, and evidence.
- [How to launch on Product Hunt](https://launchready.cc/blog/launch-on-product-hunt): Prepare a clear Product Hunt page, follow current platform rules, support real users on launch day, and measure value below the leaderboard.
- [Test backups before launching your app](https://launchready.cc/blog/test-backups-before-launch): Run a safe pre-launch recovery drill across databases, files, identities, configuration, and integrations before customer data depends on it.
- [How to prioritize startup feature requests](https://launchready.cc/blog/prioritize-feature-requests-startup): Turn feature requests into evidence about user jobs, commitments, product gaps, and tradeoffs without becoming a custom software shop.
- [Founder-led sales for first customers](https://launchready.cc/blog/founder-led-sales-first-customers): Build the first sales process through targeted accounts, honest outreach, discovery, real-work demos, bounded pilots, objections, and founder learning.
- [How to launch a startup](https://launchready.cc/blog/how-to-launch-a-startup): Launch through problem conversations, concierge results, narrow production tests, focused communities, public platforms, search, and meaningful relaunches.
- [What counts as real startup traction?](https://launchready.cc/blog/startup-traction-signals): Separate attention from activation, retention, payment, expansion, and referral—then measure early traction without hiding behind cumulative users.
- [12 common app launch problems](https://launchready.cc/blog/common-app-launch-problems): Diagnose launch symptoms including no traffic, weak signup, missing email, OAuth loops, duplicate actions, payment mismatch, indexing, and trust.
- [Why your startup website is not indexed](https://launchready.cc/blog/startup-website-not-indexed): Diagnose discovery, crawling, indexing, and ranking problems across HTTP status, robots rules, canonical URLs, rendering, links, and sitemaps.
- [Website security headers before launch](https://launchready.cc/blog/website-security-headers-before-launch): A founder-friendly guide to HSTS, CSP, framing protection, MIME controls, referrer privacy, and permissions policies without copy-paste security.
- [Why your app works locally but not in production](https://launchready.cc/blog/app-works-locally-not-production): A practical debugging order for production-only failures across configuration, domains, cookies, databases, runtimes, integrations, and logs.
- [Run a useful startup launch retrospective](https://launchready.cc/blog/startup-launch-retrospective): A one-page launch retrospective for separating product behavior, reliability, understanding, and demand from traffic and hindsight.
- [Make your startup homepage clear](https://launchready.cc/blog/startup-homepage-clarity): Replace abstract startup copy with a concrete product, audience, result, next action, and claims that people and search systems can verify.
- [Choose the right startup launch channel](https://launchready.cc/blog/choose-startup-launch-channel): Choose between Hacker News, Product Hunt, focused communities, and direct outreach based on the users and learning your product needs.
- [The first 48 hours after launch](https://launchready.cc/blog/first-48-hours-after-launch): Triage defects, confusion, user requests, strong prospects, and launch noise without losing the evidence needed for the next decision.
- [Test transactional email before launch](https://launchready.cc/blog/transactional-email-before-launch): A founder’s checklist for authentication, inbox testing, critical links, bounces, retries, recovery, and transactional-email privacy.
- [Launch traffic but no signups](https://launchready.cc/blog/launch-traffic-no-signups): Diagnose whether launch traffic failed because of audience, product clarity, trust, signup friction, onboarding, or weak retention.
- [Customer interviews without leading](https://launchready.cc/blog/customer-interviews-without-leading): Learn from past behavior, concrete work, and real commitments without steering customers toward compliments or hypothetical demand.
- [A practical launch-day runbook](https://launchready.cc/blog/launch-day-runbook): Prepare stop conditions, ownership, rollback, monitoring, and user communication before launch-day attention becomes scarce.
- [Premature scaling before product-market fit](https://launchready.cc/blog/premature-scaling-before-product-market-fit): Recognize when automation, hiring, infrastructure, and paid growth are hiding an unproven product instead of accelerating demand.
- [Launch a vibe-coded app without shipping a trap](https://launchready.cc/blog/launch-vibe-coded-app): A practical boundary between harmless rough edges and the identity, payment, data, and recovery failures that must be fixed before launch.
- [Find the first 10 users for your startup](https://launchready.cc/blog/find-first-10-users): A direct method for recruiting, observing, and learning from the first people who use a new product.
- [Fix the product’s first minute](https://launchready.cc/blog/fix-first-minute-onboarding): How to shorten the path from arrival to a useful result and find the onboarding failures hidden by founder familiarity.
- [The production checklist for an AI-built app](https://launchready.cc/blog/production-checklist-ai-built-app): Concrete production checks for authentication, authorization, payments, private data, email, recovery, and operations.
- [Review AI-generated code you did not write](https://launchready.cc/blog/review-ai-generated-code): A consequence-first code review method built around invariants, end-to-end traces, hostile cases, and human ownership.
- [Price the startup before launch](https://launchready.cc/blog/startup-pricing-before-launch): How to form one clear early offer, test willingness to pay, and keep the pricing promise consistent through checkout and cancellation.
- [Launch on Hacker News without sounding like an ad](https://launchready.cc/blog/launch-on-hacker-news): A builder’s guide to a clear, technical, available, and candid Hacker News launch that produces learning after the traffic fades.
- [The startup analytics you need in week one](https://launchready.cc/blog/startup-analytics-first-week): A small measurement system for completed jobs, failures, returns, and acquisition sources—without dashboard theatre.
- [Turn support questions into useful SEO content](https://launchready.cc/blog/support-questions-seo-content): Turn repeated user questions into precise, maintained source pages that help customers, search engines, and AI agents.
- [Website launch readiness checklist](https://launchready.cc/blog/website-launch-readiness-checklist): A founder-focused review of messaging, trust, technical delivery, search visibility, and the final user journey.
- [Website trust signals for product launches](https://launchready.cc/blog/website-trust-signals): What a new visitor looks for before signing up, paying, or sharing sensitive information.
- [SEO for AI search](https://launchready.cc/blog/seo-for-ai-search): How server-rendered copy, clean information architecture, structured data, and consistent claims help both search engines and agents.
- [Privacy](https://launchready.cc/privacy): Data handling for public light scans and private deep-scan requests.
- [Terms](https://launchready.cc/terms): Product boundaries and report limitations.

## Important limitations
- Light checks use passive, public evidence only.
- Reports are not security, legal, accessibility, or compliance certifications.
- Light-scan reports are public and may appear in the public scan directory.
- Deep scans are purchased directly through Stripe Checkout from the homepage; no account is required, and the buyer receives a private order URL.

## Agent access
- Start with [Agent quickstart](https://launchready.cc/docs/agents/quickstart.md) and [API overview](https://launchready.cc/docs/api/overview.md).
- Browser agents can call the homepage WebMCP tool named `run_launch_readiness_check`.
- Server-side agents can send `{"url":"https://example.com"}` to `POST https://launchready.cc/api/v1/scans`.
- Follow the response's `resultUrl` to read structured JSON.
- The preview API shares the public form's safety validation and durable rate limits; bulk access and an SLA are not available yet.