What Happens to Podcast RSS Feeds When Chrome Drops XSLT on November 17?

What Is Chrome Turning Off on November 17?

Chrome is removing XSLT, a W3C language from 1999 that turns XML into a web page (W3C), and with it the line many podcast feeds use to look like a show page in a browser. Chrome’s deprecation notice, published October 29, 2025, names two things that stop working: the XSLTProcessor JavaScript interface and the processing instruction <?xml-stylesheet type="text/xsl" ...?> (Chrome for Developers). That second item is the one in podcast feeds. It sits above the <rss> tag and tells a browser to restyle the raw XML with a stylesheet file.

The notice gives Google’s reason in one line: “The continued inclusion of XSLT 1.0 in web browsers presents a significant and unnecessary security risk” (Chrome for Developers). It also says Firefox and WebKit, the engine behind Safari, “have also indicated plans to remove XSLT.” The schedule runs in steps:

Dates are from Chrome’s notice (Chrome for Developers); the day counts are ours. Note what survives. Chrome says the same processing instruction “remains supported when used with CSS,” with type="text/css" (Chrome for Developers).

Which Podcast Feeds Still Use XSLT?

In our sample, about one feed in five, and only on three hosts. We took the 100 shows on Apple Podcasts’ US top chart and the 100 on its UK chart as served at 14:53 GMT on November 9 (Apple Marketing Tools), looked up each show’s public feed address, and read the opening 8 KB of every feed for an xml-stylesheet line. One US show, The Ben Shapiro Show, returned no public feed address, and 13 shows appear on both charts, which left 186 distinct feeds. All 186 answered.

The chart shows a host-level pattern, not a show-level one: where a host uses XSLT, every feed it serves in our sample does. Acast feeds pointed to /global/feed/rss.xslt or /template/rss.xsl, Audioboom feeds to audioboom.com/feeds.xsl, and the single Fireside feed to /feed.xsl. The two charts differ. On the US chart, 12 of 99 feeds used XSLT (12.1%); among the 87 shows found only on the UK chart, 28 did (32.2%), because Acast hosts more of them.

Two spot checks outside the sample: two of three Buzzsprout feeds we opened point to rss.buzzsprout.com/styles.xsl, and a Transistor feed now carries a CSS stylesheet. A podcast whose host is not in our chart sample should be checked directly; the section on buying a placement below shows how.

Do Podcast Apps Stop Working?

No. Podcast apps read the XML itself and ignore the stylesheet line, so Apple Podcasts, Spotify and other apps are unaffected. Transistor says of its change that “nothing in your feed changes for Apple Podcasts, Spotify, or any other app” (Transistor). Chrome’s notice adds a related point for sites that use its suggested polyfill script, which it says should not stop RSS readers parsing the feed (Chrome for Developers). Downloads, chart placement and subscriber counts do not depend on how a feed looks in a browser.

Who Actually Sees the Change?

People who click a feed link in a desktop browser: a listener who hits “RSS” on a show’s website, a producer checking a guest’s show, or a journalist given a newsroom feed. That audience is small but it overlaps heavily with the people a communications team cares about. A booker vetting a podcast often opens its feed to see episode dates. A reporter subscribing to a company newsroom may click the feed before pasting it into a reader.

The visible problem has already started. Transistor wrote on November 5 that Chrome “has already started showing a warning banner on feeds that use it,” and that “customers saw that banner and assumed their feeds were broken” (Transistor). Podnews described it on November 9 as “a big red error message.” We have not seen Chrome document the banner’s wording, so we do not quote it.

What Are Hosts Replacing XSLT With?

Mostly CSS: a plain stylesheet that browsers will keep applying to XML. Podnews put a CSS stylesheet on its own feed, and Transistor rebuilt its feed page in CSS with cover art, the feed address in a box, an episode list and dark mode (Transistor). We confirmed both feeds now declare type="text/css". There is a cost. Transistor notes that “CSS can’t add an audio player the way XSLT could,” so it sends would-be browser listeners to the show’s website (Transistor). CSS can style the text that is in the feed; it cannot add a sentence the feed does not contain, which is why a CSS page is plainer than an XSLT one.

Chrome’s notice lists other routes for developers: transform on the server and send HTML, use a JavaScript library such as SaxonJS, or add a polyfill script (Chrome for Developers). For feeds, it recommends a <link rel="alternate" type="application/rss+xml"> tag on the HTML site, the autodiscovery method covered in our guide to creating an RSS feed for a company newsroom.

What This Means for Anyone Buying a Placement

For a guest booking or a sponsorship, nothing about reach changes; what changes is the first impression of anyone who checks a show the old-fashioned way. Three practical points follow, and they are our recommendations, not Chrome or host rules.

• Send people to pages, not feeds. In a pitch or a media kit, link a show’s Apple Podcasts or Spotify page or its website. Our guide to embedding a podcast episode covers players that work in any browser.
• Check your own feeds. Open the feed in Chrome, view the source, and look for text/xsl in the first few lines. If it is there and your host offers no CSS option, ask when it will.
• Do not read the banner as a broken feed. A browser warning says nothing about whether apps can fetch episodes. Our explainer on why download numbers mislead covers what does affect counts.

Methodology and Limitations

We pulled the US and UK Apple Podcasts top-100 charts from Apple’s public marketing RSS API, resolved each show’s feed address through the iTunes Lookup API, and fetched the first 8 KB of each feed with a standard command-line client on November 9, 2026, between about 9:50 and 9:55 a.m. ET. We counted any xml-stylesheet line with an XSL type. Four limits apply. First, chart shows are large shows, so smaller hosts are under-sampled. Second, the hostname after redirects stands in for the host company. Third, a host can change its feeds at any time; our count is a snapshot. Fourth, we did not test how each browser renders each feed.

Conclusion

The change is cosmetic for apps and real for people. About a fifth of the chart feeds we checked will show Chrome users a plain or warning-topped page unless Acast, Audioboom and Fireside switch before Chrome 158 reaches users on November 17. The next date after that is August 17, 2027, when Chrome 176 ends the enterprise and origin-trial exceptions.

Frequently Asked Questions

Sources and Methodology

This explainer is built from Chrome’s XSLT deprecation notice, Transistor’s November 5, 2026 changelog, the Podnews newsletter of November 9, 2026, and our own scan of 186 podcast RSS feeds drawn from Apple’s US and UK charts on November 9, 2026. The host table, percentages and day counts are our arithmetic. Advice on media kits and pitches is our recommendation. We did not test rendering in Firefox or Safari.

1. platform documentation Chrome for Developers, Removing XSLT for a more secure browser. Release schedule, what stops working, CSS exception, usage figures, security quote, Firefox and WebKit plans, migration routes. Read November 9, 2026.
2. vendor Transistor, Making your podcast RSS feed look good in the browser. November 5, 2026 switch to CSS, warning banner, app impact, audio-player limit. Read November 9, 2026.
3. trade press Podnews, Podnews newsletter, November 9, 2026. Chrome’s “big red error message” on XSLT feeds; Podnews’s own CSS feed. Read November 9, 2026.
4. official Apple, Apple Marketing Tools RSS feed generator (top podcasts, US and UK). Chart lists used for our sample, updated 14:53 GMT, November 9, 2026. Read November 9, 2026.
5. official Apple, iTunes Search and Lookup API. Feed addresses for each charting show. Read November 9, 2026.
6. standards W3C, XSL Transformations (XSLT) Version 1.0. XSLT 1.0 became a W3C Recommendation on November 16, 1999. Read November 9, 2026.
7. standards W3C, Associating Style Sheets with XML documents. The xml-stylesheet processing instruction and its type attribute. Read November 9, 2026.
8. live read Acast, Audioboom, Fireside, Buzzsprout, Feed stylesheet files (Acast rss.xslt shown; audioboom.com/feeds.xsl, feeds.fireside.fm/feed.xsl, rss.buzzsprout.com/styles.xsl). Confirmed each stylesheet file is live and served as XSLT. Read November 9, 2026.