Structured data describes a webpage and its entities in a machine-readable vocabulary. On an IR website, it can help express the relationship between the company, its pages, articles, and other supported content. It should accurately reflect the public page, not create a second hidden version of the company's story.
Start with the page's purpose and the visible facts. Then select an appropriate type, connect verified identifiers, and validate the implementation.
Establish a consistent company identity
Use the company's approved name and official URL for its Organization representation. Include other identity fields only when they are verified and appropriate. Schema.org's Organization vocabulary defines the available properties; the existence of a property is not evidence that a value is correct. [1]
Use one consistent identifier for the same organization across the site. In implementation terms, an @id lets related markup refer to that entity. A planned identifier such as the official homepage followed by an organization fragment should be coordinated with existing site markup before deployment.
Keep the website publisher distinct from any company discussed in an article. For VendorGroup's resource center, VendorGroup is the publisher; a client issuer mentioned in an example would be a separate entity, not an alternate name for the publisher.
Choose markup that fits the page
For an editorial resource article, Article is an appropriate candidate. Map its headline, page URL, actual author, publication date, and meaningful modification date to the published page. Google provides Article implementation guidance, and Schema.org defines the underlying vocabulary. [2] [3]
Use BreadcrumbList for the page's genuine place in the site hierarchy. The breadcrumb should describe a navigational path that makes sense to readers. [4]
Do not automatically label every IR page as an article. An archive, company overview, event page, or video page has a different purpose. Assess suitable types against current documentation and actual visible content before adding them.
Keep financial disclosures distinct
Website schema is not the same as financial-statement tagging. The SEC's XBRL APIs serve structured financial data from filings, while general web schema describes web content and entities. [5]
Do not present a website schema installation as replacing filing requirements or as a way to certify a financial figure. If a page displays a figure, preserve the approved source, period, units, and qualifications in the visible content.
The SEC filings guide covers the website's access role. The schema layer should describe that role accurately rather than imply that the website is the filing system.
Validate facts as well as syntax
Review the generated markup against the page. Check names, URLs, dates, author identity, and any image used. Omit unknown information instead of filling a field with an invented credential or stock photo presented as an author.
Google's structured-data guidelines require representative content and do not guarantee a search feature simply because markup validates. [6] A successful technical test is one part of acceptance; factual consistency and current feature eligibility still need review.
Include markup in regression checks after template changes. Confirm that an archived article does not acquire a false new publication date and that a copied page does not retain another page's canonical identity.
Set realistic search expectations
Structured data can be useful within a broader SEO program, but it should not be sold as an AI citation switch. The AI visibility guide covers source quality, access, and measurement alongside markup.
Keep useful questions and answers in the visible article. Google's documentation records the retirement of FAQ rich results in May 2026, so an FAQ section should not be promoted as a current route to that feature. [7]
Questions companies ask
Does every IR page need the same schema?
No. Select markup according to the page's purpose and visible content. Reuse consistent organization identity without forcing every page into one type.
Is a named author required to be invented for Article markup?
Never invent one. Use the real approved authorship shown on the page, whether an actual person or an appropriate organization.
Should the modification date change every day?
Use a date that reflects a meaningful content change under the site's publishing policy. Do not fabricate freshness.
What should be delivered with schema work?
Request the field mapping, verified entity identifiers, validation evidence, and the process for keeping markup aligned with page updates.
Include those deliverables in a VendorGroup website scope so structured data remains part of the content system after launch.
Related VendorGroup resources
- SEO for Investor Relations Websites
- AI Visibility for Investor Relations Websites
- How Search Engines and AI Systems Find Public Company Information
