Search intent before a keyword list

Start with the job behind the search

A keyword is a clue, not a complete brief. Before building a list of phrases, write down what the searcher needs to decide or accomplish. Someone researching how to compare bookkeeping software needs a different page from someone ready to request a product demonstration. Matching that task helps you choose a useful page format, a realistic next step and the supporting information readers need. This is a planning method, not a promise of search visibility.

Read the results as a set of clues

Search a representative phrase and note the types of pages that appear. Are they guides, product collections, individual services, videos or local listings? Look at several results rather than treating the first one as a template. Record the questions they answer, the assumptions they make and any missing practical detail. Results change by place and time, so save the date and broad location of your review.

Do not copy a competitor's headings into your outline. Use the review to understand expectations. A page full of definitions may not meet an audience that needs a comparison worksheet. Equally, a sales page is rarely a satisfying answer to a troubleshooting question.

Group tasks rather than every variation

Create a small worksheet with columns for phrase, reader task, preferred format and proposed destination. Group phrases when one page can satisfy them without changing its main purpose. Keep them separate when the reader needs a materially different answer. Similar wording alone is not enough to make this decision.

For a hypothetical plant store, queries about watering indoor plants and choosing a watering schedule might share a guide. A query about buying a watering can probably belongs on a product page. The business context matters more than putting every phrase containing the same noun into one bucket.

Write a one-sentence page promise

Before drafting, finish this sentence: after reading this page, the reader can do what? Make the answer observable. “Understand SEO” is broad. “Choose which customer question each service page should answer” gives a writer a usable boundary. Put the direct answer near the beginning and make supporting sections follow the order a reader would act.

Decide what the page will not cover. Link to related resources rather than stretching one article across unrelated tasks. This keeps the main promise clear and gives readers a natural route to more detail when they need it.

Choose evidence and an appropriate next step

List the material the reader needs to trust the answer. That might include a documented process, a clearly labeled hypothetical example, screenshots you have permission to publish or links to primary guidance. Do not replace missing evidence with an impressive adjective. Explain limitations when advice depends on a platform setting or a business model.

The next step should match readiness. An educational guide can point to a planning tool or a related checklist. A genuine service page can offer an inquiry. Asking for a sales call before answering a basic question creates friction and weakens the value of the page.

Review overlap before publishing

Search your existing site for the same topic and compare the actual promises. If two pages solve the same task, improve the stronger destination instead of publishing another near-duplicate. When pages serve distinct needs, make the difference explicit in their titles, introductions and internal links. Keep a simple content map so future writers see those decisions.

After publishing, review the queries and landing-page activity available in your own tools. A mismatch can signal an unclear title or an incomplete answer, but small samples do not prove a pattern. Read the page again before changing it because of one unusual query.

A practical exercise

Choose a real question your audience asks. Make a four-column note with the question, the decision behind it, the evidence a reader needs and the most useful next step. Compare that note with one existing page. If the page answers a different question, change the plan before drafting. Keep the original note so a reviewer can explain why the page exists. This small exercise is more useful than collecting a hundred phrases without deciding what any of them should lead to.

Questions worth asking

Does one phrase have only one intent? Not always. A broad phrase can reflect several needs; choose the audience you can serve clearly rather than trying to cover everything.

Must every phrase have its own page? No. A complete answer can naturally address related wording without repeating it mechanically.

What should I do today? Pick one planned page, write its one-sentence promise and remove sections that do not help deliver it.