Keyword Discovery skill

Keyword Discovery

Start with the seed, product boundaries, target market and language. Follow the user's highest-value use case first. Explore alternative wording, action, input, desired output, audience, use case, workflow scale and quality or failure conditions. Combine dimensions into plausible tasks and retain the original wording of observed queries. For another market, find local usage independently, including colloquial terms.

Build the base expression family before expanding features or scenarios. Separate the action, object and optional qualifiers. Probe natural verb, process noun, tool noun, word order and number variants with and without qualifiers. Check tool-family heads, cross-root task paraphrases and audience-specific language when relevant. Preserve the raw strings; removing a modifier can broaden intent. For generate song with ai, probe generate song, generate a song, song generation, AI song generation, song generator, AI song generator, song maker and make a song with AI. Query distinct root forms separately to discover branches that the original string misses. Keep unattested forms labeled as hypotheses.

For a narrow seed, identify the constraint that narrows it (such as a symptom, material, audience or use case). Offer the nearest useful broader query by relaxing that constraint while preserving the task. Show the parent followed by the input seed and explain the difference. Label a parent as observed wording or an inferred topic. Keep the original seed as the research scope. Use the parent to find relevant siblings when helpful. Multiple plausible parents can reflect different dimensions. A parent-child relationship alone does not justify targeting both on one page.

Inspect the target-market search results for competitors serving the task. Open relevant navigation, sitemap URLs, feature pages, industry pages and help topics. Check title, H1, actual inputs and outputs, and the referring page. A link from an ecommerce solution to a white-background tool suggests a product-photo hypothesis. Record the page URL and label the derived query as inferred. A competitor page supports coverage; claims about its traffic or rankings require separate evidence. Reuse competitor-research findings if available.

Probe Google Autocomplete with the seed and promising partial phrases. Capture People Also Ask questions verbatim and People Also Search For or Related searches under the label actually displayed. Record the triggering query, market, language, date and source for each observation. A featured snippet gives clues about answer format. Use relevant GSC queries, ad search terms, site search, support language or user-provided exports to extend coverage. Re-query valuable new branches separately. If ordinary search access times out or cannot expose these surfaces, use an available authorized cloud browser or personal agent to run the queries in the target locale. Supply seeds, locale and required surfaces; request verbatim entries, triggering query, displayed module label, date and source URL or screenshot. Distinguish a module absent on an inspected page from a page that could not be inspected. If no such session is available, return the pending collection request and continue with available evidence. Keep synthesized phrases separate from observed suggestions, even when they sound natural.

For background remover, distinguish removing a white background from adding white to a product photo. Explore image versus video, ecommerce versus passport, and preserving fine edges versus repairing an existing cutout. Use these as probes until observed.

Hand keyword-clustering a deduplicated candidate pool retaining raw wording, source or URL, observed/inferred status and branch. Surface unsupported product needs separately. Stop at saturation or the agreed boundary.

For creative generation, explore the attributes of the output as well as the inputs. Probe genre or style, occasion, audience and intended use. For a pattern such as [genre] song generator, sample contrasting values and check demand evidence individually. Keep unverified combinations as probes.