DocsFoundation and setup
Understand the Data Behind Xtrusio’s Question-Demand Estimates
Xtrusio uses Google keyword data from DataForSEO or a keyword-tool export uploaded by the team to establish the initial question bank. The team may use SEMrush or Ahrefs for external research, but the application does not have a direct integration with either tool.
Availability and responsibility
Xtrusio uses Google keyword data from DataForSEO or a keyword-tool export uploaded by the team to establish the initial question bank. The team may use SEMrush or Ahrefs for external research, but the application does not have a direct integration with either tool. Question Generator builds on that foundation with buyer-persona questions, related and long-tail questions, and questions the company wants to answer about its products, proposals or positioning.

How the question bank is developed
- Research the company, its offerings, audience and competitors.
- Collect measured keyword data through DataForSEO or an approved keyword-tool export. Upload the export when using that route. Keep its source and market in the research record.
- Develop questions around the needs and decisions of the company's buyer personas.
- Expand into related and long-tail questions, including natural-language questions people could ask AI.
- Include company-requested questions even when established search demand is unavailable.
- Review relevance, coverage, priorities and the volume evidence to select 150–200 target questions.
- Agree the monitoring scope and begin collecting AI answer evidence. Search volume supports selection. It does not determine every question included, and generated questions are not evidence that people have already submitted those exact prompts. Before execution and client-specific customization proceed, Xtrusio's team reviews the Foundation with the client across meetings. The client approves the buyer questions, product and service descriptions, facts and figures. This is a manual approval process; AI-generated suggestions do not replace client approval.
What the displayed volume represents
For keyword-export distillation, Xtrusio groups related keywords into canonical questions and computes a combined volume from the imported keyword rows. When an imported question lacks measured keyword data, the interface labels a Gemini-generated estimate as an estimate. Neither is a count of prompts entered into an AI service. The basis behind a volume value can include:
- Source-keyword volume describes the keyword in the provider's defined dataset.
- Related-keyword volume supplies context for a question whose wording differs from the researched phrase.
- A Gemini estimate for an imported row without keyword data. It is labelled as an estimate rather than measured volume. The Question Generator's keyword suggestions use DataForSEO for related keywords, suggestions and People-Also-Ask data in a selected market. Imported keyword exports may come from another provider. An estimate is not a provider-validated number, and related-keyword volume is not measured demand for the exact question.
Example: a related keyword supports a longer question
Suppose keyword research shows 300 monthly searches for “contract renewal software.” The question bank includes “Which contract software helps procurement teams track renewal obligations?” and associates it with that keyword. The displayed 300 belongs to the related keyword, not the exact longer question. It does not establish that 300 people asked the question in ChatGPT. The wording and number here are illustrative. If a company imports a question about a specialized proposal requirement without a measured keyword row, Xtrusio may show a labelled Gemini estimate. That question may still deserve monitoring because the company needs a useful answer for prospective buyers.
Compare volume without overstating demand
Keep the source keyword, provider, market and measurement definition with the research when available. Check how multiple source phrases are grouped before interpreting a total. Several questions can relate to one keyword. Do not count the same source volume repeatedly as separate audiences merely because the question wording changes. Use the estimate label and ask the delivery team for the underlying keyword source before relying on a value in a quantitative comparison. Neither an estimated figure nor associated keyword volume establishes a direct count of AI conversations. Scan counts measure collected test answers, not market demand.
If the basis is unclear
Ask which keyword or estimation method supports the value before using it in a quantitative comparison. The question's strategic relevance can be assessed separately while its volume basis is clarified.