Feed integration / Webflow

Feed integration

Webflow

Serve the feed on a Webflow site: route /feed at the public edge and connect the feed sitemap.

Your team keeps publishing website pages in Webflow. Our service publishes the feed under /feed and generates its sitemap. The public routing layer sends each request to the service that owns that address.

Route requests at the public edge

If Webflow hosts the site and Cloudflare is already in front: keep the working Webflow connection. With Webflow's supported Orange-to-Orange (O2O) setup, add the Cloudflare Worker from the edge routing examples, limited to the /feed routes. O2O connects Cloudflare to Webflow; the Worker sends the feed paths to https://feeds.branly.ai.

If Webflow hosts the site directly: same-domain path routing needs an HTTP routing layer in front of Webflow. Use Webflow's O2O setup if you adopt Cloudflare. For a self-managed edge, use a published Webflow custom origin subdomain with matching Host and TLS SNI, and follow Webflow's DNS migration instructions before changing DNS.

Use a production custom origin, not the Webflow staging address.

If Webflow is the CMS and the website is hosted elsewhere: add the path rule at the current hosting provider's public edge and keep the existing hosting destination as the default.

Path rules

Routing
/feed and /feed/*             → https://feeds.branly.ai
                                (send X-Forwarded-Host: your host)
/robots.txt and /sitemap.xml  → existing site (Webflow)
All other paths               → existing site (Webflow)

Check that no Webflow page, collection route or redirect already uses /feed. Apply feed-only caching and bot rules to the /feed routes (see Engineering setup).

Connect the feed sitemap in Webflow

If Webflow serves the public robots.txt, open Site settings → SEO → Indexing, add the line below to the existing rules, save, and publish to the custom domain. Keep Webflow's own sitemap reference. If your edge serves robots.txt, add the line there.

robots.txt
Sitemap: https://www.example.com/feed/sitemap.xml

If a self-managed proxy uses a separate Webflow origin hostname, check that the public robots.txt lists both public sitemaps, and that Webflow's sitemap settings use your public domain as the base URL.

Check after publishing

Check the live robots.txt and both sitemaps on your public domain. Open a sample feed post and a Webflow page, check their canonical URLs, and check any search, forms or redirects affected by the edge change. Publish a test post in the feed admin and confirm it appears at https://www.example.com/feed.

Webflow reverse proxy · Cloudflare O2O · Webflow robots.txt · Webflow sitemaps

Last updated 19 November 2026

Questions about this page? Write to connect@branly.ai