What this FAQ covers
This page answers recurring questions about schema and json-ld for website owners, agencies, and technical teams. The answers define practical boundaries, identify the evidence that matters, and explain when a question requires account-specific, technical, contractual, or legal review.
- What is schema markup?
- What is JSON-LD?
- Does schema improve rankings?
- Can I use more than one type?
Use the answers responsibly
Apply each answer to the actual website, scope, agreement, and evidence. Avoid adding a type because it is available rather than because the page represents that entity. When the decision could affect production availability, security, accessibility, billing, privacy, or contractual commitments, document the responsible reviewer and verification plan.
Questions and answers
01What is schema markup?
Schema markup is structured data that describes entities, properties, and relationships represented by a page.
02What is JSON-LD?
JSON-LD is a JSON-based linked-data format commonly placed in a script element with type application/ld+json.
03Does schema improve rankings?
Structured data can improve machine understanding and eligibility for supported features, but it does not guarantee ranking improvement or rich results.
04Can I use more than one type?
Yes, when the page represents multiple connected entities. Use stable @id values to connect them rather than publishing inconsistent duplicates.
05Where should JSON-LD be placed?
It can be placed in the head or body. The rendered markup must be valid, accessible to the consumer, and consistent with the page.
06What is @id?
A stable identifier for an entity that other objects can reference.
07What is the difference between Schema.org validity and Google eligibility?
Schema.org defines a broad vocabulary. Google separately documents the types and properties used by its current structured-data features.
08Does valid FAQPage schema guarantee FAQ rich results?
No. Vocabulary validity does not guarantee that a consumer currently supports or displays a feature for the site or query.
09Does valid HowTo schema guarantee a HowTo rich result?
No. Check the consumer's current supported-feature documentation separately.
10What is the difference between an error and a warning?
An error may prevent parsing or feature eligibility. A warning often indicates an optional or recommended value, but it should be added only when accurate.
11Should schema describe hidden content?
No. Structured data should represent content visible to people on the page, subject to the specific feature rules.
12How do I validate schema?
Check JSON syntax, vocabulary, current consumer requirements, visible consistency, crawl access, and the rendered production page.
13Can plugins create duplicate schema?
Yes. Themes, SEO plugins, ecommerce plugins, event plugins, and custom code can publish overlapping or conflicting entities.
14Should every page use the same schema?
No. Reusable site entities can be consistent, but the page type and main entity should match the visible purpose of each route.
Turn schema and json-ld into an accountable record.
A clear, supportable answer set for schema and json-ld linked to the relevant workflow or policy.