> For the complete documentation index, see [llms.txt](https://peeklaunch.gitbook.io/peeklaunch-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peeklaunch.gitbook.io/peeklaunch-docs/landing-page-checklist.md). # Landing page checklist A short landing page checklist you can run before you submit a product (on PeekLaunch or anywhere else). Tick what you can; fix the rest before you ask strangers for attention. ### Before you publish the URL * [ ] Headline states the outcome in one line (who + result), not a vague slogan * [ ] Primary CTA is obvious above the fold on desktop and mobile * [ ] Only one primary action (Start free / Join waitlist / Submit). Secondary links stay quieter * [ ] What happens next is written under the button (time, price, review step) * [ ] Social proof is honest — real quote, logo, or small credible number. Skip empty "trusted by thousands" lines * [ ] Form is short — ask only what you need for the first step * [ ] Mobile pass — tap the CTA with your thumb; fix overlap, tiny text, and slow images * [ ] Open Graph image looks clean when the link is pasted into Slack/X * [ ] Favicon + title tag are set (browsers and bookmarks should not show a raw domain only) * [ ] Analytics records page view + CTA click (privacy-friendly is fine) ### Product clarity (60-second test) Hand the URL to someone outside your team. Without coaching, can they answer: 1. What does this do? 2. Who is it for? 3. What should I click? If any answer is wrong, rewrite the hero before you tweak colors. ### Launch-kit fields to keep ready Most directories and boards ask for the same set. Keep one note with: * Product name + URL * Tagline under 60 characters * Short description (\~160 characters) * Two short paragraphs (problem → solution) * Square logo (512×512+) * 3 screenshots * Categories / tags Copy from that note instead of rewriting under time pressure. ### After the page is live * [ ] Click every nav link and the footer legal pages * [ ] Test signup / waitlist on a clean browser profile * [ ] Confirm the thank-you or empty state tells the user the next step * [ ] Add the page to your internal sheet with date + owner ### Related * Keep this checklist next to your submit flow notes * Re-run it whenever pricing, positioning, or screenshots change Ship a clear page first. Traffic is wasted on a confusing one. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://peeklaunch.gitbook.io/peeklaunch-docs/landing-page-checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.