Turn customer interviews into SEO content pillars by extracting the customer's task, grouping related problems, and giving each proposed page a distinct question to answer. Keep every idea linked to its source note, then check existing pages and search intent before commissioning an article.
A transcript is useful evidence about someone's experience. It is not a keyword-volume report, a product specification, or permission to publish their words. This workflow helps SaaS content teams move from a conversation to a focused editorial plan without losing those distinctions.
Prepare a Usable Interview Record
Begin with a transcript you are allowed to use for this purpose. Check the recording against unclear names, product terms, and important wording. Preserve a timestamp or paragraph reference so an editor can return to the original passage. Mark uncertainty instead of asking a writer to guess what the speaker meant.
Make a working copy containing only material needed for the editorial task. Keep private details out of the public brief. A published quotation needs an approved attribution and exact wording; an internal research note can remain a paraphrase with a private source reference.
Record the interview date, the participant's relevant role, and the product context. An implementation problem before a major release may not describe the current experience. One person's observation also does not establish how frequently a problem occurs across the market.
Extract Tasks Before Collecting Keywords
Read for the work the customer wanted to finish. Capture the situation, obstacle, attempted workaround, and unanswered question. Separate those observations from your interpretation of the opportunity.
The following notes are fictional examples, written to demonstrate the method. They are not customer quotations or findings from a RoboWrite study.
| Illustrative interview note | Reader task | Editorial question | Evidence still needed |
|---|---|---|---|
| The team could not tell who owned the onboarding handoff | Assign responsibilities before implementation | What should an onboarding handoff checklist include? | A realistic ownership example and current process details |
| Two departments used different meanings of ready | Agree on a completion condition | How should a SaaS team define onboarding readiness? | Definitions reviewed by the process owner |
| The buyer compared products before checking migration needs | Evaluate a tool against implementation constraints | Which migration questions belong in an onboarding software evaluation? | Current vendor documentation for any named capabilities |
Keep the original note and the editorial question in separate columns. The third row suggests a comparison task; it does not establish that a particular vendor supports a migration feature.
Build a Pillar Around a Shared Problem
A useful pillar connects several questions that matter to the same audience. For these notes, a possible pillar is SaaS customer onboarding operations. The supporting assignments can cover preparation, ownership, readiness, and tool evaluation.
Those assignments need different boundaries. A preparation checklist should not become a software ranking halfway through. A tool-evaluation guide should give decision criteria rather than repeat the entire preparation checklist. The broad pillar page can explain the map and help readers find the next relevant answer.
Use the content pillars guide for the wider planning structure. This interview workflow supplies evidence for that structure; it does not replace the editorial decision about what your site should cover.
Check Search Intent and Existing Coverage
For each question, inspect relevant current search results and the pages you already own. Record the audience, answer format, and scope you observe. Search results help test your interpretation; they are not instructions to reproduce another article.
Add Search Console query evidence where it exists, including the page and date range. Impressions describe your site's reported exposure. They do not establish market search volume, and a small sample does not prove that a topic lacks value.
If a useful page already owns the same task, improve that page. If the existing page serves another decision, define a supporting article and link the two where the reader's task changes. Do not create separate URLs for minor wording variations.
Our keyword clustering example shows how preparation, evaluation, and measurement questions can become distinct page assignments. The interview notes add a different input: the customer's language and the context behind the question.
Turn One Question Into a Reviewable Brief
Before drafting, complete this small handoff record:
| Brief field | What the editor needs |
|---|---|
| Audience and situation | The reader's role and the task that triggered the question |
| Main answer | A direct statement of what the page will explain |
| Existing-page decision | The URL to refresh, or the reason a new page is justified |
| Source references | Interview timestamps or note IDs, plus approved external sources |
| Supplied facts | Statements the product or subject owner has verified |
| Quote treatment | Exact approved wording and attribution, or no public quotation |
| Required coverage | The decisions, examples, and limitations the reader needs |
| Exclusions | Adjacent questions that belong elsewhere |
| Reviewer and completion check | Who checks the evidence and what makes the draft ready |
Use the SEO content brief template when you need a fuller assignment. Where a Content Kit is useful, choose only the components supported by the available material. An interview does not require a quote in every resulting article.
Review the Draft Against the Evidence
Check whether the opening answers the assigned question, the example helps the reader act, and the article preserves uncertainty. Return to the recording for quotations. Check product claims against current product sources rather than treating a participant's recollection as a specification.
Keep the useful answer in readable page text. Google's AI features guidance says existing SEO fundamentals remain relevant and important content should be available in textual form. An interview-derived diagram can support the explanation, but it should not contain the only version of the answer.
After publication, distinguish search exposure, page visits, and meaningful next steps. Keep a record of the page's original question and supporting evidence so a later refresh can identify what changed.
The output of the interview is a supported editorial decision: one audience, one useful answer, and a source trail an editor can inspect. Start with one conversation and one article assignment before scaling the process.
Sources and Next Steps
- Google: creating helpful, reliable, people-first content.
- Google: AI features and your website.
- RoboWrite Content Kits: organize the requirements for a reviewed article.
