Choose SaaS blog keywords by starting with problems your customers actually need to solve. For each question, identify the answer a searcher wants, decide whether your product belongs in that answer, and check whether an existing page already provides it. Write articles for the distinct questions left over. That gives you a shortlist with a purpose for every page—not a pile of phrases selected for search volume alone.
Collect customer questions before choosing phrases
Start with questions from sales conversations, support requests, onboarding calls, community discussions, or your own product research. Record the wording people use, but write down the task behind it too. “Customer onboarding checklist” might mean “What must happen before we call a new account onboarded?” A page that supplies a usable checklist can answer that task; a page describing why onboarding matters probably cannot.
Use the fields below as a small collection worksheet. Keep the original question separate from your proposed article title so you can change the title without losing the customer problem. Google’s people-first content guidance asks whether an intended audience would find a page useful and leave knowing enough to achieve its goal. That is a better initial test than whether a phrase merely sounds searchable.
- Customer question: What did the person ask, in their own words?
- Person and source: Who asked, and where did the question arise?
- Underlying task: What decision or piece of work are they trying to complete?
- Useful answer: What would the reader be able to do after reading the proposed page?
- Possible phrase: What would that person plausibly search to find the answer?
Check the answer the searcher wants and your product’s fit
Read the question before assigning it to the blog. “How do I build an onboarding checklist?” calls for instructions and an example. “What does your onboarding software do?” calls for a product or feature page. “Which onboarding tools should I consider?” calls for a comparison that treats alternatives fairly. If the question has two plausible meanings, inspect the current search results and the language in your customer notes, then choose one clear job for the proposed page.
Next, ask whether you can help the reader without forcing a product mention. A checklist article fits software that helps teams assign and track onboarding tasks: the article can explain the checklist on its own, then show where the product helps execute it. A topic about writing welcome-email copy may attract the same teams, but if the product neither helps with messaging nor gives you a useful perspective on it, defer it. Google warns against choosing topics primarily to attract search visits rather than serve an existing audience.
Do not treat product fit as a requirement to make every article a sales page. The test is whether the product naturally helps with the reader’s task or the next step after it. If a comparison or explanation is useful to your customers but your product is not the best option for everyone, say so rather than bending the answer to fit a CTA.
Give each page a distinct job
Before approving an article, search your own site for the proposed phrase and related wording. Open the likely matches—including feature pages—and compare the answer each page already gives, not just its title. If a suitable page answers the same question, improve that page instead. If it mentions the topic but leaves a different task unfinished, the new article can cover that task and point readers to the relevant existing page.
For example, a feature page that explains how the software assigns onboarding owners may already serve a feature-focused query. It does not necessarily replace an article that gives a team a reusable handoff template. Write down each page’s reader question and promised output; if those descriptions are interchangeable, reconsider the new article. This is an editorial overlap check, not a claim that every similar page is an SEO penalty. Google explains that it may group URLs whose main content is the same or very similar and select a representative canonical URL.
Turn the remaining questions into an article shortlist
For each candidate, record its intended reader, the answer format, why your product is relevant, the closest existing page, and a decision: write, improve an existing page, or defer. Among distinct write candidates, put the questions you hear from your target customers and can answer concretely first. Search-volume or difficulty estimates, if you have trustworthy ones, can help break ties; they should not turn a poor-fit question into a priority.
Here is a hypothetical decision for software that helps teams assign and track customer-onboarding tasks. Assume customer conversations have raised the checklist and handoff questions. The site has a feature page explaining owner assignment but no checklist or handoff-template article. No search-volume, difficulty, or question-frequency figures have been measured for this example, so the order below illustrates editorial judgment rather than a forecast.
| Candidate question | Reader needs | Existing-page check | Decision |
|---|---|---|---|
| How do I make a customer-onboarding checklist? | A checklist with tasks and an owner for each task. | No page supplies the checklist. | Write first: a practical checklist article. |
| How do I hand off a new customer between teams? | A handoff template and ownership decisions. | The feature page explains owner assignment but offers no handoff template. | Write next: a distinct handoff-template article. |
| Can this software assign onboarding owners? | A clear explanation of the feature. | The feature page already addresses it. | Improve the feature page if its answer is incomplete; do not commission a duplicate post. |
| How do I write a welcome-email sequence? | Email copy and sequencing guidance. | No matching page, but the product does not help create emails. | Defer: weak product fit for this fictional product. |
Brief the selected topics, not just their keywords
For each “write” decision, hand the writer one sentence naming the reader and question, one sentence defining the deliverable, and the closest existing page to avoid repeating. The hypothetical checklist brief might read: “Help an onboarding lead build a task checklist with owners; supply a reusable example, and link to the owner-assignment feature page where that step becomes relevant.” The handoff brief would promise a template for transferring responsibility, not another general checklist.
Ranks describes its articles as built around targeted keywords and says relevant internal links can connect readers to your pages. That makes it a way to develop the selected topics once you have defined their distinct jobs; the keyword alone cannot make the overlap decision for you. For draft-level checks, use the separate AI article review guide. After publication, the Search Console and Vercel guide covers how to evaluate search exposure and visits.
