Technical SEO

Chrome 158 Dropped XSLT, and WordPress Sitemaps Now Look Like Raw XML

Chrome 158 removed XSLT support, causing WordPress sitemaps to appear as raw XML. Search Engine Journal reported the change on November 19, with a clear piece of advice attached: skip the fix and use Google Search Console to confirm crawlers still read the sitemaps. Your sitemap is not broken. It just lost its pretty formatting in one browser, and that is a display problem, not an SEO problem.

What changed in Chrome 158

XSLT is the technology that turned a raw XML sitemap into a readable, styled page when a human opened it in a browser. WordPress sitemaps relied on it to show site owners a tidy table of URLs instead of a wall of angle brackets. Chrome 158 removed XSLT support entirely, so opening a WordPress sitemap in Chrome now shows the raw XML, unstyled and hard to read.

The change is a browser decision, not a WordPress decision and not a Google Search decision. Chrome removed XSLT support in version 158, a legacy feature that WordPress sitemaps relied on for their human-readable display. The XML itself is unchanged, and every crawler that reads sitemaps reads the same XML it always read.

Why sitemaps look broken

Site owners who open their sitemap to check it will see what looks like an error: a page of raw XML with no styling, no table and no friendly message. That is alarming if you do not know what changed, and the first instinct is to fix the sitemap, install a plugin or rewrite the file. Search Engine Journal advice is to resist that instinct, because there is nothing to fix.

The confusion is understandable. For years, a styled sitemap was the visual proof that the sitemap worked, and its disappearance feels like a failure. But the styled view was always a courtesy for humans. Crawlers never needed it, and they do not miss it now.

What Google crawlers still do

Googlebot reads the raw XML directly, exactly as it always has, and XSLT played no part in that process. A sitemap that renders as raw XML in Chrome 158 is still a valid sitemap, and Google Search Console will still report it as readable as long as the XML itself is well formed. The check that matters is in Search Console, not in the browser address bar.

Site owners should open Search Console, find the sitemaps report, and confirm the sitemap status is success with the expected URL count. If that report is clean, the job is done. If it shows errors, those errors are real XML problems and were there before Chrome 158, so fix them on their own merits.

What it means for technical SEO

The episode is a useful reminder that how a page looks in a browser and how a crawler reads it are two different things. Technical SEO lives in the second world: status codes, headers, structured data and raw markup. A rendering change in one browser can look like a catastrophe and mean nothing, while a silent change in a crawler can mean everything and look like nothing.

It is also a warning about where to spend fix time. Every hour spent restyling a sitemap to look nice in Chrome is an hour not spent on crawl budget, internal linking or page speed. The sitemap works. Move on to something that changes rankings.

The lesson: browsers and crawlers are different worlds

A page can look broken in a browser and be perfectly fine for a crawler, and the reverse is also true: a page can look perfect in a browser while returning an error to Googlebot. Technical SEO lives in the crawler world of status codes, headers, structured data and raw markup.

The fix-time rule is simple: spend time where rankings change. Restyling a sitemap to look nice in Chrome changes nothing. Fixing crawl budget, internal linking and page speed changes rankings. The sitemap works, so move on to something that matters.

Sources

Sources: Search Engine Journal, November 19, 2026.

Related reading on this site: November Core Update Volatility Stays Muted as Rollout Nears Its Second Week, Gemini 4 Hydrogen Is Now Live in Google Search Worldwide, Google Moved AI Overviews to the Side for Brand Searches, and Knowledge Panels Are Fading, OpenAI Launches ChatGPT for Sales, a Plugin That Wants to Run Your Whole Sales Workflow, Perplexity Computer Multiagent Puts a Team of 16 AI Agents on One Task, and AI Overviews Are Taking Over the Map Pack, Semrush Finds.

More from Linkbaits

Turn this playbook into links

Linkbaits helps you create content that earns citations and backlinks. Start with the toolkit and build your first linkable asset this week.

Start free trial