Publish under your existing domain

Serve Aeolo-managed articles at https://www.example.com/articles while keeping your existing website. Your server or CDN forwards only the agreed content paths to Aeolo; visitors stay on your domain. This guide is for a site rendered by Aeolo. To fetch article data and render your own pages, use the custom website feed guide.

Before you start

Agree on the canonical host (including www), an unused content path and the developer responsible for your server or CDN. Ask Aeolo to register the host in path mode and provide the generated path configuration. The connection remains pending until verified. Use your supplied values. example and /articles below are placeholders. No root-domain DNS migration is needed. The Drive source folder and website path are separate settings; importing or rewriting an article does not publish it.

Responsibilities

Owner	Action
Your developer	Confirm the host, available path and server/CDN; deploy the proxy rules
Aeolo	Register the host, provide the path configuration and verify the connection
Your reviewer	Review the content and explicitly approve publication
Both teams	Verify an approved public article and prepare indexing after approval

If no approved public article exists, final verification remains pending. Do not publish a draft simply to complete connection setup.

Configure path forwarding

Incoming request	Example upstream
`/articles`	`https://example.aeolo.site/__aeolo_path/articles`
`/articles/{slug}`	`https://example.aeolo.site/__aeolo_path/articles/{slug}`
`/articles/__aeolo/sitemap.xml`	`https://example.aeolo.site/__aeolo_path/articles/__aeolo/sitemap.xml`
`/articles/__aeolo/*`	`https://example.aeolo.site/__aeolo_path/articles/__aeolo/*`

Forward the exact path and all descendants before a catch-all or SPA fallback. Preserve the path prefix and query string. Use a rewrite or reverse proxy, not a redirect. Keep TLS certificate verification enabled. Use the upstream hostname for Host and TLS SNI. Public content does not need visitor cookies or Authorization headers; configure forwarding accordingly. Respect upstream cache headers, including no-store. Your application continues to own /, /robots.txt, /sitemap.xml, verification files, login and other paths.

Vercel example

Merge these rules into existing rewrites. Check framework routing and authentication middleware before deploying.

{
  "rewrites": [
    {
      "source": "/articles",
      "destination": "https://example.aeolo.site/__aeolo_path/articles"
    },
    {
      "source": "/articles/:path*",
      "destination": "https://example.aeolo.site/__aeolo_path/articles/:path*"
    }
  ]
}

Nginx example

Add these locations to your HTTPS virtual host. Adjust the CA certificate path for your operating system and run nginx -t before applying. These examples have not been tested on your server.

location = /articles {
    proxy_pass https://example.aeolo.site/__aeolo_path/articles;
    proxy_ssl_server_name on;
    proxy_ssl_verify on;
    proxy_ssl_trusted_certificate /etc/ssl/certs/ca-certificates.crt;
    proxy_set_header Host example.aeolo.site;
    proxy_set_header Cookie "";
    proxy_set_header Authorization "";
}

location ^~ /articles/ {
    proxy_pass https://example.aeolo.site/__aeolo_path/articles/;
    proxy_ssl_server_name on;
    proxy_ssl_verify on;
    proxy_ssl_trusted_certificate /etc/ssl/certs/ca-certificates.crt;
    proxy_set_header Host example.aeolo.site;
    proxy_set_header Cookie "";
    proxy_set_header Authorization "";
}

Other CDNs need equivalent HTTPS proxy rules. An external Cloudflare Pages _redirects rule with status 200 does not replace a proxy; use a Worker or Function where appropriate.

Verify a real article

After deployment, ask Aeolo to verify the customer URL of an approved, published article. A homepage returning HTTP 200 is not sufficient.

The URL returns HTTPS 200 HTML without a redirect.
Aeolo’s verification confirms the expected site and article using a fresh challenge.
A single canonical URL matches the customer’s article URL.
Desktop and mobile pages show the body, images, navigation and related links correctly.
Existing website routes still work.

Successful verification changes the connection to serving. Connection, content approval and search indexing are separate states.

Enable search discovery when ready

While indexing is on hold, pages can retain noindex, nofollow, and the sitemap may be unavailable. After the responsible owner approves indexing, enable it in Aeolo and check that your robots.txt allows the content path. Use the sitemap URL supplied in the configuration, for example https://www.example.com/articles/__aeolo/sitemap.xml, in your sitemap setup or Search Console. Root-domain Search Console ownership stays with you. Submission does not prove indexing or AI citations.

Troubleshooting and rollback

Symptom	Check
Existing app page or 404	Exact and nested rewrites, catch-all order, folder, slug and publication state
Address changes to the upstream	Redirect used instead of proxy/rewrite
Verification fails	Canonical host, real public article, response headers and CDN caching
Sitemap returns 404	Indexing hold and the generated sitemap path
Broken images or navigation	Template and resources on desktop and mobile

Restore your previous server configuration and coordinate removal of the Aeolo host binding when rolling back. These are separate changes. For live URLs, agree on replacement URLs or redirects before removing them.

Start here

Connect your website

Write and review

CLI and MCP setup

Brand context and access

Measure and distribute

Reference

Publish under your existing domain

Before you start

Responsibilities

Configure path forwarding

Vercel example

Nginx example

Verify a real article

Enable search discovery when ready

Troubleshooting and rollback

Platform references

​Before you start

​Responsibilities

​Configure path forwarding

​Vercel example

​Nginx example

​Verify a real article

​Enable search discovery when ready

​Troubleshooting and rollback

​Related guides

​Platform references

Before you start

Responsibilities

Configure path forwarding

Vercel example

Nginx example

Verify a real article

Enable search discovery when ready

Troubleshooting and rollback

Related guides

Platform references