Next.js integration

Autonomous content for your Next.js app.

Connect Blogged to your Next.js blog with a server receiver, PostgreSQL, signed delivery, copied images, and reviewed article updates.

External publishing requires a paid content plan.

One connected workflow

  1. 1Create and review in Blogged
  2. 2Deliver to Next.js
  3. 3Verify the public article
  4. 4Review updates when content changes

Connecting a site does not change routing. Save destinations for new eligible articles when you are ready.

How Blogged works with Next.js

Install Blogged's Next.js receiver to deliver approved articles into your own application. The receiver keeps durable publication records and handles signed publishing operations while your app serves the content.

Connect

Download the receiver, configure its database and signing secret, deploy it, and verify its endpoint in Blogged.

Publish

Receive articles, copy images, handle ordered updates and withdrawal, and report completion through signed receipts. The supplied receiver supports full articles and noindex summaries.

Know the boundaries

This is a developer integration. Your app owns page rendering, hosting, SEO output, and deployment. Content API reads complement delivery but do not prove an article is live.

What you need to connect

A Node.js server, durable PostgreSQL storage, a supported after() request lifetime, and the supplied receiver. Static export is not supported.

Read the connection guide Download receiver

Included with paid content plans

Publishing integrations require an eligible paid content plan. Free Projects and trials do not include external publishing. Provider fees and setup requirements may apply.

External delivery, summaries, and retries do not consume another Post. Existing content creation and review rules still apply.

Compare plans

Keep control after the first publish.

Reviewed updates

Inspect your CMS version before sending a reviewed update. Detected human edits require review; autosave does not overwrite the external copy.

Read the guide

Verified delivery

Follow delivery activity from pending to verified Live. Withdrawal tracks each managed copy until its removal is confirmed.

Read the guide

External website analytics

Collect consented visits and configured conversions for verified articles. Install tracking on your site; reporting is separate from hosted-blog analytics.

Read the guide

Content API and signed delivery

Read approved releases with destination-scoped server keys. Custom receivers preserve article identity, copy images, and confirm completion.

Read the guide

Next.js publishing questions

How does Blogged publish to Next.js?

Install Blogged's Next.js receiver to deliver approved articles into your own application. The receiver keeps durable publication records and handles signed publishing operations while your app serves the content.

Can I use this with a statically exported Next.js site?

The supplied receiver requires a Node.js server and PostgreSQL; Next.js static export alone is not supported. A different build pipeline needs a custom receiver implementing the signed delivery contract.

Can I review changes before updating my CMS?

Yes. Save your working copy in Blogged and inspect the external version before publishing a reviewed update. Detected CMS edits require review. Importing supported CMS text does not import advanced widgets or CMS images, and existing Autopilot authority still applies.

Is external publishing included in the Free Project or trial?

Publishing integrations require an eligible paid content plan. Free Projects and trials do not include external publishing. Provider fees and setup requirements may apply.

Will connecting a CMS move my existing articles?

No. Connecting alone does not change publishing. Save your destinations to route new eligible articles. Existing drafts and published articles keep their existing destination.

Do integrations use additional Post allowance?

External deliveries, summaries, and retries do not consume another Post. Article creation keeps its existing allowance and billing rules. CMS hosting and provider fees are separate.

The workflow behind your publishing.