playbooks

home / skills / openclaw / skills / aeo-prompt-question-finder

aeo-prompt-question-finder skill

/skills/psyduckler/aeo-prompt-question-finder

This skill discovers what questions people ask about a topic by querying Google Autocomplete with modifiers and returns ready to use prompts.

npx playbooks add skill openclaw/skills --skill aeo-prompt-question-finder

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
2.0 KB
---
name: aeo-prompt-question-finder
description: Find question-based Google Autocomplete suggestions for any topic. Prepends question modifiers (what, how, why) to a seed topic and returns real autocomplete suggestions — useful for AEO prompt research, content ideation, and understanding what people ask about a topic. Use when the user wants to discover questions people search for, find content angles, or do keyword/prompt research for a topic.
---

# Prompt Question Finder

Discover what questions people ask about a topic by querying Google Autocomplete with question modifiers.

## Usage

Run the script from the skill directory:

```bash
python3 scripts/find_questions.py "travel itinerary"
```

### Options

- `--modifiers what how why should` — override default modifiers (default: what how why should can does is when where which will are do)
- `--delay 0.5` — seconds between requests (use 0.5–1.0 when running many topics in batch)
- `--json` — output as JSON for programmatic use
- `--volume` — fetch avg monthly search volume via DataForSEO (reads creds from macOS Keychain: `dataforseo-login` / `dataforseo-password`, or env vars `DATAFORSEO_LOGIN` / `DATAFORSEO_PASSWORD`)
- `--location 2840` — DataForSEO location code (default: 2840 = US)
- `--lang en` — language code for volume lookup (default: en)

### Examples

```bash
# Default modifiers (what, how, why)
python3 scripts/find_questions.py "protein powder"

# Custom modifiers
python3 scripts/find_questions.py "travel itinerary" --modifiers what how why should when

# JSON output
python3 scripts/find_questions.py "travel itinerary" --json
```

## Rate Limits

Google Autocomplete is an unofficial endpoint. Single-topic runs (10 requests) are safe. When running multiple topics in batch or parallel, always use `--delay 0.5` or higher to avoid temporary IP blocks.

## How It Works

For each modifier, the script queries `https://suggestqueries.google.com/complete/search` with `"{modifier} {topic}"` and returns the autocomplete suggestions. No API key required.

Overview

This skill finds question-based Google Autocomplete suggestions for any seed topic to reveal what people are asking. It prepends common question modifiers (what, how, why, etc.) to your topic, queries Google Autocomplete, and returns real suggestion strings useful for prompt research and content ideation.

How this skill works

For each modifier the skill sends a query to Google Autocomplete using the pattern "{modifier} {topic}" and collects the returned suggestions. It supports configurable modifier lists, optional JSON output for programmatic use, configurable request delay to avoid rate limits, and an optional volume lookup via DataForSEO when credentials are provided.

When to use it

  • When you need fresh question-based search queries for content ideation
  • When researching prompts for AEO (answer engine optimization) or search intent
  • When building FAQ sections or topic clusters from real user questions
  • When doing keyword or prompt research and you want natural-language queries
  • When preparing social posts, outlines, or article headlines grounded in what people ask

Best practices

  • Start with the default modifiers then add or remove modifiers to match your audience (e.g., who, which, where).
  • Use --delay 0.5–1.0 when running many topics or batches to reduce the risk of temporary IP blocks.
  • Run single-topic checks interactively to sample results before scaling to bulk runs.
  • Use --json output for pipelines or to feed results into content tools and spreadsheets.
  • If you need search volume, enable --volume and provide DataForSEO credentials; treat volume as an optional signal, not definitive demand.

Example use cases

  • Generate a list of real user questions to build an FAQ for a product page.
  • Produce seed prompts for AEO or long-form article outlines from topical questions.
  • Quickly assemble content briefs by combining top question modifiers with your target topic.
  • Validate topic angles by checking what question forms (how vs why) dominate user queries.
  • Create datasets of natural-language queries for prompt engineering or chat assistants.

FAQ

Do I need an API key to get autocomplete suggestions?

No. The skill uses Google Autocomplete as an unofficial endpoint and does not require an API key for suggestions.

How do I avoid getting blocked when running many topics?

Add a delay between requests (use --delay 0.5–1.0) and avoid parallelizing many simultaneous requests from the same IP.