Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

answer-engine-optimizer

Étoiles5

Forks0

Mis à jour3 juillet 2026 à 21:51

Optimize a brand's mapped content to get cited by AI answer engines — Google AI Overviews, ChatGPT, Perplexity, Gemini. Scores drafts for citation-readiness with aeo_score.py, produces a per-node hardening checklist, and spot-checks live AI answers for whether the brand (vs competitors) is cited. Use whenever the user mentions AEO, GEO, LLM SEO, "getting cited by ChatGPT/Perplexity", AI Overviews, answer engines, AI search visibility, or asks why an AI assistant recommends competitors and not them. The GEO half of seo-performance-tracker. Never invents a visibility score. Triggers on AI-visibility / answer-engine intent broadly.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

siddiqss

siddiqss/semantic-seo-suite

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en études de marché et spécialistes en marketingProfessions des affaires et des opérations financières·SOC 13-1161

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name

answer-engine-optimizer

description

answer-engine-optimizer

The citation feedback loop. Where seo-performance-tracker measures Google rankings, this optimizes for being the source an LLM quotes — which, for a tool category whose buyers research inside ChatGPT and Perplexity, is where a lot of the demand now decides.

It reuses the suite's spine: read the brand workspace, respect the grounding tier, tag every value, and feed results back into the map and calendar. It layers onto the on-page map — same nodes, hardened — it does not replace it.

Read first: ../../framework/answer-engine-optimization.md (the method + the honesty rules), then ../../framework/macro-micro-semantics.md (the writing tactics it scores).

Preconditions

entity-profile.json + topical-map.json exist (run seo-brand-foundation / topical-map-builder first).
Drafts to score live in brands/<slug>/drafts/. With no drafts yet, the skill still produces the hardening spec and the live-answer probe.
Live-answer probing needs grounding.sources.web_search: true (T1). Without it, do the offline scoring only and say the probe was skipped — do not guess citations.

Workflow

Score citation-readiness (T0, offline). For each draft:
```
python ../../scripts/aeo_score.py --draft brands/<slug>/drafts/<slug>.md \
  --schema-dir brands/<slug>/data/schema --json
```
Run it after validate_draft.py is clean — AEO is advisory, fabrication is a gate. Collect score, grade, and the specific fixes (DEF / QA / TLDR / LIFT / BREV / SELF / SCHEMA). Scores are measured (mechanical), the recommended rewrites are asserted.
Probe live answer engines (T1, web_search). For the highest-value target queries (core-section, especially comparison/alternative nodes), query them answer-style and record, per query + engine + date: is the brand named? cited with a link? which competitor sources are quoted instead? This is a dated spot check (n=1 per probe), labelled measured — not a rank tracker. Never aggregate it into a visibility %.
Write the AEO report → brands/<slug>/audits/<date>-aeo.md:
- Readiness table — per node: AEO score, grade, top fixes (measured + asserted).
- Live citations — per probed query: brand cited? competitors cited? (measured, dated, with the query text; honest about the tiny sample).
- Hardening queue — nodes <70, ranked, with the concrete edits.
- If web_search is off: state the probe was skipped; emit only the readiness table.
Feed the loop.
- Nodes scoring <70 → mark needs-update in the map; push up calendar.md.
- Apply hardening to drafts via semantic-draft-writer; ensure JSON-LD via linking-and-schema. Re-score to confirm the lift.
- Queries where competitors are cited and the brand isn't → a hardening task on the owning node and a signal for off-page authority (link-opportunities).
- New questions found while probing → query-network additions via topical-map-builder.

Definition of done

Every existing draft scored; a dated AEO report with the three sections written.
Hardening queue fed back into map statuses + calendar.
No invented visibility number anywhere — citations are dated, per-query observations or they are absent. If web_search was off, the report says so.

Grounding ladder

T0: offline aeo_score.py readiness scoring + hardening spec. Fully useful alone.
T1 (web_search): + live answer-engine spot checks (measured, dated, per query).
T2: no paid dependency; SERP-feature data from DataForSEO (if on) can corroborate which queries trigger AI Overviews, labelled measured.

Plus depuis ce dépôt

même dépôt

content-brief-generator

siddiqss/semantic-seo-suite

Generate entity-aware, Koray-style content briefs from a topical-map node or any target query — a semantically ordered heading skeleton with entity/attribute tags, internal-link targets, snippet target, word budgets, locked-facts references, and a do-not-fabricate list. Use whenever the user asks for a content brief, an article outline, writer instructions, "brief for X", or wants to start writing an article that exists in the topical map. Runs SERP recon first. Triggers on outline/brief intent broadly, not just the word "brief".

2026-07-035

content-distribution

siddiqss/semantic-seo-suite

Plan how a brand's published content gets seen — per-piece channel fit, repurposing atoms (X thread, LinkedIn post, Reddit answer, short-form video, newsletter), and a promotion cadence anchored to the publishing calendar. Use whenever the user asks how to promote or distribute content, repurpose a post, where to share an article, build a launch or content-promotion plan, drive traffic before SEO kicks in, or "we published it, now what". Matches channels to the brand's real personas; invents no reach numbers. Triggers on distribution / promotion / repurposing intent broadly.

2026-07-035

link-opportunities

siddiqss/semantic-seo-suite

Plan off-page authority for a brand — find and prioritize backlink opportunities from its topical map and competitor set, with a safe anchor-text mix and a competitor backlink-gap worksheet. Use whenever the user mentions backlinks, link building, off-page SEO, domain authority, digital PR, guest posts, "who should link to us", getting into best-of listicles, or why competitors outrank despite thinner content. Discovers real prospects via web_search (T1) or DataForSEO backlinks (T2); never invents authority numbers, referring domains, or contact emails. Triggers on off-page / link intent broadly.

2026-07-035

linking-and-schema

siddiqss/semantic-seo-suite

Generate an internal-linking plan and JSON-LD structured data from a brand's topical map and entity profile. Use whenever the user asks about internal links, anchor text, site structure, linking strategy, schema markup, structured data, or JSON-LD — or right after new content is drafted or published. Produces an actionable link checklist (with varied anchors) and validated per-node schema files. Triggers on linking/schema intent broadly.

2026-07-035

semantic-draft-writer

siddiqss/semantic-seo-suite

Write a full article draft from a semantic-SEO brief, following the micro-semantics writing rules and the brand's locked facts, then validate-and-repair it against the fabrication guard. Use whenever the user says "write the article", "draft from this brief", "turn this node into content", or asks to produce the actual copy for a topical-map node. Always runs scripts/validate_draft.py and repairs violations before returning. Triggers on drafting/writing intent for mapped content.

2026-07-035

semantic-site-auditor

siddiqss/semantic-seo-suite

Audit an existing site against its topical map — coverage gaps, keyword cannibalization, entity drift, orphan pages, and per-page micro-semantic issues. Use whenever the user asks to audit a site, find content gaps, check for cannibalization, asks "why aren't we ranking", wants to know what's missing from their niche coverage, or wants a pre-sales content audit of any domain. Produces a prioritised audit report with provenance on every finding. Triggers on audit/gap/cannibalization intent broadly.

2026-07-035

name

answer-engine-optimizer

description

answer-engine-optimizer

Read first: ../../framework/answer-engine-optimization.md (the method + the honesty rules), then ../../framework/macro-micro-semantics.md (the writing tactics it scores).

Preconditions

entity-profile.json + topical-map.json exist (run seo-brand-foundation / topical-map-builder first).
Drafts to score live in brands/<slug>/drafts/. With no drafts yet, the skill still produces the hardening spec and the live-answer probe.
Live-answer probing needs grounding.sources.web_search: true (T1). Without it, do the offline scoring only and say the probe was skipped — do not guess citations.

Workflow

Score citation-readiness (T0, offline). For each draft:
```
python ../../scripts/aeo_score.py --draft brands/<slug>/drafts/<slug>.md \
  --schema-dir brands/<slug>/data/schema --json
```
Run it after validate_draft.py is clean — AEO is advisory, fabrication is a gate. Collect score, grade, and the specific fixes (DEF / QA / TLDR / LIFT / BREV / SELF / SCHEMA). Scores are measured (mechanical), the recommended rewrites are asserted.
Probe live answer engines (T1, web_search). For the highest-value target queries (core-section, especially comparison/alternative nodes), query them answer-style and record, per query + engine + date: is the brand named? cited with a link? which competitor sources are quoted instead? This is a dated spot check (n=1 per probe), labelled measured — not a rank tracker. Never aggregate it into a visibility %.
Write the AEO report → brands/<slug>/audits/<date>-aeo.md:
- Readiness table — per node: AEO score, grade, top fixes (measured + asserted).
- Live citations — per probed query: brand cited? competitors cited? (measured, dated, with the query text; honest about the tiny sample).
- Hardening queue — nodes <70, ranked, with the concrete edits.
- If web_search is off: state the probe was skipped; emit only the readiness table.
Feed the loop.
- Nodes scoring <70 → mark needs-update in the map; push up calendar.md.
- Apply hardening to drafts via semantic-draft-writer; ensure JSON-LD via linking-and-schema. Re-score to confirm the lift.
- Queries where competitors are cited and the brand isn't → a hardening task on the owning node and a signal for off-page authority (link-opportunities).
- New questions found while probing → query-network additions via topical-map-builder.

Definition of done

Every existing draft scored; a dated AEO report with the three sections written.
Hardening queue fed back into map statuses + calendar.
No invented visibility number anywhere — citations are dated, per-query observations or they are absent. If web_search was off, the report says so.

Grounding ladder

T0: offline aeo_score.py readiness scoring + hardening spec. Fully useful alone.
T1 (web_search): + live answer-engine spot checks (measured, dated, per query).
T2: no paid dependency; SERP-feature data from DataForSEO (if on) can corroborate which queries trigger AI Overviews, labelled measured.