SEO Keyword Insights

SEO Keyword Insights

Build a decision-ready organic-search strategy from a site, product, seed topic, or competitor set. This Skill is a SandBase API workflow: it calls the named SEO capabilities in the SandBase API map through the SandBase MCP gateway. Use an authorized SandBase MCP connection and the discover → inspect → run workflow below; never request, print, or store an API key in the research output.

The primary capability is DataForSEO keyword search through SandBase: discover candidates, validate demand and difficulty, compare site visibility, and inspect live SERPs. Read example workflows when the user needs a starting prompt or wants to understand the output.

Operating principles

• Start from the business and audience, not a brand-name keyword list.
• Treat tool-returned metrics and SERP results as evidence; treat model-generated keywords, intent labels, and recommendations as hypotheses or judgment.
• Select the country, language, device, and search engine deliberately. State any default rather than silently assuming a market.
• Optimize for qualified organic traffic and the site's conversion model, not volume alone.
• Inspect live SERPs before recommending a page type or claiming a ranking opportunity.
• Keep user domains, competitor lists, raw exports, and strategy confidential. Return a summarized report unless raw data is requested.

Workflow

1. Frame the decision

Collect or infer the target site or product, target market, language, conversion goal, audience, content scope, and competitors. Classify the request as one or more of: discovery, site opportunity, competitor gap, content roadmap, or page keyword map.

If a site is supplied, form a compact site brief before researching: category, offer, ICP, jobs-to-be-done, differentiators, conversion action, current content themes, and exclusions. Inspect the homepage and a small set of representative product, use-case, pricing, docs, and content pages. Use a SandBase site/content capability when available; use SandBase web search only as a fallback. Record inaccessible or JavaScript-heavy pages as evidence gaps.

When market details are missing, choose a defensible default only if the site or request makes one clear; otherwise ask for the market. Never merge metrics from different markets or engines without labels.

2. Select and call SandBase capabilities

Read the SandBase API map before selecting tools. Treat each listed tool_name as a capability identifier to resolve through the SandBase gateway:

1. Use sandbase_discover with the provider and capability to find the current endpoint name.
2. Pass the returned name to sandbase_inspect; read inputSchema, pricing, and execute_as.
3. Follow execute_as to call sandbase_run using execute_as.arguments.name and schema-defined arguments. If it returns a run_id, poll sandbase_run_get within the task budget until completed or failed; report pending or failed runs without automatically resubmitting them.
4. Keep the returned endpoint name, market, language, device, and timestamp with the returned data.

Use the API map to select the intended SEO capability and sandbase_discover to resolve its current name. If it is unavailable, search for a relevant alternative and verify it with sandbase_inspect before running it.

Prefer this evidence ladder:

1. Site/content parsing for the supplied site.
2. Keyword discovery from site-derived, product, problem, use-case, and integration seeds.
3. Demand, difficulty, trend, and clickstream metrics for the shortlisted candidates.
4. Ranked-keyword, competitor, and intersection data when a domain comparison is useful.
5. Live organic SERPs for the leading candidates and each priority cluster.

The API map intentionally fixes the product-facing capability names, while sandbase_inspect remains authoritative for payload shape, supported locations, and optional parameters. If an expected capability is unavailable, identify the evidence gap and continue only with evidence that is available.

3. Build and validate the keyword universe

Create 3–10 justified seed themes from the site brief or product description: category, capability, use case, pain point, buyer role, integration, comparison, and transactional or informational modifiers. Keep brand terms separate unless brand SEO is explicitly in scope.

Expand a small number of diverse seeds first, then deduplicate and remove clearly irrelevant, unsafe, navigational, or off-market terms. Preserve the provenance of each candidate: site, seed, suggestion, related, competitor, SERP, or hypothesis.

Validate the promising candidates with the available SandBase capabilities. Keep search volume, difficulty, CPC, trend, clickstream, rank, and SERP features in their original market and source context. Mark unavailable metrics as unavailable; never estimate them.

For competitor work, distinguish:

• coverage gap: a competitor ranks and the target does not;
• performance gap: both rank, but the target is materially weaker;
• strategic gap: the query fits the target's offer but no adequate target page exists.

Do not call every available provider merely because it exists. Stop expanding once clusters have enough evidence to make a decision; expand again only for thin or ambiguous clusters.

Use the keyword capabilities deliberately:

• Start with keyword_suggestions, keyword_ideas, related_keywords, or Google Ads seed expansion.
• Use search_volume, historical volume, Google Trends, and bulk difficulty only after shortlisting candidates.
• Use keywords_for_site and ranked_keywords to distinguish existing coverage from true gaps.
• Use competitors_domain, domain_intersection, and serp_competitors only for a justified competitor comparison.
• Use Google organic SERP and related/autocomplete queries to validate intent and the recommended page type.