Schema

Structured data your pages are missing, with the JSON-LD ready to paste.

In appWorkspaces›Schema

What it checks

Structured data is the machine-readable summary of what a page is about. Google uses it to decide whether a page can appear as a rich result, and assistants use it when they read your site.

This list is what's missing or broken, page by page, with the type of schema each page should carry.

The side-by-side view

Worth turning on. It puts what the page has now next to what it should have, which makes it obvious whether you're adding something new or fixing something malformed.

The JSON-LD is generated for that specific page and is ready to paste as it stands.

What to do with it

Paste the JSON-LD. If you want to know why a particular one matters or which to do first, Ask Advisor takes the finding to your Strategist.

Some findings are suppressed rather than shown, where the analysis is confident the schema isn't appropriate for that page. Those sit in their own section.

Working a finding

Open any finding and you can take it somewhere else without retyping it. Ask Advisor opens the Strategic Advisor with that finding and its full context already loaded, so you can ask why it matters or what to do first and get an answer using your own numbers. Create brief (or Rebuild in Studio) opens a Content Studio session for the page, pre-filled the same way.

Both carry the finding with them. You're not starting a conversation or a brief from nothing, which is the whole point of launching them from here rather than from their own screens.

Most findings also carry an AI Playbook: a written recommendation for that specific page. Some are generated automatically after a run, the rest are generated when you ask. You can also tick several rows and generate advice for all of them in one go, with the cost shown before anything runs. How many are written automatically is the Auto-generate for top setting in that analyzer's Configure panel, and zero means they're only written on request.

Mark applied does more than tick it off. The page joins Impact Tracking in Command Center, which then follows its clicks, impressions and position from that date onward, so you can see whether the change did anything.

Getting rid of one you don't want

Ignore on any finding hides it. It leaves the queue and moves to the Ignored pill in the filter rail, where Restore puts it back, so nothing is destroyed. The Ignored pill only appears once you've ignored something.

Ignoring handles one finding. If the same pages keep coming back, add them to Excluded pages in Settings, under Data Pipeline: find Schema in the analyzer list and click Configure. One pattern per line, * as a wildcard, and plain text matches anywhere in the URL. Matching pages stop becoming findings from the next run.

That's the difference worth knowing: ignoring hides one finding, excluding a page stops future findings for it. Tag pages, author archives and paginated listings are the usual candidates.