Skill: geo-seo/seo-geo-audit (version 1.1.0)

--- name: seo-geo-audit-skill description: 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 readiness. metadata: author: GEO-SEO version: "1.1.0" homepage: https://github.com/GEO-SEO/seo-geo-audit primaryEnv: SERPAPI_API_KEY requires: env: - SERPAPI_API_KEY bins: - python3 --- # 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 ```text Run a full SEO and GEO audit for https://example.com ``` ```text Audit this homepage in boss mode: https://example.com ``` ```text 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 - crawlability - indexability - performance and rendering - security and trust headers - schema and metadata - mobile and accessibility risks 2. On-page SEO - title, meta description, headers - search intent alignment - content depth and structure - internal linking - media optimization 3. GEO and AI visibility - answer-first formatting - extractability and quotability - semantic clarity - AI crawler access signals - machine-readable brand and content signals 4. Trust, entity, and authority - author and editorial transparency - about, contact, and policy signals - organization identity consistency - entity disambiguation - third-party credibility and authority indicators 5. Off-site entity and brand mentions - LinkedIn company and leadership presence - Reddit discussion and recommendation visibility - YouTube channel and transcript-level visibility - Wikipedia and Wikidata entity presence - GitHub, Product Hunt, Crunchbase, news, podcasts, and industry-community mentions 6. Platform-specific AI readiness - ChatGPT and Bing index alignment - Perplexity citation friendliness - Google AI Overviews answer formatting - Gemini entity, schema, and Google ecosystem fit - Bing Copilot freshness, IndexNow, and LinkedIn/GitHub support signals ## Workflow 1. Define the scope. - single page - limited site crawl - domain-level strategic review 2. 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. 3. Separate evidence from judgment. Label each item as: - `Observed` - `Assessment` - `Not verified` 4. Review the site in layers. - technical layer - on-page/content layer - GEO layer - entity/authority layer - off-site mention layer - platform-specific readiness layer 5. Prioritize actions. - `P0`: blockers, trust failures, indexing failures, major performance issues - `P1`: meaningful ranking and citation improvements - `P2`: optimization and scale work 6. Present the result in the right audience mode. - `Boss mode` - `Operator mode` - `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`

path: README.md
content: [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
[![Skill Type](https://img.shields.io/badge/skill-SEO%20%2B%20GEO-blue)](SKILL.md)
[![Outputs](https://img.shields.io/badge/output-Boss%20%7C%20Operator%20%7C%20Specialist-orange)](references/output-template.md)
[![Language](https://img.shields.io/badge/language-EN%20%2F%20ZH-informational)](references/output-template-zh-boss.md)

# SEO GEO Audit

![SEO GEO Audit Cover](assets/cover.svg)

> Turn fragmented SEO checks into one executive-ready system for technical health, content quality, trust, off-site entity signals, and AI visibility.

**Positioning**

SEO GEO Audit is a unified audit framework for teams that need more than a technical SEO checklist.

It helps you diagnose whether a website is:

- technically sound enough to rank
- structurally clear enough to convert
- trustworthy enough to earn authority
- well-packaged enough to be cited by AI systems
- visible enough across external platforms to be recognized as a real entity
- aligned enough with different AI platforms to win beyond one generic GEO score

This project helps answer a harder and more useful question than a standard site audit:

> Is this website actually ready to win in both search engines and AI-driven discovery?

**Outcome**

Instead of handing leadership a pile of disconnected issues, this skill turns technical findings, content gaps, EEAT weaknesses, and GEO opportunities into one prioritized decision framework.

## Best For

- teams that need one audit spanning SEO, GEO, EEAT, entity, authority, and off-site visibility
- founders or operators who need a management-ready summary instead of raw findings
- agencies that want a repeatable audit structure across different clients
- SEO teams that want to connect technical debt, content quality, and AI visibility

## Start With These Prompts

```text
Run a full SEO and GEO audit for https://example.com
```

```text
Audit this homepage in boss mode: https://example.com
```

```text
Give me an operator-style SEO GEO audit with P0, P1, and P2 actions
```

## External Access And Minimum Credentials

This skill can run with direct page access only. Optional environments may add third-party search or crawl integrations for broader visibility checks.

Recommended minimum setup:

- no credentials required for direct page-level and site-level review
- `SERPAPI_API_KEY` only if the runtime also performs search-result enrichment

If no external integrations are configured, the audit should clearly separate observed evidence from unverified assumptions.

Access policy:

- search-result enrichment is optional, not required
- the audit should continue from observable site evidence when APIs are unavailable
- it should not imply access to private analytics, Search Console, or crawl datasets by default

**About Dageno.ai**

[Dageno.ai](https://dageno.ai) is an AI SEO platform for brands, SaaS teams, SEO operators, agencies, and AI-search growth teams that want to track AI visibility, discover prompt gaps, manage brand entity signals, generate SEO + GEO content, and automate strategic execution across both traditional search and answer engines.

## Cover

```mermaid
flowchart LR
    A["SEO GEO Audit"]:::root
    A --> B["Technical SEO"]:::node
    A --> C["On-Page SEO"]:::node
    A --> D["GEO Readiness"]:::node
    A --> E["Trust & EEAT"]:::node
    A --> F["Entity & Authority"]:::node
    A --> H["Off-site Mentions"]:::node
    A --> I["Platform Fit"]:::node
    A --> G["Unified Output"]:::node

    B --> B1["Crawlability"]:::leaf
    B --> B2["Performance"]:::leaf
    B --> B3["Security"]:::leaf
    B --> B4["Schema"]:::leaf

    C --> C1["Title & Meta"]:::leaf
    C --> C2["Intent Match"]:::leaf
    C --> C3["Internal Links"]:::leaf
    C --> C4["Media"]:::leaf

    D --> D1["Answer-First"]:::leaf
    D --> D2["Extractability"]:::leaf
    D --> D3["AI Signals"]:::leaf
    D --> D4["llms.txt"]:::leaf

    E --> E1["Author Signals"]:::leaf
    E --> E2["Editorial Clarity"]:::leaf

    F --> F1["Brand Identity"]:::leaf
    F --> F2["sameAs / Schema"]:::leaf

    H --> H1["LinkedIn"]:::leaf
    H --> H2["Reddit"]:::leaf
    H --> H3["YouTube"]:::leaf
    H --> H4["Wikipedia / Wikidata"]:::leaf

    I --> I1["ChatGPT"]:::leaf
    I --> I2["Perplexity"]:::leaf
    I --> I3["Gemini"]:::leaf
    I --> I4["Google AIO / Bing"]:::leaf

    G --> G1["Boss Mode"]:::leaf
    G --> G2["Operator Mode"]:::leaf
    G --> G3["Specialist Mode"]:::leaf

    classDef root fill:#f3f4f6,stroke:#94a3b8,color:#111827,stroke-width:2px;
    classDef node fill:#0f172a,stroke:#38bdf8,color:#f8fafc,stroke-width:1.5px;
    classDef leaf fill:#1e293b,stroke:#94a3b8,color:#f8fafc,stroke-width:1px;
```

## Why It Feels Different

Most SEO audits are good at finding defects.

Most GEO reviews are good at discussing positioning.

Most brand and EEAT reviews are good at surfacing trust gaps.

Very few workflows can do all three in one structure without collapsing into disconnected reports.

This skill is designed to unify:

- technical diagnosis
- on-page evaluation
- EEAT and trust review
- AI visibility assessment
- entity and authority analysis
- off-site entity and mention validation
- platform-specific AI search readiness
- one practical action roadmap

## What You Get

- one audit workflow
- one reporting structure
- one prioritization model
- one language for leadership and execution teams

Instead of producing separate checklists for developers, SEO teams, and founders, this skill turns them into a single decision system.

## Audit Configuration

This project has two layers of configuration.

### 1. Crawl and audit settings

Typical controls:

- target URL or domain
- single-page check vs multi-page crawl
- maximum pages to fetch
- category filtering
- faster run vs deeper performance run
- fresh crawl vs cached run

Typical execution modes:

- `single-page mode`
- `template audit mode`
- `site audit mode`
- `deep investigation mode`

Meaning of the main controls:

- page scope: one page vs a broader internal-link sample
- crawl cap: how many internal pages to inspect before stopping
- output mode: compact summary vs deeper diagnostic output
- performance depth: faster structural pass vs heavier rendering/performance pass

### 2. Report strategy settings

The reporting layer can also be configured:

- `Boss mode`
- `Operator mode`
- `Specialist mode`
- homepage audit vs site audit vs domain visibility audit
- whether to include EEAT, GEO, entity, and authority review

## How Deep It Crawls

This workflow is **page-capped**, not **fixed-depth**.

That means it does not use a strict rule like “crawl 2 levels deep” or “crawl 3 levels deep”.
Instead, it keeps discovering and following valid internal links until one of these happens:

- it reaches the configured page cap
- it runs out of valid crawlable pages

Typical crawl ranges:

- `m=1`: single-page diagnosis
- `m=20`: template-level diagnosis
- `m=50`: broader site audit
- `m=100`: deeper structural review

For the Dageno audit example, the run used a template-level crawl profile.

So the crawl was:

- multi-page
- capped at `20` pages
- optimized for a fast technical baseline
- not using a fixed recursion depth

## Recommended Presets

Use these presets as practical defaults:

| Preset | Best For | Suggested Command |
|---|---|---|
| `Fast check` | quick validation before sharing a site or page | single-page mode, fast structural pass |
| `Homepage audit` | executive review of the main commercial page | single-page mode, executive summary output |
| `Template audit` | checking homepage, product, blog, docs, and other key templates | multi-page mode, capped sample of key templates |
| `Full site audit` | broader structural review across a meaningful portion of the site | broader crawl cap with standard technical + GEO review |
| `Deep investigation` | deeper diagnosis when the site has widespread issues or many templates | high crawl cap with deeper rendering/performance analysis |

Suggested interpretation:

- use `Fast check` when speed matters more than coverage
- use `Homepage audit` when the goal is messaging, conversion, and first-impression quality
- use `Template audit` when you want the fastest meaningful site-level diagnosis
- use `Full site audit` when you are planning actual implementation work
- use `Deep investigation` when you expect template sprawl, hidden debt, or indexing complexity

## Who This Is For

- Shopify and DTC brands that want stronger AI-search visibility
- SaaS teams that need clearer comparison and recommendation positioning
- SEO and digital marketing operators who need repeatable optimization workflows
- agencies that manage SEO / GEO work across multiple clients

## Before vs After

### Traditional Audit Experience

- technical findings live in one tool
- content review lives in another framework
- GEO insights are mostly ad hoc
- trust and entity review are often missing
- leadership gets too much detail and not enough clarity

### With This Skill

- technical, content, GEO, and authority signals sit in one report
- findings are split into `Observed`, `Assessment`, and `Not verified`
- priorities are simplified into `P0`, `P1`, and `P2`
- the same audit can be delivered in boss, operator, or specialist mode

## Core Audit Layers

### 1. Technical SEO

- crawlability and indexability
- performance and rendering
- redirects, canonicals, and URL hygiene
- HTTPS and security headers
- schema and metadata quality
- mobile and accessibility risks

### 2. On-Page SEO

- title and meta quality
- heading structure
- keyword and intent alignment
- content structure and depth
- internal linking
- image and media optimization

### 3. GEO and AI Visibility

- answer-first formatting
- semantic extractability
- quotability and citation-friendliness
- AI crawler signals
- machine-readable content structure

### 4. Entity, Trust, and Authority

- author and editorial transparency
- organization identity consistency
- about, contact, and policy coverage
- entity disambiguation
- third-party credibility indicators

### 5. Off-site Mentions and Platform Validation

- LinkedIn company and leadership presence
- Reddit recommendation and discussion visibility
- YouTube channel and transcript presence
- Wikipedia / Wikidata coverage
- GitHub, Product Hunt, Crunchbase, press, podcasts, and industry communities
- platform-level fit for ChatGPT, Perplexity, Gemini, Google AI Overviews, and Bing Copilot

## Audit Map

```mermaid
flowchart TD
    A["Website / URL"] --> B["Technical SEO"]
    A --> C["On-Page SEO"]
    A --> D["GEO & AI Visibility"]
    A --> E["Entity / Trust / Authority"]

    B --> B1["Crawlability"]
    B --> B2["Performance"]
    B --> B3["Security"]
    B --> B4["Schema & Metadata"]

    C --> C1["Titles & Meta"]
    C --> C2["Headers & Structure"]
    C --> C3["Intent Alignment"]
    C --> C4["Internal Links"]

    D --> D1["Answer-First Format"]
    D --> D2["Extractability"]
    D --> D3["AI Signals"]

    E --> E1["EEAT"]
    E --> E2["Entity Clarity"]
    E --> E3["Authority Signals"]

    B1 --> F["Unified Report"]
    B2 --> F
    B3 --> F
    B4 --> F
    C1 --> F
    C2 --> F
    C3 --> F
    C4 --> F
    D1 --> F
    D2 --> F
    D3 --> F
    E1 --> F
    E2 --> F
    E3 --> F

    F --> G["P0 / P1 / P2 Roadmap"]
```

## Output Modes

### Boss Mode

Short, decision-ready summary with:

- current state
- business risks
- highest-impact opportunities
- clear next actions

### Operator Mode

Execution-focused report with:

- observed issues
- strategic assessments
- P0 / P1 / P2 roadmap
- validation gaps

### Specialist Mode

Full diagnostic report with:

- layered findings
- scoring logic
- assumptions
- data limitations

## Example Prompts

```text
Run a full SEO and GEO audit for https://example.com
```

```text
Audit this homepage in boss mode: https://example.com
```

```text
Give me an operator-style SEO GEO audit for https://example.com with P0, P1, and P2 actions
```

```text
Review this site for AI visibility, EEAT, and entity clarity: https://example.com
```

## Example Output

### Boss Mode Example

```text
One-line conclusion
The site has a strong SEO foundation, but homepage performance, security posture, and weak AI-ready trust signals are limiting growth efficiency.

Overall view
- Technical health: Medium
- Content and brand visibility: Medium
- AI / GEO readiness: Medium

Key issues
- Homepage is too heavy: slower rendering reduces ranking efficiency and conversion performance.
- Security headers are incomplete: trust and risk posture are weaker than they should be.
- Social metadata is missing: link sharing quality and CTR are being suppressed.
- Entity and trust signals are underdeveloped: the brand is harder for search engines and AI systems to confidently recognize and cite.

Priority
P0
- Reduce page weight, DOM size, and inline script/style payload.
- Add core security headers and enforce a stronger trust baseline.

P1
- Improve metadata, social cards, and mobile readability.
- Strengthen author, editorial, and organizational trust signals.

P2
- Expand to a broader site audit and connect external data sources for validation.
```

### Operator Mode Example

```text
Executive Summary
- Scope: Homepage audit
- Technical Health: 82-90 range with clear weaknesses in performance and security
- Strategic Visibility: Moderate
- Main conclusion: The site is indexable and structurally usable, but growth efficiency is being constrained by page weight, trust gaps, and incomplete AI-facing signals.

Technical SEO Findings
Observed
- Large HTML payload
- Heavy inline JavaScript and CSS
- Missing critical security headers
- Broken internal link detected

Assessment
- Technical debt is not catastrophic, but it is concentrated on high-visibility surfaces and will suppress both ranking efficiency and conversion performance.

On-Page and Content Findings
Observed
- Multiple H1 tags
- Weak social metadata coverage
- Mobile readability issues

Assessment
- The page communicates value, but the information hierarchy is not yet optimized for search clarity or fast comprehension.

GEO and AI Visibility Findings
Observed
- No llms.txt
- Limited machine-readable visibility signals

Assessment
- The site is not yet packaged as a strong AI-citable source, even if the product positioning is promising.

Entity and Authority Findings
Observed
- Limited public trust and identity reinforcement on-page

Assessment
- The brand signal exists, but it is not strong enough yet for confident entity recognition or authority transfer.

Priority Roadmap
P0
- Fix rendering weight and security baseline
- Remove structural blockers on primary pages

P1
- Strengthen metadata, trust elements, and AI-facing clarity

P2
- Extend the audit to templates, supporting pages, and off-page validation
```

## 中文老板报告示例

```text
一句话结论
网站基础 SEO 结构较强，但首页存在明显的性能、安全和品牌展示短板，会拖累自然流量放大、页面转化效率，以及在 AI 结果中的可信引用表现。

总体判断
- 技术健康度：中上
- 内容与品牌可见度：中
- AI / GEO 准备度：中

关键问题
- 首页过重：会影响页面加载、搜索表现和转化效率。
- 安全信号不完整：会削弱站点基础信任和安全治理完整性。
- 分享展示能力不足：会影响社媒、消息场景和搜索摘要中的点击率。
- 品牌与 AI 可引用信号偏弱：不利于被搜索引擎和 AI 系统稳定识别与引用。

优先级建议
P0 立即处理
- 优先压缩首页体积，减少 DOM、脚本和样式负担。
- 补齐关键安全头，建立基础信任底座。

P1 本月完成
- 补齐分享标签与移动端体验问题。
- 强化作者、品牌、组织和编辑责任等信号。

P2 后续优化
- 扩展到全站模板审计，并接入更多外部验证数据。

管理层建议
- 这不是单一 SEO 小修小补问题，而是技术基础、内容可信度和 AI 可见度需要同步升级。
- 建议先聚焦首页和核心落地页，优先拿到增长效率提升。
```

## Recommended Workflow

```mermaid
flowchart LR
    A["Choose Scope"] --> B["Run Baseline Audit"]
    B --> C["Review Technical Layer"]
    C --> D["Review Content Layer"]
    D --> E["Review GEO Layer"]
    E --> F["Review Entity & Authority"]
    F --> G["Merge Findings"]
    G --> H["Prioritize P0 / P1 / P2"]
    H --> I["Deliver Boss / Operator / Specialist Report"]
```

## Quick CTA

Use this project if you want to replace fragmented audit workflows with one structured deliverable that works across leadership, SEO, content, and growth teams.

Start with:

```text
Run a full SEO and GEO audit for https://your-site.com
```

Or for a management-facing version:

```text
请用老板版输出这个网站的 SEO + GEO 审计结果：https://your-site.com
```

## Repo Structure

```text
seo-geo-audit/
├── SKILL.md
├── agents/
│   └── openai.yaml
└── references/
    ├── output-template.md
    ├── output-template-zh-boss.md
    └── scoring-framework.md
```

## Included References

- `SKILL.md`: workflow and triggering logic
- `references/scoring-framework.md`: scoring and prioritization model
- `references/output-template.md`: operator and specialist report template
- `references/output-template-zh-boss.md`: Chinese management summary template

## Recommended Use Cases

Use this project when you need:

- a homepage diagnosis before a launch
- an executive SEO + GEO summary for leadership
- a reusable client audit structure
- a practical roadmap for technical, content, and brand visibility work

## License

MIT


path: agents/openai.yaml
content: display_name: SEO + GEO Audit
short_description: Unified audit for SEO, GEO, EEAT, entity, authority, off-site mentions, and platform-specific AI readiness.
default_prompt: Run a full SEO + GEO audit for this site and give me one prioritized report with P0, P1, and P2 actions.


path: assets/cover.svg
content: <svg width="1280" height="640" viewBox="0 0 1280 640" fill="none" xmlns="http://www.w3.org/2000/svg">
  <defs>
    <linearGradient id="bg" x1="44" y1="34" x2="1224" y2="606" gradientUnits="userSpaceOnUse">
      <stop stop-color="#F5F0E6"/>
      <stop offset="0.55" stop-color="#E8EEE8"/>
      <stop offset="1" stop-color="#D9E5F5"/>
    </linearGradient>
    <linearGradient id="panel" x1="830" y1="130" x2="1184" y2="468" gradientUnits="userSpaceOnUse">
      <stop stop-color="#0D2740"/>
      <stop offset="1" stop-color="#17465A"/>
    </linearGradient>
    <filter id="shadow" x="818" y="102" width="430" height="390" filterUnits="userSpaceOnUse" color-interpolation-filters="sRGB">
      <feFlood flood-opacity="0" result="BackgroundImageFix"/>
      <feColorMatrix in="SourceAlpha" type="matrix" values="0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 127 0" result="hardAlpha"/>
      <feOffset dx="12" dy="12"/>
      <feGaussianBlur stdDeviation="18"/>
      <feComposite in2="hardAlpha" operator="out"/>
      <feColorMatrix type="matrix" values="0 0 0 0 0.05 0 0 0 0 0.11 0 0 0 0 0.17 0 0 0 0.16 0"/>
      <feBlend mode="normal" in2="BackgroundImageFix" result="effect1_dropShadow_1_2"/>
      <feBlend mode="normal" in="SourceGraphic" in2="effect1_dropShadow_1_2" result="shape"/>
    </filter>
  </defs>

  <rect width="1280" height="640" rx="28" fill="url(#bg)"/>
  <circle cx="1110" cy="102" r="138" fill="#E9D9BC" fill-opacity="0.55"/>
  <circle cx="186" cy="578" r="194" fill="#C9D1C4" fill-opacity="0.65"/>
  <circle cx="1218" cy="552" r="166" fill="#C9D6EB" fill-opacity="0.72"/>

  <rect x="66" y="56" width="142" height="36" rx="18" fill="#0B1F33"/>
  <text x="88" y="79" fill="#F7F2E8" font-family="Arial, Helvetica, sans-serif" font-size="18" font-weight="700">SEO + GEO</text>

  <text x="66" y="158" fill="#0B1F33" font-family="Georgia, 'Times New Roman', serif" font-size="68" font-weight="700">
    <tspan x="66" dy="0">One audit system</tspan>
    <tspan x="66" dy="78">for search and AI</tspan>
    <tspan x="66" dy="78">visibility</tspan>
  </text>

  <text x="68" y="352" fill="#24435A" font-family="Arial, Helvetica, sans-serif" font-size="28" font-weight="400">
    <tspan x="68" dy="0">Technical SEO, EEAT, GEO readiness,</tspan>
    <tspan x="68" dy="42">and AI visibility in one report.</tspan>
  </text>

  <g filter="url(#shadow)">
    <rect x="850" y="136" width="350" height="320" rx="28" fill="url(#panel)"/>
  </g>

  <text x="884" y="180" fill="#F4F7F8" font-family="Arial, Helvetica, sans-serif" font-size="24" font-weight="700">Audit Coverage</text>

  <rect x="884" y="198" width="110" height="34" rx="12" fill="#F3B562"/>
  <text x="909" y="220" fill="#102A43" font-family="Arial, Helvetica, sans-serif" font-size="16" font-weight="700">Crawlers</text>

  <rect x="1006" y="198" width="90" height="34" rx="12" fill="#B8D8BA"/>
  <text x="1028" y="220" fill="#102A43" font-family="Arial, Helvetica, sans-serif" font-size="16" font-weight="700">EEAT</text>

  <rect x="1106" y="198" width="70" height="34" rx="12" fill="#A9C8D6"/>
  <text x="1121" y="220" fill="#102A43" font-family="Arial, Helvetica, sans-serif" font-size="16" font-weight="700">AIO</text>

  <rect x="884" y="250" width="292" height="56" rx="18" fill="#F4F7F8" fill-opacity="0.08" stroke="#F4F7F8" stroke-opacity="0.18"/>
  <text x="908" y="272" fill="#A9C8D6" font-family="Arial, Helvetica, sans-serif" font-size="14" font-weight="600">On-site checks</text>
  <text x="908" y="292" fill="#F4F7F8" font-family="Arial, Helvetica, sans-serif" font-size="18" font-weight="700">Schema  •  llms.txt  •  Meta  •  Security</text>

  <rect x="884" y="318" width="292" height="56" rx="18" fill="#F4F7F8" fill-opacity="0.08" stroke="#F4F7F8" stroke-opacity="0.18"/>
  <text x="908" y="340" fill="#A9C8D6" font-family="Arial, Helvetica, sans-serif" font-size="14" font-weight="600">Off-site validation</text>
  <text x="908" y="360" fill="#F4F7F8" font-family="Arial, Helvetica, sans-serif" font-size="18" font-weight="700">LinkedIn  •  Reddit  •  YouTube  •  Wiki</text>

  <rect x="884" y="392" width="292" height="12" rx="6" fill="#173042"/>
  <rect x="884" y="392" width="96" height="12" rx="6" fill="#F3B562"/>
  <rect x="990" y="392" width="72" height="12" rx="6" fill="#7CC6A6"/>
  <rect x="1072" y="392" width="104" height="12" rx="6" fill="#5A86B7"/>
  <text x="884" y="430" fill="#DCE6EA" font-family="Arial, Helvetica, sans-serif" font-size="14" font-weight="500">P0 baseline</text>
  <text x="988" y="430" fill="#DCE6EA" font-family="Arial, Helvetica, sans-serif" font-size="14" font-weight="500">P1 trust</text>
  <text x="1080" y="430" fill="#DCE6EA" font-family="Arial, Helvetica, sans-serif" font-size="14" font-weight="500">P2 platform fit</text>

  <text x="66" y="560" fill="#0B1F33" font-family="Arial, Helvetica, sans-serif" font-size="24" font-weight="700">From fragmented audits to one prioritized roadmap.</text>
</svg>


path: manifest.json
content: {
  "name": "seo-geo-audit",
  "version": "1.1.0",
  "display_name": "SEO + GEO Audit",
  "description": "Unified SEO and GEO audit workflow for technical health, content quality, trust, entity signals, off-site brand mentions, platform-specific AI readiness, and AI visibility. Supports homepage, site, and domain-level reviews.",
  "author": {
    "name": "GEO-SEO",
    "website": "https://github.com/GEO-SEO/seo-geo-audit"
  },
  "tags": [
    "seo",
    "geo",
    "audit",
    "eeat",
    "entity",
    "ai-search"
  ],
  "license": "MIT",
  "repository": {
    "type": "git",
    "url": "https://github.com/GEO-SEO/seo-geo-audit"
  },
  "integrations": {
    "search_enrichment": {
      "optional_env_vars": [
        "SERPAPI_API_KEY"
      ]
    }
  },
  "metadata": {
    "skill_type": "audit",
    "network_access": "optional",
    "minimum_permissions": "direct page access by default; third-party search enrichment is optional and should be explicitly configured",
    "data_access_policy": "Private analytics, Search Console, crawl logs, and proprietary datasets are never assumed. The audit can proceed from observable site evidence alone."
  }
}


path: references/output-template-zh-boss.md
content: # 中文老板版模板

用于管理层、创始人、负责人汇报。目标是让对方在 60 秒内明白：

- 网站整体健康度如何
- 当前最大风险是什么
- 对增长有什么影响
- 接下来先做什么

避免堆术语。不要把报告写成工程日志。

## 输出结构

### 一句话结论

用一句话回答当前状态：

- `基础健康`
- `有明显短板`
- `存在关键风险`

### 总体判断

控制在 3 行内：

- 技术健康度：`强 / 中 / 弱`
- 内容与品牌可见度：`强 / 中 / 弱`
- 站外实体信号：`强 / 中 / 弱`
- AI / GEO 准备度：`强 / 中 / 弱`

### 关键问题

只列 3 到 5 条，且每条必须带业务影响。

格式：

- `[问题]`：`会导致什么后果`

### 优先级建议

只分三层：

- `P0 立即处理`
- `P1 本月完成`
- `P2 后续优化`

每层最多 3 条。

### 管理层建议

给出 2 到 4 条管理动作。

### 可见性补充说明

如果适用，可额外用 2 行说明：

- 站外提及现状：`例如 LinkedIn / Reddit / YouTube / Wikipedia 等是否有有效存在`
- 平台差异：`例如更适合先打 ChatGPT / Perplexity，还是先补 Google AIO / Gemini`

## 语言规则

- 优先中文
- 少用英文缩写；必须出现时，在第一次出现后补中文解释
- 不写过细的实现步骤
- 不写长 checklist
- 对缺失数据只保留一句简短说明

推荐说明：

`本次结论基于页面公开可见信息和站点审计结果，不包含 Search Console、外链数据库和服务器日志。`

如果做过站外平台核查，可补：

`站外实体和社媒可见性仅基于公开可核查平台，不代表完整舆情或品牌声量数据库。`


path: references/output-template.md
content: # Output Template

Use this structure for operator and specialist reports.

## Executive Summary

- Scope:
- Technical Health:
- Strategic Visibility:
- Main conclusion:

## Technical SEO Findings

### Observed
- [factual issue]

### Assessment
- [interpretation]

## On-Page and Content Findings

### Observed
- [title, meta, headings, structure, links]

### Assessment
- [intent alignment, content depth, conversion clarity]

## GEO and AI Visibility Findings

### Observed
- [machine-readable and answer-formatting findings]

### Assessment
- [extractability, quotability, citation suitability]

## Entity and Authority Findings

### Observed
- [about, contact, schema, author, identity, trust]

### Assessment
- [entity ambiguity, weak authority signals, brand credibility gaps]

## Off-site Mentions and Entity Validation

### Observed
- [LinkedIn, Reddit, YouTube, Wikipedia/Wikidata, GitHub, Product Hunt, Crunchbase, news, podcasts]

### Assessment
- [where the brand is visible, where entity authority is weak, and which missing platforms matter most]

## Platform-Specific AI Readiness

### Observed
- [ChatGPT, Perplexity, Google AI Overviews, Gemini, Bing Copilot readiness notes]

### Assessment
- [which platforms are strongest, which are weakest, and why]

## Priority Roadmap

### P0
- [blocker]

### P1
- [important improvement]

### P2
- [optimization]

## Data Gaps and Validation Notes

- Not verified:
- Recommended external sources:


path: references/scoring-framework.md
content: # Scoring Framework

Use this framework to combine observable site findings with strategic visibility assessment.

## Presentation Modes

- `Boss mode`: use simple bands such as `Strong`, `Medium`, `Weak`
- `Operator mode`: use score ranges and priority tiers
- `Specialist mode`: include section-level scoring logic and validation notes

## Layer 1: Technical Health

Primary inputs:

- crawlability and indexability
- performance and rendering
- security and trust signals
- metadata and schema quality
- mobile and accessibility blockers

Suggested interpretation:

- `90-100`: strong technical baseline
- `75-89`: healthy but with meaningful weaknesses
- `60-74`: performance likely constrained
- `<60`: major blockers

## Layer 2: Strategic Visibility

Assess these seven areas using `Strong`, `Moderate`, `Weak`, or `Unknown`:

1. Content Quality
2. Trust and EEAT
3. GEO Readiness
4. Entity Clarity
5. Authority Signals
6. Off-site Brand Mentions
7. Platform-Specific AI Readiness

If the user explicitly wants a number, use directional conversion only:

- Strong = 85
- Moderate = 70
- Weak = 50
- Unknown = excluded

## Combined Interpretation

- Strong technical + weak strategic: the site is crawlable, but not differentiated, referenced, or citable enough
- Weak technical + strong strategic: the message is strong, but delivery is suppressing results
- Weak technical + weak strategic: fix the baseline first, then strengthen content and brand signals
- Strong technical + strong strategic: move toward scale, testing, and monitoring

For management summaries, translate this into plain language:

- growth is being held back by technical friction
- infrastructure is stable but trust, entity, and platform visibility signals are underdeveloped
- both technical delivery and market visibility need work

## Strategic Visibility Checkpoints

Use these checkpoints when scoring the seven strategic areas.

### 1. Content Quality

- intent match
- page depth and completeness
- structural clarity
- conversion clarity

### 2. Trust and EEAT

- authorship and editorial clarity
- first-party evidence
- policy and legal transparency
- source quality and freshness

### 3. GEO Readiness

- answer-first formatting
- quotable blocks
- machine-readable packaging
- AI crawler accessibility cues

### 4. Entity Clarity

- organization identity consistency
- same brand naming across pages
- brand disambiguation
- about/contact/schema alignment

### 5. Authority Signals

- third-party credibility indicators
- trust-bearing references
- external validation of expertise
- domain-level reputation indicators

### 6. Off-site Brand Mentions

- LinkedIn company and founder presence
- Reddit mention frequency and sentiment
- YouTube channel or third-party transcript mentions
- Wikipedia / Wikidata presence
- GitHub, Product Hunt, Crunchbase, news, podcasts, and industry-community visibility

### 7. Platform-Specific AI Readiness

- ChatGPT and Bing compatibility
- Perplexity discussion and citation fit
- Google AI Overviews snippet and structure fit
- Gemini entity and Google ecosystem fit
- Bing Copilot freshness, IndexNow, and Microsoft-adjacent signals

## Priority Rules

Rank issues in this order:

1. indexing and crawl failures
2. security and trust blockers
3. rendering and major performance issues
4. metadata, schema, and structural issues
5. EEAT, entity, and authority reinforcement
6. off-site mention reinforcement and entity validation
7. GEO formatting, platform fit, and citation optimization

## Missing Data Rules

Mark as `Not verified` if you do not have:

- Search Console
- backlink tool data
- server logs
- field performance data
- AI citation monitoring

Do not guess backlink strength, branded demand, or citation share from page HTML alone.
Do not infer social/community visibility unless the source platform was explicitly checked.


Security scan verdicts — ClawScan: clean | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)