Describe the organization and founder without invented authority.

Build the business and person records from supported facts.

Organization and Person descriptions should identify a real business and individual without manufacturing authority. Begin with the visible company record and the person’s approved profile. Keep the organization’s name, website and identifiers separate from the person’s name, role and biography. A founder is connected to a business; the founder is not the business.

For each proposed fact, record its controlling source, visible location, scope, date checked and reviewer. A company’s own approved records can support its identity and current contact routes; a professional qualification, legal registration or award needs the relevant evidence and permission to publish. A confident draft, a company name match or a template placeholder is not sufficient evidence.

The Organization definition and Person definition describe the available vocabulary. Their property lists are possible descriptions, not a requirement to fill every field. Omit unsupported optional data instead of inventing an impressive but unverifiable record.

Use organization identifiers with their exact scope.

Choose one accepted organization @id and reference it consistently. The public name and homepage help readers recognize the business, while a legal name, registration reference or other identifier can disambiguate it when that fact is appropriate, supported and permitted. A brand, legal company, local branch and product may require separate nodes rather than a single combined identity.

Use the field whose meaning fits the source. A registration number is not a phone number, a website address is not an organization identifier issued by a registry, and an @id chosen by the site is not proof of legal registration. Preserve the issuing system, jurisdiction or other necessary scope when an identifier would be ambiguous alone. Never create a plausible number to satisfy a field.

Check the approved contact route before adding telephone, email, address or contactPoint. Do not publish a private founder address or personal contact details merely because a search found them. A company operating online does not justify inventing a public office location. Keep volatile facts attached to a responsible company record and a review trigger.

Model a fictional agency and founder from a finite brief.

This example is entirely fictional and uses reserved example.com URLs. The stipulated company page says Example Agency is the organization’s public name, its homepage is https://example.com/, and Morgan Lee founded it. Morgan’s visible approved profile says Morgan is currently Director at Example Agency. The agency publishes that profile. No awards, legal registration, external identity profiles, customer results or qualifications are supplied.

{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Example Agency",
      "url": "https://example.com/",
      "founder": {
        "@id": "https://example.com/people/morgan-lee/#person"
      }
    },
    {
      "@type": "Person",
      "@id": "https://example.com/people/morgan-lee/#person",
      "name": "Morgan Lee",
      "url": "https://example.com/people/morgan-lee/",
      "jobTitle": "Director",
      "worksFor": {
        "@id": "https://example.com/#organization"
      }
    },
    {
      "@type": "ProfilePage",
      "@id": "https://example.com/people/morgan-lee/#webpage",
      "url": "https://example.com/people/morgan-lee/",
      "name": "Morgan Lee \u2014 founder and director",
      "mainEntity": {
        "@id": "https://example.com/people/morgan-lee/#person"
      },
      "publisher": {
        "@id": "https://example.com/#organization"
      }
    }
  ]
}

The Organization owns the founder relationship and references Morgan’s Person ID. The Person owns the current job title and worksFor relationship because this fictional brief explicitly supports them. The ProfilePage represents the document, references Morgan as mainEntity and identifies the agency as publisher. Different fragments keep the person and page distinct even though they share a profile URL.

No sameAs field is present because the brief supplies no verified external identity reference. No legalName, registration number, address, logo, award or educational credential is guessed. The example is a teaching candidate, not a live graph for a real business and not evidence of a search feature outcome.

Review the whole identity path before release.

Check syntax, term fit, relationship direction, page-versus-entity distinction, visible facts and final URLs. Inspect theme and plugin output for duplicate organization or person identities. A profile can be accurate while another template still emits an old role or a conflicting ID. Update affected references together and keep the change record.

Google’s structured data policies make accuracy and relevant visible content part of the review. A general vocabulary match or successful parse does not guarantee indexing, a knowledge panel, rankings or another search appearance. Check current platform requirements only for the specific feature being considered.

Use the structured data hub for the broader description and testing path. Return to the semantic SEO learning overview when source ownership, business identity or page purpose needs clarification. Keep one accountable reviewer for identity changes after release.