Feed integration / How feeds work

Feed integration

How feeds work

Publish posts from the Branly feed admin and serve them at /feed on your own website, with one reverse proxy rule.

We publish your content through the Branly feed service and make it available at /feed on your website, for example https://www.example.com/feed. Your team sets up the connection once; after that, your editors publish posts in our admin panel and they appear on your site without a website release.

How it works

When someone opens a feed URL on your website, your website (or its CDN) fetches the page from our service and shows it at that same address. Your engineering team sets up this connection with a reverse proxy rule for the /feed path. The pages, images, scripts and the feed sitemap all live under /feed, so one rule covers everything.

Request flow
Visitor ──▶ www.example.com/feed/<post>
              │  your CDN, load balancer or web server
              │  (rule for /feed and /feed/* only)
              ▼
            https://feeds.branly.ai/feed/<post>
              X-Forwarded-Host: www.example.com

What each team does

TeamResponsibility
Your teamTell us the exact public host (for example www.example.com), set up the /feed proxy rule, link the feed sitemap, and allow the search and AI crawlers you want on /feed.
Our teamRegister your site, create your editors' accounts, run the feed service, and keep the sitemap current.
Both teamsTest the setup before launch and agree on who to contact if a feed URL stops working.

Publishing your content

Your editors sign in at https://feed-admin.branly.ai. On the first visit they click Forgot password and set a password from the email (sent from no-reply@branly.ai).

The admin panel is never served on your own domain.

Each person has one of two roles. An Admin writes and publishes posts, uploads images, and adds people to your team. An Editor writes and publishes posts and uploads images. A post appears on your site as soon as it is published.

How search and AI tools find the content

A sitemap is a list of page addresses. We maintain one for your feed at https://www.example.com/feed/sitemap.xml, with only published posts. Your team links it from your site's robots.txt or sitemap index.

The robots.txt file tells crawlers which parts of your site they may fetch. Check that the tools you approve can reach /feed and the sitemap. Each search or AI service decides whether to list or cite the content.

Where the connection goes

Add the rule at the first public layer that can route requests by URL path: usually your CDN (such as Cloudflare or CloudFront), otherwise your load balancer or web server. Requests for /feed go to our service; your existing website keeps serving every other address.

Ready to connect? Continue with Set up the proxy, then pick your platform in Edge routing examples.

Last updated 19 November 2026

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