The playbook
Keyword Research: Checklist
Use this keyword research checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect qualified organic visits. Check an actual page or query record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
Compare “CRM software” with “CRM implementation checklist.” The first may call for product evaluation, while the second calls for an operating resource. Capture country, language, date, and data provider beside volume estimates. Do not add close-variant estimates together as though they represent entirely separate audiences.
Before you use the checklist
Name the exact item being checked and its purpose. Gather query, intent, volume source, target URL. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| Collect queries from customer questions and Search Console | A dated observation showing how query was verified | SEO lead |
| Group phrases by the task behind the search | A dated observation showing how intent was verified | content or development owner |
| Choose one useful destination for each intent | A dated observation showing how volume source was verified | analytics owner |
Check the failure path
- Look specifically for this failure: picking phrases solely because they have a large search estimate.
- Compare the query intent with the offer and the page a visitor expects. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check target URL.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “Collect queries from customer questions and Search Console,” a meeting about the subject is not the evidence itself. Retain the relevant query and intent, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents identify the language customers use when researching a problem or choosing a provider deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow qualified organic visits using a consistent definition so later reviews can connect execution quality with useful results.
Search results and indexing decisions are not controlled by the publisher. Record what your team changed and what was observed afterward. Avoid turning a correlation between a release and a traffic change into a claim of proven causation.
Skip the manual steps. Let AgentixSEO run this for every client.
Start now