Google recently released Chrome version 158, which removed support for XSLT (Extensible Stylesheet Language Transformations). This change means that WordPress sitemaps now appear as raw XML code when viewed in the Chrome browser, instead of the styled, easy-to-read format people are used to seeing.
For many website owners, especially small businesses using WordPress, this visual change can be confusing and may make them worry that their sitemaps are broken or unreadable by search engines. However, this is not the case.
According to Google Search Console, search engine crawlers continue to read WordPress sitemaps properly. The removal of XSLT support only affects the appearance in the browser. The underlying sitemap files remain fully functional and accessible to search bots like Google’s crawler and others involved in SEO and local discoverability.
Why does this matter? For sales, customer service, and local-service teams, maintaining clear local search visibility is crucial. Sitemaps help search engines understand your website structure and index your pages accordingly, which can enhance search visibility. If sitemaps were truly broken, this could negatively affect local search presence, making it harder for customers to find your business online.
Because of Chrome's update, small business owners should resist the urge to make unnecessary changes or fix something that is not actually broken. Instead, they should continue using Google Search Console to verify that their sitemaps are being crawled as expected. Monitoring sitemap health in Search Console remains the best way to ensure their website stays visible to search engines and potential customers.
This development also highlights the importance of knowing the difference between how a site looks to humans versus how it functions behind the scenes for AI-powered search engines and related technologies. While ChatGPT Search and other AI-powered search tools often pull data from structured website content indexed by engines like Google, the formatting of sitemaps in browsers does not impact AI search visibility or overall SEO effectiveness.
Moving forward, organizations should keep an eye on updates from browser makers and Google, but more importantly, they should prioritize ongoing SEO best practices such as monitoring crawl status, fixing real errors reported in Search Console, and maintaining quality content for both search engines and users.
In summary, Chrome 158’s removal of XSLT does change how WordPress sitemaps look in the browser but does not harm their function. Small businesses can breathe easy knowing their sitemaps remain fully crawlable and local search visibility stays intact.
