- JSON-LD is a widely used format for adding structured data to HTML pages.
- Structured data should match the visible content and purpose of the page.
- Organization, WebSite, Article, WebApplication, and other page-appropriate types are good starting points.
- @id standard: Organization, WebSite, WebPage, and Article entities should be connected with consistent identifiers based on canonical URLs.
- Visible-content consistency: titles, descriptions, authors, services, and offer information in JSON-LD should not conflict with what users can see on the page.
- GEO impact: Structured data makes the page publisher, page type, and topic relationships clearer to machines.
What does structured data do?
Structured data provides machine-readable context. It does not replace visible content, but it can help crawlers recognize organizations, articles, products, FAQ sections, software applications, and other entities.
Why is JSON-LD widely used?
JSON-LD is typically placed inside a script tag in the head or body of a page. It is easier to manage than inline microdata and can clearly define page-level relationships.
Choose the right structured data type
The structured data type should match the page. A guide page can use Article or TechArticle. A homepage can include Organization, WebSite, and WebApplication. If there is a visible FAQ section, FAQPage should be used only where appropriate and without exaggeration.
Avoid structured data spam
Do not add reviews, prices, claims, FAQ answers, or product information that users cannot see on the page. Misleading structured data can reduce trust and cause validation problems.
Structured data and GEO
AI systems benefit from entity clarity. Structured data helps clarify the page publisher, page type, topic, and relationship to the overall site structure.
Checklist
- Add Organization and WebSite structured data to important pages.
- Use Article or TechArticle for guide content.
- Add FAQ structured data only when visible questions exist and it matches the page purpose.
- Keep @id and URL values consistent with the canonical structure.
- Validate JSON syntax before publishing.
- Update structured data when the page title, URL, or content type changes.
Implementation order
- First determine the page type: guide, service, product, tool, contact, or pricing.
- Add only fields that match visible content to the schema.
- Use consistent @id values for Organization and WebSite.
- Validate it with Google Rich Results Test or Structured Data Markup Validator.
Frequently asked questions
Should the same schema be added to every page?
No. Structured data should match the page’s actual content. Guide pages can use Article or TechArticle, while pricing pages should use appropriate types such as Offer or Product where applicable.
Is it appropriate to put hidden content in schema?
No. Adding claims to structured data that users cannot see on the page is risky. Structured data should support and describe visible content.
Why is JSON-LD preferred?
JSON-LD makes it easy to add structured data without disrupting HTML content and is widely supported by search engines.