improvement(landing): fix SEO redirects/schema, add FAQ content

apps/sim/app/(landing)/components/site-structured-data/site-structured-data.tsx

@@ -39,12 +39,20 @@ const SITE_JSON_LD = {
         'https://www.linkedin.com/company/simstudioai/',
         'https://join.slack.com/t/sim-ott9864/shared_invite/zt-43lp8tc5v-0qrrqHGBKUsvQlpoouH~TA',
       ],
-      contactPoint: {
-        '@type': 'ContactPoint',
-        contactType: 'customer support',
-        url: `${SITE_URL}/contact`,
-        availableLanguage: ['en'],
-      },
+      contactPoint: [
+        {
+          '@type': 'ContactPoint',
+          contactType: 'customer support',
+          url: `${SITE_URL}/contact`,
+          availableLanguage: ['en'],
+        },
+        {
+          '@type': 'ContactPoint',
+          contactType: 'sales',
+          url: `${SITE_URL}/contact`,
+          availableLanguage: ['en'],
+        },
+      ],
     },
     {
       '@type': 'WebSite',

apps/sim/content/blog/copilot/index.mdx

@@ -15,6 +15,19 @@ timeRequired: PT7M
 canonical: https://www.sim.ai/blog/copilot
 featured: false
 draft: true
+faq:
+  - q: "What is Sim Copilot?"
+    a: "Copilot is a context-aware assistant embedded directly in the Sim editor. It has first-class access, with user approval, to your workflows, blocks, logs, and docs, and the system is retrieval-centric with strong guardrails and deterministic execution paths."
+  - q: "How does Copilot retrieve context from my workflows?"
+    a: "Copilot indexes workspace workflows, block metadata, execution logs, and product docs using hybrid scoring that combines BM25 lexical search with embeddings, plus recency decay and per-source caps. Content is chunked with stable anchors so proposed diffs stay line-referential."
+  - q: "Can Copilot make changes to my workflows automatically?"
+    a: "No. All writes are gated behind explicit user approval in a human-in-the-loop model: diffs are reviewed and applied only on approval. Actions are also scope-limited to the open workspace and require explicit user triggers."
+  - q: "What kinds of actions can Copilot take beyond answering questions?"
+    a: "Copilot's tooling spans read-only tools like explain, compare, and search; propose-changes tools that generate diffs; and execution tools for approved actions. It can also help set up test runs and compare outputs side by side."
+  - q: "How accurate is Copilot at proposing fixes or generating block configurations?"
+    a: "The post is explicit that this section is a benchmark scaffold: the listed numbers, including 92% top-1 retrieval and 88% edit accuracy for explaining a workflow block, versus 74% retrieval and 65% edit accuracy for generating a new block configuration, are described as placeholders for the table's structure rather than results from completed benchmark runs. Sim plans to publish a full benchmark harness with anonymized evaluation sets and a detailed methodology post."
+  - q: "Does Copilot use the same permissions as the rest of Sim?"
+    a: "Yes. Copilot works with the same permissions model already used in Sim, and it enforces scope so actions stay limited to the open workspace, with sensitive data policies and redaction applied in logs."
 ---
 
 > This is a technical deep‑dive scaffold for Sim Copilot. We’ll keep updating it as we publish more results and open up additional capabilities.

apps/sim/content/blog/emcn/index.mdx

@@ -15,6 +15,19 @@ timeRequired: PT6M
 canonical: https://www.sim.ai/blog/emcn
 featured: false
 draft: true
+faq:
+  - q: "What is Emcn?"
+    a: "Emcn is the design system that powers Sim's product and brand. It combines strongly-typed, themeable tokens with a composable component library to keep UI consistent and accessible across web surfaces."
+  - q: "Is Emcn open source?"
+    a: "Sim plans to share Emcn's foundations and many of its components as part of its broader open-source commitment. A public docs and examples site is planned for a later release stage."
+  - q: "What accessibility standard does Emcn target?"
+    a: "Emcn is built to be accessible by default at WCAG AA and above, with color contrast tracked at the token level and keyboard and screen reader interactions defined per component."
+  - q: "Does Emcn support dark mode?"
+    a: "Yes. Emcn ships light and dark themes with brand accent tokens, plus an SSR-safe color mode designed to avoid a flash on hydration."
+  - q: "How does Emcn connect Figma and code?"
+    a: "Emcn's Figma library is mapped one-to-one to code components, and its tokens are exported as both TypeScript and CSS variables, giving a direct path from design files to implementation."
+  - q: "What components does Emcn include so far?"
+    a: "The initial set spans primitives like Button, Input, and Select, navigation elements like NavBar and Tabs, feedback patterns like Toast and Dialog, layout building blocks like Grid and Card, and content components like CodeBlock and Table."
 ---
 
 > This post is the scaffolding for Emcn, our new design system. We’ll fill it in as we publish the full documentation and component gallery.
@@ -80,14 +93,6 @@ Emcn is the design system that powers Sim’s product and brand. It aims to give
 - v1: Public docs and examples site  
 - v1.x: Data display, advanced forms, charts bridge  
 
-## FAQ
-
-- What does “Emcn” mean?  
-  A short, crisp name we liked—easy to type and remember.  
-
-- Will Emcn be open‑sourced?  
-  We plan to share the foundations and many components as part of our commitment to open source.  
-
 ## We’re hiring
 
 We’re hiring designers and engineers who care deeply about craft and DX. If you want to help shape Emcn and Sim’s product, we’d love to talk.

apps/sim/content/blog/enterprise/index.mdx

@@ -15,6 +15,19 @@ timeRequired: PT10M
 canonical: https://www.sim.ai/blog/enterprise
 featured: true
 draft: false
+faq:
+  - q: "Can Sim be deployed fully on-premises or in an air-gapped environment?"
+    a: "Yes. Sim can run entirely on your infrastructure via Docker Compose or Helm charts for Kubernetes, with the application, WebSocket server, and PostgreSQL database staying inside your network. Air-gapped setups are supported by pairing self-hosting with Ollama or vLLM for local model inference, so no external network access is required."
+  - q: "Does using our own LLM API keys (BYOK) keep our data from passing through Sim's servers?"
+    a: "Yes. When you configure your own API keys for providers like OpenAI, Anthropic, Google, Azure OpenAI, or AWS Bedrock, prompts and completions route directly between Sim and that provider without passing through Sim's infrastructure. BYOK is available to everyone, not just enterprise plans, and is the default with no Sim-managed keys involved in self-hosted deployments."
+  - q: "Can Copilot be used without sending workflow data to an external AI service?"
+    a: "Yes. Copilot can run entirely within a self-hosted deployment using your own LLM keys, so prompts containing context from your workflows, execution logs, and workspace configuration route directly to your chosen provider and never leave your network."
+  - q: "What identity providers does Sim support for SSO, and what happens when an employee is deprovisioned?"
+    a: "Sim integrates with Okta, Azure AD (Entra ID), Google Workspace, OneLogin, Auth0, JumpCloud, Ping Identity, ADFS, and any SAML 2.0 or OIDC compliant identity provider. Session management ties to your IdP, so logging out there terminates Sim sessions, and account deprovisioning immediately revokes access."
+  - q: "Is Sim SOC 2 certified, and can we get a copy of the report for vendor review?"
+    a: "Sim maintains SOC 2 Type II certification with annual audits covering security, availability, and confidentiality controls, and shares the report directly with prospective customers under NDA. Sim also provides penetration test reports, architecture documentation, and completed security questionnaires (SIG, CAIQ, and custom formats) for vendor review."
+  - q: "Can we restrict which model providers or integrations are available to certain teams?"
+    a: "Yes, through permission groups that are enforced at the execution layer, not just hidden in the UI. Administrators can allowlist approved model providers so unapproved ones fail to execute, disable specific workflow blocks like HTTP calls, and block integrations that haven't cleared security review — while users outside any permission group keep full access by default."
 ---
 
 We've been working with security teams at larger organizations to bring Sim into environments with strict compliance and data handling requirements. This post covers the enterprise capabilities we've built: granular access control, bring-your-own-keys, self-hosted deployments, on-prem Copilot, SSO & SAML, whitelabeling, compliance, and programmatic management via the Admin API.

apps/sim/content/blog/executor/index.mdx

@@ -15,6 +15,19 @@ timeRequired: PT12M
 canonical: https://www.sim.ai/blog/executor
 featured: false
 draft: false
+faq:
+  - q: "How does Sim's executor handle true parallel execution instead of just interleaving branches?"
+    a: "The executor uses an event-driven ready queue: when a parallel block expands into branch-indexed nodes, all entry nodes across every branch enter the queue simultaneously and launch concurrently rather than one after another. Sim doesn't distinguish parallel branches from any other independent nodes that happen to be ready at the same time — concurrency simply emerges from the DAG structure."
+  - q: "How does Sim implement loops in a DAG, which is acyclic by definition?"
+    a: "Sim expands each loop into a sentinel start and sentinel end node during compilation. The backward edge from end to start doesn't count as a dependency initially — it only activates if the loop condition says to continue — which preserves the DAG's acyclic property while still allowing iteration."
+  - q: "Can a Sim workflow pause for human approval in the middle of a loop or across parallel branches?"
+    a: "Yes. When a block returns pause metadata, the executor stops processing its outgoing edges and captures the full execution state, including loop iteration and parallel branch progress. Each pause point gets a unique context ID based on its position, so multiple simultaneous pauses (e.g. three parallel branches each hitting an approval block) can each resume independently."
+  - q: "What gets saved when a Sim workflow pauses, and is it enough to resume later without losing state?"
+    a: "The snapshot serializes block states, execution logs, loop and parallel scopes, routing decisions, and workflow variables to JSON. The critical piece is the DAG's incoming edge state — which dependencies each node still has outstanding — so partially completed loops and in-flight parallel branches can be resumed exactly where they left off."
+  - q: "How does AI-driven routing (a router block choosing a path) stay deterministic and debuggable in Sim?"
+    a: "When a router block returns its chosen block ID, the edge manager activates only the matching outgoing edge and deactivates all others, with deactivation cascading recursively to unreachable downstream blocks. This means you can inspect the execution log afterward and see exactly which path the model chose and which alternatives were pruned."
+  - q: "How does the Sim executor know when a block is ready to run without re-scanning all connections?"
+    a: "Each node tracks its own incoming edges in a set; when a dependency completes, one element is removed from that set, and the node becomes ready the moment the set hits zero. This replaced an earlier approach that rescanned the full connection array after every block execution, which degraded as the graph grew larger."
 ---
 
 Modern workflows aren't just linear automations anymore. They involve a variety of APIs and services, loop over a model's output, pause for human decisions, and resume hours or days later exactly where they left off.

apps/sim/content/blog/mothership/index.mdx

@@ -15,6 +15,19 @@ timeRequired: PT10M
 canonical: https://www.sim.ai/blog/mothership
 featured: true
 draft: false
+faq:
+  - q: "What is Mothership in Sim?"
+    a: "Mothership is the control plane for a Sim workspace—an orchestrator with full context over your workflows, tables, knowledge bases, files, and connected integrations. It can build, test, and deploy workflows from a plain-English description and call any of your 100+ integration tools directly."
+  - q: "Can I trigger Mothership by email?"
+    a: "Yes. Enabling a Sim inbox lets Mothership read incoming emails, execute tasks using your integrations and data, and reply—turning your workspace into an email-driven automation layer."
+  - q: "What is Tables in Sim and how does it work with agents?"
+    a: "Tables gives your workspace a built-in database with typed columns (string, number, boolean, date, JSON) that agents can query, insert into, and update over time. It acts as persistent memory, with 10+ operations available as workflow blocks and direct management by Mothership."
+  - q: "How do Knowledge Base Connectors ground agent responses?"
+    a: "Connectors sync documents from sources like Google Docs, Notion, Confluence, Slack, GitHub, Jira, Linear, HubSpot, Salesforce, Zendesk, Dropbox, OneDrive, Gmail, Discord, and 15+ more, automatically chunking, embedding, and indexing them with incremental sync to stay current. This produces a vector-searchable knowledge base that any workflow block or Mothership can search directly, grounding responses in real business context instead of generic answers."
+  - q: "What's the difference between persistent and until_complete Scheduled Tasks?"
+    a: "Persistent tasks run indefinitely on a set schedule, while until_complete tasks poll repeatedly until a defined success condition is met and then stop automatically. Both support configurable max runs, 40+ timezones, and automatic disabling after 3 consecutive failures."
+  - q: "Can I upload a CSV file and turn it into a queryable table?"
+    a: "Yes. Files uploaded as CSV can be imported directly into Tables—Sim auto-detects delimiters, infers column types, and batch-inserts up to 1,000 rows, turning a raw export into a workflow-ready table in one click."
 ---
 
 I often wonder why AI agents don't already do everything for me today. Why don't they take my meetings for me? Why can't they send follow-ups to customers? Why can't they track the progress of our product launches and just start solving problems for us?

apps/sim/content/blog/multiplayer/index.mdx

@@ -11,6 +11,19 @@ tags: [Multiplayer, Realtime, Collaboration, WebSockets, Architecture]
 ogImage: /blog/multiplayer/cover.jpg
 canonical: https://www.sim.ai/blog/multiplayer
 draft: false
+faq:
+  - q: "Does Sim use CRDTs or operational transforms for multiplayer editing?"
+    a: "No. Sim uses a simpler last-writer-wins strategy with client-generated timestamps rather than Figma-style operational transforms. Workflow building has lower conflict density than text editing, since users typically work on different blocks or parts of the canvas, so the simpler approach is sufficient."
+  - q: "What happens if two users edit the same block at the same time in Sim?"
+    a: "Both clients render their local changes optimistically, then the server persists both updates based on client timestamps and broadcasts each in sequence. Clients receive the conflicting positions or values and converge to whichever carries the latest timestamp, with value conflicts on the same text field resolved by last-to-arrive within a 25ms server-side coalescing window."
+  - q: "What happens if a collaborator deletes a block I'm currently editing?"
+    a: "When the server broadcasts the deletion, your client immediately cancels all pending operations targeting that block, including subblock updates, and removes it from local state without sending those stale operations to the server or showing an error. This client-side cancellation avoids wasting network requests on operations that would fail anyway."
+  - q: "How does undo/redo work when multiple people are editing the same Sim workflow?"
+    a: "Undo/redo is a local, per-user stack: undoing an action generates an inverse operation (e.g., undo an add becomes a remove) that flows through the same operation queue as a normal edit, so collaborators see the change in real time. Undo stacks are per-user and only cover your own actions, and entries referencing entities another collaborator deleted are automatically pruned as invalid."
+  - q: "What happens if a client loses connection while editing a Sim workflow?"
+    a: "Failed operations retry with exponential backoff — structural changes get 3 attempts and text edits get 5. If all retries fail, the queue is cleared and the UI becomes read-only until the user manually refreshes."
+  - q: "Why does Sim separate blocks, edges, and subflows into different database tables?"
+    a: "Blocks, edges, and subflows have different update patterns and conflict characteristics, so storing them in separate normalized tables (workflow_blocks, workflow_edges, workflow_subflows) lets Sim make targeted updates, such as moving a block only touching its position fields, without loading or locking the entire workflow."
 ---
 
 When we started building Sim, we noticed that AI workflow development looked a lot like the design process [Figma](https://www.figma.com/blog/how-figmas-multiplayer-technology-works/) had already solved for. Product managers need to sketch out user-facing flows, engineers need to configure integrations and APIs, and domain experts need to validate business logic—often all at the same time. Traditional workflow builders force serial collaboration: one person edits, saves, exports, and notifies the next person. This creates unnecessary friction.

apps/sim/content/blog/series-a/index.mdx

@@ -17,6 +17,19 @@ canonical: https://www.sim.ai/blog/series-a
 featured: true
 draft: false
 technical: false
+faq:
+  - q: "How much did Sim raise in its Series A?"
+    a: "Sim raised a $7M Series A. The round was led by Standard Capital, with participation from Perplexity Fund, SV Angel, YCombinator, and angels including Paul Graham, Paul Bucheit, Ali Rowghani, and Kaz Nejatian."
+  - q: "Who led Sim's Series A funding round?"
+    a: "Standard Capital led the round, joined by Perplexity Fund, SV Angel, YCombinator, and several notable angel investors."
+  - q: "What will Sim do with the new funding?"
+    a: "Sim is using the funding to double down on its mission: making it simple for teams to build, ship, and scale agentic workflows in production. Separately, Sim plans to keep investing in building the community around the platform."
+  - q: "How many developers and companies use Sim?"
+    a: "Sim has grown to 60,000+ developers on the platform and over 100 companies, ranging from startups to large enterprises, using it in production. The project has also processed more than 10M workflows and reached 18,000 GitHub stars."
+  - q: "Is Sim an open-source project?"
+    a: "Yes. Sim was built to be open source from day one, and that commitment has continued as the project has grown."
+  - q: "What is Sim's long-term vision for agentic workflows?"
+    a: "Sim aims to provide the infrastructure and UX that make agentic software practical at scale, from prototyping to production and from single-agent flows to complex multi-agent systems. Its goal is to be both easy to use and powerful enough to build complex agentic workflows, unlike frameworks that require heavy coding or platforms that limit what can be built."
 ---
 
 ![Sim team photo](/blog/series-a/team.jpg)