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.
Install the SEO CLI globally.
npm i -g seoRun setup after installation.
seo startRun review bing search and crawl evidence through the report catalog.
seo reports run bing-webmaster-overview --params '{"site":"https://example.com/"}' --jsonWhat you get from this report
Find meaningful Bing traffic trends, crawl changes, and query and page opportunities with explicit provider coverage, limits, and clear verification steps.
- Best for
- You want processed Bing search and crawl insights beside your other site evidence.
- Needs
- Verified Bing Webmaster site
- You get
- Find meaningful Bing traffic trends, crawl changes, and query and page opportunities with explicit provider coverage, limits, and clear verification steps.
- Use next
- Review SEO performance
Every report follows the same rules for missing data and outside estimates.See how report data works.
What you need before you run it
The report uses the information below. Optional sources are only used when you ask for them.
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.
Use a different report for these jobs
These jobs need a different report or a manual review.
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.
You need to inspect current pages and technical findings rather than provider statistics.
Run a limited site crawl. It fetches current page evidence and groups repeated technical findings.
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.
CLI
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 --jsonOnce the input is valid, run the report through the report catalog.
seo reports run bing-webmaster-overview --params '{"site":"https://example.com/"}' --jsonMCP
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/"
}
}TypeScript
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 seoRun 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 what each source returned. 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.
Related reports
See what changed in Search Console and which pages, queries, countries or devices explain the movement before choosing what to investigate next.
Check sitemap URL status, redirects and access first. Run the full technical SEO crawl only when you need page content, links, metadata and affected URLs.
Find broken URLs and weak redirects that still have Search Console value, then decide which pages to restore, redirect or leave alone using search evidence.
Sources used by this report
These primary sources define the provider data or search controls used by the result.