# Create SEO pages around user tasks

- **Canonical URL:** https://playbook.affpartners.io/en/practices/discoverability-seo/index.html
- **Markdown version:** https://playbook.affpartners.io/en/practices/discoverability-seo/index.md
- **Module:** ASO & SEO
- **Time:** 3 hours for the first page

A useful SEO page answers one question fully before asking the reader to install the app. It shows conditions, examples, and an honest continuation in the product—not copy written only for keywords.

## Outcome

A complete plan for the first SEO page: intent, answer structure, evidence, limitations, CTA, in-app route, and update plan.

## One page — one question — one complete answer

Someone searching “how to set up notifications” needs the steps, the conditions, and a way to check the result. A generic promo page answers nothing and forces them to install the app blind.

## What you will need

- **One search intent:** A priority question from the keyword map, confirmed by search, support, or reviews.
- **Expert:** The feature owner or a support specialist who will verify the steps, limitations, and freshness of the answer.
- **Publishing and data:** Access to the site, page analytics, and the route to the matching app screen.

## Terms in plain language

- **SEO — Improving website pages for search:** Definition: Useful pages answer real user questions and help people find the product through search engines. Example: One page answers one question, explains constraints, and leads to a relevant app journey.
- **Search semantics — A map of search queries and the needs behind them:** Definition: Collects user wording, groups queries by intent, and connects each group to the right product function or page. Example: “Where is my status?” and “check application” share one intent: view a process result.
- **Deep link — A link to a specific app screen:** Definition: After a tap, the user lands in the promised journey rather than on the home screen. Example: A push about a saved lesson opens that lesson directly.
- **CTA — The main action offered to the user:** Definition: A CTA is a button or link with a clear next step and expected outcome. Example: “Continue registration” is clearer than “Next”.
- **Conversion — The share of people moving to the next step:** Definition: Shows how many people who started a step completed it or reached the next one. Example: 80 registrations completed from 100 started: 80 ÷ 100 × 100% = 80% conversion.

## When to use it

The site gets almost nothing but brand traffic, frequent questions have no dedicated answer, and the existing pages repeat keywords and lead to the home page.

## What to collect before writing

First confirm the question and the product's actual answer. The page structure follows the user's task, not the desired keyword density.

- **Keyword map**
  - **Source:** Take one high-priority intent and the combined wording people use to search for it.
  - **If access is unavailable:** Without tools, start with a recurring support question that comes up at least five times a month.
- **Current product**
  - **Source:** Walk the journey on the current version and write down the steps, conditions, errors, and availability by platform and country.
  - **If access is unavailable:** If the feature is changing, do not publish final instructions until the owner and release date are confirmed.
- **Search analytics**
  - **Source:** After publishing, watch impressions, clicks, the page's queries, and actions after reading.
  - **If access is unavailable:** If the tool is not connected yet, at least tag the CTA and deep link with a separate source parameter.

## Assemble a useful SEO page

1. **Choose one intent.** Take a specific question the product actually solves. Do not combine a guide, a comparison, and a general overview on one page.
   - **Where to do it:** In the outline's title and the primary search intent.
   - **Example:** “How to check an application status” instead of the catch-all “everything about the app.”
2. **Give the short answer immediately.** Explain the result and the key condition in the first paragraphs. The user should not scroll through promo copy to reach the point.
   - **Where to do it:** Under the H1 and in the page summary.
   - **Example:** The status is in the “History” section and updates after processing; the typical time is shown next to it.
3. **Show the path and the limitations.** Add step-by-step actions, real screenshots, availability, timelines, and common errors. Do not hide important conditions behind the CTA.
   - **Where to do it:** In the main body of the page, with the update date.
   - **Example:** Three steps, what to do about a delay, and in which countries the journey is available.
4. **Link to the relevant screen.** Offer to continue exactly the task the reader came with. The app's home screen breaks the context.
   - **Where to do it:** In one main CTA and deep link.
   - **Example:** “Open my status” leads to the history — not the home screen.
5. **Assign an update owner.** Features, conditions, and the interface change. Write down the owner, the review date, and the signals that call for a page review.
   - **Where to do it:** In the content metadata and the editorial calendar.
   - **Example:** Support checks the guide after every release and quarterly against frequent queries.

## Practical examples

- **The answer is available before the install:** The “How to check status” page immediately explains where the status lives and when it updates, then shows three steps and the limitations — and only then offers to open your own status.
- **The continuation keeps the task:** The “Open my status” CTA leads to the matching screen. If the feature is unavailable in a country, the limitation is visible on the page before the tap.

## Finished artifact: Outline of the “How to check status” page

The outline states what the user must understand and do in each block of the page.

| Block | Page answer | Backed by | Next step |
| --- | --- | --- | --- |
| Title | How to check an application status | Matches the question | See the answer immediately |
| Short answer | Where the status lives and when it updates | The current product version | Understand without installing |
| Step by step | 3 steps with screenshots | The real interface | Repeat the path |
| Conditions | Timelines, countries, common errors | Confirmed by the owner | Avoid surprises |
| Continuation | Open your status | A working deep link | Go to the right screen |

The user gets the answer at the top of the page. The in-app CTA appears as a convenient continuation — not as a condition for reaching the basic information.

## Page checklist

The page must stay useful even if the reader never installs the app.

- [ ] One page fully answers one search intent.
- [ ] The short answer sits at the top, not after a promotional intro.
- [ ] The steps, images, timelines, and limitations match the current product.
- [ ] The main CTA and deep link continue the user's original task.
- [ ] The owner, the update date, and the trigger for the next review are set.

## How to know the page helps

- **Search answer:** Relevant impressions and clicks for the chosen intent grow — not random broad traffic.
- **Page value:** Readers reach the answer, use the steps, and ask support the same basic question less often.
- **Continuation in the product:** Clicks from the site into the app open the right screen and lead to the expected action.

## Key rule

SEO does not end at the click: the user should get the full answer on the page and a clear continuation of the same task in the app.

---

- [HTML version](https://playbook.affpartners.io/en/practices/discoverability-seo/index.html)
- [All practices](https://playbook.affpartners.io/en/)