Geo Query Finder logo

Geo Query Finder

Organization
OpenClaudia
geo-query-finder

Find which ChatGPT search queries mention a given brand. Tests long-tail queries against ChatGPT's web-search-enabled model and reports which ones surface the brand. Use when the user asks to "find queries for [brand]", "check GEO visibility", "which queries mention [brand]", "geo query finder", "find AI mentions", or "test ChatGPT queries for [brand]".

Overview

PublisherOpenClaudia
Repositoryopenclaudia-skills
Skill namegeo-query-finder
Stars
714
Forks
60
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by OpenClaudia on GitHub. Read the source before you install it.

Installation

Install the Geo Query Finder AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/geo-query-finder
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git /tmp/openclaudia-skills
mkdir -p .claude/skills
cp -r /tmp/openclaudia-skills/skills/geo-query-finder .claude/skills/geo-query-finder
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Geo Query Finder in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Geo Query Finder on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Geo Query Finder is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

GEO Query Finder

Find which ChatGPT search queries mention a given brand. Tests long-tail queries against ChatGPT's web-search-enabled model and reports which ones surface the brand.

Trigger

Use when the user asks to "find queries for [brand]", "check GEO visibility", "which queries mention [brand]", "geo query finder", "find AI mentions", or "test ChatGPT queries for [brand]".

Usage

/geo-query-finder <brand_name> [--industry <industry>] [--features <feature1,feature2,...>] [--queries <custom_query1;custom_query2;...>]

Examples:

  • /geo-query-finder "Acme Corp" — auto-researches the brand and generates queries
  • /geo-query-finder "Acme Corp" --industry "smart TV OS" --features "white-label,voice-control,OEM licensing"
  • /geo-query-finder "Acme Corp" --queries "best regulatory AI;eCTD validation tool;pharma compliance software"

How It Works

Step 0: Pull pre-indexed LLM mentions (DataForSEO) — do this FIRST

Before generating speculative queries, check if DataForSEO already has indexed mentions for the brand's domain. If it does, you get ground-truth queries with search volume in one call instead of burning OpenAI dollars guessing.

Auth via DATAFORSEO_LOGIN / DATAFORSEO_PASSWORD environment variables.

bash
AUTH=$(printf '%s' "$DATAFORSEO_LOGIN:$DATAFORSEO_PASSWORD" | base64)
# Google AI Overview citations
curl -s -X POST "https://api.dataforseo.com/v3/ai_optimization/llm_mentions/search/live" \
  -H "Authorization: Basic $AUTH" -H "Content-Type: application/json" \
  -d '[{"target":[{"domain":"<DOMAIN>","search_filter":"include","include_subdomains":true}],"platform":"google","limit":700}]'
# ChatGPT citations (substitute "platform":"chat_gpt")

Critical flags:

  • "include_subdomains": true — without it, apex domains return 0 results (www.X treated as a different domain).
  • Omit location_code to get global results; add "location_code": 2840 only to scope to US.
  • platform options: "google" (AI Overview), "chat_gpt". Perplexity is NOT supported via this dataset.

Extract from each items[]:

  • question — the real search query where the brand was cited
  • ai_search_volume — monthly AI search volume (use to prioritize)
  • sources[] — entries with domain matching the brand have the exact cited URL
  • location_code, language_code, model_name — for geo/locale breakdown
  • answer — the LLM answer text (for context)

Decision rule:

  • If ≥20 queries returned → skip Steps 1–4 entirely; report these as ground-truth mentions and focus Step 5 on gap analysis (sort by volume, find URL-section winners like /guides/ vs /tools/).
  • If <20 queries → use them as seed input for Step 2 (generate variations of the query themes DataForSEO already confirmed), then run Steps 3–4 only on the gaps.
  • If 0 queries → the domain has no AI citations; proceed with the original Steps 1–5 (speculative testing) as fallback.

Step 1: Research the Brand

If no --industry or --features provided, use web search to understand:

  • What the brand does / what industry it's in
  • Key differentiators vs competitors
  • Unique features that competitors DON'T have

Step 2: Generate Long-Tail Queries

Generate 15-20 long-tail queries across these categories:

  1. Feature-specific (unique capabilities only this brand has)
  2. B2B/decision-maker (queries from buyers, not consumers)
  3. Problem-solving ("how to X without Y")
  4. Comparison/alternative ("alternative to [dominant player]")
  5. Use-case specific (niche scenarios where the brand excels)

Avoid generic queries where dominant players will always win.

Step 3: Query ChatGPT via OpenAI Search API

Use OpenAI's gpt-4o-search-preview model with web search enabled:

bash
OPENAI_API_KEY from environment variable
python
import json, os, urllib.request, ssl

OPENAI_API_KEY = os.environ["OPENAI_API_KEY"]

data = json.dumps({
    "model": "gpt-4o-search-preview",
    "web_search_options": {"search_context_size": "medium"},
    "messages": [{"role": "user", "content": "<query>"}],
    "max_tokens": 1000
}).encode()

req = urllib.request.Request(
    "https://api.openai.com/v1/chat/completions",
    data=data,
    headers={
        "Authorization": f"Bearer {OPENAI_API_KEY}",
        "Content-Type": "application/json"
    }
)

resp = urllib.request.urlopen(req, context=ssl.create_default_context(), timeout=45)
result = json.loads(resp.read())
answer = result["choices"][0]["message"]["content"]

Step 4: Check Mentions

For each query, check if the brand name (or known aliases) appears in ChatGPT's response:

  • Check case-insensitive match
  • Check variations (with/without spaces, dots, hyphens)
  • If mentioned, extract the surrounding context (200 chars around the mention)
  • Note the position (is it #1 recommended? listed among many? mentioned in passing?)

Step 5: Report Results

Output a summary table:

## GEO Query Finder Results: [Brand Name]

### Mentioned (X/N queries)
| Query | Position | Context |
|-------|----------|---------|
| ... | #1 | "Brand is the leading..." |

### Not Mentioned (Y/N queries)
| Query | What ChatGPT Recommended Instead |
|-------|----------------------------------|
| ... | Competitor A, Competitor B |

### Recommendations
- Queries where brand is ALREADY mentioned: create more authoritative content to maintain/improve position
- Queries where brand is NOT mentioned but SHOULD be: these are content gaps — create targeted pages
- Queries to AVOID: too generic, dominated by big players, not worth the effort

Rate Limiting

  • Run queries sequentially with 1-2 second delays to avoid rate limits
  • Each query costs ~$0.01 via OpenAI API
  • Default: 15-20 queries per run (~$0.15-0.20 per run)

Notes

  • Results reflect ChatGPT with web search enabled (grounded in real-time web results)
  • Results may vary slightly between runs due to search freshness
  • This tests ChatGPT specifically — Gemini and Copilot may give different results
  • For ongoing monitoring, consider scheduling periodic runs to track visibility changes over time

Frequently asked questions

What does the Geo Query Finder AI skill do?

Find which ChatGPT search queries mention a given brand. Tests long-tail queries against ChatGPT's web-search-enabled model and reports which ones surface the brand. Use when the user asks to "find queries for [brand]", "check GEO visibility", "which queries mention [brand]", "geo query finder", "find AI mentions", or "test ChatGPT queries for [brand]".

Why use Geo Query Finder on TypingMind?

Because you install it once and use it with any model. Geo Query Finder is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Geo Query Finder in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/geo-query-finder. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Geo Query Finder?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Geo Query Finder?

As many as you like. As long as a model supports skills, you can use Geo Query Finder with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Geo Query Finder AI skill free?

Yes. It is published on GitHub by OpenClaudia under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇