SkillHub

seo-geo-audit

v1.1.0

Run a unified SEO and GEO audit for a website, page, or domain. Use when the user asks for a full SEO audit, GEO audit, AI visibility review, EEAT review, entity audit, authority audit, or wants one prioritized report that combines technical findings, content quality, trust signals, and AI citation...

Sourced from ClawHub, Authored by Tim

Installation

Please help me install the skill `seo-geo-audit` from SkillHub official store. npx skills add GEO-SEO/seo-geo-audit

SEO GEO Audit Skill

Use this skill to produce one audit that covers both search performance and AI visibility, including on-site readiness, off-site entity signals, and platform-specific AI search fit.

Overview

Use this skill when you need one audit that combines technical SEO, content quality, trust, entity clarity, off-site brand visibility, and platform-specific AI readiness into a single prioritized output.

Best For

  • brands and SaaS teams that need one shared audit across SEO and GEO
  • founders or operators who want a management-ready summary, not a pile of raw issues
  • agencies that need a repeatable audit structure across multiple clients
  • SEO teams that want to connect technical debt, content quality, off-site authority, and AI visibility in one workflow

Start With

Run a full SEO and GEO audit for https://example.com
Audit this homepage in boss mode: https://example.com
Give me an operator-style SEO GEO audit with P0, P1, and P2 actions

External Access And Minimum Credentials

This audit can run with direct page access only, but some environments may also use optional search or crawl integrations.

  • SERPAPI_API_KEY: optional for broader search visibility checks or search-result enrichment
  • python3: optional helper tooling in environments that pair this skill with local audit scripts

If no external API is configured:

  • continue with direct page and site observations
  • state clearly what was observed versus what was not verified
  • do not imply access to search-console, private crawl logs, or third-party datasets unless the user provided them

Access Policy

This audit can run without private integrations.

  • search-result enrichment is optional, not required
  • local helper tooling is optional, not required
  • do not claim access to Search Console, analytics, server logs, private crawlers, or proprietary datasets unless the user explicitly provides them
  • when data is missing, mark it as Not verified and continue from observable evidence

This skill is designed for three common use cases:

  • Homepage audit: quick diagnosis for a single URL
  • Site audit: broader review across key templates and pages
  • Domain visibility audit: strategic review including entity and authority signals

What This Skill Covers

  1. Technical SEO
  2. crawlability
  3. indexability
  4. performance and rendering
  5. security and trust headers
  6. schema and metadata
  7. mobile and accessibility risks

  8. On-page SEO

  9. title, meta description, headers
  10. search intent alignment
  11. content depth and structure
  12. internal linking
  13. media optimization

  14. GEO and AI visibility

  15. answer-first formatting
  16. extractability and quotability
  17. semantic clarity
  18. AI crawler access signals
  19. machine-readable brand and content signals

  20. Trust, entity, and authority

  21. author and editorial transparency
  22. about, contact, and policy signals
  23. organization identity consistency
  24. entity disambiguation
  25. third-party credibility and authority indicators

  26. Off-site entity and brand mentions

  27. LinkedIn company and leadership presence
  28. Reddit discussion and recommendation visibility
  29. YouTube channel and transcript-level visibility
  30. Wikipedia and Wikidata entity presence
  31. GitHub, Product Hunt, Crunchbase, news, podcasts, and industry-community mentions

  32. Platform-specific AI readiness

  33. ChatGPT and Bing index alignment
  34. Perplexity citation friendliness
  35. Google AI Overviews answer formatting
  36. Gemini entity, schema, and Google ecosystem fit
  37. Bing Copilot freshness, IndexNow, and LinkedIn/GitHub support signals

Workflow

  1. Define the scope.
  2. single page
  3. limited site crawl
  4. domain-level strategic review

  5. Start with the observable baseline. Collect factual findings from live pages, crawl data, page source, rendered output, and any available audit tooling.

Recommended crawl presets: - single page: one-page diagnostic mode - fast site pass: capped multi-page sample for template-level review - broader site audit: larger sample for structural review - deeper review: larger crawl cap with heavier performance/rendering analysis

Important: this workflow is page-capped rather than fixed-depth. It follows valid internal links until the configured page cap is reached.

  1. Separate evidence from judgment. Label each item as:
  2. Observed
  3. Assessment
  4. Not verified

  5. Review the site in layers.

  6. technical layer
  7. on-page/content layer
  8. GEO layer
  9. entity/authority layer
  10. off-site mention layer
  11. platform-specific readiness layer

  12. Prioritize actions.

  13. P0: blockers, trust failures, indexing failures, major performance issues
  14. P1: meaningful ranking and citation improvements
  15. P2: optimization and scale work

  16. Present the result in the right audience mode.

  17. Boss mode
  18. Operator mode
  19. Specialist mode

Output Rules

  • If the user writes in Chinese, answer in Chinese unless asked otherwise.
  • Always begin with a short executive summary.
  • Keep technical facts and strategic recommendations distinct.
  • Do not invent data for backlinks, Search Console, server logs, or AI citation share.
  • Mark unavailable inputs as Not verified.

Audience Modes

Boss mode

Use when the user asks for 老板版, executive summary, or management briefing.

  • short
  • business impact first
  • minimal jargon
  • no long issue dumps

Read references/output-template-zh-boss.md before writing.

Operator mode

Use when the user wants a practical roadmap.

  • balanced detail
  • clear priorities
  • implementation-oriented language

Read references/output-template.md before writing.

Specialist mode

Use when the user wants deep analysis.

  • include assumptions
  • include validation gaps
  • include section-level scoring logic

Read references/scoring-framework.md before writing.

Minimum Deliverable

Every audit should include:

  • scope
  • overall technical view
  • content and GEO view
  • entity and authority view
  • off-site mention and entity validation view
  • platform-specific readiness view
  • top priorities
  • missing data and validation notes

References

  • references/scoring-framework.md
  • references/output-template.md
  • references/output-template-zh-boss.md