[vanrensbird]

What changed and why

content/04-postgresql/03-5-ways-to-host-postgresql.mdx was competing with the Prisma Postgres pages for queries like "postgresql hosting" and "managed postgres". This adds three exact-anchor internal links and retargets the FAQ free-tier link. No other copy was rewritten.

1. managed PostgreSQL hosting → https://www.prisma.io/postgres
   In "Databases managed by cloud providers": "Perhaps the most familiar type of managed PostgreSQL hosting is the kind offered by cloud or hosting providers."
2. postgres hosting → https://www.prisma.io/postgres
   In "Comparing your options at a glance": "The table below summarizes how the main postgres hosting approaches compare across the factors that usually drive the decision."
3. free PostgreSQL hosting → https://www.prisma.io/postgres/free-postgresql-hosting
   In the FAQ "Is there a free way to host PostgreSQL?": "several managed providers offer free PostgreSQL hosting".
4. The same FAQ's "start on it" link no longer goes to the Prisma Console login (console.prisma.io/login?...faq-free). It now points at https://www.prisma.io/postgres/free-postgresql-hosting.

The step-by-step "Sign in to the Prisma Console" link is unchanged. It is not the FAQ free-tier link.

The source for this page is prisma/dataguide, not prisma/web (prisma/web only rewrites /dataguide to the Data Guide deploy). Reference for the earlier FAQ handoff: prisma/web#8444. Those patches rewrite FAQ copy and add FAQPage JSON-LD, which this file has since drifted past, so they were not applied.

How it was verified

Diff is three link edits in one MDX file. No commands, SQL, or examples changed, so nothing was re-run against a database. npm test, npm run typecheck, and npm run build were not run.

Checklist

• Every command and SQL example I added or changed was run, and the output shown is the output I got.
• Examples use secure defaults (passwords, least privilege, localhost bindings) and no real credentials.
• Versions are named where behavior differs, and there is no @latest in install commands.
• lastUpdated is set only on articles that were substantively reviewed and re-tested.
• npm test, npm run typecheck and npm run build pass.
• Changes to authentication, permissions, encryption or destructive DDL are pointed out for expert review.

[vercel]

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

Project	Deployment	Actions	Updated
dataguide	Ready	Preview	Nov 6, 2026 3:17pm UTC

[prisma-gizmo]

✅ Gizmo reviewed 60bc5cc — posted 2 inline comment(s) this pass.

Open findings: 🟡 1 minor

Change walkthrough

This PR is an SEO-motivated link edit to content/04-postgresql/03-5-ways-to-host-postgresql.mdx: it adds three exact-anchor internal links pointing at the Prisma Postgres marketing pages and retargets one existing link, with no copy or code changes beyond the link syntax. The three new links target high-value search phrases — “managed PostgreSQL hosting” in the cloud-providers section (line 160), “postgres hosting” in the comparison-table intro (line 277), and “free PostgreSQL hosting” in the FAQ (line 318) — all resolving to prisma.io/postgres or its /free-postgresql-hosting page; the FAQ's “start on it” CTA was simultaneously repointed from the Prisma Console login to the same /free-postgresql-hosting page. How it fits the codebase: Link conventions. The repo widely uses concept-anchored links to topically-matched Prisma pages (e.g. hipaa → /postgres/hipaa, “missing DATABASE_URL” → /postgres/database-url-missing); this PR extends that pattern with concept anchors. Attribution consistency. The file's pre-existing promotional links carry utm_source=dataguide tracking parameters (the only UTM-tagged links in the repo); the new links are untagged, matching the file's other plain links, so the file now mixes both styles. Link checking. The repo's link checker only validates links into the Data Guide itself, so these external targets would otherwise go unchecked by CI. Verification policy. The article is recorded as unreviewed in content-verification.json with no source-hash pinning, so the content change cannot break the build's verification gate; lastUpdated was left alone per CONTRIBUTING.md, since link edits aren't substantive re-tests, and no commands, SQL, or examples changed.

[github-actions]

This PR changes the following pages (Vercel Preview Deploy links):

• /dataguide/postgresql/5-ways-to-host-postgresql (currently)

(Note that links will only be valid after Vercel preview deploy succeeded)

[prisma-gizmo]

New findings: 🟡 2 minor · trace

[prisma-gizmo]

No Gizmo finding is open and the head commit has been reviewed. Approving.