Schema Markup Heath & Live Test

Go to Post / Page Editor Mode and bottom Meta Box #

Step 1: Schema Tab #

View real-time schema health scores, detected schema types, readiness criteria, and optionally override auto-generated schema with manual JSON-LD data — all from within the post or page editor.

Navigation Path

WordPress Admin  →  Posts / Pages  →  Edit any post or page  →  SchemaEngine AI Settings meta box  →  Schema tab

Sections on This Page #

1.  Schema Health — Score Dashboard

2.  Detected Types

3.  Readiness Breakdown

4.  Override Automatically Generated Schema

1.1. Schema Health — Score Dashboard #

The Schema Health card appears at the top of the Schema tab and provides an instant, real-time assessment of the structured data output on this specific post or page. It is the primary indicator of whether your schema is correct and ready to be picked up by search engines.

✔ Live  The “Live” badge The green “✓ Live” badge in the top-right of the Schema Health card confirms that schema markup is currently active and being output on the front end of this post. If the master Enable Schema toggle in General Settings is OFF, this badge will not appear.

The Two Scores #

Score	Grade	Metric	What it measures
100	A+	Schema Validation	Confirms that all schema types output on this post pass schema.org validation. 100/100 means all 6 detected schema types are valid — no missing required properties, no type mismatches, no structural errors.
99	A	Rich Result Readiness	Measures how well the schema is optimised for Google rich results eligibility. Based on 6 criteria (see Readiness Breakdown below). 99/100 with 0 enhancements available means the schema is at maximum practical completeness.

Score Grade Scale #

Score Range	Grade	Meaning
95–100	A+	Excellent — schema is valid, complete, and fully optimised for rich results
85–94	A	Very good — minor gaps may exist but rich results eligibility is high
70–84	B	Good — schema is valid but some recommended properties are missing
50–69	C	Needs improvement — notable gaps that may reduce rich result eligibility
0–49	D/F	Poor — significant validation errors or missing required properties

↑ Back to Contents

1.2. Detected Types #

The Detected Types row lists every schema.org type that SchemaEngine AI is currently outputting for this post or page. Each type is shown as a green dot label, and the total count is displayed above the row (e.g. “DETECTED TYPES · 6”).

Example from the screenshot — 6 types detected:

● BreadcrumbList   ● Organization   ● WebSite   ● BlogPosting   ● WebPage   ● FAQPage

What each detected type means: #

Schema Type	What it tells search engines
BreadcrumbList	The navigational path to this page (e.g. Home › Blog › Post title). Helps Google display breadcrumb trails in search results.
Organization	Your site’s identity, brand name, logo, and contact details. Pulled from Site Info settings. Powers the Knowledge Panel.
WebSite	The site-wide identity and search action. Tells Google the name and URL of the site this content belongs to.
BlogPosting	The primary content type for this post — confirms it is a blog article. Enables Article rich result features.
WebPage	The page-level metadata including title, description, and URL.
FAQPage	FAQ structured data from any FAQ blocks on this post. Enables FAQ dropdowns in Google search results.

💡  More types = richer schema graph
Having multiple schema types on a single page is not duplication — it is a structured schema graph. Each type plays a different role. BreadcrumbList handles navigation, Organization handles identity, BlogPosting handles the content. Google reads all of them together to build a complete understanding of the page.

↑ Back to Contents

1.3. Readiness Breakdown #

The Readiness Breakdown section shows a detailed breakdown of the six criteria that make up the Rich Result Readiness score. Each criterion is scored independently with a progress bar, and a green checkmark confirms it has passed. The overall readiness score is the weighted average of all six.

Criterion	Score	What this criterion measures
Completeness	96%	Whether all recommended and required properties are present across all detected schema types. 96% reflects near-perfect property coverage — only optional, rarely-used properties are missing.
Rich Results	100%	Whether the schema qualifies for Google rich result features such as star ratings, FAQ dropdowns, breadcrumb trails, and product rich results. 100% means all applicable rich result requirements are met.
Cross-References	100%	Whether schema types correctly reference each other in the knowledge graph (e.g. BlogPosting references the Author entity, which references the Organisation). 100% means all cross-entity links are present and valid.
Content Depth	100%	Whether the schema properties contain meaningful, specific data values rather than empty or placeholder values. 100% means all property values are populated and substantive.
Identifiers	100%	Whether unique identifiers (such as @id URLs, brand identifiers, or product codes) are present and correctly formed. 100% means all schema entities have valid, unique identifiers.
Graph Structure	100%	Whether the overall schema knowledge graph is correctly structured — including proper use of @context, @type, @id, and nested entity relationships. 100% means the graph is fully valid and well-formed.

🔍  Enhancement Opportunities The header of the Readiness Breakdown section shows “X of Y enhancement opportunities” — the number of suggested improvements SchemaEngine AI has identified for this post. In the screenshot example: “0 of 6 enhancement opportunities” — all six criteria are maximally optimised and no further improvements are suggested. When enhancements are available, they appear as actionable suggestions below the progress bars — for example: “Add a description property to BlogPosting” or “Include an image property for rich result eligibility.” Addressing these suggestions will raise your readiness score.

↑ Back to Contents

1.4. Override Automatically Generated Schema #

The Override toggle at the bottom of the Schema tab gives you full manual control over the schema output for this individual post or page. When enabled, SchemaEngine AI replaces the auto-generated schema with the JSON-LD data you enter manually.

When to Use the Override #

✔  Use Override When

✖  Keep Auto-Generate When

This post needs a unique schema type not covered by the global Post Type Mapping setting. You have custom schema data (e.g. a specific Event, Product, or Recipe) that the AI cannot infer automatically. You want to add extra schema properties beyond what SchemaEngine AI auto-generates. A developer or SEO specialist has pre-built exact JSON-LD for this page. You are testing a specific schema configuration for Google Rich Results Test

The Schema Health score is already 95+ — the auto-generated schema is performing well. You are not familiar with JSON-LD syntax — invalid manual JSON-LD will break schema output. You want to use the Readiness Breakdown suggestions to improve schema — these only apply to auto-generated schema. The post is a standard blog post or page that the plugin handles correctly by default

⚠️  Override disables all automatic schema health monitoring for this post When Override is ON, the Schema Health scores and Readiness Breakdown reflect the manually entered JSON-LD, not the auto-generated output. Invalid JSON-LD entered manually will cause schema validation errors on this post. Always validate your manual JSON-LD using Google’s Rich Results Test (search.google.com/test/rich-results) before publishing.

💡  Override is per-post — it does not affect other content Enabling Override for one post has no effect on any other post, page, or post type. All other content continues to use auto-generated schema normally. You can mix auto-generated and manual schema across your site — for example, use auto-generation for all blog posts but manual override for a specific landing page with a unique schema requirement.

Step 2: Schema Preview #

Inspect, edit, copy, and live-test the complete JSON-LD schema markup generated for any post or page — directly from within the WordPress editor.

Navigation Path #

WordPress Admin  →  Posts / Pages  →  Edit any post or page  →  SchemaEngine AI Settings meta box  →  Schema Preview tab

📊  Schema score is visible in the editor top bar Before opening the preview modal, SchemaEngine AI shows your schema score as a badge in the WordPress block editor top bar — visible in the screenshot as “91/100” (green) and “0” (red for issues). This gives you an at-a-glance health indicator without opening the meta box.

Sections on This Page #

1.  Preview Button — View the Full JSON-LD Output

2.  Edit Button — Modify the Schema Directly

3.  Copy Button — Copy to Clipboard

4.  Test Button — Live Test on Google

5.  Reading the JSON-LD Output

 

2.1. Preview Button — View the Full JSON-LD Output #

The Preview button is the default active state when the modal opens. It displays the complete JSON-LD schema in a read-only dark code editor with syntax highlighting and line numbers.

What you can see in Preview mode:

• The complete JSON-LD object starting with @context and @graph
• All detected schema types as separate objects within the @graph array
• Every property and value for each schema type
• Unique @id URLs identifying each entity in the schema graph
• Nested objects such as itemListElement arrays within BreadcrumbList
• Line numbers for precise reference when debugging or copying specific sections

💡  Use Preview before publishing Checking the Schema Preview before publishing a post is a best practice. It lets you confirm that all expected schema types are present, properties are correctly populated, and no obviously wrong values (like placeholder text or empty fields) have been included in the output.

↑ Back to Contents

 

2.2.  Edit Button — Modify the Schema Directly #

The Edit button switches the code panel from read-only Preview mode to an editable mode, allowing you to make direct changes to the JSON-LD output. This is the same functionality as the Override toggle in the Schema tab (Step 12), but accessed from within the preview modal.

✏️  Edit Switches the JSON-LD panel to editable mode. The code becomes directly modifiable — you can add, remove, or change any property or value in the schema. Changes made here override the auto-generated schema for this post, equivalent to enabling the Override toggle in the Schema tab and entering JSON-LD manually.

⚠️  Edit mode replaces auto-generated schema — use carefully When you edit the JSON-LD in this modal and save, the Override Automatically Generated Schema toggle in the Schema tab is activated for this post. The auto-generated schema is suppressed and your manually edited version is used instead. Make sure your JSON-LD is valid before saving — invalid JSON-LD will cause schema errors on this page.

Best practices for editing:

• Use Preview mode first to understand the existing schema structure before making changes
• Only edit properties you need to change — preserve the @context, @graph wrapper, and @id values
• After editing, use the Test button (Section 13.4) to validate the modified JSON-LD in Google’s Rich Results Test before publishing
• Use the Copy button to back up the current schema to your clipboard before making changes

↑ Back to Contents

 

2.3. Copy Button — Copy to Clipboard #

The Copy button copies the entire JSON-LD schema output to your clipboard in a single click. This is useful for testing the schema outside the plugin, sharing it with developers, or backing it up before making edits.

Common uses for the Copy button:

• Paste into Google’s Rich Results Test manually (https://search.google.com/test/rich-results) for detailed validation
• Paste into the Schema Markup Validator (https://validator.schema.org) for full schema.org compliance checking
• Share the schema output with a developer or SEO specialist for review
• Back up the current auto-generated schema before switching to Override mode and editing manually
• Compare schema output between two pages or post types by copying from each and comparing side by side

↑ Back to Contents

 

2.4. Test Button — Live Test on Google #

The Test button is the fastest way to validate your schema against Google’s own structured data testing tool. It opens Google’s Rich Results Test in a new browser tab, pre-loaded with the schema from this post, so you can see exactly what Google detects and whether your content is eligible for rich results.

ℹ️  The Test button uses your live page URL Google’s Rich Results Test fetches your page from the web — it does not test the schema in isolation. For the test to reflect your current schema, the post must be published (not draft) and Googlebot must be able to access the page. If the post is a draft or behind a login, use the Copy button and paste the schema manually into the Rich Results Test URL field instead.

How to use the Test result to improve your schema: #

1. Click Test — the Rich Results Test opens in a new tab and analyses your page.
2. Review the Detected items list — confirm all expected schema types appear.
3. Check for any red Errors — these are required fields that must be fixed for rich result eligibility.
4. Check for yellow Warnings — these are recommended fields; fixing them can improve how rich results display.
5. Return to the Schema tab or Schema Preview Edit mode and address any identified issues.
6. Re-publish the post and re-run the test to confirm all errors are resolved.

↑ Back to Contents