Connect Static site to SEOryon

No CMS needed. They all deploy from a GitHub repo, so SEOryon commits each article to your repo and your site rebuilds automatically. You build a tiny receiver once, or let Claude Code build it. SEOryon never needs access to your repo or your host.

Live today All integrations
How it connects
Signed webhook events into a receiver your AI coding agent builds
Edit after publishing
Yes, updates republish the same post
Delete and unpublish
Yes, from SEOryon
Tables
Yes. Raw HTML, styled by your own CSS.

Compatible with

GitHubVercelNetlifyFirebaseCloudflare Pages
AstroNext.jsHugoJekyllEleventy

Before you connect

Get these in place first. They are the difference between a connection that goes green and one that fails on the first publish.

  • A GitHub repo your site deploys from. Vercel, Netlify, Firebase, and Cloudflare Pages all build from one.
  • A live HTTPS endpoint for the receiver, typically a serverless function next to your site.
  • Somewhere safe to store the signing secret, such as your host's environment variables.

How to connect, step by step

The same steps SEOryon walks you through in the app. This one runs entirely in SEOryon, so there is nothing to hunt for in another admin.

  1. 1

    In SEOryon, open Settings, Integrations, Static site and click Generate to create your 32-byte signing secret. Your receiver uses it to verify that each request really came from SEOryon.

  2. 2

    Copy the prompt SEOryon gives you and paste it into Claude Code, Cursor, or Codex. The full payload and signature spec are baked into the prompt, so there is nothing else to hand over. Prefer to write it yourself? The code is there to read.

  3. 3

    Deploy the receiver, store the secret in its environment, then paste the endpoint URL into SEOryon. It test-publishes to prove the endpoint works, and only then marks the connection healthy.

What happens when you click Connect

Connecting runs a real test publish. SEOryon creates a draft, verifies it, deletes it, and only then marks the connection healthy, so a connected badge means publishing genuinely works.

What you can do once Static site is connected

  • Publish, update, delete, and unpublish. All four events, and because it is your own code, removal is real.
  • Tables publish as raw HTML, rendered with your own CSS.
  • The full SEO payload, including the connected JSON-LD @graph and an optional author byline.
  • Any static framework: Astro, Next.js, Hugo, Jekyll, or Eleventy.
  • Built it with an AI builder? Replit, Base44, and Lovable each have their own guide, because there the receiver is built inside the builder's own chat.

What to know about Static site

The honest part. Every platform has edges, and you should hear about them from us before you hit them.

Your receiver has to render raw HTML inside Markdown. Hugo needs unsafe = true, markdown-it needs html: true, and Astro passes it through already.

SEOryon does not style tables inline, so they inherit whatever your site's CSS says.

SEOryon never touches your repo or your host. The receiver you own does the committing, which is the point.

Comparison tables publish as real tables on Static site. See the full table support matrix.

What publishing looks like

Approved articles are committed to your repo as Markdown or HTML with full front matter, your site rebuilds, and the post goes live in your own design.

SEO on Static site

Best practices that move the needle

You own the template, so the SEO is yours to get right. Five that matter most.

  • Render the meta title and description from the payload into the head, not just into the page body.
  • Emit the JSON-LD graph SEOryon sends, so the article, author, and site entities stay connected.
  • Rebuild and update your sitemap on publish, so new posts get discovered quickly.
  • Treat the slug SEOryon sends as the canonical path, and set the canonical tag from the payload.
  • Style headings, lists, and tables once in your site CSS, since SEOryon ships clean semantic HTML with no inline styling.

Other integrations

WordPressWebflowWixGhostGoHighLevelReplitBase44LovableWebhookShopifyFramerHubSpot CMSDuda

Meta titles and descriptions

You never hand-write a meta tag again

Every platform caps these fields at a different length, so SEOryon writes them for the platform you publish on and fits them automatically.

  • Your meta title is the article title, word for word, so the tag never drifts from the H1.
  • Your meta description is written to a 150 to 160 character target with the keyword woven in, then auto-fitted to whatever your platform allows, so it never overflows the field.

On WordPress the description goes into the post Excerpt, which Yoast and Rank Math read as a fallback. On Wix and Ghost it goes into their own SEO fields. You do not have to think about any of it.

Example snippet

yoursite.com › blog

How to Connect Your CMS to an AI SEO Agent

Connect your CMS once and approved articles publish themselves, formatted to your theme with images, internal links, and meta tags already set.

Meta titleArticle title, verbatim
Meta description150 to 160 characters
Field limitAuto-fitted per platform

See it on your own site, free.

Start a 3-day free trial and generate 3 real articles on your own site before you decide. Cancel before day 3 and you pay nothing.

Book a demo
  • Done-for-you articles, monthly
  • Built on your real search data
  • Publishes straight to your CMS
  • Built for Google and AI search
  • 3-day free trial, cancel anytime