Your WordPress Sitemap Isn’t Broken – Chrome 158 Has Dropped XSLT

The short version
Chrome 158's removal of XSLT affects how WordPress sitemaps display in browsers but not their functionality. Search engines continue to read the raw XML correctly.
Key takeaways
- Chrome 158 drops support for XSLT in sitemaps.
- Search engines read XML, unaffected by browser display changes.
- Use Google Search Console to confirm sitemap status.
Overall sentiment
NeutralThe article provides factual updates without expressing positive or negative opinions.
AI classification of the article’s tone. Coverage is limited to the effects of Chrome 158 and WordPress sitemaps.
Sources cited by the article
- Chrome 158 ↗
- drops support for client-side XSLT ↗
- Google’s November core update, ↗
- removes core’s XSLT stylesheet ↗
- Yoast 28.9 replaces XSLT with pure CSS styling ↗
- Confirmed in support channels ↗
- latest changelogs ↗
- When The WordPress Plugin Update Is The Security Risk: Why SEOs Should Pay Attention ↗
- All In One SEO WordPress Plugin Vulnerable To Two Exploits ↗
- Technical SEO ↗
- Ask an SEO: Is An XML Or HTML Sitemap Better For SEO? ↗
- HTML sitemap ↗
- Read Full Bio ↗
- 10 Spurs ↗
- SEJ ↗
- WordPress ↗
These references were linked or listed by the publisher, then selected for relevance. They are distinct from our original-source citation.