fix(landing): return 404 for invalid dynamic route slugs

[waleedlatif1]

Summary

• Add dynamicParams = false to all landing page dynamic routes (integrations, models, blog)
• Invalid slugs now show the custom 404 page instead of a client-side exception

Type of Change

• Bug fix

Testing

Tested manually

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		Apr 15, 2026 6:42pm

[cursor]

PR Summary

Low Risk
Low risk: a config-only change that restricts dynamic routes to generateStaticParams output, affecting routing/404 behavior but not core business logic or data handling.

Overview
Landing dynamic routes now reject unknown slugs. Adds export const dynamicParams = false to the blog post, integration, and model provider/model pages so only slugs returned by generateStaticParams are valid.

This makes invalid /blog/[slug], /integrations/[slug], and /models/[provider]/[model] (and /models/[provider]) URLs return the app’s 404 page rather than attempting to render and throwing client/runtime errors.

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

[greptile-apps]

Greptile Summary

Adds export const dynamicParams = false to all four landing page dynamic routes (blog, integrations, provider, and model detail). With this export, Next.js returns a 404 for any slug not emitted by generateStaticParams instead of attempting to render the page and throwing a client-side exception.

Confidence Score: 5/5

Safe to merge — minimal, targeted change that applies the standard Next.js pattern for 404-on-unknown-slugs across all landing dynamic routes.

All four files receive only the single-line export const dynamicParams = false addition, which is the idiomatic Next.js mechanism for this use case. Each route already had a correct generateStaticParams implementation, so the new export slots in without any other changes needed. No logic, state, or data-fetching is affected.

No files require special attention.

Important Files Changed

Filename	Overview
apps/sim/app/(landing)/blog/[slug]/page.tsx	Added dynamicParams = false to statically gate blog post slugs; correct and consistent with the existing generateStaticParams + revalidate setup.
apps/sim/app/(landing)/integrations/[slug]/page.tsx	Added dynamicParams = false; the existing notFound() guard inside the render function is now unreachable but harmless defensive code.
apps/sim/app/(landing)/models/[provider]/[model]/page.tsx	Added dynamicParams = false to the model detail route; pairs correctly with generateStaticParams iterating ALL_CATALOG_MODELS.
apps/sim/app/(landing)/models/[provider]/page.tsx	Added dynamicParams = false to the provider listing route; pairs correctly with generateStaticParams iterating MODEL_PROVIDERS_WITH_CATALOGS.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Incoming Request\nfor dynamic slug] --> B{slug in\ngenerateStaticParams?}
    B -- Yes --> C[Render static page\n/ revalidate if stale]
    B -- No --> D[dynamicParams = false\nNext.js returns 404]
    D --> E[Custom 404 page shown]
    C --> F[Page rendered successfully]

Loading

_{Reviews (2): Last reviewed commit: "fix(home): remove duplicate handleStopGe..." | 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 33c29cc. Configure here.}