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

# Sitemap Import

> Pull your site's pages into Gauge from your sitemap so their citations are tracked and they show up in Library.

## Sitemap Import

Sitemap import is the fastest way to get your existing pages into Gauge without a CMS connection. Gauge reads your sitemap, groups the URLs by section, and lets you choose which parts of the site to bring in. Imported pages land in [Library](/navigating/library), where Gauge starts tracking their citations alongside your other performance signals.

Use it when you want coverage of your whole site quickly, or when your site doesn't run on a CMS Gauge integrates with directly. If you're on Webflow or Framer, see [CMS Integrations](/help/cms-integrations) for a connection that also lets you edit and publish pages.

## What Gets Imported

Gauge imports the page URLs listed in your sitemap. It automatically skips non-page assets such as images, PDFs, fonts, and other binary files, so you end up with real pages rather than clutter.

URLs are grouped by their first path segment, which becomes a **section**. For example, `/blog/...` URLs form a `blog` section and `/guides/...` form a `guides` section. During the preview you'll see, for each section:

* The total number of URLs in that section
* How many are new versus already in your Library
* A sample of the URLs so you can tell what the section contains

You choose which sections to import, so you can bring in your blog and guides while leaving out low-value paths.

<Note>
  Pages already in your Library are detected and skipped, so re-running an import never creates duplicates. The preview's "new" count reflects only the pages that would actually be added.
</Note>

## How It Works

1. In Library, click **Import sitemap**.
2. Enter your website or a sitemap URL, or use your organization's website. Gauge auto-detects the sitemap from your `robots.txt` or common paths like `sitemap.xml`.
3. Click **Preview** to scan the sitemap and see the sections Gauge found.
4. Pick the sections you want. By default, every section with new pages is selected.
5. Click **Import** to queue the job.

The import runs in the background, so you can close the dialog and keep working. Each imported page is filed into a folder for its section, and a matching tag is applied so you can filter by section later. To refresh after publishing new content, just run the import again; only new URLs are added.

## Where Imported Pages Appear

Imported pages show up in [Library](/navigating/library), organized into folders by section. They populate as the job processes, so a large site may fill in over a minute or two.

Once a page is in Library, Gauge links it to the AI answers that cite it and begins tracking its citation rate, so imported pages feed directly into your [Prompts & Citations](/navigating/prompts-citations) reporting. From Library you can open any imported page to see its metrics or start editing it.

<Tip>
  Connecting a CMS after importing is complementary: Gauge matches your CMS articles onto the pages already imported from your sitemap, so you get editing and publishing on top of the pages you're already tracking.
</Tip>