The rich result leaves without notice
A dropped type means the card, the stars or the breadcrumb trail stops rendering in search. The listing shrinks to plain text.
Structured data monitoring
Heads-up
Rich results disappear without changing the page at all
Structured data earns your rich results — recipe cards, breadcrumbs, prices, review stars. None of it renders, so a template refactor or a plugin update can drop a block while the page still looks perfect.
Heads-up severity: batched into your daily digest, because this costs clicks rather than indexation.
What it may cost you
The page looks identical to a human visitor. Only the SERP listing gets smaller.
Plugin updates are the usual suspect
Markup is generated, not written. An update that changes how a block is emitted removes the type without anyone editing content.
New markup can be a problem too
Types that appear without a deploy of yours are worth a look — they are often a plugin adding claims you did not intend to make.
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 set of schema.org types found on the URL as it should be. That value is what every later run is compared against.
2
Next morning
Change detected
Wygard collects the types present in JSON-LD, Microdata and RDFa, and compares the set against your baseline.
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 URL, off by default. Turn it on for the pages whose rich results actually matter.
| Test | What it catches | Scope | Severity |
|---|---|---|---|
| Structured data types | A type from the baseline is no longer found, the set stops matching your rule, or new markup appeared. | URL · Basic | Heads-up |
Questions about structured data monitoring
What the checks do, and what they don’t.
Does Wygard validate the markup
It watches which types are present, not whether every property is valid. Use Google’s Rich Results Test for full validation.
Which formats are covered
JSON-LD, Microdata and RDFa.
Why is it off by default
Because the types that matter differ per page. You enable it where a rich result is part of the plan.
“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.