Documentation · Glossary
Documentation
Glossary
Terms used across this documentation, defined once.
- Install line
- The <script async src> tag pasted into a page. The browser loads and runs the module it points at directly — see the embed script.
- Capability token
- A scoped, per-domain token issued with an install line, binding public requests to an authorized hostname.
- Domain key
- The legacy per-domain identifier used to address a site's install and captured pages. Still accepted; the Property ID shown on your install screen is the current one.
- Property ID
- The identifier shown on the install screen and sent by current install lines. It is the identifier resolved in preference to the legacy domain key.
- Content hash
- A hash covering a rendered page's title, meta description, extracted text and HTML, computed server-side from Seogence's own render. Used to skip regenerating a page whose content has not changed.
- CACHE_HIT / GENERATED / GENERATION_IN_PROGRESS / THIN_CONTENT
- The outcomes of a schema-generation call: served from cache, freshly generated, already being generated by a concurrent request, or refused because the render came back essentially empty (a parked page or an app shell that did not hydrate).
- Keyword component
- A page-scoped topic directory rendered near the bottom of a page, independent of schema generation. Generated automatically on a page’s first eligible view, and overridable by the domain owner.
- Knowledge Layer
- The per-domain Markdown delivery surface: each captured page served as clean Markdown, discovered through the domain’s llms.txt index.
- Open Knowledge Format (OKF)
- A draft format (v0.1) for representing knowledge as a bundle of typed Markdown files. Seogence’s Knowledge Layer conforms to it; no public crawler consumes OKF bundles today.
- Account type
- The shape of an account: standard (default), influencer (creator), or agency (multi-site). Distinct from whether an account also participates in the affiliate program.
Checked against Seogence v3.19.37 on . Every claim on these pages is tied to the code that makes it true, and our build re-checks them whenever that code changes.