Bing Page Snapshot
Operated by Microsoft
Quick Facts
- User-Agent:
- BingPreview
- Category:
- Search Engines
- Operator:
- Microsoft
- Safety:
- Safe
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- www.bing.com
Confirmed by the operator
Microsoft names BingPreview on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.
What is Bing Page Snapshot?
Bing Page Snapshot is an AI search-index crawler operated by Microsoft. It collects and indexes web content so it can be surfaced as citations or answers inside Microsoft's AI search experience. Allowing Bing Page Snapshot can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Bing Page Snapshot is an AI search-index crawler operated by Microsoft. It collects and indexes web content so it can be surfaced as citations or answers inside Microsoft's AI search experience. Allowing Bing Page Snapshot can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Bing Page Snapshot uses the user-agent token BingPreview. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
What happens if you block Bing Page Snapshot?
How to block Bing Page Snapshot with robots.txt
<code>User-agent: BingPreview</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Bing Page Snapshot safe to allow?
What does Bing Page Snapshot do?
Understanding Bing Page Snapshot's purpose helps you decide whether to allow or block it.
- Indexes web pages for AI-powered search answers
- Surfaces your content as citations inside AI search results
- Builds a knowledge index used to answer user questions
- Allowing it can increase visibility in AI search
- Respects robots.txt directives
Bing Page Snapshot in context
Bing Page Snapshot is a search engine crawler operated by Microsoft. In plain terms, it builds a search or answer index. Our database files it under search engines and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 62 of the 63 search engines in our database share this tier.
Its safety rating is safe and its blocking impact is critical. So Bing Page Snapshot is both well behaved and costly to lose: the strongest case for allowing it. How we rate safety and impact.
How site owners treat Bing Page Snapshot
Our robots.txt study of the Tranco top 10,000 did not track BingPreview as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.
Does it follow robots.txt?
Bing Page Snapshot's operator does not clearly document how it treats robots.txt. Write the Bing Page Snapshot rule anyway, then confirm in your logs that its requests stop.
Microsoft crawlers and close alternatives
Bing Page Snapshot is one of 6 Microsoft crawlers in our database. A User-agent: BingPreview group controls Bing Page Snapshot only; the other Microsoft tokens below need their own lines.
BingPreview: this crawler (Tier 3)AdIdxBot: Bing Ads Crawler, checks pages for an SEO, uptime or analytics service (Tier 3)AzureAI-SearchBot: Azure AI Search, builds a search or answer index (Tier 2)bingbot: Bing Search, builds a search or answer index (Tier 3)BingVideoPreview: Bing Video Preview, builds a search or answer index (Tier 3)MicrosoftPreview: Microsoft Preview, fetches a page to build a link preview when someone shares it (Tier 3)
To give Bing Page Snapshot the same answer as its siblings, stack User-agent: BingPreview with their lines above one set of rules; to treat Bing Page Snapshot differently, give it its own group.
Other search engines that do the same job (builds a search or answer index) include Amzn-SearchBot from Amazon, Applebot from Apple, baidu from Baidu, Baiduspider from Baidu, Baiduspider-favo from Baidu, Baiduspider-image from Baidu. Deciding about Bing Page Snapshot is usually a decision about the whole group, so check how your file treats these too.
We first recorded BingPreview on September 22, 2026. Microsoft documents it on bing.com, and we recheck that page before each release.
Which rule Bing Page Snapshot actually follows
Bing Page Snapshot reads exactly one group in robots.txt, the most specific one that names BingPreview, and never combines rules across groups. This short file shows the trap:
User-agent: *
Disallow: /private/
User-agent: BingPreview
Disallow: /drafts/
- Find the group. Bing Page Snapshot looks for a group naming
BingPreview. One exists, so it ignoresUser-agent: *completely. - Apply only that group. It is refused
/drafts/and nothing else. - The surprise.
/private/is open to Bing Page Snapshot, because that rule lives in the*group it no longer reads. To keep it out of both, repeatDisallow: /private/inside its own group.
Test yourself: does a rule under User-agent: * apply to Bing Page Snapshot if the file also has a User-agent: BingPreview group?
No. Once a group names it, Bing Page Snapshot reads only that group. Put every rule you want it to follow inside its own group.
Test yourself: will blocking Bing Page Snapshot remove your pages from AI answers?
Often, yes. Bing Page Snapshot is a search engine crawler, so pages it cannot fetch can drop out of the answers or results it supports.
Test yourself: is User-agent: bingpreview the same as User-agent: BingPreview?
Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.
Should you allow Bing Page Snapshot? Decide by situation
| If you are... | Recommended setting |
|---|---|
| You publish content and want AI answers to cite it | Allow it. It is how this search engine finds your pages. |
| You license content and want to stop AI training | Blocking it does not stop training, because Bing Page Snapshot is a search engine crawler. Block the operator's training crawler instead. |
| You run an online shop | Allow it unless it is overloading your servers. |
| Your server is under load from bots | Rate-limit before blocking. It is rated safe in our database. |
Check Bing Page Snapshot on your own site
- Open
/robots.txton your domain and search forBingPreview. If it is not named, it followsUser-agent: *. - List the
Disallowlines in the group Bing Page Snapshot follows and test your key URLs against them; the longest match wins, andAllowwins a tie. - Look beyond the file. A firewall or bot manager can refuse Bing Page Snapshot even when robots.txt allows it, and that never shows in the file.
- Run our AI crawler checker to see how Bing Page Snapshot and every other crawler we track are treated in one pass, including firewall refusals.
Common mistakes with Bing Page Snapshot
The errors we see most often with Bing Page Snapshot in the files and firewalls we test:
- Blocking Bing Page Snapshot to save bandwidth and then wondering why pages drop out of that search engine. Use crawl-rate settings or caching first.
- Writing a
User-agent: BingPreviewgroup to add one rule for Bing Page Snapshot and accidentally dropping every rule it used to follow underUser-agent: *. - Disallowing CSS and JavaScript folders, which can stop Bing Page Snapshot rendering your pages properly.
All three hide inside a file that looks correct, so check Bing Page Snapshot from outside after every change.
Spotting Bing Page Snapshot in your logs
robots.txt says what Bing Page Snapshot may do; your access logs show what it actually did.
Count requests
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "BingPreview" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -c
And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "BingPreview" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20
Check the requests are genuine
Anyone can send the Bing Page Snapshot user-agent, so confirm the source before acting on a match:
BingPreview: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Bing Page Snapshot request with caution.
Frequently Asked Questions
What is the official user-agent string for Bing Page Snapshot?
BingPreview. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Bing Page Snapshot by performing a reverse-DNS lookup on the source IP.Is Bing Page Snapshot safe?
Will blocking Bing Page Snapshot hurt my SEO?
How do I block Bing Page Snapshot in robots.txt?
/robots.txt file:User-agent: BingPreview Disallow: /
This instructs Bing Page Snapshot not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Bing Page Snapshot respect robots.txt?
/robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.How do I verify if Bing Page Snapshot is crawling my site?
BingPreview (case-insensitive: grep -i "BingPreview" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).