Chrome 158 Removes XSLT Support, Causing WordPress Sitemaps to Display as Raw XML
TLDR
Chrome 158 has dropped XSLT support, so WordPress sitemaps now display as raw XML in the browser, and the article advises checking with Google Search Console that crawlers still read them.
What this Google Search policy change means for your site
- Status
- Policy change
- Platform
- Google Search
- Affects
- XSLT sitemap rendering, WordPress sitemaps
- Who
- WordPress site owners
- Effective
- Chrome 158
- Action needed
- Use Google Search Console to verify crawlers still read your sitemaps.
Optimixed Overview
Optimixed's original report on this story.
Search Engine Journal reports that Chrome's removal of XSLT makes WordPress sitemaps appear as unstyled raw XML for human visitors. The outlet advises against unnecessary fixes and recommends using Google Search Console to confirm that crawlers can still process the sitemaps.
How we got here: earlier Google Search coverage
- Oct 24Google Clarifies 503 Status Codes, Robots.txt Controls, and Bracket URL Handling
Google reiterates best practices for 503 status codes during downtime, robots.txt file controls, and bracket URL usage.
- Oct 9Google explains when HTML sitemaps remain useful for SEO
Google clarified that HTML sitemaps can still serve a purpose for SEO despite XML sitemaps becoming the standard.
- Oct 6Google Explains The “Couldn’t Fetch” Sitemap Errors via @sejournal, @martinibuster
Google Explains The “Couldn’t Fetch” Sitemap Errors via @sejournal, @martinibuster
- Jul 27Google Search Console robots.txt recrawl feature experiencing widespread errors
Google's robots.txt recrawl feature in Search Console is throwing errors for multiple users, though the issue appears intermittent.