How a corporate website should use Schema.org

Schema.org should clarify what an object is and how it relates to other objects on the page. It should never manufacture facts that the visible page does not support. A corporate website should begin with one stable company identity, then connect services, articles and pages to it.

Organization provides the entity baseline

The home or about page can describe the legal name, common name, official URL, logo, address and official contact details. Unverified fields should remain absent rather than being completed with guesses.

A stable @id, such as the root URL followed by #organization, lets every page point to the same entity and reduces ambiguity across different company names.

Use the most specific page type

• Use WebSite for the overall site;
• Service for service pages;
• Article for expert content;
• BreadcrumbList for hierarchy;
• FAQPage only when the questions and answers are visible on the page.

The type and properties must agree with the content a visitor can see.

Keep markup synchronized with content

When an article changes, update dateModified. When a page language changes, update inLanguage. When contact details change, propagate them from one verified source to both the visible page and JSON-LD.

Templates should generate the markup while content files and a central company configuration provide the facts. This minimizes contradictions caused by manual copying.

Validate syntax and facts

Structured data testing can find syntax problems, but a passing result does not prove accuracy. Also verify naming consistency, official URLs, dates, sources and whether the same facts appear visibly on the page.