Skip to content
🌍Global

Choose your region

🌍 Global / International

Chrome 158 broke sitemap viewing, not your WordPress XML sitemap

SEO News 20 November 2026 Gaurav Rajani Search Engine Journal
Chrome 158 broke sitemap viewing, not your WordPress XML sitemap

Chrome 158 changed how it displays XML files: it no longer applies XSLT stylesheets. As a result, many WordPress XML sitemap URLs that used to show a nicely formatted page now show raw XML. That visual change is what triggered the panic.

The sitemap likely still works for search engines. The bigger risk is human: teams “fixing” the wrong thing and accidentally breaking crawlability.

This kicked off after reporting from Search Engine Journal’s coverage of Chrome 158 dropping XSLT for WordPress sitemaps.

What changed (and why it looks scary)

In plain terms: your WordPress XML sitemap didn’t suddenly corrupt itself. Chrome stopped prettifying it.

Historically, lots of CMS-generated sitemaps referenced an XSL file that browsers could use to display the XML in a readable format. Chrome 158 removed that XSLT support. So your browser now shows the underlying XML tree—no columns, no “sitemap index” formatting, no friendly layout.

One phrase you’ll hear a lot this week is “broken sitemap.” For most sites, that’s wrong. What’s broken is the human-friendly rendering in one browser family.

What it means for business owners (the real risks)

If you sell something online, you don’t get paid because your sitemap is pretty. You get paid because search engines can find and index your pages.

The operational risk here is wasted time and risky edits. We’ve already seen how this goes on WordPress builds: someone pastes a snippet into functions.php, a cache plugin minifies something it shouldn’t, the server starts returning text/html instead of application/xml, and then Googlebot starts throwing warnings.

Here’s who wins and loses.

Winners: teams with boring, verified technical hygiene (sitemap fetch checks, crawl stats monitoring, log access). This is a non-event for them.

Losers: teams that treat a browser view as a diagnostic tool. Chrome’s display is not a search engine validator.

Our view: this is overhyped as an “SEO issue,” but underappreciated as a “change control” issue. The damage won’t come from Chrome 158. It’ll come from rushed, unreviewed fixes.

What we’d do this month (and what we’re not doing)

We’re not rolling out mass changes to sitemap generation because a browser stopped rendering XSLT.

We are doing quick verification passes on client properties, because the cost is low (minutes) and the downside of a real sitemap problem is high (indexation drift that you only notice after traffic drops).

Our verification checklist (fast, boring, effective)

  • Confirm HTTP status and headers: sitemap URLs should return 200, not 302 loops, and the content type should be XML-friendly (application/xml or text/xml).
  • Validate in Google Search Console: check the Sitemaps report for “Success” and recent read times; then cross-check Coverage/Indexing patterns.
  • Spot-check server logs: make sure Googlebot is successfully fetching /sitemap.xml and any child sitemap URLs without spikes in 4xx/5xx.
  • Check robots rules: confirm nothing changed that would block the sitemap or the URLs inside it.

If you don’t have log access, fix that before you “fix” the sitemap. If you need engineering support for that kind of instrumentation work, it often sits alongside mobile and web product builds, not just SEO tasks.

Everyone will miss this: the riskiest “fix” is cosmetic

The temptation will be to restore the old pretty view by forcing a stylesheet or swapping plugins. Cosmetic work has a habit of becoming structural work.

We’ve seen WordPress teams do things like:

1) Add a redirect from /sitemap.xml to a styled HTML page so “it looks right.” That can break search engine expectations fast.

2) Put the sitemap behind basic auth on staging and accidentally replicate the rule to production. Now Google can’t fetch it at all.

3) Use a security plugin rule that blocks XML endpoints because they “look like data exfiltration.” It’s well-intentioned and disastrous.

If you truly need a human-readable sitemap view for internal ops, do it as a separate endpoint (e.g., /sitemap-viewer/) and leave the XML sitemap endpoint alone.

What this means for your site

  • Don’t ship a “sitemap fix” just to make Chrome happy. Chrome is not Googlebot.
  • Open GSC and confirm the last read time for your WordPress XML sitemap and that it’s still reported as processed.
  • Fetch the sitemap with a non-browser tool (curl, HTTP client, or an SEO crawler) and confirm it returns 200 and valid XML.
  • Check caching/CDN rules so the sitemap isn’t being transformed, compressed incorrectly, or rewritten into HTML.
  • Log one change request: “No sitemap changes without SEO sign-off.” This is how you prevent a well-meaning hotfix.

How to prove it’s fine (in a way executives accept)

You need two kinds of evidence: Google’s view, and your server’s view.

Google’s view: in Search Console, the sitemap status and any reported fetch/parse errors. If Google is reading it, you’ll see it.

Your server’s view: access logs confirming Googlebot is hitting the sitemap URL and receiving 200. This is also where you’ll catch rate limiting, WAF blocks, or odd redirects.

If your marketing team doesn’t live in GSC weekly, now is a good excuse. Google has been pushing more structured education for teams; their SEO learning path playlists for fundamentals and technical SEO are a decent refresher for non-specialists who keep getting pulled into technical decisions.

If you do nothing for 90 days

If your sitemap endpoint is healthy, nothing bad happens. The XML will still be crawlable, and rankings won’t move because a browser stopped formatting a file.

If your sitemap endpoint is not healthy (quietly blocked by security rules, returning the wrong content type, timing out under load), doing nothing means you’ll only notice after you’ve lost indexation coverage—usually right when a seasonal campaign launches or right after an algorithm update reshuffles the SERP. That’s when recovery takes longer and costs more.

There’s also a second-order effect: teams will keep spending cycles debating “why the sitemap looks broken,” while competitors spend those cycles shipping pages, fixing internal linking, and improving templates. That opportunity cost is real.

What we’re changing on client sites this week

Three small moves, high signal, low risk:

1) Add sitemap endpoint monitoring (status code + response size) to uptime checks. This catches regressions from plugins, hosting migrations, and WAF updates.

2) Lock sitemap routes in change control so plugin updates can’t silently replace sitemap behavior without review.

3) Standardize a “crawl validation” mini-runbook for marketing leads: where to check in GSC, what a healthy fetch looks like, and when to escalate to engineering.

If you want to see how we typically operationalise technical SEO checks without slowing releases, skim recent delivery examples from our case studies or check how we package ongoing support and audits on our pricing page. For ongoing organic growth work, our teams run this kind of monitoring as part of SEO support for UK companies and SEO services for US teams.

Next step: send your sitemap URL and GSC property to whoever owns your website ops, and ask for a 15-minute “sitemap is readable by Google” verification—no code changes until that’s confirmed.

Primary source: Search Engine Journal

WordPressXML sitemapChromeTechnical SEOGoogle Search Console
Consultation with our teamTeam working together

Need any help? Contact us today

+1 (502) 780-5714

Frequently Asked Questions

FAQ: Chrome 158 and WordPress XML sitemap display changes

1. Is my WordPress XML sitemap broken if it shows raw XML in Chrome?

Usually no. Chrome 158 stopped applying XSLT styling, so the sitemap looks unformatted to humans. Search engines can still read the XML if the endpoint returns 200 and valid XML.

2. What’s the safest way to check if Google can still use my sitemap?

Check the Sitemaps report in Google Search Console for successful processing and recent read time, then confirm in server logs that Googlebot is fetching the sitemap URL with 200 responses.

Let’s make something great work together.

From day one to enterprise – we’re your partner in long-term tech success.