A silent template change costs conversions
A price that stops rendering or a stock badge that vanishes does not break a single SEO check, and nobody files a bug for it.
Custom on-page monitoring
Heads-up
Watch anything on the page, not just the SEO fundamentals
Every site has signals the standard tests do not cover — an in-stock indicator, a price, the number of products in a listing, a promo banner that should never disappear. When one of those breaks, no SEO check notices. Your conversions do.
Heads-up severity: batched into your daily digest, because this costs clicks rather than indexation.
What it may cost you
The gap between “the SEO is fine” and “the page still does its job” is where this one lives.
Renamed classes break quietly
A redesign that renames a class removes the element from the page as far as your tooling is concerned, with no error anywhere.
The important elements are yours, not ours
No predefined catalogue can anticipate the one block your revenue depends on. That one needs naming explicitly.
How an alert reaches you
Three steps, running every day, on something nobody looks at twice a year.
1
Every run
Baseline stored
The first crawl saves the element your selector points at as it should be. That value is what every later run is compared against.
2
Next morning
Change detected
The value the selector extracts is compared against the baseline, using the match method you configured.
3
Daily digest
Alert in your digest
Heads-up findings are batched into one email, so this never buries an alert that needed you an hour ago.
You decide what counts as broken
The stored value is your desired state, not a guess. When a later run differs you get both versions side by side — and if the change was intentional, one click adopts it as the new baseline.
Severity matches the damage
This one waits for the daily digest by default, so it never competes with an alert that needed you immediately. Raise it to Danger per site if it matters more to you.
Set it once, then leave it
Pick the frequency and the user agent Wygard should send, switch on JS rendering if your pages need it, and the rest needs no attention.
What we check
One check per selector you define. Selectors are saved to a reusable library, so the same rule can be applied across URLs.
| Test | What it catches | Scope | Severity |
|---|---|---|---|
| Custom on-page test | The extracted value changed, the selector matched nothing, or the match rule you set is no longer satisfied. | URL · Basic | Heads-up |
Questions about custom on-page monitoring
What the checks do, and what they don’t.
Which selector types are supported
CSSPath, XPath and regular expressions.
Can I reuse a selector on several URLs
Yes. Saved selectors live in a library, so a rule written once can be applied wherever it makes sense.
Can this watch things that are not SEO
That is the point. A stock indicator, a price, a chat widget — if it is in the page source, it can be watched.
“This app has completely transformed how we manage our SEO. The real-time alerts ensure we never miss an issue. It's a game-changer for protecting our rankings!”
Why Wygard?
Trust, but verify. You build the site — Wygard makes sure your key SEO elements work as intended.
Your SEO protected
How quickly would you notice if your canonical tags changed? We catch it for you.
Time saved
Don't waste time on massive crawls and endless data. With 15 years of hands-on SEO experience, we know how to focus on what really matters.
Easy to Use
You don't have to be an SEO expert — your site still deserves expert monitoring. That's exactly what our tool delivers.
Single site or the whole portfolio? We can handle all today
Every online business deserves protection. No matter the size.