What does this skill do, and when should you use it?
This is the Claude SEO repository's dedicated Bing Webmaster Tools and IndexNow extension, focused on non-Google indexing surfaces. It supports URL submission for Bing, Yandex, Seznam, and Naver, while connecting Bing index visibility with Microsoft Copilot citation eligibility. It also queries and compares Bing link data. It fits teams that need to encourage fresh-page discovery or investigate Bing-specific links, but it is not a Google indexing workflow.
The skill calls Python scripts for Bing Webmaster Tools to retrieve link data for a URL and compare two URLs. Its IndexNow script submits one URL, submits a batch from a file, or verifies the IndexNow setup. It reads BING_WEBMASTER_API_KEY from ~/.claude/settings.json, plus optional INDEXNOW_KEY and INDEXNOW_KEY_LOCATION configuration, and produces the corresponding query, comparison, submission, or verification result.
- An SEO lead has published fresh pages and wants to prompt discovery by Bing, Yandex, Seznam, or Naver.
- A content team wants to improve the chance that new pages enter the Bing index and become eligible for Microsoft Copilot citations.
- An SEO consultant needs to compare Bing link data for two URLs.
- A researcher needs Bing link data that is not surfaced by Google's API.
How do you install this skill?
- Before submit or submit-batch, show the target URLs, request scope, and external submission impact, and require user confirmation.
- Add credential-storage and redaction guidance, actionable failure messages, retry behavior, and partial-failure handling for batch submission.
- Provide version-pinned target scripts, key-path tests, representative outputs, and mainland-China network availability guidance.
- Shell / CLI
- Network access
- Local filesystem
Python 3Bing Webmaster Tools API keyOptional IndexNow host key
From the Claude SEO repository, run extensions/bing-webmaster/install.sh; on Windows, run extensions/bing-webmaster/install.ps1. Configure BING_WEBMASTER_API_KEY in the environment section of ~/.claude/settings.json. For IndexNow, optionally configure INDEXNOW_KEY and publish the host key at the URL declared by INDEXNOW_KEY_LOCATION. The source does not document the install script's internal steps.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/extensions/bing-webmaster/skills/seo-bing" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
In Claude Code, run /seo bing links <url> for Bing link data; /seo bing compare <urlA> <urlB> to compare URLs; /seo bing submit <url> for one URL; /seo bing submit-batch <file> for a batch; and /seo bing verify-indexnow for verification only. The underlying scripts are python3 scripts/bing_webmaster.py and python3 scripts/indexnow_submit.py.
What are this skill's strengths and limitations?
- Covers IndexNow submission scenarios for Bing, Yandex, Seznam, and Naver.
- Provides Bing Webmaster Tools link queries and URL comparison.
- Connects Bing indexing visibility with Microsoft Copilot citation eligibility.
- Supports single-URL submission, batch submission, and configuration verification.
- Requires a Bing Webmaster Tools API key; IndexNow also requires host-key configuration.
- It explicitly targets non-Google indexing and does not replace Google's sitemap-driven workflow.
- The source provides no independent test count, detailed error behavior, or standalone output sample for this skill.
- It relies on Claude Code's `/seo bing` command routing and therefore needs adaptation for other clients.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Bing Visibility & IndexNow this page | 48 · Use with care | ★ 19k | 23d ago | MIT |
| Backlink Profile Analyzer | 47 · Use with care | ★ 19k | 23d ago | MIT |
| GEO Technical SEO Audit Skill (geo-technical) | 54 · Use with care | ★ 11k | 22d ago | MIT |
| Technical SEO Auditor | 49 · Use with care | ★ 19k | 23d ago | MIT |
| Competitor SEO & GEO Analyst | 51 · Use with care | ★ 3k | 13d ago | Apache-2.0 |
Unlike seo-google indexing, this skill targets Bing, Yandex, Seznam, and Naver through IndexNow; seo-google indexing handles Google's sitemap-driven model. Unlike seo-backlinks, which provides multi-source backlink confidence weighting across Bing, Moz, and Common Crawl, this skill focuses on Bing Webmaster Tools link data.
How did FollowSkills review this skill?
The file explicitly requires BING_WEBMASTER_API_KEY and places configuration in ~/.claude/settings.json env, but it does not explain credential handling, data flows, permission boundaries, or third-party processing. It also does not require confirmation before IndexNow submission, and batch submission has no rollback or cancellation guidance, so points are deducted. No red-line risk is evident.
The routing table clearly maps links, compare, submit, submit-batch, and verify-indexnow to scripts. However, the target scripts, dependency availability, abnormal-input behavior, failure feedback, and key-path tests are not shown in the selected file, and static review cannot verify execution, so the score remains below the static ceiling.
Use cases, command entry points, and boundaries with the Google indexing and backlinks skills are stated. Inputs, output contracts, non-fit ranges, and semantic trigger conditions remain brief, while reachability of Bing/Yandex/Seznam/Naver and Copilot services from mainland-China networks is not addressed, so points are deducted.
The file provides a name, version 2.2.0, compatibility requirements, prerequisites, routing, and cross-skill delegation. Repository context supplies MIT licensing, version information, and a security policy. The selected skill itself lacks examples, FAQs, limitations, changelog details, maintenance ownership, and an update path, preventing a near-full score.
The skill directly covers Bing link data, competitor comparison, IndexNow submission, and verification, with a clear core value proposition. The selected file provides no representative output, success criteria, retry behavior, or result examples, so static evidence cannot establish complete, directly usable results; the score follows the static cap conservatively.
The file mentions a 2024-2025 Gary Illyes claim but provides no verifiable citation. Repository CI and test evidence mainly cover other security and audit paths and do not establish the Bing/IndexNow key paths, so only limited verifiability is awarded.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →