Skip to content
Documentation

Sitemap Performance: Search Console traffic per sitemap

Join every URL in your sitemaps with Search Console data to see which sitemaps earn clicks, how many URLs get none, and which never appear in search.

Property → Analytics → Sitemap PerformanceRun analysis3 min read

Sitemap Performance treats each sitemap as a segment of your site. It downloads the sitemaps you choose, joins every URL in them with Search Console's page data, and reports clicks, impressions and the share of URLs without traffic per sitemap. Sites that split sitemaps by type (products, categories, articles, locales) get a section-by-section health check without any extra setup.

Choose the sitemaps

Under Add Sitemaps:

  • Select from Google Search Console: tick any of the sitemaps registered for the property.
  • Or paste sitemap URLs (one per line) and press Add Sitemaps. Sitemap index files are expanded into their child sitemaps.

If you select nothing, every sitemap registered in Search Console is analysed (index files are only used when no plain sitemap is registered). Up to 25 sitemaps run at once, each read up to 50,000 URLs. Downloaded sitemaps are cached for 24 hours; Refresh fetches them again. Set the date range, comparison and filters at the top, then run the analysis.

If a download fails with 403, your server is blocking the fetch; allow the user agent AutoPSEO-Bot/1.0.

How the numbers are worked out

Each sitemap URL is matched to Search Console's page rows after ignoring http/https, www., trailing slashes and fragments. For each sitemap:

  • URLs is the number of distinct URLs it lists.
  • Clicks, Impressions, CTR and Avg. position add up its URLs (position weighted by impressions), with the comparison period alongside.
  • No traffic counts URLs without a single click, and No traffic % divides that by the sitemap's URLs.
  • Not in GSC counts URLs Search Console did not report at all in the period.
  • Share of clicks is the sitemap's share of the clicks across all analysed sitemaps.

The cards at the top count unique URLs across the sitemaps, so a URL listed in two sitemaps is counted once there.

Read the results

Clicks per sitemap shows where the analysed clicks come from, and URLs without traffic per sitemap shows each sitemap's share of URLs that earned nothing. The Status column flags each sitemap as OK, Index (an index file whose children were read), Truncated (more URLs than were read) or Failed (a download or parse error; hover for the reason). Pick a sitemap under URL details to see its URLs one by one with their own status: with traffic, impressions only, no traffic or not in Search Console.

What to do with it

  • A sitemap with a high No traffic % points at a section Google indexes but does not rank, or does not index at all. Bulk-inspect a sample from Sitemaps to tell the two apart.
  • Many URLs not in Search Console often means the sitemap lists addresses Google does not index as written: redirected, canonicalised to another URL, blocked or noindex. A sitemap should list the canonical URLs you want in search (Google's sitemap guidance).
  • A small sitemap with a large share of clicks marks the section to protect when you change templates or URLs.
  • Clicks outside every sitemap: compare the analysed clicks with the property's total. Pages that earn traffic but are missing from your sitemaps deserve a place in one.

How AutoPSEO helps

If AutoPSEO hosts a section of your site for you, the hosted renderer publishes that content type's own sitemap at <type path>/sitemap.xml, with every language as an alternate; add it here to follow those pages as their own segment (hosting). If your own site renders the articles AutoPSEO delivers, list them in your sitemap as usual and analyse that one.

Related: Page Performance, Subdomain & Folder.

Put your SEO content on autopilot

Connect Search Console and your site. AutoPSEO scans it and plans the first topics right away. No credit card needed.