How it works
From a URL to a clear history.
Rich results often depend on JSON-LD hidden in a page. A template, plugin or field change can break it while the page looks normal. Here is how SchemaSignal helps you notice through live monitoring and CI/CD release checks.
Setup in five steps
- 01
Create a workspace
Sign up, then open your dashboard. There is nothing to install on your site.
- 02
Add a site, then its key pages
Enter the site homepage as its first watched page, then add other pages on the same site. Name each one and optionally put it in a client group. Each watched page counts toward your plan.
- 03
Pick a schedule
Hourly, daily or weekly. Scheduled checks become due on that cadence; they are not real-time. You can also run a manual check whenever you like.
- 04
Read the findings
Each check reads the JSON-LD on the page and reports what it found, in plain language, on the page’s detail view.
- 05
Look back through history
Every check is kept, scheduled or manual, so you can compare what the page looked like over time and share the evidence with a client.
Optional CI/CD release gate
Check structured data before promoting a release.
Open Automation in your dashboard. Save an approved result from your live page as the comparison point (the “baseline”), or choose the structured-data types the preview must contain. Your developer then approves the preview address and creates an access key for that monitor, stored securely in your repository’s secrets.
- 01
Build and deploy your preview
Download the packaged GitHub Action from Automation or use its CLI to check one to 20 configured URLs after deployment. You can also call the CI API for each URL.
- 02
Review the check result
A passing check exits successfully; a schema failure and a service or fetch error have separate failing statuses. Reports remain separate from scheduled monitoring, its live page status and email alerts.
- 03
Make it a release gate
Require the check in your repository’s branch rules or make your deployment job depend on it. A workflow by itself does not block merges or promotion.
Release checks (CI) read the page code sent by the server. They do not run JavaScript, sign in to private previews or inspect your project’s source files. Results cover the addresses you checked, not the whole site, and do not guarantee enhanced Google search results.
CI/CD is intended for Studio and Partner, not Solo. Plans remain illustrative previews and checkout is not active yet; see the FAQ for current preview access and soft check allowances.
CI/CD access and limitsFor agencies and client work
Put each client’s pages in a client group to see their status together. When a client asks what happened to a listing, the check history gives you dated evidence to review. Built for e-commerce, recruitment, local service and recipe or content sites alike.
What to expect, honestly
- SchemaSignal checks structured data in the JSON-LD format: extra information a page provides for search engines. Other markup formats are not covered.
- Regular monitoring first checks the downloaded page code. If no JSON-LD is found, it tries a short browser check for data added by JavaScript. An unfinished check is reported as incomplete, not confirmed missing.
- Checks use public pages without signing in or clicking consent buttons. Data added much later or after interaction may not appear. Release checks remain HTML-only.
- Scheduled checks are due-based, not real-time. Manual and CI checks run on demand. With email delivery enabled, a newly detected live-monitor break can trigger an email alert. Manage alerts and weekly snapshots in your profile. Slack alerts are not supported.
- It does not measure Google rich results, AI answer citations or traffic. Structured data may help search systems interpret a page and support rich-result eligibility, but SchemaSignal cannot show whether an AI service selected or cited a page. Nothing guarantees a rich result, citation, ranking or traffic.