> ## Documentation Index
> Fetch the complete documentation index at: https://rogus-docs.frimty.com/llms.txt
> Use this file to discover all available pages before exploring further.

# The feed URL

> Every generated feed gets a public URL you paste into Google Merchant Center. How the address works, and how to look after it.

Once a feed has been generated it gets a public address. That address is what you give Google, or any other channel — they fetch the file from it whenever they need your current catalog.

Find it on the feed page under **Feed URL**.

## What the address looks like

```
https://your-rogus-host/feeds/8f3c9a1e…d2b7.xml
```

The long string in the middle is unique to that feed. A CSV feed ends in `.csv` instead.

**The extension is part of the address, not decoration.** A feed answers on its own extension only. This is one of the reasons the feed type cannot be changed after the feed exists — switching it would change the address you already gave your channel.

## Treat the URL as a secret

<Warning>
  **Anyone with the address can read the file.** There is no password on it — the unguessable string *is* the protection, in the same way as a private sharing link.
</Warning>

The file contains your product catalog: titles, descriptions, prices, stock and images. Most of that is already public on your storefront, but the file also gives someone your complete catalog in one convenient download.

Practically:

* Paste it into your channel's settings. Don't post it anywhere public.
* If it does leak, use **Download** to keep the data and create a replacement feed with a new address, then update the channel.

## Download

**Download XML** (or **Download CSV**) gives you the same file as the channel receives. Useful for checking what actually published, or for uploading by hand to a channel that has no scheduled fetch.

It is exactly the same content as the URL serves — not a separate export that could be out of step.

## How channels fetch it

The address always serves the **most recent completed generation**. There is no separate publish step: a finished run replaces what the URL serves.

Two things follow:

* **A failed run does not empty your feed.** The last good file stays until a new one succeeds.
* **A channel may lag by a few minutes.** Rogus lets fetchers hold the file briefly, and channels have their own schedules — Google typically fetches once a day, whatever you do at your end.

Rogus also answers "has this changed?" cheaply, so a channel checking often does not cost you anything.

## Setting the fetch up in Merchant Center

In Google Merchant Center, add a product source that fetches from a URL, paste the address in, and choose a schedule. Daily is normal. There is no benefit in Google fetching more often than Rogus rebuilds — see [Generating a feed](/feeds/generating).

The alternative is to skip the URL and let Rogus send products to Merchant Center directly: [Send to Merchant Center](/google/send-to-merchant-center).

## After uninstalling

If you remove Rogus from your store, your feed URLs stop working and all your data is deleted within 48 hours. Any channel still fetching the address stops receiving your products — which usually means it removes them from its listings. Move your channel to another source before uninstalling.