Chrome will stop running XSLT on its stable channel on November 17, 2026. Most small business websites will not notice, but a few pages could change from a readable layout to plain text or raw code. This post explains what XSLT is, where it hides on business sites, and how to check yours in under an hour.
The facts here come from Chrome's own deprecation guide. We have kept to what that page confirms and flagged where your web team needs to verify details on your specific site.
What XSLT Is, in Plain Words
XSLT is an older web technology that turns a data file, usually XML, into a styled page that people can read. A file with an XSLT stylesheet attached can look like a neat web page in the browser. Without it, the same file looks like a wall of code.
Chrome has been warning about the change for a while. Its guide lists a clear timeline, and the final date for stable Chrome is November 17, 2026, with Chrome version 158.
The Timeline Chrome Published
Chrome's guide, first published on October 29, 2025, sets out the steps. Early console warnings began in Chrome 142 in October 2025. Official deprecation began with Chrome 143 on December 2, 2025.
- Chrome 145: XSLT is turned off by default in the Canary, Dev and Beta channels.
- Chrome 146 (March 10, 2026): an enterprise policy became available for testing.
- Chrome 152 (August 25, 2026): an origin trial went live.
- Chrome 158 (November 17, 2026): XSLT stops working on stable Chrome.
- Chrome 176 (August 17, 2027): all exceptions end.
That means you have a few weeks. After the 2027 date, no temporary workaround remains.
How Many Sites Does This Touch?
Very few. Chrome's guide says fewer than 0.001 percent of page loads use XSLT processing instructions, and about 0.02 percent of page loads use XSLT at all. Most owners can stop worrying after a short check.
Still, a small number of sites do depend on it, and the ones that do often forget it is there. A developer set it up years ago, and nobody has looked since.
Where XSLT Can Hide on a Business Website
Think about files that are not regular pages. These are the usual places to look.
- RSS or Atom feeds: a blog or news feed that shows as a styled page when someone clicks the feed link.
- Sitemaps: some sites attach a stylesheet to the sitemap so it looks tidy to people. Google describes a sitemap as a file that lists the pages, videos and other files on your site, so the file itself is meant for machines.
- Old reports or catalogs: a price list, product feed or staff directory built from XML and shown through a stylesheet.
- Embedded devices and kiosks: a device in your shop or office that serves a settings page using XSLT.
Your customers rarely open these files. Your staff, your partners or an old integration might.
A Short Checklist for Owners
Work through these steps with your web team or hosting contact. Each one takes a few minutes.
- Open your feed and sitemap addresses in Chrome. If the file looks like a styled page, a stylesheet is probably attached. If it looks like plain text or code already, you are likely not affected.
- Ask your web team to search the site for XSLT. They can look for an xml-stylesheet line at the top of XML files. Chrome also points to its Reporting API for finding XSLT use.
- List who uses each file. If only a machine reads it, the missing style is cosmetic. If a person must read it, you need a fix.
- Pick a fix for each file that matters. The options are in the next section.
- Test in Chrome after November 17. Open each file again and confirm it still works for the people who need it.
- Write down what you changed. The next person who maintains the site will thank you.
Fix Options From Chrome's Guide
Chrome lists several paths. Which one fits depends on the file.
For RSS and Atom Feeds
Chrome suggests linking to your feed from an HTML page with a standard alternate link tag. People then reach a normal web page, and feed readers still find the feed. Chrome also notes that a single line of polyfill code can be added to feeds so that readers keep working.
For Pages Built Through a Stylesheet
Move the transformation to your server. The server turns the data into regular HTML, and the browser receives a finished page. This is the cleanest long-term fix, and it works in every browser.
For Devices You Cannot Update
Chrome mentions an extension that provides XSLT support, and a WebAssembly based polyfill for backward compatibility. Both are stopgaps. Talk to the device maker about a permanent update.
For Larger Rebuilds
Chrome also lists moving to JSON with JavaScript, or using a client-side XSLT library. These suit sites with real application logic, not simple feeds.
What This Does Not Mean
Chrome's guide does not say this change affects search rankings, crawling or AI answers. It describes a browser behavior. Do not let anyone sell you an urgent search project because of it.
It also does not mean your whole site will break. Regular HTML pages, images, forms and checkout flows do not use XSLT. The risk is limited to the odd XML file that a person opens in Chrome.
One point to confirm with your web team: if your sitemap carries a stylesheet, make sure the sitemap still loads and still lists the right pages after the change. Looking plain is fine. Failing to load is not.
Why a Small Check Still Pays Off
Browser changes like this one show a habit worth building. Once or twice a year, ask your web team to review old technology on the site and remove what no longer earns its place. Old code is where security gaps and surprise failures tend to hide.
Chrome now ships on a faster schedule, so dates like this one arrive often. A light review habit costs far less than a rushed fix the week something stops working.
Your Next Step
Open your feed and sitemap in Chrome today. If they look plain, you are done. If they look styled, send the addresses to your web team and ask them to pick a fix before November 17.
Sources
Want a second pair of eyes on this for your own site? Contact us or schedule a call.
Tags
Frequently Asked Questions
Will Chrome removing XSLT hurt my Google rankings?
Nothing in Chrome's documentation says it will. The change affects how Chrome displays XML files that use an XSLT stylesheet. Ask your web team to confirm that your pages, sitemap and feeds still load and read correctly after the date.
How do I know if my site uses XSLT?
Open your sitemap and feed addresses in Chrome. If they look like a styled, readable page instead of raw code, a stylesheet is probably in use. Your web team can also check the page source for an xml-stylesheet line, or use Chrome's Reporting API.
Do I need to act before November 17?
Only if you rely on XSLT to display something visitors or staff need to read. Most small business sites use it only for decoration on feeds or sitemaps. A quick check this month is enough.
Enjoyed this article?
Share it with your network
