Skip to content
LiftUp
Headless blog CMS

Blog CMS for Next.js, with review built in.

Write, review and publish posts for each product, then serve them to any frontend through the blog API. On publish, LiftUp triggers revalidation on your Next.js site, so the page updates without a redeploy. Calendar, media library and WordPress import included.

Start 14-day Growth trialCompare plans
  • 4-state review workflow
  • On-publish revalidation
  • Flat price, not per seat

Talk to us

See Content on your own site.

Tell us what you’re publishing today and what you’d move off. A human replies with a plan, not a deck.

Goes straight into a LiftUp inbox — scored and on the clock. No card, no deck.

Protected by reCAPTCHA. Google’s Privacy Policy and Terms of Service apply.

Editorial workflow
4-state
Blog API rate limit
60/min
Posts on the Free plan
10
Users on Growth, one price
20

The short answer

How does LiftUp work as a blog CMS for Next.js?

LiftUp Content is a headless blog CMS. Writers draft posts for each product, editors move them from Draft to In review to Published, and old posts go to Archived. The public blog API serves published posts as JSON to any frontend. On publish, LiftUp triggers on-demand revalidation on your connected Next.js site. An editorial calendar, media library and WordPress import are included.

Approval workflow

A four-state approval workflow for every post.

Posts move from Draft to In review to Published, then to Archived when they retire. Editors review and approve in the same editor writers draft in, and comments stay on the post instead of in email threads.

Draft

2

Writers draft, AI assists

In review

2

Comments + approval

Published

2

Live via revalidation

Archived

1

Kept, out of the way

Publishing calls your Next.js revalidation endpointOn publish
  • Draft → In review → Published → Archived
  • Approval routing before a post goes live
  • Editorial comments on every post
  • Content Manager is one of 7 built-in roles

A/B headline tests

A/B test blog headlines on the posts you publish.

Give a post variant titles. The v2 blog API serves the variants to your frontend and records impressions and clicks for each, so you can see which headline earns the click on your blog index and post cards.

  • Variant titles per post
  • Impressions and clicks tracked per variant
  • Served by the public blog API v2
  • On the Growth and Enterprise plans
Headline A/B2,000 impressions
Variant A4.80% · 96 clicks

“Our Q3 pricing changes, explained”

Variant B6.40% · 128 clicks

“We replaced four tools with one console”

B leads on click-through

+33% click-through

Editorial calendar

An editorial calendar that syncs to Google Calendar.

See every scheduled post for the month in one view and set future publish dates. The calendar syncs to Google Calendar, so writers, editors and stakeholders see the schedule in the calendar they already use.

  • Month view of every scheduled post
  • Future publish dates per post
  • Google Calendar sync over Google OAuth
  • On the Growth and Enterprise plans
SeptemberGoogle Calendar synced
CRM vs HubSpot · in review5 scheduled

WordPress to headless

Move a WordPress blog to Next.js without retyping it.

Import your WordPress blog over GraphQL. Run a dry run first to see what will come across, then review and publish from LiftUp. From then on, each publish triggers revalidation on your connected Next.js site.

  • WordPress import over GraphQL
  • Dry run before anything is imported
  • Media library (DAM) for every asset
  • On-publish Next.js cache revalidation
WordPress importDry run first

  1. PostsRunning

    From your WordPress site

  2. Categories + tagsQueued

    Your taxonomy, carried across

  3. MediaQueued

    Into the media library

Posts, taxonomy and media over GraphQL.

How content ships

From idea to live in four steps.

A repeatable editorial loop your whole team runs every week.

  1. 1

    Plan

    Slot the post into the editorial calendar.

  2. 2

    Draft

    Write in the editor — with AI assist for first drafts, outlines, and meta.

  3. 3

    Review

    Editors comment and approve. Set an A/B headline test if you want.

  4. 4

    Publish

    Publish now or on a date. LiftUp triggers on-demand revalidation on your Next.js site.

Everything in Content

What the blog CMS includes.

Scoped per product, permissioned per role, priced per workspace.

Full blog CMS

Create, edit, publish, search, and filter posts.

Editorial workflow

Draft → In review → Published → Archived.

Taxonomy

Categories, tags, and author bylines.

SEO hub

Meta coverage, slug health, and search tie-ins.

Editorial calendar

Scheduled publishing + Google Calendar sync.

Media library (DAM)

Upload, manage, and reuse assets.

WordPress import

GraphQL import with a dry run first.

A/B headlines

Variant titles with impression and click tracking.

Editorial comments

Collaborate inside each post.

On-publish revalidation

Triggers Next.js cache busts on publish.

Public blog API

GET /api/v1/blog — no key for published posts.

Featured + inline media

Cover and inline images per post.

FAQ

Blog CMS questions, answered.

Can’t find what you need? Contact us — we reply fast.

Does the blog CMS have an approval workflow?

Yes. Every post moves through four states: Draft, In review, Published and Archived. Editors review and approve a post before it is published, and editorial comments stay on the post. The workflow and approvals are included from the Starter plan up.

How do published posts reach my Next.js site?

Your frontend reads published posts from the public blog API (GET /api/v1/blog). It needs no API key for published content and allows 60 requests a minute. When a post is published, LiftUp triggers on-demand cache revalidation on your connected Next.js site, so the page updates without a full rebuild.

Can I use LiftUp with a frontend that isn’t Next.js?

Yes. The blog API returns JSON, so any framework, static site generator or backend that can make an HTTP request can render your posts. The on-publish revalidation call is built for Next.js. Other frontends pick up changes through their own caching or rebuild rules.

Can I migrate my WordPress blog to LiftUp?

Yes. LiftUp imports a WordPress blog over GraphQL, and you can run a dry run first to preview the result. If any URL changes during the move, set 301 redirects from the old paths, and check titles and meta descriptions after import. WordPress import is included from the Starter plan up.

How do A/B headline tests work?

You add variant titles to a post. The v2 blog API serves the variants to your frontend and records impressions and clicks for each one, so you can compare click-through rates. Headline tests are included on the Growth and Enterprise plans.

Is the blog CMS priced per seat?

No. LiftUp is priced per workspace, not per user. Free covers 2 users and up to 10 posts. Starter is $49 a month (₹2,499 in India) for 5 users, and Growth is $149 a month (₹7,999) for 20 users and 10 products. CRM, AI and analytics are in the same plan.

Is content kept separate for each product or site?

Yes. Each product in your workspace has its own posts, categories, tags, media and AI writing-style presets, and you manage all of them from one login. Starter covers 3 products and Growth covers 10.

Run your blog where your leads already land.

Plan the post on the calendar, draft it, route it through review and publish to your Next.js site. Enquiries from that same site land in the LiftUp CRM next door.

Start 14-day Growth trialTalk to sales

No credit card · full Growth trial · cancel from the dashboard