# Turn field questions into a builder keyword plan

Builder keyword research starts in your own inbox and job sites, not in a tool. Collect the phrases buyers use on lot walks, in plan reviews, during allowance and selections talks, at draws, on the punch list and on warranty calls. Group them by decision. Confirm you can answer each from a real document. Assign each group to one page.

## Where should builder keyword research start?

Start with the conversations already costing the team time. Sales hears the first questions. Estimating hears where expectations and scope split. Design hears which selections confuse buyers. Construction hears schedule and access questions. Warranty hears what owners misunderstood at [handoff](/process/handoff/).

Those are more than content ideas. They are evidence of buyer language and operating friction. A phrase repeated at every plan review deserves a page, because buyers search it before they ever reach your office.

### Build a field-source inventory

| Source | Language to capture | Likely content use |
| --- | --- | --- |
| Inquiry forms and call notes | Place, home type, lot status and starting questions | Service, qualification and lot pages |
| Plan review notes | Room changes, dimensions, options and constraints | Plan and design guides |
| Allowance discussions | Included work, selection ranges and overage questions | Specification and allowance pages |
| Construction updates | Draws, inspections, access, sequence and delays | Process articles |
| Punch and warranty intake | Completion standards, requests and responsibility | Handoff and aftercare pages |

Strip the buyer and project names. Keep the phrasing, the intent and the operating subject.

## How do keywords become buyer decisions instead of a spreadsheet?

A keyword list earns its keep once each phrase is tied to a decision. “Custom home allowances” might mean a buyer comparing specs, sizing their cash exposure or preparing for selections. Those belong on one page only if one page can answer them without becoming a catchall.

1. **Write the phrase exactly as heard.** Do not clean it into industry language yet.

2. **Name the underlying decision.** Identify what the buyer needs to choose, check or prepare.

3. **Identify the source of truth.** Point to the plan set, specification, [allowance schedule](/glossary/allowance-schedule/), process document or responsible reviewer.

4. **Choose a page type.** Assign the subject to a plan, process, project, community, guide or FAQ page.

5. **Define the next page.** Decide where the reader should go after receiving the answer.

Mark the topic not ready if its source or reviewer is missing, whatever the tool says about volume.

## How should a builder judge keyword value without guessing?

Search volume informs priority. It does not measure fit. A low-volume question can matter because it shows up during serious lot evaluation or contract preparation. A broad phrase can draw attention and produce poor-fit inquiries.

Score topics against evidence the team can inspect:

- Does the question appear in real inquiries or meetings?

- Does the builder have a clear and reviewable answer?

- Does the answer help a buyer take a meaningful next step?

- Can the page connect to a plan, project, community or process page?

- Will the subject remain useful long enough to maintain?

- Could a careless answer create a false scope, schedule or warranty expectation?

Write down the reasoning. A topic marked “later” carries a reason: missing source material, or a process still under revision.

## What should the final keyword map contain?

The map is a publishing control sheet, not an export dump. Every topic gets a target URL, a primary buyer question, related questions, a source owner, a review status and an internal link destination.

### Assign one primary job to each URL

If two proposed pages answer the same decision, merge them or make the difference explicit. A selections process page explains sequence and responsibility. A separate cabinet selection page covers measurement, lead times and approval handoffs. Two selections pages for the same task get resolved before drafting.

The [builder topical map example](/articles/search-and-answer-engines/builder-topical-map-example/) shows how clusters and supporting pages fit. The [search and answer engine hub](/articles/search-and-answer-engines/) connects that structure to drafting, links and measurement.

### How does keyword research differ from topic selection?

This sheet records the phrases buyers used and the page assigned to each decision. Whether a proposed article clears up project fit is a separate editorial screen. Keep demand evidence, source readiness and topic approval in separate fields, so a good headline cannot pass for a recorded inquiry.

Our agents handle the research, drafting, building and checking. People choose the sources, set priorities and review every output. The research is strongest where an agent's pattern matching meets a superintendent's, an estimator's or a sales lead's knowledge of what buyers ask.

Once the map is approved, the [Semantic content stage](/process/semantic-content/) turns it into a connected content wave. The [home builder SEO guide](/guides/home-builder-seo/) explains how those pages support plans, projects and communities.

## How should keyword research stay current?

Update the map when the operation changes, not when a reporting calendar says so. A new plan library creates new fit questions. A revised [allowance schedule](/glossary/allowance-schedule/) changes buyer language. A new community creates local subjects. A punch list misunderstanding that keeps recurring points to a missing completion explanation.

Keep a simple intake lane for new questions: wording, source team, decision, current answer. At content review, decide whether the question belongs on an existing page, needs a new one or stays private. That keeps the site from becoming a stack of thin articles.

For page-level phrasing once the map is set, use the [article on writing builder process articles](/articles/search-and-answer-engines/writing-process-articles/).

## Questions about builder keyword research

### Do we need a paid keyword tool to begin?

Builder keyword research can begin with inquiry language, meeting notes and recurring field questions. A paid tool can add comparison data but cannot replace operating evidence.

### Should we target the broadest phrase in every article?

A builder article should target the decision it can answer from approved sources. Reserve broad subjects for hubs and focus supporting articles on distinct tasks.

### Can one page target several related phrases?

One builder page can address related search phrases when they express the same decision and use the same sources. Split tasks with different reviewers or next steps.

### What should be removed from research notes?

Remove buyer names, contact details, confidential project information and private contract material from keyword research notes. Preserve the de-identified question and necessary operating context.