Indie SaaS Public Surface Flow

# Launch Page Search Intent Map

A launch page should not target every possible keyword. For a small SaaS product, the first search intent map is a filter that decides which pages deserve careful writing and which ideas should stay as notes. The goal is to match a real query with a product promise, not to create a large directory of thin pages.

## Intent buckets
Start with four buckets: problem, comparison, setup, and proof. Problem searches sound like “how to track X” or “why does Y happen.” Comparison searches weigh alternatives. Setup searches need instructions. Proof searches ask whether the product is credible, safe, or worth paying for. Each bucket needs a different page type.

## Canonical pages first
A canonical product page, guide, comparison, or integration note is usually better than many parameterized search pages. Search results pages can help users navigate internally, but they should not be treated as SEO targets unless they contain durable editorial value.

## Evidence fit
Every page should have one proof element: screenshot, API response example, workflow example, pricing rule, customer scenario, or limitation. Without proof, the page becomes generic marketing copy. For an indie product, visible limitations can increase trust because they show the product is not pretending to serve everyone.

## Avoid keyword drift
If a page starts with “API monitoring for solo founders” and ends with generic productivity claims, it loses search intent. Keep the page anchored to the original job.

## Practical map
For each candidate page, write query, user anxiety, product answer, proof element, and non-goal. If the non-goal is missing, the page may expand into vague positioning instead of answering a searcher.

Launch Page Search Intent Map

// COMMENTS

ON THIS PAGE