Schema

Use Schema to see which Schema.org structured data a page exposes, which required and recommended properties are missing, and what to fix. Every check is saved in the project, so you can hand the results to a developer, come back to them later, and check the page again to confirm the fix worked.

Check a page

Open Schema from the sidebar. Enter the full address of a public page and select Check. If you leave the field empty, PromptEye checks your project’s domain. An address without https:// is treated as HTTPS. The page must be publicly reachable: pages behind a login, drafts, and local previews cannot be checked. Each check reads one page; to review many pages in one run, use WWW Audits.

When the check finishes, its result opens on the right. If the page cannot be fetched, you see an error and nothing is added to the history, so you can fix the address and try again.

Only people who can edit the project can run checks. People with view-only access see the same history and results but no Check or Check again buttons.

Read the results

The checker reads JSON-LD and, when it cannot parse any JSON-LD block, attempts to read Microdata markup from the page. It does not infer structured data from ordinary visible text or use a sitemap. Markup added only after browser-side JavaScript runs may not be detected.

Each detected schema object shows its required and recommended properties as present or missing. A missing required property makes that schema invalid; a missing recommended property is an improvement suggestion and does not change that status. When the page has structured data, AI Recommendations adds up to six suggestions ordered by priority. They are written in the app language of the person who ran the check and are saved as they were written, so a teammate using another language sees them in the original language. When no structured data is found, you get a fixed list of commonly useful types instead.

A page gets one of three results:

• Valid — every detected schema has its required properties.
• Missing required fields — at least one schema lacks a required property. Fix these first.
• No schema — the checker found no structured data it recognizes.

The Recommendations column counts what is left to do: Critical is the number of missing required properties, Recommended the number of missing recommended ones.

A valid result means the checker found the required fields it evaluates. It does not guarantee rich search results, indexing, AI citations, or that every consumer of structured data will interpret the markup the same way.

Use the analysis history

The Analysis history table lists every page checked in the project, one row per page, showing its newest result. It is shared with everyone who can open the project, and older checks are kept rather than overwritten.

PromptEye treats addresses that differ only in www, http/https, a trailing slash, a ?query or a #fragment as the same page. For example, http://www.example.com/blog/ and https://example.com/blog share one row and one history. Two pages whose content depends on a query parameter are therefore also merged into one row.

Pages are grouped by site; subdomains such as shop.example.com form their own group. Use the result filter to show only pages with a given result, search by address or schema type, collapse a site, or clear Group by site to see a flat list.

Select a site’s row to see a summary for that site: how many pages are valid, have gaps, or have no schema, the total critical and recommended gaps, which schema types appear and on how many pages, and the list of its pages. Select any page there, or in the main table, to open its details.

Compare before and after a fix

A page’s details show its newest result and a Check history list with every earlier check of that page, newest first and marked current. Select an older check to show that result in place of the newest one; the history list stays below, so you can switch back and forth.

A typical loop:

1. Check the page and share the missing items with your developer.
2. Generate the missing markup if you need it (see below) and have it added to the site.
3. Open the page in Schema and select Check again. The new result becomes the current one, and the earlier result stays in the history for comparison.

Check again re-checks the exact address used in the newest check.

Generate missing markup

In a page’s details, select Generate missing to open Schema Generator. The generator opens on the first schema type that has missing required properties. If nothing is missing, it opens on the first type found on the page; if the page had no schema, it opens on Organization. The generator does not copy the page’s existing values into the form. Use the back button to return; the check results are still in the history.

If you cannot open Schema

The sidebar disables project workspace items when you do not have access to an active project workspace. A missing XML sitemap or missing Schema.org code does not hide Schema. If the item is disabled, select a project you can access or ask an owner to grant project access.

Common questions

Are results saved if I leave the page?

Yes. Every successful check is saved in the project history, and you can reopen it at any time from Analysis history.

Who can see the history?

Everyone who can open the project. Only people who can edit the project can run new checks.

Why does it find zero schemas?

The checked page did not expose structured data that this checker recognizes. Confirm the address is the intended public page and that its JSON-LD or Microdata is deployed there, then check again. Malformed JSON-LD blocks are ignored. A sitemap XML file is not required.

I checked a page again but the result did not change.

The checker reads the page as it is served now. If the new markup is not in the response yet — for example, the change is not deployed or a cache still serves the old page — the result stays the same. Confirm the markup is on the exact public URL, then select Check again.

Can I delete a check?

No. Checks stay in the project history.

Does a check change my website or my project?

No. A check only reads the page. It does not change your website, your project settings, or your Visibility results.

Can I check a page on another domain?

Yes. Any public page can be checked; it is saved in the current project’s history under its own site group.