SEO by platform
SEO for Next.js
Two paths for a Next.js site. The blog package scaffolds list, article, tag and sitemap routes and fills them from the articles your project publishes, with nothing to host on your side. Or commit markdown into your existing content folder through the GitHub connection and leave your rendering alone.
How publishing works on Next.js
The package reads the content API with a scoped credential, so there is no CMS to run and no markdown pipeline to write. It scaffolds app/blog into your repo without overwriting files you already have, pages render with ISR so a newly published article shows up within the hour with no redeploy, and each article page carries its title, description and OpenGraph metadata, with /blog/sitemap.xml listing every article for Search Console. Sites that already have a blog system are better served by the GitHub connection committing markdown into the existing content folder.
A scaffold, not a takeover
npx searchblueprint-nextjs-blog scaffolds app/blog, or src/app/blog, and never overwrites a file you already have. Your site keeps its own rendering everywhere else.
Help centre: Nextjs blogFresh within the hour, no redeploy
Pages render with ISR, revalidate 3600, so a newly published article appears within the hour. Lower revalidate in the scaffolded routes if that is too slow for you.
Metadata and a sitemap included
Each article page carries its title, description and OpenGraph metadata, and /blog/sitemap.xml lists every article for Search Console.
Or commit markdown instead
For a repo that already renders posts, the GitHub connection commits articles as markdown with front matter into your content folder, and your build does the rest.
Articles come off a planned calendar
Plan items on the content calendar and write them two ways: click Write on a card, or let Auto-write pick each one up at midnight on its calendar date. Both run the same researched pipeline, which drafts the article and then revises it against the content score across sweeps.
What this connection will not do
Stated up front, because finding out after the first publish costs more. Each line is a fact about what we send Next.js, not a guess about the platform.
A Pages Router site is not supported, the scaffold expects app/ or src/app/. Use the GitHub connection for those sites instead. Documented: Nextjs blog
The package renders content. Publishing cadence and article quality are the calendar's job. Documented: Nextjs blog
One credential covers one project. A second project means a second install with its own value. Documented: Nextjs blog
Connect it in three steps
The same fields the connect wizard asks for, in the order it asks.
Create a content API key
In the project's Publishing tab, open Developer and create a content API key.
Install and scaffold
Run npm install searchblueprint-nextjs-blog, then npx searchblueprint-nextjs-blog. Put the key in .env.local as SEARCHBLUEPRINT_API_KEY, server-side only, a NEXT_PUBLIC_ prefix would ship it to the browser. Set NEXT_PUBLIC_SITE_URL so canonical and sitemap URLs come out absolute.
Deploy
Add the key to the deployment's environment, your local .env.local does not travel to Vercel on its own. /blog lists your articles and /blog/<slug> renders each one.
Questions people ask
The ones that decide whether this fits, answered with the verdict first.
- Where does the package come from?
- The public npm registry, as searchblueprint-nextjs-blog. Install it with npm install like any other dependency; there is no tarball to request and no private registry to configure.
- The blog list is empty after deploying. Why?
- SEARCHBLUEPRINT_API_KEY is missing from the deployment's environment, or it belongs to a different project. Local env files do not travel to the host on their own.
- An article page 404s right after publishing. Why?
- ISR has not refreshed yet. Wait for the revalidate window, or trigger a redeploy if you cannot wait.
Other platforms
Same pipeline, different door. Every platform page states what its connector sends and what it will not.
GitHub
Articles commit as markdown files into the repository and path you choose, and your deploy turns each commit into a page. Built for Next.js, Astro, Hugo, Jekyll and any headless setup where a committed file becomes a page on the next build.
Framer
Framer does not expose a public API that lets an outside service create CMS items on any site, so there is no direct connector to pretend with. What Framer does offer is two doors we already serve: it imports a CMS collection from an RSS feed, and its official Zapier and Make integrations create CMS items from a webhook.
Ghost
Articles arrive in your Ghost site through Ghost's Admin API, with content, images and metadata ready to review in Ghost's editor. New connections publish as drafts, so nothing goes live until someone presses publish in Ghost.
SEO by platform
See it on your own site
A free audit grades your site A+ to F, then the calendar, the writer and the Next.js connection do the week's work. No card required.