Schema.org output

What is generated#

Each captured page produces a schema.org JSON-LD document — the structured data search engines use to understand what a page is (an article, a product, an FAQ, and so on) beyond what plain text tells them. The generated schema is valid and eligible for Google Rich Results; eligibility is not the same as a guaranteed rich result, which Google itself decides case by case.

How it is delivered today#

The embed module appends the JSON-LD to the page client-side, in the visitor’s browser, after the page has loaded — your own server never sends it. That is a stated, tracked gap rather than an oversight, and this page updates the day it changes.

When it regenerates — and when it does not#

For a URL that already has a stored schema, the embed serves the stored one and stops: it reads before it writes, so a repeat view generates nothing. Editing that page does not by itself produce a new schema through the embed — the stored result keeps being served until something refreshes it.

When a generation is triggered, Seogence renders the page itself and hashes what it saw — title, meta description, extracted text and HTML. That hash gates the generation path, so a page whose content has not changed returns CACHE_HIT rather than calling the model again; a page with a fresh stored result short-circuits earlier still, without a re-render. Refreshing a changed page today is an explicit action: regenerate it from the dashboard, or have a whole-domain refresh run. We would rather state that plainly than imply an automatic freshness we do not yet deliver.

Reading what was published for a page#

Your install page includes a panel that looks up the stored schema for any address on your domain and shows the actual document it publishes, not a summary of it.