docs: improve query alignment of Vercel app deployment guide (GEO) by vanrensbird · Pull Request #7997 · prisma/web

vanrensbird · 2026-07-03T08:10:28Z

Why

Promptwatch flagged /docs/guides/vercel-deployment as an untapped page: 59 AI crawls in the last 30 days from 2 unique crawlers, but 0 citation-bot visits and 0 AI clicks. Crawlers evaluate the page for Vercel-deployment queries and consistently decide not to cite it.

The likely cause: the page described itself in internal vocabulary ("instant app deployment") instead of the language of the queries it should own (deploying apps programmatically via API, provisioning a database per deployment, AI app builder / agent platform workflows).

What changed

Frontmatter: meta title/description now lead with "deploy apps to Vercel with a database via API" and name the audience (AI app builders, no-code platforms, agent workflows).
Intro: answers the question in the first paragraph with concrete, quotable claims (six API requests, what each does, no dashboard steps), and states what Prisma Postgres is (managed PostgreSQL with built-in connection pooling).
Disambiguation note: routes the three distinct Vercel intents to the right pages (own-app deployment → ORM guide, Marketplace → /guides/postgres/vercel, non-Vercel provisioning → Management API). Helps both readers and AI engines match the right page to the right query.
FAQ section: six self-contained Q&As built only from facts already on the page or in sibling docs (database limits, claim billing transfer, 24h claim code validity, pooling, frameworks, Management API).

No changes to the deployment steps, code samples, or API reference content.

🤖 Generated with Claude Code

Summary by CodeRabbit

Documentation
- Updated the deployment guide to better explain full-stack app deployment on Vercel with a provisioned Prisma Postgres database.
- Clarified the end-to-end API-based flow, from project creation through database setup and code deployment, with no dashboard steps.
- Added an FAQ covering database limits, billing responsibilities, supported frameworks, pooling requirements, and database provisioning options.

Rewrites the intro to answer the target query directly, adds a disambiguation note routing the three Vercel intents (own-app deployment, Marketplace integration, programmatic deployment), and adds an FAQ section with self-contained answers. Addresses a crawl-to-citation gap: the page gets AI crawler traffic but no citations, likely because it described itself in internal vocabulary rather than the queries it should answer. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

vercel · 2026-07-03T08:10:35Z

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

Project	Deployment	Actions	Updated (UTC)
blog	Ready	Preview, Comment	Jul 3, 2026 8:11am
docs	Ready	Preview, Comment	Jul 3, 2026 8:11am
eclipse	Ready	Preview, Comment	Jul 3, 2026 8:11am
site	Ready	Preview, Comment	Jul 3, 2026 8:11am

github-actions · 2026-07-03T08:12:31Z

🍈 Lychee Link Check Report

27 links: ✅ 20 OK | 🚫 1 errors | 🔀 0 redirects | 👻 6 excluded

❌ Errors

apps/docs/content/docs/guides/integrations/vercel-deployment.mdx

[ERROR] https://pris.ly/vercel-app-demo-live | Error (cached)

Full Statistics Table

Status	Count
✅ Successful	20
🔀 Redirected	0
👻 Excluded	6
🚫 Errors	1
⛔ Unsupported	0
⏳ Timeouts	0
❓ Unknown	0

coderabbitai · 2026-07-03T08:12:41Z

Walkthrough

Updates the Vercel deployment guide documentation: revises frontmatter and introductory text to describe a six-request API flow for deploying with a provisioned Prisma Postgres database, and adds a new FAQ section addressing limits, billing, frameworks, and pooling.

Changes

Vercel Deployment Guide Update

Layer / File(s)	Summary
Intro and frontmatter rewrite `apps/docs/content/docs/guides/integrations/vercel-deployment.mdx`	Frontmatter description/meta tags and introduction updated to explain the six-request API flow and platform-builder positioning, with no dashboard steps.
New FAQ section `apps/docs/content/docs/guides/integrations/vercel-deployment.mdx`	Adds FAQ answers on single-API-flow deployment, plan-based database limits, partner access, billing after claim, supported frameworks, pgBouncer/pooling, and Management API provisioning without Vercel.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Related PRs: None specified.

Suggested labels: documentation

Suggested reviewers: None specified.

🐰 A poem for the docs

A rabbit hops through Vercel's door,
Six API calls, nothing more,
No dashboard clicks, just clean, swift flight,
FAQs now bloom, both clear and bright,
Pooling built-in, no bouncer to chase—
Docs polished up, a tidier place.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the main change: improving the Vercel deployment guide’s search/query alignment.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

_{Comment @coderabbitai help to get the list of available commands.}

argos-ci · 2026-07-03T08:13:44Z

The latest updates on your projects. Learn more about Argos notifications ↗︎

Build	Status	Details	Updated (UTC)
default (Inspect)	✅ No changes detected	-	Jul 3, 2026, 8:19 AM

coderabbitai

🧹 Nitpick comments (1)

apps/docs/content/docs/guides/integrations/vercel-deployment.mdx (1)
18-20: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Minor prose polish in disambiguation note.

Static analysis flags two small style nits here: three consecutive bullets start with "To" (line 18-20), and "outside of" on line 20 is redundant ("outside" suffices).
✏️ Suggested tweak
-- To create and manage Prisma Postgres databases programmatically **outside of Vercel**, see the [Management API](/management-api).
+- Need to create and manage Prisma Postgres databases programmatically **outside Vercel**? See the [Management API](/management-api).
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@apps/docs/content/docs/guides/integrations/vercel-deployment.mdx` around
lines 18 - 20, Polish the disambiguation note in the Vercel deployment guide by
revising the three link bullets so they don’t all begin with “To,” and replace
the redundant “outside of Vercel” phrasing in the Management API item with
cleaner wording. Update the prose in the existing bullets in the
vercel-deployment.mdx content, keeping the same links and meaning while
improving style and variety.
Source: Linters/SAST tools

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@apps/docs/content/docs/guides/integrations/vercel-deployment.mdx`:
- Around line 18-20: Polish the disambiguation note in the Vercel deployment
guide by revising the three link bullets so they don’t all begin with “To,” and
replace the redundant “outside of Vercel” phrasing in the Management API item
with cleaner wording. Update the prose in the existing bullets in the
vercel-deployment.mdx content, keeping the same links and meaning while
improving style and variety.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 62c1b24a-d408-41fc-8349-bf1aa5c6f1d6

📥 Commits

Reviewing files that changed from the base of the PR and between 171386a and 30d7af0.

📒 Files selected for processing (1)

apps/docs/content/docs/guides/integrations/vercel-deployment.mdx

Removed all em dashes, added verified expected output to the migrate and seed steps, converted exact prerequisites to a list, and rephrased the 'How it works' and availability headings as questions ('Where does the history come from?', 'Where does the Migrations view appear?') so they match how readers ask, following the GEO pattern from the Vercel deployment guide refresh (#7997). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

) * docs(studio): add Studio with Prisma Next and the Migrations view Prisma Studio's Migrations view reads the migration ledger Prisma Next writes into the database and renders it as a timeline, with a visual diff, the executed SQL, and a schema diff per applied migration. The Prisma Next docs had no Studio coverage at all, so this adds a page and links it from the places a reader would look. New page: /studio/prisma-next — prerequisites, `npm create prisma@next`, Prisma Postgres, the plan/apply loop, launching Studio, reading the view, where it's available (local + Console), limitations, and troubleshooting. Linked from the Studio landing page and getting-started, the four Prisma Next migration pages, the Prisma Next overview, and the Prisma Postgres "Viewing data" guide. Every command and schema block was run against a fresh `npm create prisma@next` project on Prisma Postgres, and the screenshots come from that database's six applied migrations. Notes for review: - The view shipped in @prisma/studio-core 0.32.0; the Prisma CLI only carries a new enough Studio on its `dev` release today, so the page says `npx prisma@dev studio` explicitly rather than implying `prisma@latest` works. Worth a follow-up once it lands in a stable CLI. - Two scaffold gotchas are documented because a reader hits both: `db.orm` is namespace-keyed (`db.orm.public.User`), and Studio needs DATABASE_URL loaded from .env before `--url` resolves. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(studio): prose polish and query-aligned headings Removed all em dashes, added verified expected output to the migrate and seed steps, converted exact prerequisites to a list, and rephrased the 'How it works' and availability headings as questions ('Where does the history come from?', 'Where does the Migrations view appear?') so they match how readers ask, following the GEO pattern from the Vercel deployment guide refresh (#7997). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * docs(studio): rewrite as task-oriented guide Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: Nurul Sundarani <sundarani@prisma.io>

vercel Bot deployed to Preview – site July 3, 2026 08:10 View deployment

vercel Bot deployed to Preview – docs July 3, 2026 08:11 View deployment

coderabbitai Bot reviewed Jul 3, 2026

View reviewed changes

ankur-arch approved these changes Jul 3, 2026

View reviewed changes

ankur-arch merged commit 0c7f2df into main Jul 3, 2026
16 of 18 checks passed

ankur-arch deleted the docs/vercel-deployment-geo branch July 3, 2026 08:16

Navigation Menu

Uh oh!

docs: improve query alignment of Vercel app deployment guide (GEO) - #7997

docs: improve query alignment of Vercel app deployment guide (GEO)#7997
ankur-arch merged 1 commit into
mainfrom
docs/vercel-deployment-geo

vanrensbird commented Jul 3, 2026 •

edited by coderabbitai Bot

Loading

Uh oh!

vercel Bot commented Jul 3, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jul 3, 2026

Uh oh!

coderabbitai Bot commented Jul 3, 2026 •

edited

Loading

Uh oh!

argos-ci Bot commented Jul 3, 2026 •

edited

Loading

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

vanrensbird commented Jul 3, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Why

What changed

Summary by CodeRabbit

Uh oh!

vercel Bot commented Jul 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jul 3, 2026

🍈 Lychee Link Check Report

❌ Errors

Uh oh!

coderabbitai Bot commented Jul 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

argos-ci Bot commented Jul 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vanrensbird commented Jul 3, 2026 •

edited by coderabbitai Bot

Loading

vercel Bot commented Jul 3, 2026 •

edited

Loading

coderabbitai Bot commented Jul 3, 2026 •

edited

Loading

argos-ci Bot commented Jul 3, 2026 •

edited

Loading