Skip to content

Does Bingbot render JavaScript? Check with Bing URL Inspection

Does Bing render JavaScript? What Bing's guidelines and crawler docs say today, and a URL Inspection test that compares Bing's HTML with your raw and rendered page.

By Crawlito · 8 min read

In short

  • Bing's crawler documentation says Bingbot's rendering engine is kept on the most recent stable version of Microsoft Edge, which is what the Chrome/W.X.Y.Z part of its user agent reports.
  • The current Bing Webmaster Guidelines tell sites to avoid hiding critical content behind client-side rendering, and warn that content Bing cannot reliably render may not be indexed or used for grounding.
  • Bing's October 2018 post said Bingbot is generally able to render JavaScript but cannot do so at scale on every page of every site; treat it as dated background, not current policy.
  • Bing's URL Inspection help does not say whether the HTML it shows is the fetched source or the rendered DOM, so a page with a known script-only phrase is the way to find out.
  • If a phrase written only by JavaScript is missing from what Bing shows, put that content in the server HTML rather than relying on Bing to run the script.
On this page

Bingbot can render JavaScript: Bing's crawler documentation says it keeps its web page rendering engine on the most recent stable version of Microsoft Edge. But Bing does not promise to render every page, and its current Webmaster Guidelines tell you to avoid hiding critical content behind client-side rendering. The practical answer is to put important content in the server HTML, then use Bing Webmaster Tools URL Inspection to check what Bing actually received for your page.

This post quotes what Bing documents now, separates it from older blog posts, and gives a test procedure for comparing Bing's fetched HTML with your raw and rendered HTML. Why Bing matters for Copilot is covered in Bingbot and AI search, and index statuses are covered in site not showing in Bing. Bing's pages were read on 15 November 2026.

What Bing documents about JavaScript today

Two current Bing pages speak to rendering. Neither gives a rendering budget, a timeout or a list of supported frameworks.

The crawler documentation. Bing's page Which crawlers does Bing use? lists Bingbot's user agents with a Chrome/W.X.Y.Z token. It says Bing regularly updates its web page rendering engine to the most recent stable version of Microsoft Edge, and that W.X.Y.Z is replaced with the Edge version in use. The desktop string looks like this:

Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/W.X.Y.Z Safari/537.36

So Bing tells you which engine it renders with. It does not say that every fetch is rendered.

The Webmaster Guidelines. The current Bing Webmaster Guidelines say they describe how Bing crawls, indexes and surfaces content across Bing search, Copilot and grounding API results. Section 8, "Allow Efficient Crawling and Rendering", lists things to avoid, including:

  • "Hiding critical content behind client-side rendering"
  • "Excessive or unnecessary HTTP requests to render the content"
  • blocking important URLs unnecessarily, or blocking Bingbot in robots.txt

The section ends with the line that matters most: content that cannot be reliably rendered "may not be indexed or selected for grounding results." The guidelines do not mention JavaScript by name. They talk about client-side rendering and the number of requests a page needs, which is the cost Bing is warning about.

The same guidelines list cloaking, showing search crawlers different content from what users get, among the practices that reduce ranking eligibility and grounding visibility, and say sites should not serve materially different experiences to crawlers and visitors. That matters if your fix involves serving pre-rendered HTML to Bingbot, covered below.

What Bing's older posts add, and why they are dated

Two Bing blog posts are often quoted as if they were current policy. They are useful history, but the guidelines above are what Bing maintains today.

SourceDateWhat it said
bingbot Series: JavaScript, Dynamic Rendering, and Cloaking31 October 2018Bingbot "is generally able to render JavaScript", but processing it at scale on every page of every site is difficult. Recommended dynamic rendering for sites relying heavily on JavaScript, and said it is not cloaking if you make a good-faith effort to return the same content to all visitors.
The new evergreen Bingbot9 October 2019Bing was adopting Microsoft Edge as the engine to run JavaScript and render pages, would switch gradually, and committed to keeping the rendering engine updated.
Crawler documentationCurrentRendering engine kept on the latest stable Edge; version shown in the user agent.
Webmaster GuidelinesCurrentAvoid hiding critical content behind client-side rendering; unreliably rendered content may not be indexed or used for grounding.

The 2018 post predates the Edge switch, so its point about unsupported frameworks may no longer apply. Its point about scale is consistent with the current guidelines, which still ask you to reduce rendering cost. For AI crawlers other than Bingbot, which mostly did not run JavaScript in the public data available, see do AI crawlers run JavaScript?.

What Bing URL Inspection shows, and what it does not

Here is what Bing's URL Inspection help page says at the time of writing. You can only inspect URLs on a site you have added to Bing Webmaster Tools. Relevant to rendering:

  • Index card. Shows when and where Bing discovered, crawled and indexed the URL, with an option to see the HTML and the HTTP response details. For an indexed URL, Bing says you can copy and search that HTML.
  • Live URL tab. Bing says it lets you "see exactly what the Bingbot sees while downloading a page" and can show whether a site sends different HTML to Bingbot and to users. It sends a request to Bingbot, so a few seconds of delay is normal, and you can search the result for specific details. If it cannot crawl the page because of a block, Bing says it tells you.
  • Redirects. Live URL does not follow redirects. It reports the redirect and the destination, and you use Inspect redirect destination to fetch the target, which Bing says mirrors how Bingbot crawls.
  • SEO and Markup cards. These report SEO issues and structured data in HTML Microdata, Microformats, Open Graph and JSON-LD.

What the help page does not say is just as important:

  • It does not say whether the HTML shown is the raw response or the DOM after Edge has run your scripts.
  • It does not document a screenshot, a JavaScript console log or a list of loaded resources, unlike Google's URL Inspection tool.
  • It does not say whether the indexed copy was rendered.

Because those points are not documented, do not assume either way. Test it with a page where you know exactly which text comes from the server and which comes from a script.

How to compare Bing's HTML with your raw and rendered HTML

You need a verified site in Bing Webmaster Tools, a terminal and headless Chrome. The idea is to plant two unique phrases: one in the server HTML, one written only by JavaScript. Then you check which of them Bing shows.

1. Publish a test page with two marker phrases

Create a page on the verified site, for example /bing-render-test, served as normal HTML with a 200 status:

html
<!doctype html>
<html lang="en">
<head><title>Bing render test</title></head>
<body>
  <p>Marker server alpha 7731</p>
  <div id="slot"></div>
  <script>
    document.getElementById('slot').textContent = 'Marker script ' + 'bravo 7731';
  </script>
</body>
</html>

Use made-up words that appear nowhere else on the site. The script joins two strings on purpose: the full phrase Marker script bravo 7731 never appears in the source, so it can only show up in HTML where the script has actually run.

If your real pages load content with fetch after the page mounts, add a second slot that does the same, since inline scripts and network-loaded data are not the same test.

2. Save your raw and rendered versions

bash
URL=https://www.example.com/bing-render-test
UA='Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm) Chrome/131.0.0.0 Safari/537.36'

curl -sL -A "$UA" -o raw.html -w '%{http_code}\n' "$URL"
google-chrome --headless --dump-dom "$URL" > rendered.html

grep -c "Marker script bravo 7731" raw.html rendered.html

131.0.0.0 is a placeholder for Bing's W.X.Y.Z. raw.html should report 0 and rendered.html should report 1. If raw.html already contains the script phrase, the test page is not doing what you think. The general method for reading raw against rendered HTML is in raw HTML vs rendered HTML.

3. Run Live URL and search the result

In Bing Webmaster Tools, open URL Inspection, enter the test URL and switch to the Live URL tab. Use the search Bing offers there to look for both markers. If Bing reports that it could not crawl the page, or what comes back is a block, a challenge page or a redirect, you are testing your firewall or redirects, not rendering.

4. Repeat on a real template

Once you know how the tool behaves, inspect one real page of each template (product, article, category) and search for a sentence that your app writes client-side, such as a price or review text.

How to read the result

Server markerScript markerWhat it tells you
FoundFoundThe view you inspected contains script output, so it reflects rendering for this page
FoundMissingThe view shows the fetched HTML, or Bing did not run the script; either way, it is not evidence of rendering
MissingMissingBing did not get your page: check the status code, firewall, redirects and robots.txt first

A "found" result on Live URL is good news, but it is one fetch of one page. It does not tell you Bing renders every URL on a large site, and the guidelines' warning about reliability still applies. A "missing" result does not prove Bing never renders; it proves that this view does not show script output, so the content is not safe to rely on.

The comparison also catches a quieter problem. If the indexed copy's HTML is missing changes you have since made to your server HTML, Bing is probably still working from an older crawl: check the crawl date on the Index card. Fix the page, then use the request indexing option, which Bing says depends on your URL submission quota.

How to fix content Bing may not render

The fix is the same one that helps every crawler: make the content exist without JavaScript.

  1. Put key content in the first response. Server-side rendering, static generation or moving data fetches to the server puts prices, product details and article bodies in the HTML that Bingbot and non-rendering AI crawlers both read. The framework options are in do AI crawlers run JavaScript?.
  2. Cut rendering requests. Bing's guidelines name excessive HTTP requests as a problem. Bundle scripts, avoid chains of API calls before content appears, and do not block the JavaScript and CSS files a page needs in robots.txt.
  3. Prerender if you cannot change the app. Bing's 2018 post said dynamic rendering is not cloaking if you make a good-faith effort to return the same content to everyone, and the current guidelines still list cloaking as abuse, so the pre-rendered HTML must match what visitors get. The trade-offs are in prerendering and dynamic rendering.

After each change, rerun the curl check and Live URL, and confirm your key sentence is in the raw HTML. Remove the test page when you are done.

Frequently asked questions

Does Bing render JavaScript?

Yes. Bing says it regularly updates Bingbot's rendering engine to the most recent stable version of Microsoft Edge. Its current guidelines still warn that content hidden behind client-side rendering, or that cannot be reliably rendered, may not be indexed or used for grounding.

Does Bing URL Inspection show rendered HTML?

Bing's help page does not say. It offers the HTML and HTTP response for the indexed copy and a Live URL fetch, so test with a page that has a script-only phrase to see which version you get.

Is dynamic rendering allowed by Bing?

Bing's 2018 post recommended it for JavaScript-heavy sites and said it is not cloaking when everyone gets the same content. The current guidelines say sites should not serve materially different experiences to crawlers and visitors, so any pre-rendered version must match the user version.

Does Copilot see content that only JavaScript adds?

Microsoft does not document Copilot fetching pages separately from Bing's index. Bing's guidelines say unreliably rendered content may not be selected for grounding, so put content you want available to Copilot in the server HTML.

Run the same check on your pages

The marker test tells you what Bing shows; the curl step tells you what every non-rendering crawler gets. To check a page's raw HTML and crawler access without a terminal, run the free check, which needs no account.

Filed under Rendering and content. Topics: bingbot, javascript, rendering, troubleshooting