RankHive

URL cannot appear on Bing

Where you see it: Bing Webmaster Tools → URL Inspection → Bing Index tab

Bing’s URL Inspection shows this when the URL isn’t in Bing’s index, so it can’t appear in Bing results. The reason sits beside it, most often “Discovered but not crawled” (Bing knows the address but hasn’t fetched it) or “Blocked”. On WordPress the cause is usually a setting that shuts Bingbot out, a site Bing barely knows, or pages it hasn’t judged worth indexing.

Act if pages you want in Bing show it. A new site may only need time.

Read the reason first. A block from robots.txt, noindex or a firewall is yours to fix today. Discovered but not crawled on a new site with few links is expected for a while. On an older site, look at quality, which Bing lists among its indexing factors.

Check a URL nowCan RankHive fix it? Partly

Check the URL Bing Webmaster Tools listed

Enter your site’s address and leave the robots.txt box empty so the tool fetches the live file. Put the URL Bing listed in Test URL and set User agent to Bingbot: a rule can block Bingbot while letting Googlebot through.

Robots report

Fetch or paste robots.txt to test crawler access.

Starter robots.txt
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

# The WordPress core sitemap. SEO plugins serve their own instead,
# such as /sitemap_index.xml for Yoast SEO and Rank Math.
Sitemap: https://rankhive.app/wp-sitemap.xml

Reading the result

  • Crawl decision Blocked: the Matched rule line is what keeps Bingbot out. Remove it, or narrow it to the paths you meant to block.
  • Matched rule shows Disallow: /. Find that line in the fetched robots.txt the tool prints and check which User-agent group it sits in. Under User-agent: * it is usually a staging rule that never came out; under a bingbot group, someone shut Bing out on purpose.
  • Allowed, Matched rule None: robots.txt isn’t your problem. Move on to noindex, your firewall and Bing’s quality guidelines.
  • Sitemaps empty: add a Sitemap: line with your sitemap’s full address so Bing can find it on its own.

The same tool with its full guide: Robots.txt

Why it happens on WordPress

Google and Bing crawl and judge separately, so a site can be fine in one and missing from the other. Here are the WordPress settings and add-ons that keep Bing out, and Bing’s own call.

“Discourage search engines” left ticked

The box under Settings → Reading is easy to tick on a new build and forget at launch. Since WordPress 5.3 it prints a noindex robots meta tag on every page, and Bing doesn’t index pages carrying noindex.

A robots.txt rule left over from staging

A Disallow: / under User-agent: *, or a bingbot group someone added, keeps Bingbot out. A physical robots.txt in the web root replaces the one WordPress generates, so plugin robots.txt settings may not be what Bing reads.

A firewall that treats Bingbot as a threat

Wordfence’s rate limiting can catch Bingbot and serve it Wordfence’s own block page; the redirect checker shows which status that page returns. On Cloudflare, bot and WAF rules can challenge crawlers, Bingbot included.

Noindex set in your SEO plugin

A post switched out of search in Yoast SEO, Rank Math or SEOPress is noindexed for Bing too, as are archives turned off in their settings.

A site Bing has barely heard of

A new site with no links pointing to it and no sitemap in Bing Webmaster Tools gives Bing nothing to follow. Bing says it needs at least one link to your site to find it.

Pages below Bing’s quality bar

Bing’s help names thin content, duplicate content and quick redirects as reasons a site falls short, and its guidelines say mass-generated content without editorial review may be left out. On WordPress: one-post tag archives, attachment pages, ?replytocom copies, near-identical location pages.

URLs blocked inside Bing Webmaster Tools

Bing’s Block URLs tool hides pages without touching your site. If anyone used it during a redesign, check for entries still in force.

How to fix it

Work from the outside in: Bing can reach the site, may index it, then has a reason to.

  1. 1. Add the site to Bing Webmaster Tools

    Use Import on the My Sites page to bring your Google Search Console sites across, already verified. Otherwise:

    • XML file: upload BingSiteAuth.xml to the site’s root folder, often public_html.
    • Meta tag: paste Bing’s code into your SEO plugin’s verification setting, not the theme.
    • CNAME: add the record Bing gives you at your DNS host.

  2. 2. Untick “Discourage search engines”

    Go to Settings → Reading, clear Search engine visibility and save. Then search a page’s source for noindex; if it’s still there, purge the cache.

  3. 3. Test robots.txt as Bingbot

    Use the checker above, or the robots.txt tester in Bing Webmaster Tools, and remove any rule blocking pages you want found.

    • Physical file in the web root: edit it by FTP or your host’s file manager, or in Yoast SEO → Tools → File editor, which edits that file and creates one if there is none.
    • No physical file: Rank Math SEO → General Settings → Edit robots.txt changes the version WordPress generates.

  4. 4. Inspect one URL and read the reason

    In URL Inspection, the Bing Index tab shows what Bing has stored; Live URL fetches the page now, as Bingbot. If Live URL is clean but the index still says Blocked, that is an older crawl. Request indexing for main pages; it draws on a daily quota Bing sets per site.

  5. 5. Let verified Bingbot past your firewall

    Find blocked Bingbot requests in your security plugin or CDN log, and confirm the IP with Bing’s Verify Bingbot tool or a reverse DNS lookup ending in search.msn.com.

    • Wordfence: in the Rate Limiting options, use throttle rather than block for crawler rules.
    • Cloudflare: look in Security Events for blocked or challenged Bingbot requests, and find the bot or WAF rule that acted on them.

  6. 6. Submit a sitemap and switch on IndexNow

    In Bing Webmaster Tools, open Sitemaps and submit its full address; Bing says it tries to fetch a sitemap as soon as it is submitted. Then let one plugin send IndexNow pings for new and updated posts.

    • Yoast SEO and Rank Math: https://example.com/sitemap_index.xml. SEOPress: /sitemaps.xml. No SEO plugin: /wp-sitemap.xml.

  7. 7. Give Bing better pages to index

    If every check passes and URLs stay Discovered but not crawled, improve the site instead of resubmitting: noindex one-post tags, link to new posts from older ones, merge thin posts.

Check the fix in Bing Webmaster Tools

There is no Validate fix button in Bing. Check each layer, then give Bingbot time.

  1. Run Live URL on a key page. It should fetch the page with no robots.txt or noindex problem.
  2. Open Sitemaps and check your sitemap shows a successful read and a recent last read date.
  3. Inspect your requested pages again later; the Bing Index tab changes once Bing recrawls them.
  4. Search Bing for site:example.com, with your own domain, to see which pages are in.

Bing’s support page says a site can take a couple of weeks to show after a major launch or redesign. If pages still read Discovered but not crawled after that, contact Bing Webmaster support.

Can RankHive fix this?

Partly. When Bing passes over thin or poorly linked posts and pages, RankHive can rewrite them and link to them from related posts. Noindex, firewalls, verification and Bing Webmaster Tools stay with you; RankHive doesn’t read Bing’s data.

What it writes, once you approve

  • Rewrites of thin posts and pages, a passage or the whole body.
  • Internal links from related posts to pages Bing hasn’t crawled.
  • Lines in WordPress’s virtual robots.txt, such as your Sitemap: address. A physical robots.txt in the site root overrides them.

What it can’t do here

  • Untick “Discourage search engines”, or set or remove noindex anywhere.
  • Change Wordfence, Cloudflare or host firewall settings.
  • Verify your site, submit sitemaps or URLs, or send IndexNow pings.
  • Read URL Inspection or any other Bing Webmaster Tools data.
  • Edit a physical robots.txt file, archives, attachment pages or WooCommerce products.

Every change is drafted next to the current value and waits for your approval. Each one written is logged in the Change Log, with Revert.

Check the rest of your site while you’re here

The free site check reads your public pages for titles, meta descriptions, headings, canonical tags and schema, and shows what needs fixing. If you sign up, RankHive reads your Google Search Console data every week, drafts the fixes, and writes the ones you approve to WordPress. Nothing changes on your site until you say yes.

Free site check. No sign-up needed.

Related issues

Common questions

Why is my site on Google but not on Bing?

Because they crawl and judge separately. On WordPress the usual gap is a firewall or rate limit that stops Bingbot, a robots.txt group aimed at bingbot, or a site never added to Bing Webmaster Tools.

Do I need Bing Webmaster Tools for Bing to index my site?

No. Bing finds sites through links, sitemaps named in robots.txt and IndexNow. You need it to see why a URL is left out and to request indexing.

How long does Bing take to index a new site?

Bing gives no fixed time; new sites take time to be found and crawled. Links from other sites and a submitted sitemap help.

What does “Discovered but not crawled” mean in Bing?

Bing knows the URL from a link, sitemap or submission but hasn’t fetched it, so it can’t be indexed yet. On a new site, give it time and links; on an older one where every check passes, read Bing’s quality guidelines.

Does Request indexing or IndexNow force Bing to index a page?

No. Both put the URL in front of Bing, which still decides whether to crawl and index it. Bing says IndexNow doesn’t guarantee either.

Read next

Sources

Checked against these pages on .