Bing Webmaster report

See what changed in Bing and what deserves attention without fetching the site. Read provider coverage first, then verify important findings against current page or crawl evidence.

Install and run the report

Install the CLI once, then run seo start to connect your site and Google data. After setup you can run this report yourself or ask your agent to run it.

Runafter install

Install the SEO CLI globally.

npm i -g seo

Run setup after installation.

seo start

Run review bing search and crawl evidence through the report catalog.

seo reports run bing-webmaster-overview --params '{"site":"https://example.com/"}' --json

What you get from this report

Find bounded Bing traffic trends, crawl changes, and query and page opportunities without crawling page bodies.

Best for: You want processed Bing search and crawl insights beside your other site evidence.
Needs: Verified Bing Webmaster site
You get: Prioritized findings with observed evidence, cautious interpretation, and a verification step.
Use next: Review SEO performance

What you need before you run it

This report uses bing Webmaster daily traffic and crawl statistics plus weekly top query and page lists.

Verified Bing Webmaster site

Defines the exact site and provider account evidence to request.

Local Bing credential

Authorizes the request without including the secret in report output.

What the monitor checks

The monitor compares limited snapshots over time. It keeps failed, deferred and unchecked pages separate so missing evidence does not look like a recovery.

Requests traffic, crawl, query, and page statistics in parallel with strict response, time, and row limits.

Validates and orders provider rows, preserves invalid and capped counts, and keeps failed sections separate.

Compares matched traffic periods and crawl snapshots without hiding missing dates.

Compares movements only for query and page entries observed in every weekly top list in both periods and keeps incomplete coverage visible.

Check what ran before trusting the status

Start with the selected pages, dates and quota use. A page that was not checked has an unknown status, even when the rest of the run looks healthy.

Read first	Why it matters
Result	Prioritized findings with observed evidence, cautious interpretation, and a verification step.
More detail	Traffic trends, crawl changes, and bounded query and page opportunities with explicit provider coverage.
Read it with	Read provider status and coverage before findings. Verify important traffic or crawl changes against the exact dates and live site.

What the result cannot prove

Bing evidence describes Bing only. Its inIndex statistic is not independent URL level proof of indexing. A query or page missing from a weekly top list is unknown, not zero. Partial, capped, invalid, or unavailable evidence cannot support an all clear.

Read provider status and coverage before findings. Verify important traffic or crawl changes against the exact dates and live site. Run a site crawl when current page evidence is needed.

Use a different report for these jobs

You need URL level indexing proof or a complete view across every search engine.

You need Google search performance evidence for the same site.

Run the search performance overview. It uses Search Console evidence and keeps its provider scope separate from Bing.

SEO performance report

You need to inspect current pages and technical findings rather than provider statistics.

Run a bounded site crawl. It fetches current page evidence and groups repeated technical findings.

Sitemap health check and technical site crawl

Use the report with an agent or in code

The command above is enough for most work. These options let an agent, script or application run the same report with explicit input and structured output.

Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the report with the validated parameters.

Check the current input before the agent or script runs the report.

seo reports describe bing-webmaster-overview --json

Once the input is valid, run the report through the report catalog.

seo reports run bing-webmaster-overview --params '{"site":"https://example.com/"}' --json

An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the report.

Ask the MCP server for the current report input.

{
  "id": "bing-webmaster-overview"
}

Run the report after the agent has checked and filled the input.

{
  "id": "bing-webmaster-overview",
  "params": {
    "site": "https://example.com/"
  }
}

Install the package in a Node 22 project when your application needs to run the report directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server.

Add the SEO package to your project.

npm install seo

Run the report from your TypeScript application.

import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'bing-webmaster-overview',
  {
  "site": "https://example.com/"
},
)

console.log(result)

What to do next

Start with the highest-priority finding, then check its exact dates and source coverage. Run a current site crawl or page audit before changing anything because provider statistics cannot explain the cause on their own.

01Check the same date range in Bing Webmaster Tools.
02Run a site crawl when current page evidence is needed.

See where clicks and impressions changed, which pages or queries account for the movement, and what to inspect next.