JarvisAEO/SEOHelpdeskMarketingCRM

Vercel / Netlify / Cloudflare Pages

Set up blog integration using your cloud hosting platform's built-in rewrite rules.

Modern hosting platforms like Vercel, Netlify, and Cloudflare Pages support proxy rewrites natively: no server configuration needed. You add a small config file and the platform handles everything. This is the easiest production setup for any static site or SPA.

1

Vercel: Add rewrites to vercel.json

Create or edit vercel.json in your project root:

{
  "rewrites": [
    {
      "source": "/blog",
      "destination": "https://aeo.how/blog"
    },
    {
      "source": "/blog/:path*",
      "destination": "https://aeo.how/blog/:path*"
    }
  ]
}

Deploy as usual. Vercel automatically proxies /blog requests to AEO and forwards the Host header.

If you're using Next.js on Vercel, you can use either vercel.json rewrites or next.config.js rewrites; both work. Pick one.

2

Netlify: Add redirects to netlify.toml

Create or edit netlify.toml in your project root:

[[redirects]]
  from = "/blog"
  to = "https://aeo.how/blog"
  status = 200
  force = true

[[redirects]]
  from = "/blog/*"
  to = "https://aeo.how/blog/:splat"
  status = 200
  force = true

The status = 200 is critical: it tells Netlify to proxy (rewrite) rather than redirect. The :splat placeholder captures the rest of the URL path.

Alternatively, you can use a _redirects file in your publish directory with the same rules.

3

Cloudflare Pages: Add a _redirects file

Create a _redirects file in your build output directory (usually dist/ or build/):

/blog https://aeo.how/blog 200
/blog/* https://aeo.how/blog/:splat 200

The 200 status code tells Cloudflare to proxy rather than redirect.

4

Test after deployment

After deploying, visit yourdomain.com/blog. Check that articles load correctly, and that the browser URL stays on your domain (no redirect to aeo.how).

Always use status 200 (proxy/rewrite), not 301 or 302 (redirect). A redirect would send visitors to aeo.how instead of keeping them on your domain.

All three platforms automatically handle Host header forwarding for proxy rewrites.

These config files work regardless of your frontend framework (React, Vue, Angular, Svelte, plain HTML).

Vercel / Netlify / Cloudflare Pages | Jarvis AEO/SEO Help