serp-rank-verification
Use when checking whether a site, page, product, publication, or competitor appears in search results, or when reporting organic search positions, indexing, snippets, SERP blocks, captcha blockers, regions, locales, or rank-readback evidence.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- serp-rank-verification
- description
- Use when checking whether a site, page, product, publication, or competitor appears in search results, or when reporting organic search positions, indexing, snippets, SERP blocks, captcha blockers, regions, locales, or rank-readback evidence.
02 资源文件 1
- 参考文档agents/openai.yaml297 B
03 SKILL.md 正文
SERP Rank Verification
Use this skill for search-result presence, indexing, and organic position checks.
Required Readback
A rank claim must record:
- search engine and host;
- query exactly as searched;
- region, locale, language, device or viewport when relevant;
- date and time;
- result type counted;
- target URL or domain matched;
- whether ads, shopping, maps, snippets, AI blocks, or promo modules were excluded.
Organic position means an organic result only. Ads, shopping blocks, maps, promo widgets, sitelinks, and other modules are not organic rank positions unless the user asked for that module separately.
Blocker States
Captcha, robot checks, tunnel failures, partial browser navigation, blocked screenshots, missing region control, and failed search access are blocker or partial states. They do not prove absence from search results.
If only indexing is proven, say indexing is proven. Do not turn indexing into ranking, traffic, lead, or revenue proof.
Evidence Table
Use a compact table for repeat checks:
query engine region locale checked_at result_type position target_url match_type excluded_modules blocker proof_artifact
When access is blocked, keep position empty and fill blocker with the concrete failure.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.