The Next.js blog package (searchblueprint-nextjs-blog) gives your Next.js site a ready-made blog. It scaffolds a list page, article pages, tag pages and a sitemap into your app, then fills them from the articles your project publishes. Nothing to host on your side. It reads the content API with a scoped credential, so there is no CMS to run and no markdown pipeline to write.
The package is on the public npm registry as searchblueprint-nextjs-blog, so npm install reaches it with no extra setup.
What to know before you start
Use it when the project's site is Next.js on the App Router and you want articles live without building blog plumbing. Already have a blog system in the repo? Then the GitHub connection committing markdown into your existing content folder is the lighter path, because it leaves your rendering alone.
The package renders your own generated article HTML, fetched with your own credential. That is the same trust model every headless-CMS Next.js blog uses.
Set up the package
To set it up:
- In the project's
Publishingtab, openDeveloperand create a content API key. - In your Next.js app, run
npm install searchblueprint-nextjs-blogand thennpx searchblueprint-nextjs-blog. The second command scaffoldsapp/blog(orsrc/app/blog) and never overwrites a file you already have. - Put the value in
.env.localasSEARCHBLUEPRINT_API_KEY. - Set
NEXT_PUBLIC_SITE_URLto your site's address so canonical and sitemap URLs come out absolute. - Deploy.
/bloglists your articles and/blog/<slug>renders each one.
Keep SEARCHBLUEPRINT_API_KEY server-side. A NEXT_PUBLIC_ prefix would ship it to the browser.
What happens after you publish
Pages render with ISR (revalidate = 3600). A newly published article shows up within the hour and no redeploy is needed. Each article page carries its title, description and OpenGraph metadata, and /blog/sitemap.xml lists every article for Search Console.
Limits and usage
- The package renders content. Publishing cadence and article quality are the calendar's job.
- ISR means up to an hour between publish and page. Lower
revalidatein the scaffolded routes if that is too slow for you. - One credential covers one project. A second project means a second install with its own value.
- The scaffold expects
app/orsrc/app/. A Pages Router site is not supported.
If something isn't working
The blog list is empty. SEARCHBLUEPRINT_API_KEY is missing from the deployment's environment, or it belongs to a different project. Your local .env.local does not travel to Vercel on its own.
An article page 404s right after publishing. ISR has not refreshed yet. Wait for the revalidate window, or trigger a redeploy if you cannot wait.
The build fails after scaffolding. Almost always a Pages Router project, which the scaffold cannot serve. Use the GitHub connection for those sites instead.