Edge Hosting Guide
Serve articles from our global CDN under your own domain. Two routing modes — path-based (yoursite.com/blog/…) or subdomain (blog.yoursite.com) — pick whichever fits your stack.
When to use Edge Hosting
- Your CMS doesn't expose a content API (Squarespace, Webflow, custom builders)
- You want the simplest possible setup — no credentials, no API tokens, no build pipeline
- You want articles served from the same root domain as your main site for SEO consolidation
- You want a hosted landing page with an article index
Routing Modes
Edge Hosting offers two routing modes. The right choice depends on what your DNS provider supports.
Path-based — yoursite.com/blog/article-slug
Articles live at a path on your existing domain. Best for SEO because everything is consolidated under one hostname.
How it works:
- You pick a path prefix (e.g.
blogorarticles) - We store your articles on our global edge CDN
- You add a reverse-proxy rule that forwards requests matching that prefix to our edge worker
- Visitors see articles at
yoursite.com/blog/…
Provider support:
SEO Sniper auto-detects your DNS provider
The Edge Hosting card shows the exact steps for your specific provider once it's detected. If your provider doesn't support reverse-proxy on a non-enterprise plan, it offers a one-click switch to the subdomain method instead.
Setup Steps
Open the Edge Hosting card
Settings → Integrations → Edge Hosting. Pick path-based or subdomain at the top of the card.
Configure your route
Path-based: enter the path prefix (e.g. blog). Reserved paths like api, admin, or _next aren't allowed.
Subdomain: enter the subdomain (e.g. blog → produces blog.yoursite.com).
Complete the DNS / proxy setup
Path-based: SEO Sniper detects your DNS provider and shows you exact instructions (or opens the provider's dashboard for you). For Cloudflare Workers, Next.js, or Nginx, there's a copy-paste code snippet for each.
Subdomain: add the CNAME shown on the card to your DNS. We auto-check every 10 seconds and flip the connection to Active as soon as it resolves.
Publish your first article
Any article you publish in SEO Sniper auto-deploys to the edge. The landing page (article index) regenerates on every publish.
What You Get
Global CDN delivery
Articles served from edge nodes worldwide for low latency.
Auto-provisioned SSL
HTTPS certificates are issued automatically once your DNS resolves (usually within 5 minutes).
Full SEO meta per article
Meta title, description, canonical URL, Open Graph, Twitter Card, Article JSON-LD structured data.
Custom CSS, head HTML, header, footer
Match the look of your main site. Configure styling per-site under Settings → Article Styling.
Hosted landing page
A dynamic article-index page at the root of your edge URL. Pick from four templates: Minimal, Cards, Magazine, or Simple.
Editable routing after setup
Change the path prefix or subdomain from the connection card without re-running setup.
Troubleshooting
Cloudflare path-based isn't working
Cloudflare's Origin Rules require an Enterprise plan. Either use Cloudflare Workers (free tier — there's a copy-paste snippet on the card) or switch to the subdomain method (CNAME only, works on free).
DNS verification stuck on “Pending”
Verify the CNAME record exists by running dig blog.yoursite.com CNAME in your terminal. If it doesn't return edge.seosniper.io, re-check the record in your registrar. Some providers (Squarespace registrar, GoDaddy) can take up to an hour to propagate.
Path-based proxy returns 404
The proxy rule is matching the wrong path. Confirm the source pattern in your provider's config matches /blog/* (with the trailing wildcard) and the destination is https://edge.seosniper.io/blog/*.
SSL handshake error / NET::ERR_CERT_COMMON_NAME_INVALID
Subdomain method: certificates take ~5 minutes to provision after the CNAME first resolves. Wait, then refresh.