[vanrensbird]

What changed and why

content/04-postgresql/03-5-ways-to-host-postgresql.mdx was ranking for hosting queries that should land on the Prisma Postgres product pages. This adds exact-anchor links in sentences that were already there. The article is not rewritten.

The tested patches in prisma/web#8444 (.handoff/dataguide-5-ways-to-host-postgresql-faq/) no longer apply. The page has since grown the laptop-migration copy, the paid-plan backup wording, and the current provider list, so those anchors are fitted to the current sentences instead.

Anchors:

• managed PostgreSQL hosting → https://www.prisma.io/postgres
  In Databases managed by cloud providers, the opening sentence already used this phrase. Only the link was added.
• postgres hosting → https://www.prisma.io/postgres
  In Comparing your options at a glance, the table intro now reads "main postgres hosting approaches".
• free PostgreSQL hosting → https://www.prisma.io/postgres/free-postgresql-hosting
  In the FAQ Is there a free way to host PostgreSQL?, "a free tier" is now this link. The Free plan facts in that answer are unchanged.
• 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 Console link in Create your first Prisma Postgres database is unchanged.

After this ships, request indexing for the live article:

https://www.prisma.io/dataguide/postgresql/5-ways-to-host-postgresql

The source for that URL is this repo. prisma/web only rewrites /dataguide/* to the Data Guide deploy.

How it was verified

No commands or SQL were added or changed. The two destination URLs were opened: https://www.prisma.io/postgres/free-postgresql-hosting returns the Free PostgreSQL hosting page, and https://www.prisma.io/postgres is the existing product URL already used in this article.

npm test, npm run typecheck, and npm run build were not run. The edit is three external links in one MDX file, and the guide's link checker only validates links inside /dataguide.

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:16pm UTC

[prisma-gizmo]

✅ Gizmo reviewed 4c38a18 — posted 0 inline comment(s) this pass.

Open findings: none

Change walkthrough

This PR adds exact-anchor outbound links in content/04-postgresql/03-5-ways-to-host-postgresql.mdx so the article ranks and converts for hosting-related search queries, routing readers to the Prisma Postgres product pages. Three lines change; no facts, commands, tables, or structure are altered.

Fit with the codebase

• The edit follows the article's existing link conventions: www.prisma.io links in this article (the provider list, the docs and blog links) carry no UTM parameters, while the Console login and pricing links in "Create your first Prisma Postgres database" keep their UTMs and were deliberately left unchanged. The new links match the first group.
• The destinations are consistent with how the article already references Prisma Postgres — the same two URLs' parent (https://www.prisma.io/postgres) already appears in the cloud-provider list at line 172.
• src/cta/pageMap.ts:37 already maps this article to the postgres_hosting cluster at high priority, so the CTA side needs no change.
• content-verification.json records this article as unreviewed / not-applicable, so the build's hash-evidence checks for executed articles don't apply and no registry update is needed.
• lastUpdated was correctly not bumped, per the AGENTS.md rule for changes that aren't a substantive re-test; the verification checklist boxes for tests are likewise honestly unchecked, and no code or build paths are touched.

[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: none · trace

[prisma-gizmo]

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

[vanrensbird]

Closing as a duplicate of #544, which is the PR we're keeping.