fix(landing): complete Organization schema with legalName, foundingDate, and address

[waleedlatif1]

Summary

• Follow-up to fix(landing): complete Organization schema, add CollectionPage/BlogPosting JSON-LD, fix TechArticle rich-result eligibility #5638, which intentionally omitted legalName, foundingDate, and address from the Organization JSON-LD pending real values
• Adds legalName: "Sim, Inc" — matches the entity named throughout the Terms of Service
• Adds foundingDate: "2025"
• Adds address (real registered office: 80 Langton St, San Francisco, CA 94103) as a PostalAddress

Researched schema.org Organization property value before adding: address and legalName are genuine trust/entity signals for Google's Knowledge Panel and AI answer engines (ChatGPT, Perplexity, Google AI Overviews) that parse schema for verified facts; foundingDate is lower-impact but standard practice and harmless to include. All three are purely additive JSON-LD fields — no risk of regression to existing rich results.

Type of Change

• Bug fix

Testing

• bunx tsc --noEmit clean
• bun run lint clean
• Real production build + curled /pricing — confirmed legalName, foundingDate, address all render correctly in the Organization JSON-LD

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jul 13, 2026 8:20pm

[cursor]

PR Summary

Low Risk
Additive JSON-LD metadata on the landing shell with no runtime, auth, or data-path changes.

Overview
Completes the site-wide Organization JSON-LD in SiteStructuredData with entity fields that were deliberately left out earlier.

Adds legalName: "Sim, Inc" (aligned with Terms of Service), foundingDate: "2025", and a PostalAddress for the San Francisco office. Updates the file comment so maintainers keep legalName in sync with apps/sim/app/(landing)/terms.

These are additive schema.org fields only; landing layout and page-specific JSON-LD @id wiring are unchanged.

^{Reviewed by Cursor Bugbot for commit a01ba3a. Configure here.}

[greptile-apps]

Greptile Summary

This PR adds more Organization metadata to the landing JSON-LD graph. The main changes are:

• Added legalName for the company entity.
• Added foundingDate to the Organization node.
• Added a registered-office PostalAddress.
• Updated the maintenance note for the legal name source.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.
• The added fields are static data in an existing JSON-LD object.
• The serializer accepts nested object data and the existing graph references stay unchanged.

Important Files Changed

Filename	Overview
apps/sim/app/(landing)/components/site-structured-data/site-structured-data.tsx	Adds static Organization JSON-LD fields without changing graph IDs or rendering flow.

_{Reviews (1): Last reviewed commit: "fix(landing): complete Organization sche..." | Re-trigger Greptile}

[greptile-apps]

Greptile Summary

This PR adds organization details to the landing-page JSON-LD graph. The main changes are:

• legalName added to the shared Organization node.
• foundingDate added as a static year.
• A PostalAddress added for the registered office.
• A maintenance note added for the legal name source.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
apps/sim/app/(landing)/components/site-structured-data/site-structured-data.tsx	Adds static legal entity metadata to the shared Organization JSON-LD node.

_{Reviews (2): Last reviewed commit: "fix(landing): complete Organization sche..." | Re-trigger Greptile}

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit a01ba3a. Configure here.}