Start with what the reader needs to do, then choose the page that can help. Tutorials explain steps, comparisons support a choice, FAQs handle short questions, and product or collection pages usually carry specifications, prices, and buying conditions.
18 parts · 3 checkpoints · 2 free / 16 member parts →
Begin with one real question and an existing URL. The previous lesson’s page-promise record can help check what a product page promises, but it is not a prerequisite. Decide whether to write, improve an existing page, or pause for evidence , then choose a format.
A SKU identifies a product or specification variant. Check the correct SKU for each size, capacity, or part. SERP means search results page; URL means page address.
The classroom example is a commuter tumbler with a stated capacity of 20 US fl oz (about 591 mL) . This is a page-planning exercise, not a test or buying review. Claims such as “keeps drinks hot for 6 hours,” “leakproof,” or “ships in the United States” are examples that require separate evidence about the product, test conditions, and shipping policy.
Key point Questions to answer in this lesson
What is the reader trying to do? Which existing URL is best placed to help? What checkable information is missing? Who will review the answer?
This lesson helps you answer
Choose whether to write, improve, or pause
Check which page is already close to the reader’s question, then identify what its answer lacks. Do not open a blog post only because a term has search volume.
Write, improve, or pause
Write new content
- Current situation
- The reader needs steps, troubleshooting, comparison criteria, or a full situation.
- What to do first
- Add a help page, tutorial, or comparison only if an existing page cannot answer fully.
- What to record
- User question, result-page format, source, and exceptions.
Improve an existing page
- Current situation
- The question concerns specifications, price, inventory, fit, buying, or policy.
- What to do first
- Fill the missing explanation on a product, collection, FAQ, or policy page first.
- What to record
- Target URL, missing field, source, page promise, and reviewer.
Pause for evidence
- Current situation
- The source, decision criteria, scope, or maintainer is unclear.
- What to do first
- Name the gap, who will find evidence, and when it will be reviewed.
- What to record
- Unchecked field, acceptable source, and condition for resuming.
Series start
A pause still has a next step
“No evidence yet” should become a concrete task, such as finding the current product instructions and cleaning limits, rather than a longer paragraph that fills the factual gap.
Choose the response closest to the question
For specs, price, fit, or buying conditions, check the page responsible for the transaction.
For a short answer, troubleshooting, or steps, verify product instructions and safety limits first.
When the source, scope, or maintenance owner is unclear, record the gap and who will resolve it.
Let search intent guide the page format
Start with the reader’s state: are they learning, comparing, getting ready to buy, or troubleshooting? Use this table as a starting point. Check results for the target market and language, and whether an existing page can do the job.
Search task and page format
Learn
- What the reader needs to do
- Understand a concept, steps, or decision criteria.
- Pages to check first
- Tutorial, explainer, guide, or FAQ.
- Mismatch to avoid
- Push a product without explaining how to choose.
Compare
- What the reader needs to do
- Choose between options, materials, or specifications.
- Pages to check first
- Comparison table or guide with fair criteria.
- Mismatch to avoid
- Brand claims or SKU specs without interpretation.
Browse options
- What the reader needs to do
- Shortlist candidates and differences.
- Pages to check first
- A list or collection page with fit criteria.
- Mismatch to avoid
- Products without applicability conditions.
Buy
- What the reader needs to do
- Confirm a product, specification, price, and buying terms.
- Pages to check first
- Product, collection, or filter page.
- Mismatch to avoid
- A broad article that blocks a transaction answer.
Troubleshoot or get support
- What the reader needs to do
- Find a safe action, limitation, or help route.
- Pages to check first
- FAQ, help page, policy, or troubleshooting steps.
- Mismatch to avoid
- Burying the answer or omitting safety limits.
Reader state is only a starting point. Check page types, evidence, and related next steps in the same market and language; these checks do not guarantee rankings or sales.
Free account to read · Parts 3-18 · 16 parts
Advanced practice: evidence, cases, and review records
This part includes
- Match a product page, FAQ, comparison, or guide to the search task
- Turn recurring support questions into checkable help content
- Find evidence gaps before expanding a draft or using AI
1 self-check question
An account is free; sign in to read this part.
Checking your membership…
Next lesson
Technical SEO basics
Keep the content decision before updating the page. It does not prove technical eligibility, crawling, indexing, or traffic.
FAQ
- Does content SEO always mean writing blog posts?
Start with the reader's task, existing pages, and SERPs for the same market and language. Specifications, buying conditions, or cleaning instructions may need an update to a product page or FAQ. A comparison, guide, or blog may be useful when readers need criteria, steps, and exceptions. Blogging is one candidate format, not the default destination for every keyword.
- Should product facts, user questions, comparisons, FAQs, and cases become the same type of page?
Separate product facts, user questions, comparisons, and cases. Check product or collection pages for specifications and limits, and existing FAQs or help pages for recurring questions. Comparisons need verifiable criteria and scope. A case needs a real scenario, the relevant SKU, sources, and a next step; rewritten general advice is not first-hand experience.
- Can support questions, reviews, and site-search terms become SEO content?
They can suggest topics, but repeated store questions do not establish external search demand. Keep the user wording, SKU, source, date, and a verifiable answer, then check SERPs and Search Console query performance separately. Decide whether the gap belongs in product information, support, or search content before creating another page.