Keyword research for a new website means deciding, before launch, which needs your first pages answer and in what order. You do it by asking five questions about search demand (how much, who, what leaks, what is missing, how big) and turning the answers into a short page plan.
This tutorial is for developers who build the site and get asked "what pages should it have?". The output is a page plan you can commit next to the code.
The running example: you are building the site for a mobile bike repair service in Austin. The mechanic comes to the customer's home or office.
1. Write the needs, not the words
Start with what customers want done, one line each. Don't start with phrases.
fix a flat at home
full tune-up
e-bike repair
brake repair
price of a tune-up
compare mobile repair with a shop
book for this weekend
Each line is one need. Later, many wordings will fall under each one ("bike tune up austin", "bicycle tune up near me"). They stay one need and one page.
2. How much: put a monthly count on each need
For every need, write down roughly how many people in your market search for it each month. Use whatever counts you trust; what matters is how you read them.
- Group the wordings of one need first, then judge the group. Two wordings of one need are still one page.
- A count is not visits. A page earns only a share of it.
- Small counts are fine for a local service. "e-bike repair austin" may be small and still full of buyers.
3. Who: mark buyers and learners
The same words come from people who want to pay and people who want to learn. Mark each need:
- buyer: "mobile bike repair austin", "book bike tune up"
- learner: "how to adjust bike brakes", "how often to tune up a bike"
Buyers get service pages first. Learners get a guide later, and that guide links to the page that sells.
4. What leaks: find the searches that look right and bring no one
Some needs look like yours but come from the wrong people. In the example, "bike mechanic jobs austin" shares the words and brings job seekers, not customers.
Mark these no page. If the business runs ads, they also go on its negative list before launch. This is not a small detail: in one US market, freight factoring, 272 of 1,569 searches looked relevant and came from the wrong audience.
5. What is missing: look at the leading competitors
Open the sites of the three or four businesses that already win these customers. For each need, note whether they have a page that answers it.
need shop A shop B mobile C
fix a flat at home no no yes
e-bike repair yes no no
price of a tune-up no no no
A need with demand that nobody covers well ("price of a tune-up" above) is often the cheapest page to win on a new domain.
6. How big: check the market is worth the build
Multiply roughly: buyers a month you might win, times what one job is worth. If a handful of tune-ups a month covers the cost of the site, a modest count is enough. If not, rethink the offer before you write pages.
7. Pick the first ten pages
Now rank. Buyer needs with demand and a gap come first, then buyer needs the competitors cover, then one or two learner guides that link to them.
# pages.yml: the launch plan
- path: /
need: mobile bike repair austin
- path: /tune-up/
need: full tune-up
- path: /tune-up-price/
need: price of a tune-up # gap: no competitor answers it
- path: /flat-tire-repair/
need: fix a flat at home
- path: /e-bike-repair/
need: e-bike repair
- path: /brake-repair/
need: brake repair
- path: /book/
need: book for this weekend
- path: /mobile-vs-shop/
need: compare mobile repair with a shop
- path: /service-area/
need: which parts of town we cover
- path: /guides/how-often-to-tune-up-a-bike/
need: learner guide, links to /tune-up/
Ten pages, each with one job. Anything else waits until the site has a few weeks of real visits.
8. Wire it into the build
A few habits that keep the plan intact in code:
- One need per route. The need's main wording goes in the
<h1>and the<title>. - Learner guides link to the buyer page they serve, in the text, not only in a footer.
- Keep
pages.ymlin the repo. When someone asks for a new page, it gets a row and a need first. - Don't ship two routes for two wordings of the same need. Pick one and redirect the other.
The checklist
- [ ] Needs written as plain lines, not phrases
- [ ] A rough monthly count on each need
- [ ] Each need marked buyer or learner
- [ ] Wrong-audience needs marked
no page - [ ] Competitor coverage noted for each need
- [ ] Market size checked against what one job is worth
- [ ] Ten pages chosen, buyer gaps first
- [ ]
pages.ymlcommitted next to the code
Each of the five questions is explained, with examples from real markets, at querytally.com/search-demand/.
Top comments (0)