On This Page
Schema Settings
Schema settings control how SETN represents your website and content in machine-readable JSON-LD.
Enable only schema that accurately describes the page or entity. SETN may defer overlapping output when a supported SEO/schema provider already owns that responsibility.
Setup Principles
- Prefer accurate data over maximum data.
- Avoid creating schema for content that is not actually present or represented.
- Keep canonical organization information consistent.
- Review provider compatibility before disabling another plugin’s schema.
Organization & Website Schema
Organization and Website schema establish the identity of your organization and website.
These foundational entities may connect to services, authors, topics, pages, articles, FAQs, and other entities in the SETN Knowledge Graph.
If another supported provider already creates equivalent Organization or WebSite schema, SETN may operate in a compatible mode to reduce unnecessary duplication.
Service Schema
Service schema describes services your organization actually provides.
Use clear service names and descriptions that match the corresponding service page. Where appropriate, connect a service to the organization, relevant topics, related articles, FAQs, or service areas.
Avoid creating generic service entities solely for keywords that do not correspond to a real service offering.
FAQ Schema
FAQ schema should represent genuine question-and-answer content available to users.
Use FAQs to clarify products, services, policies, processes, or important customer questions. Do not create invisible FAQ content simply to generate schema.
Google and other platforms may change how FAQ rich results are displayed, but well-structured FAQ content can still be useful as part of your website’s machine-readable knowledge.
Schema Output & JSON-LD
SETN outputs supported structured data using JSON-LD, typically inside <script type="application/ld+json"> elements.
To review output, view the public page source and search for application/ld+json, an entity @id, or a relevant @type.
Use SETN diagnostics and external validators as appropriate, but remember that a validator warning is not always a critical error. Evaluate whether the field is required for the schema type and whether the page actually contains the corresponding information.
