seo-orchestrator

Name: seo-orchestrator
Author: Hainrixz

68installs2forks

How to install seo-orchestrator?

hainrixz/claude-seo-ai/seo-orchestrator

$npx -y skills add Hainrixz/claude-seo-ai --skill seo-orchestrator

Installs into the current project.

Summary

Orchestrates a full SEO + AI-search audit — detects the site vertical, builds a shared PageSnapshot, dispatches read-only specialist subagents in parallel, merges their findings, computes the two scores, and renders the report. Invoked by the audit command (the /claude-seo-ai:a

Files · 1

View on GitHub

SKILL.md

1	# seo-orchestrator (Layer 2)
2
3	Coordinates the whole audit. Three phases: detect → dispatch → synthesize.
4
5	## 1. Detect
6	1. Resolve the target (URL or local path).
7	2. Run seo-crawl-render to build the shared `PageSnapshot` (raw HTML, rendered DOM when available, response headers, status chain, plus site artifacts: `robots.txt`, sitemap set, `llms.txt`). Record the data tier reached (0/1/2).
8	3. Run seo-vertical-detect to classify the target. Read `references/routing.md` to get the always-on + conditional module set and the subagent dispatch table.
9
10	## 2. Dispatch (parallel)
11	Spawn the read-only specialists in parallel (one message, multiple Task calls) so their verbose intermediate output stays isolated. Pass each the PageSnapshot location/contents, the detected vertical, and its assigned modules:
12	- technical-auditor → M1, M2 (+M3), M4, M7, M7b (mobile), M7c (headings), M8, M9, M10, M15, M17
13	- ai-search-geo-specialist → M6, M11, M12, M14, M21
14	- content-eeat-analyst → M13, M16
15	- schema-generator → M5 (and M18/M19 schema when those verticals are active)
16
17	Each subagent returns an array of findings conforming to `schema/finding.schema.json`. Subagents are read-only (no Write/Edit tool) — the audit can never mutate files.
18
19	## 3. Synthesize
20	1. Merge all findings; dedupe by `id` (keep the most severe status).
21	2. Run seo-score over the merged findings to get the two scores with category breakdowns and severity gating.
22	3. Render the report (see `references/scoring-model.md` for bands/interpretations):
23	- Header: Search SEO band/score + AI Visibility band/score, each with a one-line interpretation.
24	- Per-category table for each score (value, weight, active?).
25	- Data confidence: tier reached + count of `needs_api` findings.
26	- Prioritized actions: top findings sorted by `severity × magnitude ÷ effort`, each showing status, evidence, recommendation, fixability (auto/proposed/advisory), and `expected_impact` (axis + confidence + magnitude).
27	- Footer: how to run `/claude-seo-ai:fix`.
28
29	## Notes
30	- Keep this skill's own output tight — the value is the merged report, not narration.
31	- If the target is a multi-page crawl, analyze the homepage + one instance of each detected template first, then sample additional pages; log what was sampled (never silently cap coverage).
32	- Degrade gracefully: if a render/PSI/GSC tier is unavailable, proceed at the lower tier and mark affected findings `needs_api`.

People who liked this also viewed

6 picks

Type

seo-orchestrator

68installs2forks

View on GitHub

How to install seo-orchestrator?

hainrixz/claude-seo-ai/seo-orchestrator

$npx -y skills add Hainrixz/claude-seo-ai --skill seo-orchestrator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# seo-orchestrator (Layer 2)
2
3	Coordinates the whole audit. Three phases: detect → dispatch → synthesize.
4
5	## 1. Detect
6	1. Resolve the target (URL or local path).
7	2. Run seo-crawl-render to build the shared `PageSnapshot` (raw HTML, rendered DOM when available, response headers, status chain, plus site artifacts: `robots.txt`, sitemap set, `llms.txt`). Record the data tier reached (0/1/2).
8	3. Run seo-vertical-detect to classify the target. Read `references/routing.md` to get the always-on + conditional module set and the subagent dispatch table.
9
10	## 2. Dispatch (parallel)
11	Spawn the read-only specialists in parallel (one message, multiple Task calls) so their verbose intermediate output stays isolated. Pass each the PageSnapshot location/contents, the detected vertical, and its assigned modules:
12	- technical-auditor → M1, M2 (+M3), M4, M7, M7b (mobile), M7c (headings), M8, M9, M10, M15, M17
13	- ai-search-geo-specialist → M6, M11, M12, M14, M21
14	- content-eeat-analyst → M13, M16
15	- schema-generator → M5 (and M18/M19 schema when those verticals are active)
16
17	Each subagent returns an array of findings conforming to `schema/finding.schema.json`. Subagents are read-only (no Write/Edit tool) — the audit can never mutate files.
18
19	## 3. Synthesize
20	1. Merge all findings; dedupe by `id` (keep the most severe status).
21	2. Run seo-score over the merged findings to get the two scores with category breakdowns and severity gating.
22	3. Render the report (see `references/scoring-model.md` for bands/interpretations):
23	- Header: Search SEO band/score + AI Visibility band/score, each with a one-line interpretation.
24	- Per-category table for each score (value, weight, active?).
25	- Data confidence: tier reached + count of `needs_api` findings.
26	- Prioritized actions: top findings sorted by `severity × magnitude ÷ effort`, each showing status, evidence, recommendation, fixability (auto/proposed/advisory), and `expected_impact` (axis + confidence + magnitude).
27	- Footer: how to run `/claude-seo-ai:fix`.
28
29	## Notes
30	- Keep this skill's own output tight — the value is the merged report, not narration.
31	- If the target is a multi-page crawl, analyze the homepage + one instance of each detected template first, then sample additional pages; log what was sampled (never silently cap coverage).
32	- Degrade gracefully: if a render/PSI/GSC tier is unavailable, proceed at the lower tier and mark affected findings `needs_api`.

People who liked this also viewed

6 picks

Type