A friendly lookout for your pages

Keep watch on the schema behind your rich results.

Monitor JSON-LD that search engines and AI answer tools may use to interpret pages. Catch broken markup on live pages and public previews before release.

Add a site by its homepage, then the pages that matter. No code to install.

A clearer view

Keep an eye on what visitors can’t see.

Hidden JSON-LD

Read the structured data search engines use for rich results.

Plain findings

A readable summary when something needs a closer look.

Check history

Revisit past checks for evidence of what changed.

The problem

The page looks fine. The markup underneath may not.

A developer changes a template. A plugin updates. A field goes missing. The page still loads and reads normally, but the JSON-LD underneath, which search engines and AI answer tools may use as machine-readable context, can quietly break.

Nobody notices: not the client, the agency or the developer who made the change. Catching broken schema is useful groundwork for GEO (generative engine optimization), but does not guarantee an AI citation, rich result, ranking or traffic. Google decides what appears in its results; SchemaSignal helps you see when the markup changes.

How it works

Three steps, no install.

  1. 01

    Give us the URL

    Add the page you want watched. Nothing to install, no plugin, and no setup on your client’s side.

  2. 02

    We check on a schedule

    Choose hourly, daily or weekly. Checks run when they become due, or run one yourself any time.

  3. 03

    Review what changed

    Findings and check history live in your dashboard, so you can see what happened and when.

See the full walkthrough

An extra check before release

Put structured data in your CI/CD release checks.

Before releasing an update, check its public preview against a saved, approved version of your live page or the structured-data types you require. Your development team can use a failed check to stop the release until the issue is reviewed.

These release reports are separate from regular monitoring and its alerts. They check the page code sent by the server, not data added later by JavaScript or private files from your build.

See how release checks work

Built for agencies

Twenty client sites is too many to check by hand.

Group monitored pages by client and see each client’s status together. When someone asks why a listing changed, you have the check history to look back through, rather than guesswork.

Who this is for

Anyone whose pages lean on rich results.

E-commerce
Keep an eye on the product markup your price and stock details depend on.
Recruitment and job boards
Job listings rely on structured data, and a broken block shows no visual sign on the page.
Local service businesses
Review markup is part of how your business can earn star ratings in search.
Content and recipe publishers
Rich results can be a big share of traffic. Notice markup problems before the analytics dip.

A Twenty Signals product

Find out about a broken rich result from your dashboard, not from a traffic dip.

Start monitoring