Google search volume and AI search volume: a practical keyword workflow
Guides
Choose content topics with two distinct signals: Google Ads keyword demand and modeled AI question demand. Includes a bounded MCP workflow and the limits that matter.
Start with a decision, not a bigger keyword list. Suppose you are choosing the next page or guide for a business website. Write down a small set of relevant public business terms, the target country and the language. Ask which topic deserves further research. This is a workflow example, not a claim that any topic will produce visits or sales.
Keyword Metrics returns available Google Ads search volume, CPC, advertising competition and monthly history through DataForSEO. Use these fields to compare demand and advertising context. Advertising competition does not measure organic SEO difficulty. Keep the CPC value as returned: our response has no separate currency field, so an agent should not invent a currency label.
AI Search Volume adds a different signal. DataForSEO models question-related keyword demand using an algorithm that includes Google People Also Ask data. It is not a count of private ChatGPT, Perplexity or other assistant logs. It also does not say whether an assistant mentions your business. Use the supplied monthly periods; the time you download a response is not the time all underlying observations were made.
For a useful comparison, keep the keyword set, country and language identical across the two requests. Put Google search volume and modeled AI search volume in separate columns, with available periods and missing values visible. Do not add them into a total or divide them to claim an AI market share. A topic with relevant commercial intent and useful question signals may deserve a closer look; neither metric replaces reviewing the actual search results and your offer.
The CONNSKILL Keyword Research page now provides an MCP example for keyword_metrics and ai_search_volume. Start the adapter without a wallet and with X402_MAX_USD set to 0 to inspect the tools without buying. For example, both accept keywords ["seo api", "keyword research"], location_code 2276 and language_code "de". Those are illustrative inputs for Germany, not recommendations or instructions to buy.
Before enabling a paid call, confirm your own inputs, the current service status and each complete payment quote. Keyword Metrics and AI Search Volume are separate purchases; the AI check is optional. Approve the combined spending limit and any additional fees explicitly. The adapter cap applies per call, not to the whole workflow. A timeout or unclear result is a reason to reconcile the existing purchase, not authorize another one.
After successful delivery, have your agent propose one content topic and explain which returned fields support it. Keep the original inputs, result and payment reference privately. Publish useful content that answers the chosen question, then use your own analytics and delivered order records to evaluate visits and purchases. This workflow helps make a better-informed choice; it does not guarantee rankings or revenue.