A check reports a change, you open it, and it is something you do not care about: a chat bubble in a different state, a counter that went up, a block that only some visitors see. Once is fine. Every day is annoying, and it trains you to ignore alerts.
Good news first: most of this noise never reaches you. Before every screenshot, WebChange Detector blocks ads and trackers, handles cookie banners, removes popups that cover the page, stops sliders on their first slide, freezes animations, videos and GIFs, and neutralises parallax effects. After the comparison, our AI marks content that changes on every visit as OK. When something still slips through, this guide helps you pick the right fix for the situation.
Which Fix for Which Situation
| Situation | Fix |
|---|---|
| The AI already marked the change as OK | Nothing to do |
| The same harmless change comes back again and again | A feedback rule |
| An element should never be in the screenshot | Hide it with CSS |
| The page needs a certain state, like an open tab or a closed popup | Run JavaScript before the screenshot |
| Pages sometimes come out incomplete when many are checked in a row | Increase the screenshot delay |
1. Check the AI Verdict First
Open the check and look at the AI change analysis. Every highlighted area has a verdict: OK, Unsure or Alert. If your plan includes AI verification, alerts are only sent for changes the AI confirmed. An area marked OK is already handled, even though it shows up in the comparison. You only need to act on areas marked Alert or Unsure that you know are harmless.
2. The Same Harmless Change Keeps Coming Back: Create a Feedback Rule
Made for: a date in your footer, a rotating testimonial, a console warning you accept. These are part of your site and should stay in the screenshot, you just do not want an alert for them.
Click Ignore in future on that area of the check, choose whether the rule applies to this page or the whole website, and confirm. From then on, the AI marks that type of change as OK. A different problem on the same element still raises an alert. All steps for the Web App and the plugin are in Teach the AI What to Ignore.
3. An Element Should Never Be in the Screenshot: Hide It with CSS
Made for: a chat widget, a live visitor counter, a “recently viewed” block, a cart badge, a floating “back to top” button. Elements that change on their own and tell you nothing about whether your site works. The CSS you add is applied to the page right before the screenshot, so the element is simply not in the picture.
In the Web App
CSS is part of the website settings, so it applies to every page of that website.
- Open the Monitoring tab (or the On-Demand tab).
- On the website’s row, click ⋯ and choose Website Settings.
- Open Advanced Settings and add your rules to CSS Injection. The
<style>tags are already there; write only the CSS. - Click Save.
Only one page needs it? Expand the website in the same tab, click the settings icon on that page’s row to open Webpage Settings, and use CSS Injection under Advanced settings there.
In the plugin for WordPress
- Go to WebChange Detector → Monitoring or WebChange Detector → On-Demand Checks.
- Add your rules to CSS Settings.
- Click Save Settings.
CSS and JavaScript are saved separately for Monitoring and for On-Demand Checks, in the dashboard and in the plugin. If you use both, add your code in both places. Ready-made snippets are in the recipes section below.
4. A Page Needs a Certain State: Run JavaScript
Made for: an FAQ that should be captured with the first answer open, a pricing table that should show the yearly tab, a site-specific overlay that our automatic popup removal does not catch. Your JavaScript runs on the page after it has loaded, before we scroll through it and take the screenshot.
You add it right next to the CSS: JS Injection in the dashboard’s Website Settings or Webpage Settings, JS Settings in the plugin. The <script> tags are added for you. An example that clicks the first FAQ question (replace the selector with the one from your site):
var firstQuestion = document.querySelector('.faq-item button');
if (firstQuestion) {
firstQuestion.click();
}
Keep scripts short and defensive: check that the element exists before you use it, so the page still renders when the layout changes one day.
5. Pages Come Out Incomplete When Many Are Checked: Increase the Screenshot Delay
Made for: smaller hosting that struggles when many pages of the same site are loaded one after another. You notice it when some screenshots of a run miss images or show half-loaded sections, while the same pages look fine on their own.
The screenshot delay sets how many seconds pass between the start of one screenshot and the next on your site. It does not make us wait longer on a single page; it gives your server a breather between pages. The default is 10 seconds.
- Web App: Website Settings → Advanced Settings → Screenshot Timing → Delay between screenshots (seconds).
- plugin for WordPress: Monitoring or On-Demand Checks page → Screenshot Delay.
A longer delay means a run over many pages takes longer to finish. Raise it step by step.
You will also find a Difference threshold field in these settings. Its own hint recommends leaving it at 0, because the AI classification already filters out the noise.
CSS Recipes for Common Noisy Elements
Copy what you need into the CSS field. Each recipe covers popular tools; delete the lines you do not use.
Chat Widgets
/* Intercom */
#intercom-container,
.intercom-lightweight-app { display: none !important; }
/* Tidio */
#tidio-chat { display: none !important; }
/* Crisp */
.crisp-client { display: none !important; }
/* HubSpot */
#hubspot-messages-iframe-container { display: none !important; }
/* LiveChat */
#chat-widget-container { display: none !important; }
Cookie Banners the Automatic Handling Misses
Cookie banners are handled automatically in most cases. Use this only if a banner still shows up in your screenshots.
/* Cookiebot */
#CybotCookiebotDialog { display: none !important; }
/* Complianz */
#cmplz-cookiebanner-container { display: none !important; }
/* Borlabs Cookie */
#BorlabsCookieBox { display: none !important; }
/* OneTrust */
#onetrust-consent-sdk { display: none !important; }
Counters, Live Numbers and Dates
/* Visitor counters and "people online" badges */
[class*="visitor-count"],
[class*="online-users"] { display: none !important; }
/* Social share counts */
.share-count { display: none !important; }
/* A date line, keeping its space so the layout does not shift */
.last-updated { visibility: hidden !important; }
Floating Buttons and Badges
/* Back to top buttons */
[class*="back-to-top"],
.scroll-to-top { display: none !important; }
/* WooCommerce cart count in the header */
.cart-contents .count { display: none !important; }
A Slider We Do Not Recognise
Sliders from the common WordPress slider plugins are stopped on their first slide automatically. For a custom slider that still moves, hide it:
.my-custom-slider { visibility: hidden !important; }
How to Find the Right Selector
- Open your site in Chrome.
- Right-click the element you want to hide and choose Inspect.
- Look for an
idor aclasson the highlighted element or its container. - Test your rule in the browser’s developer tools first, then paste it into WebChange Detector.
Prefer an #id, then a clear .class-name. Avoid selectors that hide too much (like div) and generated class names like .css-1a2b3c that change with every build. Use display: none to remove an element, and visibility: hidden to keep its space so nothing below it moves. Add !important so the site’s own styles cannot override your rule.