菜单
SEO Audit workflow skill. Use this skill when the user needs to diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance while preserving upstream workflow intent, copied support files, and provenance.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/diegosouzapw/awesome-omni-skills --skill seo-audit-v4命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Daily Gift workflow skill. Use this skill when the user needs Relationship-aware daily gift engine with five-stage creative pipeline — editorial judgment, synthesis, concept generation, visual strategy, and rendering in H5, image, or video and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Daily Gift workflow skill. Use this skill when the user needs Relationship-aware daily gift engine with five-stage creative pipeline — editorial judgment, synthesis, concept generation, visual strategy, and rendering in H5, image, or video and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
High-Agency Frontend Skill workflow skill. Use this skill when the user needs building high-agency frontend interfaces with strict design taste, calibrated color, responsive layout, and motion rules and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
基于 SOC 职业分类
| name | seo-audit-v4 |
| slug | seo-audit-v4 |
| description | SEO Audit workflow skill. Use this skill when the user needs to diagnose and audit SEO issues affecting crawlability, indexation, rankings, and organic performance while preserving upstream workflow intent, copied support files, and provenance. |
| version | 0.0.1 |
| category | business |
| tags | ["seo-audit-v4","seo-audit","technical-seo","indexation","crawlability","search-console","canonicalization","javascript-seo","structured-data","core-web-vitals","omni-enhanced"] |
| complexity | advanced |
| risk | caution |
| tools | ["codex-cli","claude-code","cursor","gemini-cli","opencode"] |
| source | omni-team |
| author | Omni Skills Team |
| license | unknown |
| date_added | 2026-04-27 |
| date_updated | 2026-05-12 |
| source_type | omni-curated |
| maintainer | Omni Skills Team |
| family_id | seo-audit-v4 |
| family_name | SEO Audit |
| variant_id | omni |
| variant_label | Omni Curated |
| is_default_variant | true |
| derived_from | skills/seo-audit-v4 |
| upstream_skill | skills/seo-audit-v4 |
| upstream_author | sickn33 |
| upstream_source | community |
| upstream_pr | 271 |
| upstream_head_repo | diegosouzapw/awesome-omni-skills |
| upstream_head_sha | 93ab394af5645f7127d5003ee02c9566ae5353cd |
| curation_surface | skills_omni |
| enhanced_origin | omni-skills-private |
| source_repo | diegosouzapw/awesome-omni-skills |
| replaces | ["seo-audit-v4"] |
This skill preserves the intent of the upstream SEO audit workflow while making it more reliable to execute as a disciplined diagnostic review.
Use it when the goal is to identify, explain, and prioritize SEO issues affecting crawlability, indexation, rendering, canonicalization, structured data, content quality, and organic performance. Outputs should be evidence-led, scoped, and decision-oriented.
This is an audit skill, not an implementation skill.
Use this skill when the user asks for any of the following:
Do not use this skill as the primary workflow when:
Before starting, confirm the operating boundary. Ask for missing inputs first.
If core access is missing, continue only with an explicit limitation statement such as:
"This is a constrained SEO audit based on public evidence and supplied artifacts only. Findings may miss issues that require Search Console, logs, or authenticated crawling data."
Return findings in a structure that supports action and review:
A useful finding is specific enough that another operator can verify it without guessing.
Confirm scope and access
Collect baseline evidence
Audit crawl and index controls
Audit rendering and page quality signals
Audit search appearance and structured signals
Assess internal linking and architecture
Prioritize findings
Produce the audit report
At minimum, review these issue families:
Use a simple and defensible severity scale:
Severity should reflect business impact plus scope, not just technical purity.
Issue: Product pages excluded because canonical points to category URLs
Severity: High
Affected scope: ~3,200 product detail pages
Evidence:
- Sample product URLs return 200 and are internally linked
- HTML canonical points to parent category URL
- Search Console coverage for sampled pages shows alternate page with proper canonical tag
Likely cause: Template-level canonical logic inherited category canonical setting
SEO impact: Product pages are unlikely to be indexed as independent landing pages
Confidence: High
Recommended next validation step: Confirm the canonical tag rule across templates and sample recrawl after correction
Issue: Google may be penalizing the site
Severity: Critical
Evidence: Traffic went down
Why weak: No direct evidence, no technical mechanism, no separation between correlation and cause
For a fuller worked example, open examples/review-example.md.
Do start with scope, access, and known business events before reviewing symptoms.
Do use representative URL samples across templates instead of relying on one page.
Do distinguish public-web evidence from Search Console-only evidence.
Do state limitations when access gaps reduce confidence.
Do tie every major finding to proof, affected scope, and next validation step.
Do identify whether an issue is page-level, template-level, or architecture-level.
Do prioritize blockers before metadata refinements.
Do not promise ranking lifts, recovery timelines, or penalty explanations without direct evidence.
Do not mark every issue High; calibrate by impact and breadth.
Do not confuse canonical preference with indexation guarantee.
Do not treat all Core Web Vitals or performance issues as primary SEO blockers if crawl/index signals are healthy.
Do not recommend broad robots blocking or noindex changes without clearly stating the risk.
Do not claim JavaScript SEO failure unless raw/render evidence shows missing or altered critical signals.
Symptoms: Many important URLs are absent from search results, but pages load normally in the browser.
Solution: Check indexation evidence first: noindex directives, canonicals, redirects, duplicate clusters, sitemap inclusion, and Search Console page indexing states. A page being reachable is not the same as being indexable.
Symptoms: Search Console shows "Crawled - currently not indexed" on many pages.
Solution: Avoid a single-cause explanation. Review duplication, thin template content, weak internal linking, soft-404 characteristics, and canonical ambiguity. Treat this as a diagnostic state, not a verdict.
Symptoms: Important content exists after user interaction but not reliably in initial HTML.
Solution: Compare raw versus rendered output for content, links, canonicals, metadata, and structured data. If critical elements depend on delayed JS execution, classify it as a rendering risk and scope the affected templates.
Symptoms: Sitemaps exist, but discovery and indexing remain poor.
Solution: Check whether sitemap URLs are canonical, indexable, return valid status codes, and align with internal linking. Sitemaps support discovery; they do not override poor canonical or quality signals.
Symptoms: Structured data is present but rich result eligibility is inconsistent.
Solution: Validate syntax, required properties, policy fit, and consistency with visible content. Separate markup validity from search feature eligibility.
Symptoms: Organic traffic dropped after a migration or redesign.
Solution: Compare pre/post behavior for redirects, canonicals, status codes, internal links, robots rules, sitemap coverage, and rendering changes. Prioritize migration regressions before broader content theories.
references/review-criteria.md — open this during the audit to classify issue families, evidence standards, severity logic, and validation paths consistently.examples/review-example.md — open this when you need a concrete example of a scoped, evidence-based SEO audit write-up.No related local skills were supplied in the source context.