The Short Answer
If your site still shows as indexed in Bing Webmaster Tools, reports no errors, and has dropped to zero impressions from one day to the next, resubmitting sitemaps and URLs will not bring it back. What restored the one site we have been through this with was a short support ticket asking for a human review of the domain, with the exact date of the drop, a plain statement that the dashboard shows nothing wrong, and the phrase indexed but not served. The site was serving again two days after the ticket went in.
The one sentence version
When Bing stops serving a site it still has indexed, the fix is a person at Microsoft, and the way to reach one is a 500 character message that gives them the date, the symptom and nothing to argue with.
What Indexed but Not Served Looks Like
The pattern is distinctive once you have seen it, and confusing the first time, because every tool that normally warns you about a problem stays quiet. The pages are there. Bing can crawl them. They simply stop being shown to anyone.
| Signal | What you see | Why it is confusing |
|---|---|---|
| Search performance in Webmaster Tools | Impressions fall to zero or close to it on a single day and stay there | No manual action, no crawl error and no warning appears alongside it |
| URL inspection | Pages report as indexed and eligible | The tool says the page is fine while nobody sees it |
| A brand search on Bing | Your own name returns other sites, or your site far down the page | The pages exist in the index, so a site search may still list them |
| AI Performance report | Copilot citations stop on the same day as the impressions | Citations can go from hundreds a day to none with no message |
| Google Search Console | Nothing changes | It is a Bing problem, so every Google tool reports normal |
The combination is the diagnosis. A single one of those signals has many possible causes. All of them together, starting on the same day, is the signature of a site that Bing still knows about and has stopped serving.
Rule Out the Lookalikes First
Support staff work from the same data you do, and a ticket that turns out to be an ordinary technical fault wastes a review and your credibility for the next one. Spend twenty minutes ruling out the common causes before you file anything.
| Possible cause | How to check it | What rules it out |
|---|---|---|
| A robots.txt rule blocking bingbot | Fetch robots.txt from outside and read every rule that applies to bingbot or to all agents | Bing is allowed and pages report as crawled recently |
| A noindex tag or header added by a deploy | View the source and the response headers of a few key pages | No noindex anywhere on pages that dropped |
| A manual action or policy issue | Check the messages and any security or policy sections in Webmaster Tools | No message and no listed issue |
| A site move or canonical change | Check that canonicals point at the live address and redirects resolve in one hop | Canonicals are self referencing and unchanged |
| An ordinary ranking decline | Look at the shape of the impressions line | A decline slopes over weeks; a suppression drops to zero on one day |
If anything on that list is broken, fix it and wait a week before concluding anything. If all of it is clean and the line still fell off a cliff on one date, you are looking at the pattern this guide is about. It is worth running the same checks from our technical SEO checklist too, because a clean bill of health is part of what you will tell support.
What Happened to One of Our Sites
A free tool we run dropped to zero Bing impressions on the 15th of May 2026. Its Copilot citations stopped the same day. Webmaster Tools reported no errors, no penalties and normal indexing. We also know of another site that fell the same way around the 17th of May, which made it look less like something we had done and more like something that had happened to a group of small sites at once.
For two months we did everything the documentation suggests. We resubmitted the sitemap, pinged every page through IndexNow, submitted key URLs by hand and improved the content and structured data. None of it moved the line even slightly. Around the 17th of July we filed a support ticket asking for a human review of the domain. On the 19th of July the site was serving again.
| Measure | During the suppression | After the review |
|---|---|---|
| Bing impressions | Zero from 15 May | About 1,200 a day |
| Copilot citations | Zero from 15 May | 344 a day |
| Compared with the previous best | Not applicable | About 2.4 times the old peak |
We never received an explanation of why the site had been suppressed, and we do not want to pretend to know. What we can say is what the pattern looked like, what did not work, and the exact kind of message that did.
Why Resubmitting Does Not Help
Sitemaps, IndexNow and URL submission all do the same basic job. They tell Bing that a page exists or has changed so it can be crawled and indexed. In a suppression, that part of the system is already working, which is why the pages keep showing as indexed. The decision that changed is whether to show them, and none of the submission tools touch that decision.
That is also why the problem is so easy to misread. Every tool you would use to investigate reports success. IndexNow accepts the ping, the sitemap is processed, URL inspection says the page is fine. It is entirely possible to spend weeks confirming that everything works while the one thing that matters stays switched off.
Keep IndexNow running anyway
Stopping your submissions will not fix anything, and it will slow your recovery once serving returns. Keep your IndexNow setup automated through the whole episode, so every page is current in Bing the day a reviewer turns the site back on.
Where to File the Ticket
Open Bing Webmaster Tools for the affected site
Sign in with the account that owns the verified site, so support can see the data you are describing.
Open help from the question mark icon at the top right
Look for the option to contact support or raise a support ticket.
Choose the problem type about your site not appearing in search
Pick the category closest to missing from Bing results rather than a crawling or technical category.
Write the description within the character limit
The description box accepts 500 characters. Everything below is about using them well.
Submit and watch your email
Support replies by email, and that thread is where the longer explanation goes.
Menus change, so if the exact labels differ, look for any route to a human support request from inside Webmaster Tools. The public forums are useful for learning whether other sites are seeing the same thing, but they are not a substitute for a ticket on your own domain.
The 500 Character Message
The description box stops at 500 characters, which rules out the long formal letter most people want to write. That turns out to be an advantage. The shortest version of your case is also the most persuasive one, and it contains exactly three things.
The exact date of the drop
Not recently or a few weeks ago. The date from your own impressions graph, so the reviewer can find it in theirs within seconds.
That the dashboard shows nothing wrong
Say that pages are indexed and crawlable with no errors. It tells support you have ruled out the ordinary causes.
The phrase indexed but not served
It names the symptom in the terms support uses and separates your case from a crawling problem.
Close by asking for a human review of the domain. Everything else is optional. This is the shape of the message that worked for us, with the specifics removed:
A message you can adapt, under 500 characters
My site [your domain] dropped to zero impressions in Bing search on [exact date] and has stayed at zero since. Copilot citations stopped the same day. Webmaster Tools shows no problems: my pages are indexed and crawlable with no errors, so the site looks indexed but not served. It is a real [one line on what the site does]. Please can a human review the domain and restore serving, or tell me what needs to change. Thank you.
Two details in that message do more work than they appear to. Mentioning Copilot citations stopping on the same day shows the drop is across the board, not one query. And asking them to either restore serving or tell you what needs to change reads as a request for a review rather than a demand for a result, which is the honest position when you do not know the cause.
What Not to Write
Overstating the numbers
If the dashboard shows 30 impressions, do not write zero. Support is looking at the same graph, and one wrong number makes everything else in the message suspect.
Blame or outrage
An angry ticket is still read by a person, and it gives them nothing to act on. Facts and a request fit the limit. Outrage does not.
A list of everything you tried
Save it for the reply thread. In the first message it pushes out the three facts that matter.
Claims you cannot support
Do not say the site was penalised, attacked or targeted unless you know. Describe what you see, not what you suspect.
After You Submit
When support replies, the email thread has no length limit, and that is the place for the fuller picture: when the drop began, what you checked and ruled out, what you resubmitted and when, what the site is and who uses it, and anything you changed recently. Keep the same tone as the first message. Specific, calm, and candid about what you do not know.
One line is worth including in that reply if it is true for you: that you would rather understand the real reason than simply get the site restored. It signals that you are trying to fix whatever caused it, which is the attitude a reviewer wants to see from a site they are about to put back into results.
| When | What to check |
|---|---|
| Every morning | Bing impressions for the previous day in Webmaster Tools |
| Every morning | Copilot citations in the AI Performance report |
| Once a week | A brand search and a search for your best page title on Bing |
| When serving returns | That your most important pages are the ones coming back first |
Once You Are Back
Recovery can be sudden and larger than the old baseline, as it was for us, and that is not a reason to relax. The point of the episode is that a site can vanish from Bing with no warning at all, so the monitoring that would have caught it on day one is worth putting in place now.
Alert on a zero day
Pull daily Bing impressions and alert if a normally active site records zero. Two months is a long time to notice by accident.
Watch citations as well as clicks
The AI Performance report shows Copilot citations falling at the same moment as impressions, which makes it a second tripwire.
Keep submissions automated
IndexNow on every publish means pages are current the moment serving returns.
Keep a runbook of this exact process
The symptoms look like a technical fault and send teams searching the codebase. A written note saves weeks next time.
Why Bing Matters More Than It Used To
For years a site could treat Bing as a rounding error. That stopped being true when AI assistants started searching the web. Copilot grounds its answers in Bing search, so a site Bing is not serving cannot be cited by Copilot at all, which is exactly what the AI Performance report showed us. Bing is also the primary documented third party index behind ChatGPT search, which is why Bing indexation is one of the first things to check when a site is missing from ChatGPT.
So a Bing suppression is no longer a small loss of search traffic. It can remove a site from several assistants at once while every Google tool reports that all is well. For the fuller picture of what Copilot rewards once you are serving again, see our guide to getting cited by Microsoft Copilot.
The Bottom Line
Indexed but not served is a decision, not a bug, and submission tools cannot reverse a decision. Rule out the ordinary causes, then ask a person to look, in a message short enough to fit the form and precise enough to be checked in seconds: the date, the clean dashboard, the phrase indexed but not served, and a request for a human review. It took two months of the wrong fixes and two days of the right one for us to learn that. The monitoring that tells you on day one is the part worth building before you need it, alongside the rest of your AI visibility tracking.