Is your WordPress sitemap broken in Chrome 158? No. Google Chrome 158 has dropped support for XSLT, so WordPress sitemaps now display as raw XML instead of a formatted table. The sitemap file and what search engines see are the same as before, and Google Search Console remains the right place to confirm that crawlers can still read it. The issue was highlighted by Search Engine Journal, which advises site owners to skip unnecessary fixes.
For anyone managing a WordPress site, opening a sitemap URL and seeing a wall of angle brackets can be alarming. The change is in the browser, not your site. This article explains what happened and what to check.
- What changed: Google Chrome 158 has dropped XSLT support (Search Engine Journal).
- Visible effect: WordPress sitemaps now display as raw XML in Chrome (Search Engine Journal).
- Impact on crawling: The sitemap isn't broken; the change affects how it displays (Search Engine Journal).
- Recommended action: Use Google Search Console to verify crawlers still read the sitemap (Search Engine Journal).
Why does my WordPress sitemap show raw XML in Chrome?
An XML sitemap is a machine-readable file. It lists URLs and optional details such as last-modified dates. It was always meant for crawlers like Googlebot and Bingbot, not people.
To make these files easier to read, WordPress and popular SEO plugins attach an XSL stylesheet to their sitemaps. XSLT (Extensible Stylesheet Language Transformations) tells the browser to turn the raw XML into a styled HTML page with tables, columns and clickable links. This includes the native sitemaps in WordPress core and the sitemaps generated by plugins such as Yoast SEO and Rank Math.
Without XSLT, Chrome has no way to apply that styling. It shows what the file actually contains, which is plain XML. The data is unchanged. Only the presentation layer has gone.

Does Chrome dropping XSLT affect SEO or Google crawling?
Not in itself. Search engine crawlers fetch the sitemap file and parse the XML directly. The stylesheet reference at the top of a sitemap is an instruction for browsers, and crawlers have never needed it to extract URLs. A sitemap that was valid last month is still valid now.
This is why the episode is a useful reminder about troubleshooting. A browser is a rendering tool, and a rendering change can make a healthy file look faulty. To judge a sitemap's health, check how search engines process it, not how it looks in a tab.
| Aspect | Before Chrome 158 | After Chrome 158 |
|---|---|---|
| How a human sees the sitemap in Chrome | Styled table via XSLT | Raw XML |
| Sitemap file contents | XML list of URLs | Unchanged |
| What crawlers read | Raw XML | Raw XML (unchanged) |
| Where to verify health | Google Search Console | Google Search Console |
What fixes should WordPress site owners avoid?
When something looks broken, the urge is to act fast. In this case, quick fixes can do more damage than the display change ever could. Search Engine Journal's advice is to skip unnecessary fixes, and in practice that means avoiding the following:
- Disabling or swapping sitemap plugins. Moving from one SEO plugin to another can change sitemap URLs, create duplicate sitemaps or leave old ones orphaned in Google Search Console.
- Installing unvetted "sitemap fix" plugins. Each extra plugin increases your attack surface. The recent Ultimate Member WordPress plugin flaw that put 200K sites at risk shows how one extension can expose a whole site.
- Hand-editing core or theme files to strip the stylesheet reference. The change gains nothing for crawlers, and it will be overwritten on the next update.
- Resubmitting sitemaps repeatedly out of panic. If Google Search Console already reports the sitemap as read successfully, resubmitting does not help.
Agencies should prepare for the same question from several clients. A short standard explanation, sent before clients notice, can prevent unnecessary support tickets and emergency changes.
How to verify your WordPress sitemap in Google Search Console
Google Search Console shows how Google actually processes your sitemap. A quick health check looks like this:
- Open the Sitemaps report for the relevant property in Google Search Console.
- Check the status of each submitted sitemap. You want it to read as successfully processed, not show fetch or parsing errors.
- Look at the last read date to confirm Google is still fetching the file regularly.
- Compare discovered URLs against the number of pages you expect to be indexed. A sudden drop is worth investigating, but the browser change would not cause it.
- Spot-check with the URL Inspection tool on a few important pages to confirm they are known to Google and indexable.

Other ways to read the sitemap yourself
If you just want to see the URLs, raw XML is still readable once you know what to look for. Each page appears inside a loc tag. Using the browser's view-source option, a command-line request, or an XML validator also confirms the file is well-formed. Teams that report on technical SEO regularly can add sitemap status checks to their dashboards. Our guide to top SEO reporting tools for agencies covers options that bring Search Console data into client reports.
What the XSLT change means for technical SEO monitoring
The broader point is that browsers are updated constantly, and visual assumptions do not last. Workflows built on "open the URL and eyeball it" will keep producing false alarms. Monitoring built on how search engines process a site, using Google Search Console data, crawl logs and scheduled crawls, holds up much better.
Plugin developers may eventually change how sitemaps are presented to humans, perhaps with an HTML view inside the WordPress admin. Until that happens, raw XML in Chrome is expected behavior, not a fault. The same principle applies elsewhere in marketing operations: decisions are only as good as the data behind them, as we discussed in why AI ad strategy depends on data quality.
Key Takeaways
- Google Chrome 158 dropped XSLT, so WordPress sitemaps now render as raw XML instead of styled tables.
- The sitemap isn't broken. Crawlers read the XML directly and never needed the stylesheet.
- Avoid reactive fixes such as switching plugins, installing unvetted extensions or editing core files.
- Use the Google Search Console Sitemaps report to confirm status, last read date and discovered URLs.
- Base technical SEO health checks on search engine data, not on how a file looks in a browser.
Frequently Asked Questions
Why does my WordPress sitemap look like code in Chrome now?
Google Chrome 158 has dropped support for XSLT, the technology that converted XML sitemaps into styled, readable tables. Chrome now shows the raw XML instead. The sitemap's contents are unchanged.
Will Chrome dropping XSLT hurt my search rankings?
No. Search engine crawlers read the raw XML in a sitemap and never depended on the browser stylesheet. The change affects how people see the file in Chrome, not how Google processes it.
How can I check that Google can still read my WordPress sitemap?
Open the Sitemaps report in Google Search Console and check the status, last read date and number of discovered URLs for each sitemap. You can also use the URL Inspection tool on key pages to confirm Google knows about them.
Should I install a plugin to fix the raw XML sitemap display?
It is generally unnecessary, because the sitemap is not broken. Each extra plugin adds maintenance and security risk, so it is better to verify sitemap health in Google Search Console than to add a cosmetic fix.

