A read-only status card that tells you whether your property pages are publishing structured data correctly for Google and AI assistants, and flags it the moment emissions start failing.
What it does #
The HomeRunner plugin publishes structured property data (JSON-LD) on every property page so search engines and AI assistants can read your rates, address, and amenities correctly. That publishing runs quietly in the background, which is exactly the problem: if it starts failing, on some sites the first sign is a drop in AI or Search visibility weeks later, not an error anyone saw.
Schema Health reports the plugin’s own schema state in plain terms, in two places: a card in the Toolkit Hub, and a test under Tools → Site Health, so a site is covered even if nobody opens the Hub. It changes nothing. It only reads what the HomeRunner plugin is already doing and tells you about it.
The card shows:
- Whether the schema emitter is switched on for this site.
- How much address detail is being published (exact address, or general area only), and how many properties have their own override of that setting.
- How many published properties can potentially emit schema.
- A running count of successful and failed emissions, plus how many of each happened since you last opened the card.
- Whether the AI Booking Channel has taken over the property page’s structured data. When it has, the plugin’s own counters stop moving on those pages, which is expected and not a sign something broke.
If a failure shows up, the card and the Site Health test both surface the last recorded error message, so you know what to check without digging through logs.
How to turn it on #
1. Switch on Schema Health #
In the HomeRunner Toolkit Hub, switch on Schema Health, listed under Analytics. The card appears on the Hub right away.
2. Read the status #
A colored status line tells you where things stand: healthy, new failures to look at, the schema emitter switched off, or (on an older, unsupported install of the core plugin) telemetry unavailable. The detail rows below it fill in the rest.
3. Mark counts as reviewed, once you have looked #
After checking a failure, click Mark these counts as reviewed on the card. That resets the “since last opened” totals to the numbers you just saw, so the next time you look, you see only what is new.
Settings #
| Setting | What it controls |
|---|---|
| Schema emitter | Whether the HomeRunner plugin’s structured-data publishing is on or off for this site. This is a HomeRunner plugin setting, shown here for visibility, not changed here. |
| Address precision | How much location detail the plugin publishes in the schema: the full address, or the general area only. |
| Per-property overrides | How many properties have their own precision setting instead of following the site-wide policy. |
| Published properties | How many published property pages can emit schema. |
| Successful / failed emissions | Running totals since the counters were installed, plus how many of each happened since this card was last opened. |
| AI Booking Channel | Whether that module has taken over the property page’s structured data. When it has, the plugin’s own emission counters stop moving on property pages, since the module is publishing that data instead. |
| Mark these counts as reviewed | Resets the “since last opened” totals to what the card is currently showing. Nothing else changes. |
Tips #
- The same status is available from Tools → Site Health, under the label “HomeRunner property schema,” so a site can be checked without opening the Toolkit Hub at all.
- A “telemetry unavailable” status means the installed HomeRunner core plugin predates this reporting, not that anything is broken. Updating the core plugin resolves it.
- If your site runs the AI Booking Channel, check that card’s own analytics first when something looks off with AI-driven traffic. Schema Health only reports the underlying plugin schema, not the channel’s feeds.
- New to the Toolkit? See the Toolkit Overview for the full module list.