Skip to main content
SEOPilot is designed to publish directly to your domain, no matter what stack you use. This guide covers how to wire up automatic publishing using a webhook handler for the most popular static site frameworks. Because every article is served from your own domain, all SEO credit — backlinks, authority, rankings — stays with you.
For Vercel and Netlify, you can add a deploy hook URL as a second step in your webhook handler to trigger an automatic rebuild after each article is saved.

​
Next.js

Create an API route at /api/seopilot that receives the SEOPilot webhook, writes the article body as an MDX file into your content/blog/ directory, and then triggers Next.js Incremental Static Regeneration (ISR) so the new page goes live without a full rebuild.
1

Create the API route

Add a new file at pages/api/seopilot.js (Pages Router) with the handler below. If you use the App Router, see the note after the code example.
2

Add your webhook URL to SEOPilot

Go to Settings → Integrations and enter https://yoursite.com/api/seopilot as the webhook URL.
3

Deploy and test

Deploy your changes, then use the Test webhook button in SEOPilot to confirm the handler writes the file and revalidates correctly.
pages/api/seopilot.js
Before writing the file, verify the X-SEOPilot-Signature header using your secret token. See the Webhook guide for the full verification helper.
App Router users: res.revalidate() is a Pages Router API and is not available in App Router route handlers. Use revalidatePath from next/cache instead. Create app/api/seopilot/route.js and call revalidatePath('/blog/' + article.slug) after saving the file.
Writing files at runtime won’t persist on Vercel or Netlify — their serverless filesystem is read-only, and statically generated pages only change on a new deploy. For a statically generated blog on these hosts, commit the article to your Git repo instead and let the push trigger a redeploy. See Git Auto-Publish.

​
Astro

Astro’s Content Collections make it straightforward to consume SEOPilot MDX files. Create a lightweight webhook handler (e.g., a serverless function on Vercel or Netlify) that writes incoming MDX payloads to src/content/blog/, then fires your CI provider’s deploy hook to trigger a rebuild. The webhook payload fields (title, slug, meta_title, meta_description, keyword, generated_at) map directly to a standard Astro content collection schema — build the frontmatter from them in your handler before writing the file. Define your collection in src/content/config.ts and Astro will pick up new files automatically on the next build.
If you don’t want to write custom code, use the MDX export and drag the files into your content directory manually. The webhook approach just automates that step.

​
Hugo

Hugo reads Markdown content from content/posts/. Point your webhook handler to write each article’s body_md field (Hugo accepts standard Markdown with YAML frontmatter) into content/posts/${slug}.md, then trigger a rebuild via your hosting provider’s deploy hook. A minimal Hugo frontmatter block looks like this:
content/posts/crm-for-solo-realtors.md
SEOPilot’s webhook payload fields map directly to Hugo’s standard front matter keys, so no translation layer is required.

​
Any other framework

The integration pattern is the same regardless of your framework or hosting provider:
1

Receive the webhook

Accept the POST request from SEOPilot at an endpoint you control. Verify the signature before proceeding.
2

Save the article body

Write article.body_md (the article body is Markdown, found at req.body.data.article) to the appropriate content directory for your framework.
3

Trigger a rebuild or revalidation

Call your hosting provider’s deploy hook, or use your framework’s built-in revalidation API, to make the new page live.
The exact rebuild trigger depends on your hosting provider. Vercel and Netlify both offer one-click deploy hooks you can call with a simple HTTP POST. Other providers such as Render, Fly.io, and Railway have equivalent mechanisms in their dashboards.