Prerequisites
Blog routes are live at
{your-domain}{blogPath} (for example https://acme.com/blog).RANKBUDDY_API_KEY is set in your production environment (server-only, never NEXT_PUBLIC_).Your RankBuddy project uses the same website URL and blog path you configured during onboarding.
Steps
1
Create a RankBuddy account
Sign up at rankbuddy.io/auth/signup.
2
Confirm project settings
In RankBuddy, open your project and verify:
- Website matches your live domain (e.g.
https://acme.com) - Content path matches your blog route (e.g.
/blog)
website + content path + slug → https://acme.com/blog/my-article.3
Ask your AI SEO Employee to create an article preview
- Open the project chat and select Content Generation.
- Describe the article you need, or ask the employee to find a topic opportunity.
- The employee gathers the required SEO context and generates the article in a review canvas.
- Review the rendered article or switch to Markdown view.
4
Publish a saved article
Publishing remains available for articles that already exist in Articles. Open an article and change its status to Published, or schedule a future time.Generated chat previews cannot be published until the explicit save workflow is added. Nothing goes live from article generation automatically.
5
Verify on your site
- Open
{blogPath}— your published post should appear in the listing. - Open
{blogPath}/{slug}— full article, cover image, and metadata should render.
If you use on-demand caching (
dynamic = "force-static" with
revalidate = false), call your revalidation endpoint or webhook after
publishing so the exact index, article, topic, and sitemap paths refresh.
For the simplest first launch, use time-based revalidation
(revalidate = 3600) as described in the blog setup guide.Get your API key
- In RankBuddy, open Settings → API keys (or your project’s integration settings).
- Create a key with access to read published articles.
- Add it to your hosting provider as
RANKBUDDY_API_KEY. - Redeploy if the variable was added after the last deploy.