Changelog

What shipped, what got simpler, what changed.

Public shipping notes for the parts that matter to customers. Fewer vague release announcements, more concrete changes you can actually use.

LatestApril 25, 2026

One-command Next.js integration is live

You can now start the RankFirst integration from inside a Next.js repo with `npx rankfirst`, link the repo to your RankFirst account in the browser, and end up with generated routes, env vars, sitemap support, and revalidation wiring in place.

This release

CLI
`npx rankfirst`
Link flow
Signed-in browser approval
Adapter
`@rankfirst/next` published
Output
Blog routes + sitemap + revalidate

Release date

April 25, 2026

One-command Next.js integration is live

You can now start the RankFirst integration from inside a Next.js repo with `npx rankfirst`, link the repo to your RankFirst account in the browser, and end up with generated routes, env vars, sitemap support, and revalidation wiring in place.

What changed

  • `npx rankfirst` now guides the full setup inside the current Next.js project
  • Optional browser linking pulls the API key and webhook secret from the signed-in RankFirst account
  • Generated files cover blog routes, article pages, revalidation, and sitemap support
  • The public `rankfirst` CLI and `@rankfirst/next` adapter are both live
terminalready
$ npx rankfirst
Check project
Write integration files
Open browser link
Store env vars locally

We built this because the old setup still asked too much up front. The adapter worked, but the path into it was a checklist: create credentials, copy them over, wire routes, then hope the repo still matched the docs.

Now the setup starts where developers already are. The CLI inspects the project, writes the integration files, and can hand off the credential step to a browser approval flow so the repo ends up configured in one pass.

The generated app still keeps the practical parts. You get resilient snapshot support, signed revalidation webhooks, and plain route files that stay readable in your own codebase.