Review page evidence and JSON-LD
Inspect observed schema, validate a Forge page draft, and verify a reviewed WordPress publication.
A page can contain structured data from its website software, theme, plugins, and Forge. The Page JSON-LD editor separates observed evidence from Forge's page-owned draft so you can improve a specific page without treating every existing block as yours to replace.
Use the Northgate ESD Packaging demo's packaging information page as an example. The goal is to describe the visible page accurately, not to add claims that the page itself does not support.
Open and inspect the page
- Select the correct account and WordPress storefront.
- Open AEO & Agentic Storefronts > Pages.
- Locate the managed page by title and URL.
- Open its Page JSON-LD editor.
- Read Observed WordPress Schema and its observation date.
- Choose Refresh Evidence if you need a current inspection.
Expand the observed objects to inspect their types and values. If an audit retained an older snapshot or could not parse some blocks, read that notice before relying on the evidence. The editor may show valid objects even when another block failed to parse; visible objects do not mean the entire page passed inspection.
The page title, path, and canonical URL identify the target. Check them before editing, especially when several Northgate pages discuss similar packaging topics.
Prepare only the intended Forge blocks
Use Forge Page-Owned JSON-LD for the proposed page data. You can edit the text, choose Append Object, or use Import File. Normalize Pasted JSON accepts supported JSON shapes, including objects, arrays, graphs, and JSON-LD script content.
Keep the draft aligned with the page. If a Northgate page answers a question about ordering custom inserts, the structured answer should agree with the published wording and approved ordering process. Do not invent dimensions, reviews, ratings, or service promises to fill a field.
Observed external and site-wide blocks remain outside this draft. Copying all observed schema into the Forge editor can create unnecessary duplication. Add only the page-owned material you intend Forge to manage.
Validate and publish
- Choose Save Draft & Validate.
- Resolve any validation error shown beneath the editor.
- Read the normalized objects and confirm the intended values.
- Confirm that the current draft is saved and the target page is correct.
- Choose Publish under Publish to WordPress when your reviewed draft is ready and you have permission.
- Inspect the queued task's progress and verification result.
Publishing replaces this page's Forge blocks. It preserves external and site-wide blocks. An empty array removes only Forge page blocks, so use that deliberately rather than as a general schema cleanup method.
The editor reports queued work through Tasks. A queued task is not a completed publication. Wait for its result, then inspect current evidence to confirm what renders on the page.
Why Publish may be disabled
The control requires publishing permission, enabled WordPress publishing, a saved version, and a valid draft. Unsaved changes also block publication. Read the explanation near the button and fix that specific condition.
If the latest evidence is stale or an inspection failed, establish current source evidence before making a replacement decision. A connection problem is not fixed by repeatedly saving the same JSON.
If you are trying to remove schema supplied by another plugin, this page-owned editor is not a blanket suppression tool. Keep the external ownership visible and have the authorized operator review the appropriate replacement process.
Confirm the outcome
Completion means the intended Forge page blocks are saved, published, and verified at the correct URL. It does not prove that an answer system will cite the page. Use the Citation Observatory for that separate observation and Journeys for traffic evidence.