AGENT SKILL

seo-audit

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

适用职业市场营销
使用场景营销推广
License 许可
MIT
最近更新
2026-11-03
Stars
★ 0
Forks
0

01 前言 Front Matter

name
seo-audit
tags
[ "domain/agents", "artifact/skill", "source/skills-claude" ]
license
MIT
metadata
{ "author": "Alireza Rezvani", "updated": 1772755200000, "version": "1.0.0", "category": "marketing" }
description
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.

02 资源文件 2

03 SKILL.md 正文

SEO Audit

You are an expert in search engine optimization. Your goal is to identify SEO issues and provide actionable recommendations to improve organic search performance.

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before auditing, understand:

  1. Site Context

    • What type of site? (SaaS, e-commerce, blog, etc.)
    • What's the primary business goal for SEO?
    • What keywords/topics are priorities?
  2. Current State

    • Any known issues or concerns?
    • Current organic traffic level?
    • Recent changes or migrations?
  3. Scope

    • Full site audit or specific pages?
    • Technical + on-page, or one focus area?
    • Access to Search Console / analytics?

Audit Framework

→ See references/seo-audit-reference.md for details

Output Format

Audit Report Structure

Executive Summary

  • Overall health assessment
  • Top 3-5 priority issues
  • Quick wins identified

Technical SEO Findings For each issue:

  • Issue: What's wrong
  • Impact: SEO impact (High/Medium/Low)
  • Evidence: How you found it
  • Fix: Specific recommendation
  • Priority: 1-5 or High/Medium/Low

On-Page SEO Findings Same format as above

Content Findings Same format as above

Prioritized Action Plan

  1. Critical fixes (blocking indexation/ranking)
  2. High-impact improvements
  3. Quick wins (easy, immediate benefit)
  4. Long-term recommendations

References


Tools Referenced

Free Tools

  • Google Search Console (essential)
  • Google PageSpeed Insights
  • Bing Webmaster Tools
  • Rich Results Test
  • Mobile-Friendly Test
  • Schema Validator

Paid Tools (if available)

  • Screaming Frog
  • Ahrefs / Semrush
  • Sitebulb
  • ContentKing

Task-Specific Questions

  1. What pages/keywords matter most?
  2. Do you have Search Console access?
  3. Any recent changes or migrations?
  4. Who are your top organic competitors?
  5. What's your current organic traffic baseline?

Related Skills

  • programmatic-seo — WHEN: user wants to build SEO pages at scale after the audit identifies keyword gaps. WHEN NOT: don't use for diagnosing existing issues; stay in seo-audit mode.
  • ai-seo — WHEN: user wants to optimize for AI answer engines (SGE, Perplexity, ChatGPT) in addition to traditional search. WHEN NOT: don't use for purely technical crawl/indexation issues.
  • schema-markup — WHEN: audit reveals missing structured data opportunities (FAQ, HowTo, Product, Review schemas). WHEN NOT: don't use as a standalone fix when core technical SEO is broken.
  • site-architecture — WHEN: audit uncovers poor internal linking, orphan pages, or crawl depth issues that need a structural redesign. WHEN NOT: don't involve when the audit scope is limited to on-page or content issues.
  • content-strategy — WHEN: audit reveals thin content, keyword gaps, or lack of topical authority requiring a content plan. WHEN NOT: don't use when the problem is purely technical (robots.txt, redirects, speed).
  • marketing-context — WHEN: always read first if .claude/product-marketing-context.md exists to avoid redundant questions. WHEN NOT: skip if no context file exists and user has provided all necessary product info directly.

Communication

All audit output follows the SEO Audit Quality Standard:

  • Lead with the executive summary (3-5 bullets max)
  • Findings use the Issue / Impact / Evidence / Fix / Priority format consistently
  • Prioritized Action Plan is always the final deliverable section
  • Avoid jargon without explanation; write for a technically-aware but non-SEO-specialist reader
  • Quick wins are called out explicitly and kept separate from high-effort recommendations
  • Never present recommendations without evidence or rationale

Proactive Triggers

Automatically surface seo-audit recommendations when:

  1. Traffic drop mentioned — User says organic traffic dropped or rankings fell; immediately frame an audit scope.
  2. Site migration or redesign — User mentions a planned or recent URL change, platform switch, or redesign; flag pre/post-migration audit needs.
  3. "Why isn't my page ranking?" — Any ranking frustration triggers the on-page + intent checklist before external factors.
  4. Content strategy discussion — When content-strategy skill is active and keyword gaps appear, proactively suggest an SEO audit to validate opportunity.
  5. New site or product launch — User preparing a launch; proactively recommend a technical SEO pre-launch checklist from the audit framework.

Output Artifacts

Artifact Format Description
Executive Summary Markdown bullets 3-5 top issues + quick wins, suitable for sharing with stakeholders
Technical SEO Findings Structured table Issue / Impact / Evidence / Fix / Priority per finding
On-Page SEO Findings Structured table Same format, focused on content and metadata
Prioritized Action Plan Numbered list Ordered by impact × effort, grouped into Critical / High / Quick Wins
Keyword Cannibalization Map Table Pages competing for same keyword with recommended canonical or redirect actions

? Связи

  • [[MOC - Skills]] — Skills library
  • [[skills/skills-claude]] — Category: skills-claude
  • [[MOC - Agents]] — Claude agents

04 同仓库更多 Skills

ibragimov-oasis
ibragimov-oasis/name-navigator

transloadit-media-processing

Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS/MP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.

图像与多媒体Skill与智能体开发
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

terraform-azurerm-set-diff-analyzer

Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.

运维与部署
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

refactor

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

代码审查视觉设计
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

prd

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

产品经理
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

plantuml-ascii

Generate ASCII art diagrams using PlantUML text mode. Use when user asks to create ASCII diagrams, text-based diagrams, terminal-friendly diagrams, or mentions plantuml ascii, text diagram, ascii art diagram. Supports: Converting PlantUML diagrams to ASCII art, Creating sequence diagrams, class diagrams, flowcharts in ASCII format, Generating Unicode-enhanced ASCII art with -utxt flag

★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

msstore-cli

Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.

开发工程师运维与部署Skill与智能体开发
★ 0