Chrome Extension Update Alerts: Track Version, Date and Owner Changes
A Chrome Web Store listing shows the version, the Updated date and who offers the extension, but no changelog. Here is a rule that alerts on new versions and new owners and skips rating noise.
By AyeWatch Team4 min read
Short answer: A Chrome Web Store listing shows each extension's version and Updated date in its Details section, with no changelog and no way to follow it. Chrome installs updates silently. To get an alert, put an AyeWatch web page monitor on the listing with a rule for a new version, a new owner under Offered by, or a privacy change.
What a Chrome Web Store listing shows
We read the listing for uBlock Origin Lite on 21 November 2026. It opened without signing in. The top of the page shows the rating (4.5 from 3.9K ratings, with a note that "Ratings are updated daily"), the user count (23,000,000 users) and a line saying it follows recommended practices for Chrome extensions. Then comes the overview text.
The Details section is the part to monitor. It read: Version 2026.1116.1650, Updated November 17, 2026, Offered by Raymond Hill (gorhill), Size 8.68MiB, 60 languages, a developer email and a non-trader notice. A Privacy section says what the developer has disclosed about data use. There was no changelog, no "what's new" text and no follow or notify button anywhere on the listing.
How Chrome handles updates
Chrome's developer docs say the browser checks installed extensions for updates every few hours. The Web Store docs say each new version must have a larger version number than the one before, and that when an update needs more permissions, users are prompted to accept them or disable the extension. Apart from that prompt, updates arrive without telling you.
That is fine for most people. It is a problem for anyone who needs to know what changed: a security team that allows a list of extensions, a developer whose product depends on another extension, or a business that competes with one.
The field most people miss: Offered by
A version bump is routine. A change in who offers the extension is not. An extension can change hands, and whoever owns it can publish an update to every user. The listing shows the owner in Offered by and the developer contact below it. A rule that alerts on either one changing is the cheapest early warning you can set up for that risk.
The rule and a sample alert
Paste the listing link, which looks like chromewebstore.google.com/detail/name/ followed by a long ID, into a web page monitor.
Sample rule. "Alert me when the Version or Updated date changes, when Offered by or the developer contact changes, or when the Privacy section changes. Ignore changes to the user count, the rating and the number of ratings. Put an owner change first in the headline."
Sample alert. The headline reads "TabTidy: new owner, and version 3.8.0." The summary says Offered by changed from TabTidy Labs to Brightline Media Ltd, the developer email moved to a new domain, the version went from 3.7.2 to 3.8.0 with an Updated date of 2 March, and the Privacy section now says the extension collects website content. It links to the listing. TabTidy and Brightline Media are invented.
Getting the release notes
The listing has no changelog, so the notes live wherever the developer publishes them: a GitHub releases page, a blog or a changelog on their site. Add a second page monitor there. For a GitHub-hosted extension, how to monitor an open-source project covers the releases page and feed, and the changelog monitor page covers the rest.
Pace and cost
Daily checks use 30 credits a month per extension. A security team with 20 approved extensions checked daily uses 600, more than Pro's 500, so check every other day on Pro (300 credits) or move to Pro+ with 1,500 credits. AyeWatch Pro is $9/mo with 50 topics and hourly checks; Pro+ is $19/mo with 200 topics and ASAP mode. Every plan starts with a 7-day free trial. Paid plans send alerts to email, Slack or a signed webhook, so an owner change can open a ticket.
What this can't do
It reads the public listing, not the extension's code. It can't diff the package, list the permissions an update asks for, or block an install. For managing extensions across a company, the listing itself points admins to Chrome Enterprise Core. If you came here looking for a Chrome extension that monitors web pages, that is a different question; see Chrome extension website monitor alternatives.
| Listing field | What a change means | Alert on it? |
|---|---|---|
| Version | A new release | Yes |
| Updated | The date the new version was published | Yes |
| Offered by and developer contact | Possible new owner | Yes, first in the headline |
| Privacy section | New data use disclosed | Yes |
| Users, rating, number of ratings | Normal daily movement | No, tell the rule to ignore it |
Start a monitor in under a minute
Describe a topic or paste a URL. Cancel before the trial ends and you pay nothing.
Try it free for 7 daysThe bottom line
List the extensions you depend on, paste each listing into a page monitor with a rule that puts owner changes first and ignores ratings, and add the developer's release notes page for the two or three that matter most.
FAQ
Can I get notified when a Chrome extension updates?
Chrome doesn't offer this on the listing. Put an AyeWatch web page monitor on the Chrome Web Store listing with a rule for Version and Updated date changes.
Where is the changelog for a Chrome extension?
The Web Store listing has none. Look for the developer's GitHub releases page, blog or site, and monitor that page too.
How often does Chrome update extensions?
Chrome's developer docs say the browser checks installed extensions for updates every few hours.
How do I know if a Chrome extension was sold?
Look for a change in the Offered by field or the developer contact on the listing. An AyeWatch rule can put that change first in the alert.
How many extensions can I monitor on Pro?
Pro has 50 topics and 500 credits a month. Daily checks use 30 credits per extension, so about 16 extensions fit, or more if you check every other day.
