Your footer prints today’s date. Your homepage shows a different customer quote on every visit. A chat script logs the same harmless warning on every page. None of this is a problem, but if every check reports it again, you start skimming your alerts. That is the real danger: the one alert that matters gets lost between ten you already know.
Feedback rules fix that. You tell our AI once that a certain change is fine, and from then on it marks that change as OK instead of raising an alert. This guide shows how the AI judges a change, when a rule is the right tool, and how to create and manage rules in the Web App and in the plugin for WordPress.
How Our AI Judges a Change
When a check finds a difference, our AI looks at every highlighted area of the screenshot and gives it one of three verdicts: OK, Unsure or Alert, together with a short description of what changed. The description quotes the text it read before and after, so you can check the verdict instead of taking it on faith.
A lot of everyday noise is recognised without any help from you: relative times like “4 days ago”, review counts inside third-party widgets, embedded social feeds, sliders caught mid-transition, weather and live data widgets, “Open now” labels and similar content that changes on every page load.
Some things are never waved through on purpose: prices, stock levels, product data, opening hours and dates in your own content always raise an alert, because the AI cannot know whether that change was intended. And if the AI cannot verify a change, it shows it to you rather than hiding it. That is exactly where feedback rules come in: you know your site, so you decide which of these changes are expected.
When a Rule Is the Right Tool
Create a rule when a change is harmless, you have checked it yourself, and it keeps coming back. Typical cases:
- A date or “last updated” line in the footer that changes every day
- A testimonial, quote or featured product that rotates on every visit
- A console warning from a third-party script that you know about and accept
Do not create a rule for a change you are unsure about, or for a real problem you plan to fix later. Set that check to To fix instead (see How to Review Checks). A rule is meant to stay.
What a Rule Does, and What It Does Not Do
A rule describes a type of change on a certain element, for example “testimonial text changed”. On every following check, the AI compares new changes with your rules. When the same element shows the same type of change, the area is marked OK and labelled Auto-ignored by your rule, so it does not trigger an alert.
- Matched by meaning, not exact wording. “Testimonial changed” also covers “a different testimonial is shown”.
- A different problem still alerts. If the whole testimonial section disappears, or the change happens in a different element such as the header navigation, the rule does not apply and you are told.
- Screenshots still run. A rule only changes the verdict after the comparison. The page is still captured and compared as before.
- Console rules ignore one message. A rule created from a console entry makes WebChange Detector skip that message on future checks. Any other new error is still reported.
Choose the Scope
When you create a rule, you decide where it applies:
- Only this URL: for something that exists on one page, like the testimonial slider on your homepage.
- All URLs in (your website): for something that appears on every page, like a footer date or a site-wide chat widget.
When in doubt, start with “Only this URL”. You can widen the scope later on the AI Rules page without creating the rule again.
In the Web App
Create a Rule from a Check
Rules are always created from a real check, so the AI knows exactly which change you mean.
- Open the Checks tab and click the check you want to look at.
- In the AI change analysis panel on the right, find the area you want to ignore. The numbers on the cards match the numbers on the screenshot.
- Click Ignore in future on that card. The button appears on areas marked Alert or Unsure.
- In the window “Ignore this type of change in future?”, choose Only this URL or All URLs in your website.
- Click Confirm. The card now shows Rule created.
For a console message, scroll to the Browser console section of the same check, click Ignore in future next to the new entry, choose the scope in “Ignore this console error in future?” and confirm. The entry then shows Ignored.
Working in MainWP? The add-on lists your checks, but rules are created in the Web App. Log in there with the same account, open the check on the Checks tab and follow the steps above. A rule belongs to the page or the website, so it also counts for the checks you start from MainWP.
Manage Your Rules
Open AI Rules in the left menu. Every rule of your account is listed with:
| Column | What it tells you |
|---|---|
| Status | A switch to pause the rule without deleting it |
| Type | Visual (a screenshot area) or Console (a console message) |
| Description | The type of change the rule covers |
| Scope | “This URL” or “All URLs of website”; click the other option to change it |
| URL and Website | The page the rule was created on and the website it belongs to |
| Created | When you created it |
| Matches | How often the rule has applied, and when it last did |
| Actions | The trash icon deletes the rule |
In the plugin for WordPress
Create a Rule in wp-admin
The plugin works the same way, right inside wp-admin.
- Go to WebChange Detector → Checks and click Show on a check.
- In the AI Change Analysis section, click Ignore in future on the area you want to ignore.
- Choose Only this URL or All URLs in the group, then click Confirm.
For a console message, click Ignore next to the new entry in the Browser Console section and confirm the scope.
Manage Rules in wp-admin
Go to WebChange Detector → AI Rules. You see the rules of this website with the same controls as in the dashboard: switch a rule off and on, widen its scope from This URL to all URLs of the group or website, check its matches, or delete it. On a multisite network, the network admin can show or hide this page for each subsite.
Three Real Examples
The Date in Your Footer
Your footer shows today’s date, so every page looks different every day. Dates in your own content always alert by design, so this one needs a rule. Open any check where the footer date is highlighted, click Ignore in future and choose All URLs in your website, because the footer is on every page. One rule, and the footer is quiet everywhere.
A Rotating Testimonial
Your homepage shows a random customer quote on every visit. Create the rule from the homepage check with Only this URL. A new quote no longer raises an alert. If the testimonial section breaks or vanishes one day, that is a different type of change, and you still get told.
A Console Warning You Accept
A third-party chat or booking script writes the same warning to the browser console, and you cannot change that script. Click Ignore in future (in the plugin: Ignore) next to the entry in the Browser console section and apply it to all URLs of the website. Only do this for messages you understand. A new error after a plugin update is a reason to investigate, not to ignore (see Catch Broken JavaScript, Not Only Broken Layouts).
Rule or CSS?
A rule keeps the element in the screenshot and only changes the verdict. If you never want to see an element at all, for example a chat bubble or a live visitor counter, hiding it with a line of CSS is often cleaner. My Check Shows Changes I Do Not Care About explains both options side by side.
Keep Your Rules Healthy
- Watch the Matches column. A rule that matches often is saving you reviews. A rule that has not matched for a long time probably covers an element that no longer exists; delete it.
- Pause instead of delete. Before a relaunch, switch a rule off to see every change again, then switch it back on.
- Widen, do not duplicate. If the same element causes noise on more pages, change the scope of the existing rule instead of creating a second one.
Feedback rules work on top of our AI verification. If your plan does not include it, the AI change analysis panel shows an upgrade note instead of verdicts.