How Bing Handles HTTP Status Codes on Pages

Last updated: October 20, 2026

Bing uses HTTP status codes to decide whether a page should stay in its crawl queue, be dropped, or be revisited later. If the server returns the right code, Bing gets a clean signal; if it returns the wrong one, Bing has to guess, and that guess can slow crawling or keep dead URLs hanging around longer than they should.

What Bing reads from HTTP status codes on a page

Bing treats the HTTP response as the first signal about a URL’s state, though site owners should confirm the exact behavior with Microsoft guidance or a technical SEO professional. A 200 OK says the page is available and can be crawled normally. A 301 Moved Permanently generally indicates the content has moved to a new URL, so Bing can pass users and crawling attention there. A 404 Not Found indicates the URL does not exist right now. A 410 Gone indicates it has been removed on purpose. A 503 Service Unavailable indicates the server is temporarily unable to serve the page and Bing should try again later.

That sounds simple, but the difference matters. A 200 on a deleted page tells Bing the URL still exists, so the crawler will keep checking it as if it might have content. A 404 or 410 gives the opposite signal: the content is no longer there, and the URL should age out of the crawl schedule. A 503 sits in the middle. It is not a permanent removal signal; it is a short-term failure state.

The practical question is not “does Bing understand the code?” It does. The question is whether your server returns the code that matches the page’s real condition. That is where many site issues start.

Microsoft’s Bing Webmaster Guidelines cover crawlable pages and correct status delivery, and the HTTP/1.1 semantics are defined in RFC 9110 from the IETF. Those two references are the standard frame for the rules here.

How should a live page respond with 200 OK?

A live page should return HTTP 200 OK and the actual HTML content in the same response. That is the cleanest signal Bing can get.

For normal pages, the response should be immediate and consistent. If a product page, article page, or category page is available, Bing should not have to follow a redirect chain or infer that the page exists from another route. A 200 tells the crawler the URL is valid enough to revisit on a normal schedule.

Use this as the baseline checklist:

1. Request the URL directly in a browser or HTTP client.
2. Confirm the response status is 200, not 3xx or 4xx.
3. Check that the body contains the intended content, not an error template or placeholder.
4. Make sure the page is not returning 200 for every broken URL on the site.
5. Re-test after deployments that change routing, caching, or edge rules.

The fifth step matters because many accidental status problems come from infrastructure, not from the page template itself. A reverse proxy can rewrite responses. A CDN can cache an error page for 5 minutes or longer. A custom application route can serve a pretty “not found” message while still sending 200, which is the exact signal mismatch you do not want.

This is where Bing’s interpretation becomes predictable: a true 200 keeps the page in the active crawl set. It does not guarantee ranking, and it does not solve content quality problems. It only tells Bing the URL is live and reachable.

A page that should exist but returns anything other than 200 is a separate technical problem, not a content problem.

How does Bing handle 404 Not Found?

Bing treats HTTP 404 Not Found as a signal that the URL is missing, so the page is eventually removed from normal crawl attention.

A 404 is the standard response for a URL that no longer exists and is not expected to come back. That is the right response for many deleted blog posts, retired documentation pages, and obsolete landing pages that have no replacement. It tells Bing the absence is real, not temporary.

The trade-off is simple: 404 is a blunt but useful signal. It says, “This URL does not have content now.” Bing can then reduce how often it checks the URL. It may still revisit occasionally, especially if the URL has backlinks or a long history, but the crawler should not keep treating it like a live page.

Do not use 404 when the page is down for a short outage. That turns a temporary problem into a permanent signal. If the page is expected back, 503 is the better fit.

A common mistake is leaving old URLs to resolve with a custom page that still returns 200. That costs crawl efficiency because Bing has to spend crawl budget on dead routes. Another mistake is sending 404 for pages that have simply moved. In that case, a 301 is usually the right response, because the old URL is not “gone”; it has a replacement.

For removed content, 404 is acceptable when no direct substitute exists. It is not a cleanup tool for every stale page on the site. If the URL has an obvious new home, a redirect gives Bing a much clearer path.

What does a 410 Gone signal to Bing?

HTTP 410 Gone tells Bing the URL was removed intentionally and should be dropped faster than a generic 404 in many cases.

A 410 is stronger than a 404 because it removes ambiguity. A 404 can mean “missing for now” or “missing because nobody configured it yet.” A 410 says the removal is deliberate. For content that is permanently retired, that is a cleaner signal.

Use 410 when the page is not coming back and there is no replacement worth redirecting to. Common examples include expired event pages, discontinued campaign URLs, or old promo pages that have no current equivalent. In those cases, a 410 can shorten the time Bing spends revisiting the URL.

The downside is that 410 is less forgiving. If a page might return later, even after several weeks, 410 is the wrong choice. You would be telling Bing to treat it as permanently removed when it is only temporarily absent. That can create avoidable churn later when the page comes back and has to earn crawling attention again.

A useful rule is this: 404 means “not here”; 410 means “not here, and do not keep hoping.” Bing understands both, but the second one is a sharper signal. If you manage large sites with frequent content retirements, that sharper signal can be helpful. If you manage seasonal pages that come back each year, it can be too aggressive.

When does a 503 Service Unavailable make sense?

A 503 Service Unavailable makes sense when the page is temporarily offline and you want Bing to retry later instead of treating the URL as removed.

This code is for short-term outages: maintenance windows, overloaded origin servers, deployment incidents, or dependency failures. It is not for deleted content, and it is not a substitute for 404 or 410.

The best use of 503 is when the page should return soon. If the outage is short, Bing can interpret the response as a temporary condition and come back later. If the outage lasts too long, the page may still be at risk of losing crawl attention simply because the crawler keeps hitting an unavailable URL.

A 503 response can also include a Retry-After header. That header gives a specific time or delay for a retry, which is more informative than a bare 503. If you know the maintenance window will last 2 hours, expressing that in the response is better than leaving the crawler to guess.

The drawback is obvious: if you leave 503 in place for too long, the page stops looking temporary. Search engines do not like guessing whether a site is in maintenance or broken. If the page is genuinely back, return 200 as soon as possible.

Use 503 for downtime, not for content decisions. If the content has been removed permanently, return 404 or 410 instead. If the page has moved, use a 301.

How Bing handles soft redirects and mixed signals

Bing can be confused by soft redirects because the server says one thing while the page behaves like another.

A soft redirect usually means the page returns 200 OK but immediately sends visitors to another page through script, meta refresh, or a template-level redirect pattern that is not a real HTTP 3xx response. That creates mixed signals. The server says the original URL is live. The page content says “go somewhere else.” Bing has to reconcile those signals, and that is rarely ideal.

A cleaner pattern is a true 301 Moved Permanently when the old URL has a direct replacement. That status code tells Bing exactly where the content now lives. A proper 301 also aligns with the HTTP semantics documented by the IETF and the guidance from Microsoft.

Soft redirects are often a symptom of one of three things:

• the CMS cannot issue proper server-side redirects
• the site is trying to preserve vanity URLs without changing routing
• the page is using a template designed for humans, not for crawlers

The cost is wasted crawl effort and weaker signal clarity. Bing may still follow the destination, but the original URL can linger as if it were still meaningful. That is especially awkward on large sites with thousands of retired pages.

There is one narrow place where a soft redirect appears by design: some applications use a 200 page with a visible message and a single transition after a few seconds. Even there, the safer choice for permanent moves is a real 301. If the page is truly gone, a redirect page should not pretend to be the old content.

What does Bing do with 301 redirects from old pages?

Bing follows HTTP 301 redirects to the new URL and treats the target as the page to crawl going forward.

A 301 is the right answer when content has permanently moved. It preserves continuity between the old URL and the new one, which is better than leaving the old address to die as a 404 if a valid replacement exists.

Use 301 when you change slugs, reorganize sections, migrate protocols, or consolidate duplicate pages into one canonical destination at the routing level. Bing sees the old URL as retired and the new URL as the destination worth checking.

The main risk is redirect chains. A 301 that points to another 301, which points to a third URL, adds delay and weakens efficiency. Keep the path direct: old URL → final URL. If the page lives at /product-a/ now, do not send Bing through /old-product/ → /legacy/product-a/ → /product-a/.

Another issue is redirecting to the wrong kind of page. If a product page is gone and you send users to the homepage, that is technically a redirect but not a strong content match. Bing can follow it, but the signal is weaker than a redirect to a close equivalent.

A 301 is a routing decision, not an index-cleanup trick. It should reflect the actual destination of the content. When that destination does not exist, a 404 or 410 is more honest.

What mistakes cause Bing to misread status codes?

The biggest mistakes are returning the wrong code, hiding an error behind 200, and mixing temporary and permanent states.

A few patterns cause trouble more often than others:

• Custom 404 pages that return 200: This tells Bing the page exists even when it does not. The cost is wasted crawl time and muddy signals.
• Temporary outages served as 404: This makes a short outage look permanent. The cost is slower recovery.
• Permanent removals served as 503: This tells Bing to keep trying. The cost is unnecessary revisits.
• Redirect chains longer than one hop: This burns crawl budget and slows the transfer from old URL to new URL.
• Soft redirects with no 3xx response: This leaves Bing to infer intent instead of reading it directly.

A good rule is to align the code with the page’s real life cycle. Live page: 200. Permanent move: 301. Removed forever: 404 or 410. Temporary outage: 503.

That rule sounds basic because it is. The hard part is making the server, the CMS, the CDN, and any edge rules all agree. If one layer says 200 and another layer says 404, the outermost response wins, and Bing only sees the final answer.

If the site is large, this is worth checking at the template and infrastructure level, not just in the browser. A browser can make a broken URL look fine; the HTTP response is what Bing actually reads.

For a broader picture of how crawl signals fit together, the hub on Bing crawling and indexing mechanics sits upstream of this topic and gives the wider framework.

Key takeaways

• Bing reads the HTTP response before it reads the page content.
• A real 200 keeps a page in the normal crawl flow.
• A 404 says the URL is missing; a 410 says it is intentionally gone.
• A 503 is for temporary unavailability, not deletion.
• A 301 is the clean answer when content has moved for good.
• Soft redirects blur the signal and are weaker than a proper server-side redirect.

What status code should removed pages return?

If a page is permanently removed and has no replacement, return 404 or 410. A 410 is the clearer signal when you want to say the removal is intentional. A 404 is still acceptable when you simply want to show that the URL no longer exists. Do not return 200 for removed pages.

Does Bing treat 410 differently from 404?

Yes, Bing can treat 410 as a stronger removal signal than 404. A 404 means the page is missing; a 410 means it is gone on purpose. That difference can help Bing stop revisiting dead URLs sooner, although both codes tell it the page is not available.

Will a 503 keep pages from dropping out of Bing?

A 503 can help Bing understand that an outage is temporary, but it is not a long-term holding pattern. If the page stays unavailable for too long, the crawler may still reduce attention to it. Use 503 only for real short-term downtime, and switch back to 200 as soon as the page is live again.

Drafted with AI; not yet reviewed by a person.