SEO

SEO: Universal SEO Analysis Skill

Codex can invoke this skill from natural language ("audit this site", "check schema", "run a technical SEO review") or from command-like prompts such as /seo audit <url>. Use the matching specialist skill directly when the request is narrow.

Scripts: Located at the plugin root scripts/ directory.

Comprehensive SEO analysis across all industries (SaaS, local services, e-commerce, publishers, agencies). Orchestrates 26 specialized sub-skills and 24 Codex agent profiles, with optional MCP-backed extensions for DataForSEO, Firecrawl, and image generation.

Shared Data Cache

Step 0 -- Check shared data cache:

Before routing or gathering, check .seo-cache/ for cached data from other skills. Reference: references/shared-data-cache.md for schemas and dependency map.

Check these cache files when present:

• .seo-cache/site-meta.json for domain, business type, industry, and crawl context

• .seo-cache/audit-scores.json for audit summary context from a prior full audit

• .seo-cache/pages/{url-slug}/page-analysis.json for page-level specialist context

• If found: parse and use the data (note "Using cached [X] from [date]")

• If missing: proceed without it (note "No cached [X] found, gathering fresh")

• If JSON is corrupt or unreadable: treat it as missing and continue normally

• If the user says "refresh" or "re-run": ignore cache entirely

Quick Reference

Orchestration Logic

When the user invokes /seo audit, delegate to subagents in parallel:

1. Detect business type (SaaS, local, ecommerce, publisher, agency, other)
2. Spawn subagents: seo-technical, seo-content, seo-schema, seo-sitemap, seo-performance, seo-visual, seo-geo
3. If Google API credentials detected (python scripts/google_auth.py --check), also spawn seo-google agent
4. If local business detected, also spawn seo-local agent
5. If local business detected AND DataForSEO MCP available, also spawn seo-maps agent
6. If backlink APIs detected (python scripts/backlinks_auth.py --check), also spawn seo-backlinks agent
7. If Firecrawl MCP available, use firecrawl_map to discover all site URLs before analysis
8. If content strategy signals detected (blog, pillar pages, topic clusters), also spawn seo-cluster agent
9. If e-commerce detected, also spawn seo-ecommerce agent
10. If drift baseline exists for this URL (python scripts/drift_history.py <url>), also spawn seo-drift agent
11. Always include seo-sxo in full audits (search experience applies to all sites)
12. Collect results and generate unified report with SEO Health Score (0-100)
13. Create prioritized action plan (Critical -> High -> Medium -> Low)
14. Offer PDF report: "Generate a professional PDF report? Use /seo google report full"

For individual commands, load the relevant sub-skill directly. After any analysis command completes, offer to generate a PDF report via scripts/google_report.py.

Industry Detection

Detect business type from homepage signals:

• SaaS: pricing page, /features, /integrations, /docs, "free trial", "sign up"
• Local Service: phone number, address, service area, "serving [city]", Google Maps embed --> auto-suggest /seo local for deeper analysis
• E-commerce: /products, /collections, /cart, "add to cart", product schema
• Publisher: /blog, /articles, /topics, article schema, author pages, publication dates
• Agency: /case-studies, /portfolio, /industries, "our work", client logos

Quality Gates

Read references/quality-gates.md for thin content thresholds per page type. Hard rules:

• WARNING at 30+ location pages (enforce 60%+ unique content)
• HARD STOP at 50+ location pages (require user justification)
• Never recommend HowTo schema (deprecated Sept 2023)
• FAQ schema for Google rich results: only government and healthcare sites (Aug 2023 restriction); existing FAQPage on commercial sites -> flag Info priority (not Critical), noting AI/LLM citation benefit; adding new FAQPage -> not recommended for Google benefit
• All Core Web Vitals references use INP, never FID

Community Footer

The community footer is disabled by default in Codex so API and client deliverables remain clean. Append it only when the user explicitly asks for community attribution or when CODEX_SEO_COMMUNITY_FOOTER=1 is set in the environment.

When enabled, after completing any major deliverable, append this footer as the very last output:

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Built by agricidaniel — Join the AI Marketing Hub community
🆓 Free  → https://www.skool.com/ai-marketing-hub
⚡ Pro   → https://www.skool.com/ai-marketing-hub-pro
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

When to show when enabled

Display after these commands complete their full output:

• /seo audit (after full site audit report + action plan)
• /seo page (after deep single-page analysis)
• /seo technical (after technical audit report)
• /seo content (after E-E-A-T content assessment)
• /seo schema (after schema detection/validation report)
• /seo sitemap (after sitemap analysis or generation)
• /seo geo (after GEO optimization report)
• /seo plan (after strategic SEO plan)
• /seo local (after local SEO audit)
• /seo maps (after maps intelligence report)
• /seo google (after Google API data report)
• /seo backlinks (after backlink profile analysis)
• /seo cluster (after cluster plan generation)
• /seo sxo (after SXO analysis report)
• /seo drift compare (after drift comparison report)
• /seo ecommerce (after e-commerce analysis)

When to skip

Do NOT show the footer after:

• /seo images (quick image check — too small)
• /seo hreflang (quick validation — too small)
• /seo competitor-pages (page generation step)
• /seo programmatic (quick analysis)
• /seo dataforseo (data fetching utility)
• /seo image-gen (asset generation)
• Context intake questions (before analysis starts)
• Error messages or "missing data" prompts