Entity Knowledge-Graph Optimizer
Queries the Google Knowledge Graph and Wikidata to assess how well a brand entity is defined, connected, and disambigua…
Updated
About this skill
Entity Knowledge-Graph Optimizer is a AI Search (AEO and GEO) skill for AI agents, published in the seoskills.sh catalog. Reach for it when your work involves answer and generative engine optimization for AI Overviews, Perplexity, and ChatGPT. Install it with one command and it runs inside your own agent, so the work happens in your workflow, not a separate SEO tool.
SKILL.md
Entity Knowledge-Graph Optimizer
AGENT ROLE: Autonomous entity-grounding agent. Resolve the brand entity in the Google Knowledge Graph and Wikidata, score its grounding, and emit prioritized recommendations per references/output.schema.json. Recommend; never assert the entity is "verified" beyond what the graphs return.
OBJECTIVE
Determine whether the brand is an established, disambiguated entity that AI systems can ground answers on, and produce the specific structured-data and corroboration steps to improve it.
INPUTS
brand(REQUIRED):{ name, domain, type_hint?: "Organization|LocalBusiness|Person|Product" }.wikidata_qid(OPTIONAL): known Wikidata Q-id to skip search disambiguation.expected_sameas(OPTIONAL string[]): canonical profile URLs the brand controls (LinkedIn, Crunchbase, official social).
AUTHENTICATION
- Google Knowledge Graph Search API: REQUIRE env
KG_API_KEY(Google Cloud API key with "Knowledge Graph Search API" enabled).- IF unset THEN set
kg_status="skipped_no_key"and proceed with Wikidata only (do NOT hard-fail — Wikidata alone is still useful).
- IF unset THEN set
- Wikidata: public, no key. Use a descriptive UA
seoskills-entity-optimizer/1.0and respect the WMF API etiquette.
EXPECTED TOOL CALLS
- Run
scripts/entity_audit.py --brand brand.json [--qid Q123]. - KG:
GET https://kgsearch.googleapis.com/v1/entities:search?query={name}&types={type}&key={KG_API_KEY}&limit=5. - Wikidata:
GET https://www.wikidata.org/w/api.php?action=wbsearchentities&search={name}&language=en&format=json; thenwbgetentitiesfor claims of the chosen Q-id.
PROCEDURE (deterministic)
STEP 1 — KG RESOLUTION: search KG; pick the top result whose @type/name best matches AND whose url/detailedDescription references brand.domain. Record resultScore, @type, description, detailedDescription.url. IF no domain-consistent match THEN kg_entity="unrecognized".
STEP 2 — WIKIDATA RESOLUTION: use wikidata_qid if given, else wbsearchentities; disambiguate by matching official website (property P856) to brand.domain. IF none matches domain THEN wikidata_entity="unrecognized_or_ambiguous".
STEP 3 — GROUNDING CHECKS (each yields a finding with severity):
NOT_IN_KG(high) IF KG unrecognized (and key was present).NOT_IN_WIKIDATA(high) IF no domain-matched Wikidata item — the single biggest AI-grounding gap.MISSING_OFFICIAL_WEBSITE(high) IF the Wikidata item lacksP856= brand.domain.WEAK_SAMEAS(medium):expected_sameasprofiles not linked from the entity / not in the site's Organization schemasameAs.MISSING_ENTITY_TYPE(medium) IF no clearinstance of(P31) / schema@type.THIN_DESCRIPTION(low) IF KG/Wikidata description < 10 words.NO_CORROBORATION(medium) IF fewer than 2 independent authoritative references (Wikidata refs / KG detailedDescription source). STEP 4 — RECOMMEND per finding (concrete): e.g., "PublishOrganizationschema on {domain} withsameAslinking {expected_sameas}", "Create/complete a Wikidata item with P856={domain} and P31={type}", "Add corroborating coverage on authoritative third-party sources". STEP 5 — SCOREgrounding_score0–100 = weighted pass rate of the checks. EMIT.
RATE LIMITS & ERROR HANDLING
- KG API: on
429backoff2^attempt(max 4); on persistent failure setkg_status="rate_limited"and continue with Wikidata. - Wikidata: serialize requests, ≥ 100ms apart; on
429/maxlaghonor the retry hint. Never hammer the WMF API. - Any single upstream failure downgrades that source's findings to
unknown, never to a false "missing".
MISSING / INSUFFICIENT DATA
- IF BOTH graphs are unavailable THEN
status="sources_unavailable", return no false negatives. - Absence of an entity is reported as a finding to fix, distinct from "we could not check".
OUTPUT
One JSON object per references/output.schema.json. No prose.
FILES
scripts/entity_audit.py— KG + Wikidata resolver, grounding checks, recommendations.references/output.schema.json— output contract.
Not using the CLI? Copy the SKILL.md and paste it straight into ChatGPT, Claude, or any agent.
Embed a badge
Install into your agent
More in AI Search (AEO and GEO)
ai-seo
When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site
seo-geo
SEO & GEO (Generative Engine Optimization) for websites. Analyze keywords, generate schema markup, optimize for AI search engines (ChatGPT, Perplexity, Gemini, Copilot, Claude) and traditional search (Google, Bing). Use when user wants to improve search visibility, search optimization, search ranking, AI visibility, ChatGPT ranking, Google AI Overview, indexing, JSON-LD, meta tags, or keyword research.
optimize-for-ai
Optimize content for AI search engines — ChatGPT, Perplexity, Claude, Gemini, Google AI Overviews. Use when the user asks about AI SEO, AISO, getting cited by AI, appearing in AI answers, answer engine optimization, AEO, GEO, LLMO, AI Overviews, zero-click search, or how to appear in ChatGPT/Perplexity results. For traditional SEO, see diagnose-seo.
seo-aeo-best-practices
SEO and AEO best practices for metadata, Open Graph, sitemaps, robots.txt, hreflang, JSON-LD structured data, EEAT, and content optimized for search engines and AI answer surfaces. Use this skill when implementing page SEO, technical SEO, schema markup, international SEO, AI-overview readiness, or improving content for Google, ChatGPT, Perplexity, and similar assistants.
seo-maps
Maps intelligence for local SEO: geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification, competitor radius mapping, and LocalBusiness schema generation. Three tiers: free (Overpass + Geoapify), DataForSEO, and DataForSEO + Google. Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", or "SoLV".
seo-dataforseo
Live SEO data via DataForSEO MCP server: SERP analysis, keyword research (volume, difficulty, intent, trends), backlink profiles, on-page analysis, competitor and content analysis, business listings, AI visibility (LLM mention tracking), and domain analytics. Requires DataForSEO extension installed. Use when user says "dataforseo", "live SERP", "keyword volume", "backlink data", "AI visibility check", or "real search data".