Catch Broken JavaScript, Not Only Broken Layouts

A plugin update runs overnight. The next morning every page looks exactly like yesterday. But the contact form’s send button does nothing, the payment step of your checkout throws an error, and your analytics stopped counting. A screenshot comparison cannot see any of this, because nothing moved on the screen.

Broken JavaScript leaves a trace in the browser console, the place where browsers write script errors. WebChange Detector reads that console on every check and tells you when a new error shows up. This guide explains what is recorded, how we keep it from turning into noise, and where you find console changes.

What WebChange Detector Records

While a page loads for its screenshot, we collect the JavaScript errors and page errors that come from your site itself. General browser noise is filtered out, while mixed-content warnings (a secure page loading an insecure file) are kept on purpose, because they are a security signal.

We then compare the console of the “before” screenshot with the console of the “after” screenshot and report two things:

  • New entries (+): errors that were not there before. These are the ones to look at.
  • Removed entries (-): errors that are gone. Usually good news, for example after a fix.

This works for every type of check: On-Demand Checks, Auto Update Checks and Monitoring.

Why It Does Not Flood You

A console that reports every tiny difference would be useless after a week. So the comparison is built to report real changes only:

  • Redeploys do not count. When your site ships a new build, file names, cache busters and line numbers inside an error change. We ignore those parts. An error only counts as new when its message or the functions behind it change.
  • Flickering errors are reported once. Some errors come and go between visits. Such an error is reported when it first shows up and then stays quiet: it counts as new only when it was missing from the last three checks of that page and device.
  • You still see the real error. The entry you read always shows the original message from your site, not a cleaned-up version.

How Our AI Judges Console Changes

When your plan includes our AI verification, a new console error gets the same scrutiny as a visual change before it becomes an alert. Clearing a site’s cache often renames script files and changes ids inside error messages, so a long-known error can look new after every update. The AI checks for exactly that: if the wording is the same apart from such changing parts, it is treated as the known error and raises no alert. A different message, a different address or a different status code still does.

With AI verification, the severity shown next to an entry is the AI’s verdict, so an error it recognised as an old one is no longer shown in red.

Where You See Console Changes

In the Web App

Every check has a Browser console section in the panel on the right, below the AI change analysis and the visual changes.

From the run to a single check: the Browser console section sits at the end of the panel on the right.
  1. Open the Checks tab and click a check.
  2. Scroll the right panel to Browser console. A status line tells you what happened: “New Error Console Entries”, “Error Console Entries Removed” or “Console Changes Detected”. If nothing changed, you see “No console changes”.
  3. Each new entry shows its severity, the message and the script it came from. Removed entries are listed with a minus sign.

In the plugin for WordPress

  1. Go to WebChange Detector → Checks and click Show on a check.
  2. Find the Browser Console section next to the screenshot. It uses the same status lines and lists new and removed entries with their source script.

On the Public Link

When you share a check with a client through its public link, the console result is part of that page whenever your plan includes console tracking. Your developer or your client sees the same error you do, without an account. More in Alerts: Get Told, Share with Your Client.

If your plan does not include console tracking, the Browser console section shows a short upgrade note instead.

What to Do with a New Console Error

  1. Read the source. The script address usually tells you which plugin or theme is involved, for example a path containing the plugin’s folder name.
  2. Test the function on the live page. Send the form, add a product to the cart, open the menu. Does it still work?
  3. Mark the check. Set it to To fix so your team knows it is open (see How to Review Checks).
  4. Fix or roll back the update that caused it, then run an On-Demand Check to confirm the error is gone. It then shows up as a removed entry.

If the message turns out to be harmless and you cannot change the script that writes it, for example a warning from a third-party widget, create a feedback rule for it. Teach the AI What to Ignore shows how.

WebChange Detector Newsletter

News, feature Updates, and insights.
No spam. Unsubscribe anytime.