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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview, Comment	Jun 12, 2026 12:58am

PR Summary

Low Risk
Marketing/SEO and static landing metadata only; no auth, billing, or runtime workflow logic changes.

Overview
Landing FAQ accordion now keeps every answer in the DOM (height animation instead of unmounting) so crawlers and FAQPage JSON-LD see full Q&A text; questions are wrapped in h3 with aria-controls wiring.

Integrations SEO: Per-slug FAQs are rewritten with integration-specific facts and related pairings; generic questions move to a single catalog FAQ on /integrations with FAQPage JSON-LD. Integration pages gain INTEGRATIONS_UPDATED_AT (sitemap lastModified, visible last-updated, JSON-LD dateModified), richer metadata/keywords, sr-only summary, expanded SoftwareApplication schema (category, tags), and HowTo JSON-LD is removed. Related integrations scoring adds same category. Catalog JSON shape is integrations + updatedAt.

OG images: createLandingOgImage in shared og-utils replaces models-only helpers; new dynamic PNG routes for /integrations and /integrations/[slug]. Models and integrations pages drop hardcoded openGraph/twitter images (they 404’d vs Next’s hash-suffixed file convention) and remove runtime = 'edge' on OG routes.

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

Greptile Summary

This PR overhauls the landing integration pages for SEO/GEO: FAQ answers are now always in the DOM (collapsed via CSS/framer-motion height animation instead of conditional mounting), making them visible to non-JS AI crawlers; per-integration FAQs are rewritten with integration-specific facts; and dynamic OG images are added for /integrations and /integrations/[slug] while broken hardcoded opengraph-image URL overrides are removed across all model and integration pages.

• FAQ & schema improvements: answers always server-rendered with aria-hidden toggling visibility; h3 headings for questions; HowTo schema dropped; SoftwareApplication gains applicationSubCategory, keywords, and dateModified; catalog-generic FAQs (pricing, agent tool use) consolidated onto /integrations instead of repeating across 207 pages.
• OG image fixes: edge runtime dropped; explicit images: overrides (which 404 in prod because Next serves file-convention images at hash-suffixed URLs) removed from all model and integration metadata; new opengraph-image.tsx files added for /integrations and /integrations/[slug].
• Freshness signals: integrations.json gains a top-level updatedAt field stamped only on real content changes by generate-docs.ts; wired into sitemap lastModified, JSON-LD dateModified, and a visible "Last updated" line on every integration page.

Confidence Score: 5/5

Safe to merge — all changes are landing-page/SEO-layer with no writes to user data, auth, or execution paths.

The diff touches only landing page rendering, FAQ copy generation, OG image routes, sitemap output, and the integrations.json catalog file. The generate-docs.ts change is additive and the early-return/stamp logic is sound. No data-path, auth, or executor code is modified.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[generate-docs.ts] -->|content hash diff| B{Content changed?}
    B -- No --> C[Skip write, keep existing updatedAt]
    B -- Yes --> D["Write integrations.json with updatedAt + integrations array"]
    D --> E["lib/integrations/index.ts"]
    E --> F["sitemap.ts lastModified"]
    E --> G["integrations/slug/page.tsx buildFAQs + dateModified"]
    E --> H["integrations/page.tsx catalog FAQ"]
    G --> I["opengraph-image.tsx /slug"]
    H --> J["opengraph-image.tsx /integrations"]
    G --> K["LandingFAQ always-in-DOM answers"]
    H --> K

_{Reviews (3): Last reviewed commit: "Merge remote-tracking branch 'origin/sta..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review