跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
营销与销售

seo-ops

Structural checklist and checker script for SEO foundation engineering. Use when reviewing or accepting a site/page for SEO/GEO structural compliance (robots, sitemap, canonical, 301 canonicalization, JSON-LD, OG, hreflang, CWV, AI crawler access, rendering strategy), when running the machine checks to produce a report, or when judging whether a frontend change will affect indexing and citation. Also for answering "what exactly does this check require" and "why does it exist".

tigerless-labs · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add tigerless-labs/seo-ops --skill seo-ops

技能说明


name: seo-ops description: Structural checklist and checker script for SEO foundation engineering. Use when reviewing or accepting a site/page for SEO/GEO structural compliance (robots, sitemap, canonical, 301 canonicalization, JSON-LD, OG, hreflang, CWV, AI crawler access, rendering strategy), when running the machine checks to produce a report, or when judging whether a frontend change will affect indexing and citation. Also for answering "what exactly does this check require" and "why does it exist". compatibility: Requires Python 3.9+, requests, PyYAML, and network access to the target site

seo-ops · SEO foundation engineering

Review a site's templates and output against the C set (30 structural checks), or run the checker to produce an acceptance report.

How to work

When this skill triggers, introduce it in one sentence — "30 structural checks (the C set): can crawlers fetch, read, index, and cite this site" — then immediately ask one question (as selectable options if your environment has an option/question UI):

What should I check?

  1. A URL — live domain or local deployment (http://localhost:<port>), both fine; produces a report
  2. The code — review templates/pages in this repo against the checklist, no script

That one answer decides the path; don't ask anything else before starting — no config is needed, the checker runs with defaults on a bare --target. Never bring configuration up on your own; it only becomes relevant if the user asks for the extras (CrUX field data, IndexNow, multi-site roster — see "Configuration").

The user gavePathSection to follow
a domain / URL (live or localhost)run the checker, produce a report"Run the checker" → then "Read the report"
code, templates, a PR, page filesno script; review the machine-readable output surface against the C set item by item"Scope" sets the boundary; references/checklist/checklist.md lists the items — but judge each one by its canonical doc references/checklist/references/C<N>.md, not by the index row alone

Once intent is confirmed, do not keep asking for permission. Everything else: the user asks why a check exists / how to fix it → "After the report"; dependencies won't install → "Environment".

Both paths treat references/checklist/checklist.md as authoritative — never judge from memory; if unsure about an item, read references/checklist/references/C<N>.md. Cite items by ID (C12); IDs are permanent — never renumber or reorder.

After the report

The report itself is the conclusion — don't walk through it item by item unprompted. Each row carries a Docs column: the GitHub link to that check's canonical doc — that link is for the person reading the report (it opens wherever the report is sent). What you yourself read is the local copy: references/checklist/references/C<N>.md.

When the user asks about a check, read references/checklist/references/C<N>.md before answering (for C12, read references/checklist/references/C12.md): "why it's a problem" comes from ## Introduction, "how to fix it" from ## Implementation guidance. Never answer by inferring from the evidence — evidence only says which pages failed; it can't tell you why the check exists, what the correct fix is, or where the authoritative reference lives.

Environment

python3 -c "import requests, yaml" || pip install -r scripts/requirements.txt

On externally-managed-environment (PEP 668, common on Debian/Ubuntu), use the system packages apt install python3-requests python3-yaml or create a venv — do not add --break-system-packages; that gambles the system Python for a two-line dependency.

Scope

SEO foundation engineering = the machine-readable structure a site must have so that search engines and AI retrieval can fetch, read, index, and cite it.

What it checks: the machine-readable surface of the final HTTP/HTML output — regardless of who produced it (backend templates, frontend code, third-party scripts); if a crawler can see it, it's covered. The boundary is "machine-readable surface / human-perceivable surface", not frontend/backend.

What it doesn't check: styling, interaction, UX, code quality; content truthfulness and quality; ranking and traffic; process. All green ≠ fully compliant.

The human gate is a separate set: the R1-R8 prohibitions (buying links, cloaking, fake structured data, PII in prompts, etc.) live in redlines.md; the machine doesn't check them. Read them before touching content strategy, links, or structured data.

What's here

PathWhat it is
references/checklist/checklist.mdThe C set index: 30 checks, split into site-level / per indexed page / conditional
references/checklist/references/C<N>.mdEach C check's canonical doc: ## Introduction (why) + ## Implementation guidance (how to fix) + authoritative references
references/content/The T set: for tracing a red C back to "who owes the input"; outside this skill's duties
scripts/run.py · scripts/config.pyCheck logic / check parameters
references/ai-crawlers.yamlThe AI crawler UA roster for C1, read at runtime
references/{sites,config}.example.yaml · references/.env.exampleThree config templates, see "Configuration"

<N> maps one-to-one to the IDs in the checklist; C12's canonical doc is references/checklist/references/C12.md. Gaps in the numbering are normal (retired IDs are never recycled).

The skill directory is read-only — zero writes. Updates overwrite the whole package; anything written inside will be lost.

Run the checker

Confirm the target is an origin → run. No config file is required and none should be asked about — defaults cover everything; the optional file

阅读完整来源 ↗