Chrome sends users to it itself: an XSLT patch extension out-ranks Google engineers on the official search page
What it is A free Chrome extension that brings XSLT back into the browser, so pages like RSS feeds, sitemaps, e-invoices and remote desktop web portals keep displaying after Chrome removes the feature. It also bundles an XML viewer and an XSLT tester.
Why it took off Chrome shows a red warning bar on pages that use XSLT, linking to a store search for "XSLT Polyfill". The extension puts that exact term in its title, and its description, screenshots and ratings are better than the official one's, so it ranks first and catches the traffic the platform sends.
CHow you could follow it Don't follow this one; learn the playbook. Watch each platform's deprecation timeline, look for events where the official alternative is "install something from the store" and the official option is bare-bones, and ship 6 to 8 weeks before the cutoff with a title that grabs the term the official page names. The nearest open window is Edge, which doesn't drop XSLT until December.
40,000 users · rating 4.714285714285714 (14)
Chrome 158 removes XSLT in Nov 17 2026. Starting late September, every page that uses XSLT shows a red warning bar at the top, and the words "install a browser extension" link straight to a Chrome Web Store search for "XSLT Polyfill". A free extension called "XSLT Browser Support", first listed Oct 2, ranks first on that search page, ahead of the official extension Google's engineers built. It grew to 40k users in 5 weeks. It didn't win on features; it won on its listing page. Below: where this traffic comes from, how the extension captured it, where the money is, and why this window is already closing.
An IT notice and a red warning bar
In Nov 5, Dartmouth College's IT help desk published a knowledge-base article titled "Using RDWeb after XSLT deprecation (11/17/2026)". The first line reads: "Starting Nov 17 2026, RDWeb may fail to load in Microsoft Edge and Google Chrome... This is an industry-wide change, not a problem with your computer or account." The school's official advice: switch to Firefox.
RDWeb is Microsoft Remote Desktop's web portal, used by companies, hospitals and schools worldwide. Its pages use XSLT in the browser to render the XML the server returns. Microsoft published KB5130994 about it in October. Anyone who opens it from Sep 22, when Chrome 154 reached stable, sees a red bar at the top of the page:
This site uses XSLT; that functionality is being removed from this browser very soon… You might be able to install a browser extension that allows you to continue viewing it.
Clicking "install a browser extension" leads to a Chrome Web Store results page for "XSLT Polyfill". The link is hardcoded in Chromium's source; an article on ortamarco.me that checks it line by line cites the original commit. As of Nov 6, the first result on that page is XSLT Browser Support; the second is XSLT Polyfill, the one Chrome's official docs name.
What it is
A free Chrome extension that compiles libxslt (the same XSLT engine Chrome used to ship) into WebAssembly and runs it in the browser, so pages that depend on XSLT keep working after Nov 17: styled RSS and sitemaps, e-invoices, government and legal documents, library catalogs, and intranet reports. Nothing to configure after install.
Beyond the patch, it adds an XML tree viewer that handles large files, an XSLT Studio tester (live preview, parameter passing, xsl:message output), local file support, and a timeout that stops stylesheets that run away.
The developer is credited as seokadabra.com, a small brand that makes free SEO browser tools. Under the same account there's another SEO-checker extension with 506 users, and in Nov 3 it also launched a page SEO audit tool.
The numbers: the closer the cutoff, the faster it grows
| Date | users | Score |
|---|---|---|
| 10-04 | 287 | 1 |
| 10-08 | 1,000 | 3 |
| 10-16 | 4,000 | 4 |
| 10-29 | 10,000 | 5 |
| 11-01 | 20,000 | 8 |
| 11-04 | 30,000 | 9 |
| 11-06 | 40,000 | 14 |
(Chrome Web Store listing and extension stats site extops.dev. Store user counts are coarse; read them for trend only.)
The first 4 weeks it reached only 10k, then after November it added 10k every two or three days. The closer to Nov 17, the faster it climbed, a textbook deadline-driven curve. After Nov 17, pages actually broke, and the warning bar turned into a real blank screen, so there may be another jump (inferred).
You can gauge how big this traffic was from the official extension: XSLT Polyfill had only 6,000 users on Sep 28. After the warning bar reached stable, it jumped to 70k by Oct 4, reached 100k by Oct 13, and the store has shown "100,000" ever since. In other words, one warning bar drove installs in the 100k range within two weeks (extops.dev).
These users also almost never uninstall. They installed because a page they need for work broke, and as long as RDWeb or the invoicing system hasn't changed, the extension stays.
Where users come from: the term the official page names, ranked first
The main channel is Chrome itself. Warning bar → store search page → first result. As of Nov 6, the top results for "xslt polyfill" were: ① XSLT Browser Support ② official XSLT Polyfill ③ XSLT Prism ④ XSLT Fix ⑤ XMLNest. Searching "xslt" also puts it first.
Why it can rank above the official one. Put the two listing pages side by side and the difference is obvious:
| XSLT Browser Support | Official XSLT Polyfill | |
|---|---|---|
| Title | XSLT Browser Support - XSLT Polyfill, XML Viewer & Tester | XSLT Polyfill |
| Description | Long; opens with "XSLT not working in Chrome? XML page showing raw code instead of the page it used to be?" and names RSS, sitemaps and e-invoices | Short |
| screenshots | 5 screenshots | 1 screenshots |
| Rating | 4.7 (14 reviews) | 4.3 (11 reviews) |
| Permissions | Established publisher | — |
The official docs name "XSLT Polyfill", so it puts that exact phrase in the title, then adds "XML Viewer" and "Tester", terms people also search for. Shipping many features lets the title legitimately stack this many keywords.
The ratings were likely pushed (inferred). On Nov 4, 3 generic five-star reviews appeared in one day. One reads "cool extension to work with xml and xslt files, with seo tools and stuff"; another suggests "use it with AI integration add ons". Accountants and remote workers forced to install an extension because their page broke wouldn't write that. The rating count went from 9 to 14 in a day, and the average rose from 4.56 to 4.71, which held up the ranking.
There's also a web landing page. Its headline is "XSLT Not Working in Chrome? Restore XSLT, View XML & Test", with an FAQ that asks "Why does my XML sitemap look like plain code now?" People searching for the problem online get caught too. A user on a software forum at groups.io posted its store link on their own. Beyond that, it isn't on X, TikTok, or in the press, and I found no ads.
Where the money comes from: nothing yet
The extension is free, with no in-app purchases, the site says "no accounts, no analytics", and there's no pricing page. The likely play is to build installs and credibility for the SEOkadabra developer account and funnel people to the same account's SEO tools (inferred). The extension requests read and write access to all sites, so adding features or monetizing later is technically open.
So this isn't a money-making case; it's a traffic-capture case. 40k "never uninstalled" installs are a foundation that a small browser-tools brand could rarely buy.
Who it's competing with
| Competitors | Launched | Scale (Chrome Web Store, 11-06) | Compared with alternatives |
|---|---|---|---|
| XSLT Polyfill (official, by Google engineer Mason Freed) | 2025 years | 100,000 users, rated 4.3 | Named in Chrome's docs and open source, but patch-only, bare listing page, second in search |
| XSLT Prism | 10-10 | 7,000 users, rated 5.0 / 25 reviews | Copies its title and selling points nearly word for word, 8 days late |
| XMLNest | 10-17 | 3,000 users | XML reader as the main product, 55 languages, content on the official site |
| XML Viewer & Formatter … XSLT Polyfill | October | 808 users | Old viewer that retitled itself to ride the term |
| XSLT Loom, XSLT Fix, XSLT Bridge and others | Late October to November | Tens to a hundred or two | Arrived too late |
| Enterprise policy XSLTEnabled and Microsoft's KB workarounds | Since March | — | Usable by IT admins, expires August 2027; not usable by ordinary visitors |
At least 8 similar ones have appeared since Oct 10. They're fighting for the same top-three slots on the same search term, and those who arrived two weeks later mostly have only dozens of users.
If it were you
C: learn the playbook, don't copy this one. It shows something valuable: when a platform removes a feature and writes the workaround as "go search the store for a term," the official page is effectively giving that term free traffic, and whoever has the best listing page captures it. But this XSLT wave has only 11 days left before the cutoff, 8 copycats already crowd the same search term, the top two sit on 140k users, and this kind of extension charges nothing.
Who it suits: people building browser extensions, apps or WordPress plugins who understand store SEO and already hold a developer account they want to grow installs on.
Who it doesn't suit: people hoping to make money from this one directly. These users installed only to get a page working and won't pay for it.
How to do it: use it as a template and go find the next one. Watch Chrome's deprecation schedule (chromestatus.com), Edge's release plan, Android and iOS API removals, and WordPress core deprecations. Look for events that meet three conditions: the affected users are mostly not developers; the official fix is "install something"; and the official something is bare-bones. Ship 6 to 8 weeks before the cutoff, copy the term the official page gives, add two or three related high-volume terms, open the description with the question users actually ask ("X not working in Chrome?"), fill every screenshot slot, and build a web page that answers that question. The nearest window that isn't fully crowded yet is Edge: Edge doesn't drop XSLT until the week of Dec 10 159, and as of Oct 23, XSLT Polyfill wasn't yet in Edge's extension store (ortamarco.me). Whether Edge users' warning bars link somewhere else, and what the Edge store looks like now, are unverified.
How to get users: no paid acquisition needed, the platform supplies the traffic. You only need to do two things: take the top search spot for that term as early as possible, and get the first real users to leave ratings.
When to get in: each event like this has a window from "warning appears" to "one to two weeks after the cutoff." This time Chrome's window closed by the end of November.
What would show this read is wrong: (1) after Nov 17 it and the official extension multiplied several times over, and later entrants still got tens of thousands of users, meaning this wave is longer than it looks and following it was still worth it; (2) it starts charging, or funnels users to a paid SEO tool that people actually buy, showing this install volume can turn into money, so the grade should go up; (3) the Chrome store starts pinning the official extension to first place for these searches, and the playbook stops working.
---
Data & sources: Chrome Web Store detail page, reviews page, search page (11-06); extops.dev user curve; Chrome deprecation doc developer.chrome.com/docs/web-platform/deprecating-xslt and chromestatus; two ortamarco.me articles on XSLT removal (original banner text and link, Edge timeline); xsltplayground.com; Dartmouth College IT knowledge base (11-05); securityonline.info (10-12); Microsoft KB5130994; seokadabra.com official site. Places marked "inferred" or "unverified" are inferences or unverified.
Research notes: competitor table, acquisition evidence, full research report
- Competitors
Name Where Launched Scale How it differs from this one XSLT Polyfill (official extension by Google engineer mfreed7) Chrome 2025 100,000 users, 4.3 points/11 ratings Named as the recommended option in official docs, open source, patches only; store page is bare (short title, 1 screenshots), ranks #2 for "xslt polyfill" search XSLT Prism Chrome 2026-10-10 7,000 users, 5.0/25 ratings Same stack (libxslt WASM + viewer + tester), copies this product, launched 8 days later XMLNest Chrome 2026-10-17 3,000 users, 4.5/15 ratings Positioned as an XML reader (sitemap tables, podcast player), 55 languages, website doing content SEO XML Viewer(legopflakafagikcpiapgnbokgkbejlk) Chrome 2019 300,000 users, rated 2.4 Just a general XML viewer, does not restore XSLT XSLTEnabled enterprise policy / Origin Trial / Microsoft KB5130994 Big-company features From ¥2026-03 — Only usable by admins or site owners, until 2027-08 expires; ordinary visitors can't use it mfreed7/xslt_polyfill site-side script Open source 2025 — Requires site owners to change code; many unmaintained sites and devices can't be changed Firefox version of XSLT Polyfill Other Not checked Not checked Firefox hasn't removed XSLT yet, low demand - Where users come from
- Verified Platform event: Chrome banner → Store "XSLT Polyfill" search page: Chrome's official docs say the banner links to the extension search page; ortamarco.me states it links to chromewebstore.google.com/search/XSLT%20Polyfill; 2026-11-06 live-checked, the top result for this search is this product
- Verified Store search SEO (keyword title, long description, 5 screenshots, Established publisher): ranks #1 for both "xslt" and "xslt polyfill", ahead of the official extension; title stuffs in XSLT Polyfill, XML Viewer, Tester
- Inferred Web SEO landing page: seokadabra.com/xslt-browser-support/, page title "XSLT Not Working in Chrome?", with FAQ; a groups.io forum has users recommending the store link on their own
- Inferred Incentivized reviews: 11-04 generic five-star reviews in one day (Bald Streak / Aditya Jain / Bharat Modi), rating count 9→14 with 3 reviews
XSLT Browser Support - XSLT Polyfill, XML Viewer & Tester (Chrome extension) research report
- Store page: chromewebstore.google.com/detail/xslt-browser-support-xslt/g…
- Developer: seokadabra.com (SEOkadabra, a brand making free SEO browser tools, [email protected]); official landing page www.seokadabra.com/xslt-browser-support/
- Launched 2026-10-02, v1.0.4 (2026-11-02 update), free, collects no data, no in-app purchases, no pricing on the official site; store shows the "Established publisher" badge (chromestore library established=True)
- Current status (2026-11-06): 40,000 users, 4.7 points / 14 ratings (store page HTML live-scraped)
Bottom line
Chrome 158 (2026-11-17) officially removes XSLT. From Chrome 154, Chrome shows a red warning banner at the top of pages that use XSLT, with the words "install a browser extension" linking directly to the Chrome Web Store search results for "XSLT Polyfill". This extension ranks first in that search (and in the search for "xslt"), ahead of the official extension by Google engineer Mason Freed. Its users are basically traffic Chrome sent over, and it won the top spot in that traffic.
1. Timing: the platform event gave it traffic
Chrome's official deprecation timeline (https://developer.chrome.com/docs/web-platform/deprecating-xslt):
- Chrome 142 (2025-10-28): console starts warning; Chrome 143 officially announces deprecation
- Chrome 146 (2026-03): enterprise policy XSLTEnabled launched; Chrome 152 (2026-08): Origin Trial launched
- From Chrome 154: a red warning banner appears at the top of pages using XSLT: "This site uses XSLT; that functionality is being removed… You might be able to install a browser extension…" Chrome 156 (2026-10-20 into Stable) translated the banner into multiple languages and added a close button (source: ortamarco.me/en/blog/chrome-removes-xslt-what-breaks/)
- Chrome 158 (2026-11-17): XSLT disabled on the Stable channel; Chrome 176 (2027-08-17) enterprise policy and Origin Trial also stop working
- Edge follows (Edge 159, December); Firefox / WebKit also say they will remove it (chromestatus)
Official docs quote: "when XSLT is disabled, Chrome now shows a warning banner that links directly to an extension search page". The "Chrome extension" link in the docs also points to chromewebstore.google.com/search/xslt%20polyfill, not to a specific extension. The ortamarco.me article is more specific: the link in the banner is chromewebstore.google.com/search/XSLT%20Polyfill. This is secondhand; I could not verify it in the Chromium source.
Many people are affected, and most aren't developers:
- Microsoft RD Web Access (remote desktop web portal). Microsoft issued KB5130994 and Message Center notice MC1491832 (2026-10-08) for this; securityonline, askwoody, Dartmouth and other IT knowledge bases have covered it; several r/sysadmin threads discuss the banner appearing on RDWeb
- Styled sitemaps, RSS and podcast feeds on WordPress / Yoast and similar
- E-invoices (Italian FatturaPA, UBL, Turkish e-Fatura, etc.), government and legal documents, library catalogs
- Enterprise intranet systems and embedded devices: vendors including Acumatica, Nintex, SharePoint classic views, InterSystems and Aras have published notices
2. Growth data
User curve (recorded by extops.dev, extops.dev/extensions/gnkkhnfelideebkkoehcdkkphmhmonka; points from 11-01 onward match our chromestore library item_snap):
| Date | users | Score |
|---|---|---|
| 10-03 | Launched | 0 |
| 10-04 | 287 | 1 |
| 10-08 | 1k | 3 |
| 10-16 | 4k | 4 |
| 10-23 | 6k | 5 |
| 10-29 | 10k | 5 |
| 11-01 | 20k | 8 |
| 11-04 | 30k | 9 |
| 11-06 | 40k | 14 |
- Listed for 4 weeks and reached 10k users; from Nov 1 it added 3k users every 2 to 10 days. Growth accelerates the closer it gets to 11-17, matching a deadline-driven curve
- Compare the official extension XSLT Polyfill (hlahhpnhgficldhfioiafojgdhcppklm): at 2026-09-01 it had 2k, at 09-28 it had 6k, then jumped to 70k at 10-04, reached 100k at 10-13, and the store has shown 100,000 ever since. The jump at the end of September lines up with Chrome 154 shipping the banner into Stable (around 09-22), which suggests the banner-driven traffic was on the 100k scale. The official extension has stayed at "100,000" since, which may be a store display quirk (the scale is coarser above 100k) or may be because someone else took the top search spot. Neither is verified.
- This kind of traffic barely retains: users install it because a page broke, then leave it alone (no setup). As long as RDWeb, e-invoice pages and similar stay unchanged, the extension won't get uninstalled
3. Acquisition channel breakdown
- Chrome banner → store search page → #1 result (main channel, mechanism confirmed, share not verified). 2026-11-06 I live-checked the store search page:
- Search "xslt": ① this product ② XSLT Tester ③ official XSLT Polyfill ④ XSLT Prism ⑤ XSLT Loom ⑥ XSLT Fix ⑦ XMLNest …
- Search "xslt polyfill" (the term the banner and official docs link to): ① this product ② official XSLT Polyfill ③ XSLT Prism ④ XSLT Fix ⑤ XMLNest ⑥ XML Viewer & Formatter… ⑦ Cabo Verde ⑧ XSLT Loom
Likely reasons it ranks first: the title is packed with keywords (XSLT Browser Support + XSLT Polyfill + XML Viewer + Tester); the long description includes sentences users actually type, like "XSLT not working in Chrome?", along with scenario terms such as RSS, sitemap and e-invoice; it has 5 screenshots; it carries the "Established publisher" badge; rating 4.7. The official extension's title is just "XSLT Polyfill", its description is very short, it has only 1 screenshots, and its rating is 4.3.
- SEO landing page (confirmed to exist, traffic share not verified). The page title of seokadabra.com/xslt-browser-support/ is "XSLT Not Working in Chrome? Restore XSLT, View XML & Test", with an FAQ ("Why is XSLT not working in Chrome?" / "Why does my XML sitemap look like plain code now?"). When I searched Jina for "XSLT Browser Support", this page and the store page both ranked near the top. Users in the ZTreeWin groups.io forum have recommended the store link on their own.
- Suspected review farming (unconfirmed). 11-04 got 3 generic five-star reviews in a single day, from Bald Streak, Aditya Jain and Bharat Modi. One says "with seo tools and stuff", another "use it with AI integration add ons". The tone doesn't read like ordinary users who came in because the page was broken. The rating count went from 9 to 14, and the score from 4.56 to 4.71. That directly lifts its store ranking.
- What I didn't find: no relevant discussion on X (x-radar returned 60 results over the last 0 days for both "XSLT" and "seokadabra"). No threads naming this extension on Reddit or HN; Reddit blocks scraping, so Reddit coverage is incomplete. No ads or TikTok found, and no media coverage.
4. Competitors
| Name | Channel | Launched | Scale (2026-11-06) | How it differs from this one |
|---|---|---|---|---|
| XSLT Polyfill (official, mfreed7) | Chrome | 2025 years (already 2k in early September) | 100,000 users, rated 4.3 / 11 reviews | Recommended by name in Chrome's docs. Open source, patch only. The store page is bare, but it ranks #2 for "xslt polyfill" searches. |
| XSLT Prism - XSLT Polyfill, XML Viewer & XSLT Tester(xslt-polyfill.com) | Chrome | 2026-10-10 | 7,000 users, 5.0 / 25 reviews | Title structure and selling points (libxslt WASM + viewer + tester) are nearly copied from this one. Listed 8 days later. |
| XMLNest – XML Viewer & XSLT Polyfill(xmlnest.com) | Chrome | 2026-10-17 | 3,000 users, 4.5 / 15 reviews | Mainly an XML reader (sitemap tables, podcast player) in 55 languages. Does SEO through content on its website. |
| XML Viewer & Formatter: Tree, Table, Excel Export & XSLT Polyfill(devarq.dev) | Chrome | 2026-10 | 808 users | An old XML viewer that added XSLT keywords to ride this traffic. |
| XSLT Polyfill — Cabo Verde(ai-solutions.cv) | Chrome | 2026-11 | 193 users | Only serves one government portal in Cape Verde. |
| XSLT Loom(xsltpolyfill.com) | Chrome | 2026-11-02 | 79 users | Pushes RSS, sitemaps, and e-invoices. Listed a month later. |
| XSLT Fix (devrim.me), XSLT Bridge (zingersoftwaresolutions), Sitemap XSLT Table Viewer | Chrome | Late 2026-10 to November | Nothing under 100, or the store doesn't show it | Copycats |
| XSLT Tester | Chrome | Old extension, last updated 2023 years ago | 1,000 users | Just a tester, but it ranks #2 when you search "xslt" |
| XML Viewer(legopflakafagikcpiapgnbokgkbejlk) | Chrome | 2019 | 300,000 users, rated 2.4 | Just a general XML viewer, doesn't restore XSLT |
| Firefox version of XSLT Polyfill | Firefox | — | Not checked | Firefox hasn't removed XSLT yet |
| Enterprise policy XSLTEnabled, a site Origin Trial, Microsoft KB5130994 | Big-company features | From ¥2026-03 | — | Admins or site owners can fix it themselves, but 2027-08 is the deadline. Regular users can't. |
| Site-side polyfill script (github.com/mfreed7/xslt_polyfill) | Open source | 2025 | — | Site owners can change one line, but many sites have no one maintaining them. |
5. What's the differentiation, and is it why it broke out?
- Feature gap: the official extension only does "automatically apply the polyfill." This one uses the same libxslt (compiled to WASM) and adds: a per-site button to restore XSLTProcessor, an XML tree viewer that stays smooth on large files, XSLT Studio (editing, preview, parameters, xsl:message), local file support, badges and popups for processing results, timeouts that stop runaway stylesheets, and compatibility with legacy encodings.
- But the main reason it ranks is not the features. It's that its store listing is better than the official one. These points all show it: users arrive on its search page straight from Chrome's warning bar. Most people who install it are RDWeb users and non-developers like accountants, who have no use for XSLT Studio. The official extension has 100k users and is the one Chrome's docs name. This one ranks first because of keywords in the title and description, screenshots, ratings, and badges, all store SEO. The extra features mainly serve two purposes: they let the title and description legitimately include high-volume terms like "XML Viewer" and "Tester," and they support the ratings.
- The developer makes SEO tools (SEOkadabra), which is exactly their field.
6. How many people see it right now
- The extension itself is "barely known": no media coverage, "0" on X, nothing found on Reddit or HN. Only extension-tracking sites (extops, extensiontracker, extpose, extwatch, chrome-stats) index it.
- But "Chrome removes XSLT" itself has been widely discussed (LWN, ppc.land, r/webdev's "XSLT.RIP," Microsoft KB, and others). Copycats have piled in: since Oct 10, at least 8 similar extensions have appeared, and XSLT Prism copied this one's title word for word.
- The developer has not published any revenue, and the product doesn't charge.
7. Where the money comes from
Not visible. The extension is free, has no in-app purchases, and has no analytics (the official FAQ says "no accounts, no analytics"). The likely play is building install volume and "Established publisher" account credibility for the SEOkadabra brand, then funneling users to the same account's SEO tools: "Site: Seo Check in Google" (506 users) and 11-03 newly listed "Kestrel SEO – On-Page Audit…". The extension requests <all_urls> and scripting permissions, so there's room to add features or monetize later. All of this is speculation, unverified.
8. What to borrow
- Watch platform deprecation timelines. Each time Chrome, Edge, iOS, or Android removes a feature, if the official workaround is "install an extension" or "search for a term," the platform is effectively giving that term free traffic. Whoever takes the #1 spot for that term first catches the wave. Official fixes usually have few features and bare store pages, and they're easy to outdo.
- The listing targets the exact search term the official one names. Both the warning bar and the docs link to "XSLT Polyfill," so this listing puts that phrase verbatim in the title and adds the wording users actually type ("XSLT not working in Chrome?", "XML Viewer"), with multiple screenshots and an early batch of ratings.
- The extra features exist to attach more keywords. A single polyfill can only attach one.
- The window is short: listing 6 to 8 weeks before the cutoff is the sweet spot. This one reached Stable about 10 days after the warning bar went live, but was 1 to 2 weeks ahead of the copycat crowd.
9. Still unclear
- Whether the link in the warning bar really is
search/XSLT Polyfill: the source is a secondhand writeup on ortamarco.me plus the official docs' wording. I did not check the Chromium source. - The day it reached #1 in search: the jump between 10-29 and 11-01 could be from taking the top spot, Chrome 156 localizing the warning bar, the deadline getting closer, or Edge starting to show the warning too. I can't tell which.
- The official extension's real user count: the store's "100,000" may be a coarse bucket.
- Whether the reviews from 11-04 were incentivized or bought.
- Whether enterprises force-install it, which would inflate the user count. Also whether traffic will multiply again after 11-17 (when Stable actually disables it and pages break).
- Whether the developer has a monetization plan.
Sources
- Chrome deprecation docs: developer.chrome.com/docs/web-platform/deprecating-xslt
- chromestatus:chromestatus.com/feature/4709671889534976
- Warning bar details: ortamarco.me/en/blog/chrome-removes-xslt-what-breaks/, xsltplayground.com/blog/chrome-xslt/this-site-uses-xslt-warn…
- RDWeb: securityonline.info/rd-web-access-chrome-xslt/, mc.merill.net/message/MC1491832, services.dartmouth.edu/TDClient/1806/Portal/KB/Article/17367…
- User curves: extops.dev/extensions/gnkkhnfelideebkkoehcdkkphmhmonka, extops.dev/extensions/hlahhpnhgficldhfioiafojgdhcppklm, extops.dev/extensions/lgnkojpgnjbbhiplnahmlfdcneajjfkc, extops.dev/extensions/pacekgoilnidbbfmfechgkpjgcpcokkn, extensiontracker.com/extension/gnkkhnfelideebkkoehcdkkphmhmo…
- Store search rankings and competitor user counts: 2026-11-06 scraped directly from the chromewebstore.google.com search and detail pages
- Our library: chromestore.item / item_snap (2026-11-01~06)
- Official site: www.seokadabra.com/xslt-browser-support/, xmlnest.com
- Reviews: chromewebstore.google.com/detail/xslt-browser-support-xslt/g…