作者抽查 45 個 Shopify 店面,73% 仍載入將於 2027 年 3 月 1 日停用的 ScriptTag
73% of the Shopify stores I checked still load scripts that stop on 1 March 2027
作者抽查 45 個公開 Shopify 店面,發現 33 個(73%)仍載入至少一個 ScriptTag。
Disclosure: I build Citebeam, and the free checker linked below is mine.
Shopify will stop injecting ScriptTags into storefronts on 1 March 2027. I wanted to know how many real stores still depend on them, so I measured it: of 45 public Shopify storefronts I checked, 33 (73%) still load at least one ScriptTag. I built a free checker for this at Citebeam, an independent Shopify app (not affiliated with Shopify). You paste a store address and it shows what will stop and what to ask your vendors. This post is the data behind it, and the two-minute manual version if you would rather not use any tool.
What is changing
From the Shopify developer changelog (published 24 August 2026):
- Since 1 October 2026, apps can no longer create or update ScriptTags.
scriptTagCreateandscriptTagUpdatereturn an error, and the REST resource rejectsPOSTandPUT. This applies to all API versions, so pinning an old version does not defer it. - Existing ScriptTags keep running until 1 March 2027, when Shopify stops injecting them into storefronts.
- The
scriptTagsquery andscriptTagDeletestill work, so apps can audit and clean up. - The replacements are app embed blocks in a theme app extension (for general JavaScript) and web pixels (for analytics and conversion tracking only).
This covers ScriptTags scoped to the online store. Scripts on the order status page fall under a separate, earlier deprecation.
How I measured it
- 45 stores: one theme demo store plus 44 drawn at random from a list of live stores (30 on custom domains, 14 on
*.myshopify.com). - For each store I fetched only what any visitor can fetch:
robots.txt, the public home page, and/account/login(only where robots.txt allows it). Honest user agent, robots.txt respected, no retries, no proxy. - Shopify injects ScriptTags into the page head as an
asyncLoadfunction with avar urls = [ ... ]list. That list parsed as JSON on all 33 pages that have it. I counted the URLs in it.
Limits, so you can weigh the numbers: I looked at the home page only, so scripts that load on other page types are not counted. The sample is small, and it leans toward smaller stores. The list shows what a store injects, not which app owns it, so I can only name the host a script is served from. I could not compare against any store's admin.
What I found
- 33 of 45 stores (73%) inject at least one ScriptTag. 12 (27%) have none.
- 95 ScriptTag URLs in total. Among the stores that have any: median 2, mean 2.9, max 11 in a single store.
- 29 of 45 stores (64%) also load at least one theme app embed asset, so many stores are mid-way: some apps already moved, some did not. 26 stores have both.
- Most common hosts the scripts are served from, by number of stores:
nfcube.com8,chimpstatic.com6,hextom.com5, andtrustpilot.com,avada.ioandprintful.com3 each. Another 25 or so domains appear once: chat, reviews, pop-ups, back-in-stock, email capture, upsell, affiliate and analytics apps.
A script served from a vendor's domain does not mean that vendor has not migrated. Many vendors already offer an app embed, and the old ScriptTag may just be a leftover. For any domain you see, check with the vendor.
What actually breaks
A ScriptTag is how many older apps put something on your storefront without editing the theme: a pop-up, a chat bubble, review stars, a back-in-stock form, an upsell. When injection stops, whatever that script drew or did stops loading, unless the app has moved to an app embed. And even after a vendor ships an app embed, it is off until someone switches it on in the theme editor. A vendor saying "we migrated" and your storefront showing the widget are two separate facts.
Check your own store in two minutes (no tool needed)
- Open your home page in a private window, view the page source (Ctrl+U or Cmd+Option+U).
- Search for
asyncLoad. - Right below it you will see
var urls = [ ... ]. Every URL in that list is a ScriptTag. If the block is not there, you have none on the home page. - Look at the domains and match them to apps you installed. Theme app embeds look different (
cdn.shopify.com/extensions/...) and do not appear in that list.
Or let the free checker do the reading: paste your store address, no sign-up. It makes two requests to your public storefront, lists the ScriptTags with the vendor host behind each, shows any theme app extensions, and checks the legacy account question below. It is free, and it only reads pages any visitor can open.
What to do about it
- Ask each vendor which of its features use a ScriptTag today and what its plan is for 1 March 2027. You want to hear "app embed" or "theme app extension" and a date.
- Switch on the app embed in the theme editor once the vendor ships it, and test the page.
- Analytics and conversion scripts should move to a web pixel, which needs no action from the merchant.
- If a vendor has no plan, you have until 1 March 2027 to replace the app, which is a lot easier in November than on 28 February.
One more deadline: legacy customer accounts
Shopify deprecated legacy customer accounts on 26 February 2026. The final sunset date is to be announced later in 2026. In my sample, 8 of the 43 stores I could read (19%) still showed the classic login form, the signal that a store is still on legacy accounts (the other 35 redirect to the new sign-in; 2 stores' robots.txt does not allow /account/login, so I did not fetch it). The checker reports this too.
If you look after more than one store
Agencies and freelancers can run the same check across a whole client list with the Apify actor Shopify Script Tag Checker. Give it a list of store domains (or a CSV link) and you get one row per store: a risk level, the ScriptTags and the vendor hosts behind them, the number of app embeds, whether the store is still on legacy customer accounts, and plain-English next steps. It checks a store for $0.01, so a 50-store client list is 50 cents, and stores it cannot check are free. It is going public on the Apify Store now.
You can see a public example run here: Will 20 Shopify stores break on 1 March 2027?. And here is a short YouTube walkthrough of the checker.
Your next step
- Check one store now: free ScriptTag checker.
- Run it on every client store: Apify actor.
- Forward this to the person who installed the apps, and put "ask vendors about 1 March 2027" on this week's list.
The deadline is fixed and the vendor answers take time. A short list of questions sent today beats a broken storefront in March.
Written with AI assistance.
來源:DEV Community · dev.to