One v0 prompt — your Next.js project gets a self-filling blog.
There is no v0 API for posting articles, but a published v0 project is a full Next.js app on a Vercel production deployment, and that is enough. DraftSEO’s prompt has v0 add a route handler that checks every signature, a posts table in your connected database and server-rendered /blog pages — after that, each finished article reaches your project unattended.
| Connection | A single prompt pasted into v0 — the signing secret lives in Environment Variables, never in the chat |
|---|---|
| What v0 builds | Route handler + posts table + /blog pages — posts saved through your Neon or Supabase integration |
| Webhook address | Your production domain only — generated deployment URLs sit behind Vercel’s login |
| Secret | Active once you publish again — Vercel applies a new variable only to later deployments |
| Images | Re-hosted in a public Vercel Blob store — v0 makes stores private by default, and that cannot be switched later |
| SEO | Server-rendered Next.js pages + meta fields — the prompt also asks for sitemap entries, canonical tags and BlogPosting JSON-LD |
Who does what
Paste the prompt into v0, publish, save the signing secret under Environment Variables and publish once more. When the test delivery comes back green, articles keep arriving with no work from you.
v0 wires it up once; DraftSEO keeps the posts coming.
Setup
Copy the build prompt DraftSEO prepares for Next.js projects made in v0.
~30 seconds
v0 adds app/api/draftseo-webhook, a posts table and server-rendered /blog pages. Publish, then take the webhook URL from the production domain.
~a few minutes
From the Project menu open Settings → Environment Variables, save DRAFTSEO_WEBHOOK_SECRET for Production and republish so the new deployment can read it.
~2 minutes
Send the test from DraftSEO; a green result means your route accepted the HMAC signature.
~1 minute
New articles land in your v0 app’s database and show up on /blog without a redeploy.
Ongoing · zero clicks
FAQ
Your v0 project is a Next.js app, so it can run its own server code. The prompt has v0 write a route handler that verifies DraftSEO’s HMAC signature, saves each article to your database and serves it on /blog — DraftSEO simply posts every finished article to that route.
Your production domain — your-project.vercel.app or your own domain — followed by /api/draftseo-webhook. A generated deployment URL such as your-project-abc123.vercel.app is protected by Vercel’s login, so DraftSEO is turned away before your route ever runs.
Vercel applies an environment variable only to deployments made after it was added. Publish the project again once DRAFTSEO_WEBHOOK_SECRET is saved for Production, then resend the test.
Article images are shown to every visitor, and a private store cannot serve them. v0 creates Blob stores private by default and a store cannot be made public afterwards, so the prompt asks for a public store and uploads each image with public access.
Yes. The prompt has /blog and /blog/[slug] rendered per request, or revalidated after every save, so a delivered article shows up on its own. Publishing again is only needed after you change an environment variable.
No card required. v0 builds the route; DraftSEO keeps /blog stocked.