improvement(landing): keyword-forward SEO copy on the home and enterprise pages

[waleedlatif1]

Summary

• Rewrote /enterprise copy against the SEO brief: keyword-forward H1 (Sim is the enterprise AI agent platform for governed workflows.), expanded hero description, new definitional paragraph, and rewritten row H2s/subtitles/card descriptions
• Shortened the enterprise meta description to the suggested one (Build and govern enterprise AI agents in Sim with SSO, approvals, audit trails, versioning, and 1,000+ integrations.)
• Homepage: new title order (The AI Workspace | Build, Deploy & Manage AI Agents | Sim), expanded H1 + hero description, second hero paragraph, rewritten "Describe it. Sim builds it." subtitle, and Everything your AI agents need, in one workspace.
• Added two optional content fields so the copy fits the existing layout contract instead of overloading it: SolutionsHeroConfig.definition (second hero paragraph, rendered by the shared LandingHeroHeader) and SolutionsCardRowConfig.note (second subtitle paragraph, used for the self-hosting line)
• Applied the same entity-explicit theme to the platform pages' row H2s (bare "agents" -> "AI agents") on Workflows, Knowledge, Tables, Files, Logs, and Scheduled Tasks

Notes

• Both suggested H1s dropped "Sim", which the landing rules require in the single H1 (and "AI workspace" alongside it). Kept "Sim" in both while taking the keyword expansion, and worked "AI workspace" into the enterprise hero description so the first 150 visible characters still carry Sim / AI workspace / AI agents.
• Verified every new claim ships: ssoProvider and permissionGroup tables, Enterprise-gated configurable data retention, audit logs, and Docker Compose + Helm self-hosting.
• Solutions pages (/solutions/*) already lead with keyword-bearing H1s and use deliberately terse H2s, so they were left alone.

Type of Change

• Improvement

Testing

Typecheck and lint pass. Copy-only change plus two additive optional props; no visual regression check run.

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)

[vercel]

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

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jul 23, 2026 3:34pm

[cursor]

PR Summary

Low Risk
Copy and optional presentational props only; no auth, data, or runtime behavior changes.

Overview
Landing SEO and GEO copy on the homepage and /enterprise, plus light keyword alignment on several platform pages. No product logic changes.

The homepage gets a new canonical title (HOME_PAGE_TITLE: The AI Workspace | Build, Deploy & Manage AI Agents | Sim) wired through metadata, OG/Twitter, and JSON-LD. Hero H1, primary description, and a new second paragraph (definition) stress AI agent/workflow builder positioning; mothership and product-demo sections get similar keyword tweaks.

/enterprise is rewritten against an SEO brief: new H1, expanded hero + definitional paragraph, shorter meta description, richer row subtitles/card copy, and a self-hosting note on the deploy row.

Two optional layout hooks support this without overloading existing fields: SolutionsHeroConfig.definition → LandingHeroHeader, and SolutionsCardRowConfig.note → SolutionsCardRowHeader (enterprise deploy row uses the latter).

Platform pages (Workflows, Knowledge, Tables, Files, Logs, Scheduled Tasks) only change row H2 wording from “agents” to “AI agents.”

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

[greptile-apps]

Greptile Summary

The PR updates landing-page SEO copy and completes the homepage title synchronization by sharing one title constant across metadata, social previews, and JSON-LD.

• Adds optional secondary hero and card-row paragraphs to support expanded enterprise copy.
• Rewrites homepage, enterprise, and platform-page headings and descriptions with explicit AI-agent terminology.
• Uses HOME_PAGE_TITLE for the homepage title, Open Graph title, Twitter title, and structured-data name.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains in the homepage title synchronization fix.

Important Files Changed

Filename	Overview
apps/sim/app/(landing)/components/home-structured-data/home-structured-data.tsx	Defines and exports the shared homepage title used by JSON-LD and metadata surfaces.
apps/sim/app/(landing)/page.tsx	Replaces duplicated homepage title strings with the shared title constant, completing the previous synchronization fix.
apps/sim/app/(landing)/components/hero/components/hero-header/hero-header.tsx	Adds optional rendering for a second hero paragraph.
apps/sim/app/(landing)/enterprise/enterprise.tsx	Rewrites enterprise SEO and visible copy while using the new optional definition and note fields.

_{Reviews (2): Last reviewed commit: "fix(landing): sync homepage JSON-LD titl..." | Re-trigger Greptile}

[waleedlatif1]

@greptile

[waleedlatif1]

@cursor review

[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 484bda7. Configure here.}