Paperboy for Next.js
Paperboy has no Next.js connector. It gives your AI builder a prompt that adds a /blog reading Paperboy's public feed. The first article is free.
Paste-in promptPaste-in prompt (a /blog that reads Paperboy's JSON), or a webhook
Short answer as of October 29, 2026
As of October 29, 2026, Paperboy gives you a prompt that tells your coding agent to build a /blog in your Next.js app that reads articles from Paperboy's public JSON feed, so new articles appear without a redeploy. If you would rather receive articles than fetch them, a signed webhook can POST each one to a route handler.
Set up
How it connects: Paste-in prompt (a /blog that reads Paperboy's JSON), or a webhook.
Paste your site address into Paperboy and write the first article free.
In Publishing, choose "Paste a prompt into your AI site builder" and set where the blog will live, for example https://yoursite.com/blog.
Copy the prompt and give it to the agent that works in your repo (Claude Code or Cursor, for example). It asks for /blog and /blog/[slug] pages that fetch on the server, and it names the feed's two endpoints.
Review what the agent built. The prompt asks for the title tag and description from the feed, a canonical link, the JSON-LD in the head, a sitemap entry per article, an IndexNow key file at your site root and a Blog link in the navigation.
Deploy. Paperboy counts the prompt as installed the first time your site calls the feed.
POST https://your-endpoint.example/paperboy
Content-Type: application/json
X-Paperboy-Signature: sha256=<HMAC-SHA256 of the raw body, hex>
User-Agent: Paperboy-Webhook/1.0
{
"event": "article.published", // or "article.updated", or "test"
"sent_at": "2026-10-29T12:00:00.000Z",
"site": { "id": "...", "url": "https://yoursite.com" },
"article": {
"id": "...", "title": "...", "slug": "...",
"meta_title": "...", "meta_description": "...", "excerpt": "...",
"html": "...", "markdown": "...",
"faq": [{ "q": "...", "a": "..." }], "faq_html": "...",
"schema_json_ld": [ ... ],
"sources": [ ... ],
"published_at": "..."
}
}Paperboy shows the exact values in your dashboard. Nothing here is a real key.
What you get
What lands on your site, every time an article passes its fact check.
The article body as HTML: an H2 and H3 outline, tables or numbered steps where they make the answer easier to scan, and inline links to the sources it cites.
Your site decides the layout. The prompt asks the builder to use your fonts, header and footer, to set the title tag and meta description from Paperboy's fields, and to add the canonical address.
Article and FAQPage JSON-LD from the feed's schema_json_ld field, which the prompt tells the builder to put in the page head.
A short FAQ of three to six questions, written into the page, plus Article and FAQPage JSON-LD.
Two to four links to your own pages (picked from the pages Paperboy read on your site) and one call to action link to the address you chose.
Sitemap entries for every article (the prompt asks for them with lastmod from updated_at) and an IndexNow key file at the root of your site.
No images inside the article body today. The hosted blog adds a 1200 by 630 share image for each article; other methods do not.
Honest limits
What Paperboy does not do here, so there are no surprises after you sign up.
Next.js documents Route Handlers as route.ts files in the app directory that export functions named after HTTP methods, POST included (read October 29, 2026). That is the shape a webhook receiver takes, and the signature check above belongs at the top of it.
IndexNow's documentation says the key is 8 to 128 characters and is checked against a file on your own site (read October 29, 2026). That is why the prompt asks for a text file at your site root named after the key.
You own the rendering. The prompt describes the pages, but your agent writes the code, so read it before you ship.
The feed returns published articles only. It needs no API key, and anyone can read it, because the articles are public.
The prompt asks for server rendering with a cache of at most 10 minutes, so a new article can take that long to show. Next.js caching rules change between versions; check the cache setting your agent chose against the docs for your version.
If you would rather push than pull, use the webhook method and a route handler. Check the signature before you trust the body.
Compare
Each platform has its own route, because each one exposes something different. Every row links the platform's own docs.
| Platform | How Paperboy connects | What you set up | Checked against |
|---|---|---|---|
| Next.js | Paste-in promptPaste-in prompt (a /blog that reads Paperboy's JSON), or a webhook | A prompt your AI builder or coding agent runs. | Next.js documentation: route handlersRead Oct 29, 2026 |
| Astro | Paste-in promptPaste-in prompt (a /blog that reads Paperboy's JSON), or a webhook | A prompt your AI builder or coding agent runs. | Astro documentation: content collections and loadersRead Oct 29, 2026 |
| WordPress | Direct connectionDirect connection (WordPress REST API) | A login key from WordPress. Nothing to install. | WordPress REST API handbook: authentication and application passwordsRead Oct 29, 2026 |
| Ghost | Direct connectionDirect connection (Ghost Admin API) | A login key from Ghost. Nothing to install. | Ghost Admin API documentationRead Oct 29, 2026 |
| Webflow | Hosted blogHosted blog on a subdomain, or a webhook you connect | One DNS record and a Blog link in your menu. | Webflow Data API: create collection item (staged)Read Oct 29, 2026 |
| Framer | Hosted blogHosted blog on a subdomain, or a webhook you connect | One DNS record and a Blog link in your menu. | Framer Server API introductionRead Oct 29, 2026 |
Statements about each platform come from its own documentation, read on October 29, 2026. Vendors change their pages, so confirm there. See all 13 platforms.
FAQ
No. Paperboy has no GitHub or git integration. Your site reads the feed at request time, or you receive articles by webhook and write files yourself.
No. The two feed endpoints are public and read-only, and they answer with published articles only.
Not if the pages fetch on the server and cache briefly, which is what the prompt asks for. If your agent built the pages statically instead, they will need a rebuild.
Yes. Choose the webhook method. Paperboy POSTs signed JSON with the HTML and Markdown, and a Next.js route handler can verify the signature and store the post.
A header named X-Paperboy-Signature holding sha256= and the hex HMAC-SHA256 of the raw request body, using the secret Paperboy generated for your site.
Sources
Statements about Next.js come from its own pages, read on October 29, 2026. Vendors change their pages, so confirm there. Statements about Paperboy come from how it works in the product today. If we got something wrong, tell us at hello@paperboyseo.com.
Keep going
Paste your address. In under ten minutes you read a finished article written for your site, with its full fact check. Free, no card.
Prefer to run it yourself? Self-host it (repo coming soon). Using an agent? Add the MCP server.