Skip to main content
Use the Sitemap screen to see your storefront’s URLs, control what search engines find at /sitemap.xml, and add your own routes. A route can show a product, a page, or a template at an address you choose, or send visitors somewhere else, and it can do something different for each country.
A non-credited route can break reps’ shared links and collide with a rep’s username. Read Rep credit before you create a route for a URL that reps or customers share.

​
Where to find it

In the admin sidebar, under Platforms, click Website > Sitemap. If you don’t see the Search Engine Visibility card, Create Custom Route, or the row switches, your role can view the sitemap but not change it. See Roles.

​
What’s on the screen

The top of the screen has these buttons:
  • Theme: Picks whose routes you see and edit. It starts on your active theme, marked (Active). Choose Reset to active theme to go back. Only routes on your active theme reach visitors.
  • View Sitemap: Opens your live /sitemap.xml in a new tab.
  • Create Custom Route: Opens the drawer for a new route. See Create a custom route.
Below them are the Search Engine Visibility card and the route list:
  • Viewing for: Shows All countries, or only the routes that have a country route for the country you pick.
  • Table and Structure: Switch between a searchable, filterable table and a tree of your URLs. Structure isn’t available when the theme has more than 10,000 routes.
  • Each table row shows the URL’s Path, its Country Routes, and an Include in Sitemap switch. Click a row to open it.
  • Select rows to delete routes.
New products, pages, and other content can take up to five minutes to appear in the list.

​
Your sitemap

Fluid publishes your sitemap at /sitemap.xml on every storefront domain your company uses, such as https://acme.fluid.app/sitemap.xml or https://www.example.com/sitemap.xml. /sitemap.xml is an index. It links to one sitemap for each kind of content that has something to list: /sitemap-static.xml for your home, shop, and join pages, then /sitemap-pages.xml, /sitemap-products.xml, /sitemap-media.xml, /sitemap-enrollments.xml, /sitemap-categories.xml, /sitemap-collections.xml, /sitemap-posts.xml, /sitemap-libraries.xml, and /sitemap-custom.xml for custom routes. What the sitemap lists:
  • Every URL uses your primary domain. If you have a connected primary domain, the sitemap uses it. Otherwise it uses https://<your-subdomain>.fluid.app. See Domains.
  • Content uses its /home/ address, the one with no rep in it, such as /home/products/beet-blend. Posts use /home/blog/<slug>.
  • Only live content that search engines may index. Drafts, scheduled items that haven’t gone live, and items whose SEO settings block search engines are left out.
  • Only routes on your active theme.
Your storefront also serves /robots.txt. It lets search engines crawl every page and points them to your sitemap.

​
Search Engine Visibility

The Search Engine Visibility switch is on by default. When you turn it off:
  • /sitemap.xml and every sitemap it links to return not found.
  • /robots.txt stops pointing to your sitemap.
Turning it off doesn’t hide your storefront. Your pages still load, and search engines can still find and index them through links. To keep a page out of search results, turn off search indexing in that page’s SEO settings.

​
Include in Sitemap

Each row’s Include in Sitemap switch adds or removes that one URL from your sitemap. The page itself stays live either way. The setting applies to your company’s sitemap, whichever theme you’re viewing.
On a custom route, the Include in Sitemap switch inside the route’s drawer currently does more than its label says: saving the drawer with it off also switches the route off, so the route stops serving visitors. To hide a custom route from the sitemap and keep it working, use the switch in the table row instead. After you save a route’s drawer, click Visit Link to check that it still loads.

​
Create a custom route

A custom route is a URL you add yourself, such as /about-us or /spring-sale.
For a marketing URL such as /tv-offer, or an address from your old website, a redirect to the product or page is usually better than a custom route. See Rep credit.
  1. Click Create Custom Route.
  2. Enter the Path. It must start with / and can’t contain spaces or //.
  3. Choose the URL Shape. See The two URL shapes.
  4. Choose a Default override: what the route shows when no country route applies.
  5. Fill in the fields that override needs, then click Save.
The Theme field shows the theme you’re adding the route to. It’s the one picked in Theme: at the top of the screen. The Default override can be:
  • URL Redirect: Sends visitors to the Redirect URL you enter, with a temporary redirect.
  • Home Page, Shop Page, or Join Page: Shows that page with the Theme Template you pick.
  • Product, Page, Media, Enrollment, or Collection: Shows the Resource you pick, with the Theme Template you pick. The template must be a template for that type of content, on the same theme.
Post and Playlist also appear in the list, but a route that shows a post or a playlist can’t be saved today. Some paths are taken by your storefront’s own pages. You can’t create a custom route at /shop or /join, or at any path that starts with /products/, /pages/, /collections/, /categories/, /media/, /enrollments/, or /libraries/. A new or changed route can take up to about 90 seconds to reach every visitor.

​
The two URL shapes

A credited route doesn’t answer at the bare /spring-sale. That address shows your home page instead. Use a non-credited route only for an address that must stay in the visitor’s address bar. Read Rep credit first.
The sitemap currently lists a credited custom route at /<path>, without /home/. That address shows your home page rather than the route.

​
Country-specific routing

Country-Specific Routing in a route’s drawer shows something different to visitors from particular countries. It works on custom routes and on your storefront’s own pages, such as a product page.
  1. Click Add Country Route.
  2. Pick one or more Countries.
  3. Pick an Override Type, fill in its fields, then click Done.
The Override Type can be:
  • Template override: Shows the same page with a different Theme Template. Not offered on custom routes.
  • URL Redirect: Sends these visitors to another address, with a temporary redirect.
  • Disabled: The page returns not found for visitors from these countries.
  • Home Page, Shop Page, or Join Page, or a type of content: Shows that page or item instead.
The card says each route can enable Fair Share attribution. That setting has no effect today. A country route never changes who gets credit for a visit.

​
How a visitor’s country is chosen

Fluid uses the first of these that it finds:
  1. A region in the link, such as ?region=CA. Use this to test a country route, not in links you share.
  2. The country in the visitor’s language and country choice, from your storefront’s locale selector.
  3. The country the visitor is browsing from.
  4. Your company’s default country.
  5. The United States.
Fluid then uses the route’s rule for that country. If there’s none, it uses the route’s default override. If that’s missing too, it uses the rule for your company’s default country. Country routes depend on the country only, not the language. To show a page in another language, translate the page or template rather than adding a country route.

​
Rep credit

Fluid credits a rep when a visitor lands on that rep’s credit path. That’s a storefront URL whose first part is the rep’s username, such as /jordan-lee/products/beet-blend. The rep keeps that credit as the visitor browses other pages and comes back later. /home/... pages, custom routes, and redirects don’t give credit to anyone. They also don’t take away credit a visitor already has. See FairShare: sales rep attribution and Fair Share. A non-credited route’s first part is your route, not a username. Here’s what that means today:
  • A non-credited route doesn’t establish credit. A visitor who reaches /spring-sale from search, an ad, or another site without a rep’s credit places an order with no rep. A visitor a rep already credited keeps that rep’s credit.
  • Rep links to a non-credited route return not found. A rep who shares /jordan-lee/spring-sale sends customers to a not-found page. Reps should share the product’s or page’s own credit path instead, such as /jordan-lee/products/beet-blend.
  • A rep whose username matches a non-credited route loses their own link. If a rep’s username is spring-sale, /spring-sale shows your route, not their storefront. Fluid doesn’t stop you from creating a route that matches a username, or a rep from choosing a username that matches a route.
  • A rep whose username matches a non-credited route’s path is credited for its visitors. Fluid looks for a rep in the first part of the path, so visits to /spring-sale credit the rep named spring-sale.
  • A Fair Share setting on a country route doesn’t change credit. See Country-specific routing.
A marketing URL such as /tv-offer, or an address from your old website, is what customers without a rep type or click: from TV, print, ads, or old links. Send that traffic to the real product or page with a URL redirect, such as /tv-offer to /home/products/<slug>. Reps don’t use that URL. When they share from the Fluid mobile app or their own links, they use credited paths such as /<username>/products/<slug>, so they get credit for their customers.
  • Keep rep-shared links on credited paths. Reps share /<username>/... links, never a non-credited route.
  • Don’t add ?username= to a marketing URL. It serves customers who arrive without a rep.
  • Use non-credited routes only where the address must stay in the address bar and the page doesn’t need to establish credit: company pages, search landing pages, and old URLs from a previous site that must keep their address.
  • Check usernames before you add a non-credited route. Make sure no rep uses the route’s first path segment as their username.

​
Redirects

To send an old address to a new one with a permanent redirect, use the URL Redirects screen. See URL Redirects.
Email Fluid support at help@fluid.app. The Getting help page lists what to include in your request.