Findings · 2026-11-13 · By VSNARY | Emmanuel Orta
Booking links counted as missing sitemap pages
Our index alerts said five small sites had hundreds of new pages Google had never fetched. The sites had 15 to 55 pages each. The rest were booking links.
On 11 November 2026 CrawlCheck's index alert reported that unfetched sitemap pages had jumped on five sites we run, for example from 19 to 501. It was false. The sites' sitemaps list 15 to 55 addresses. The extra rows were the same pages with booking and ad parameters that Google adds to links from a business listing, which appeared in search performance data and were counted as separate pages. We now drop those parameters before counting, and the alert counts sitemap addresses only.
We run a weekly check that asks Google, page by page, whether it has fetched and indexed each address a site lists. If the number of unfetched pages jumps, it raises an alert. On 11 November it raised five in an afternoon.
The alerts #
| Site | Unfetched before | Unfetched reported |
|---|---|---|
| A | 19 | 501 |
| B | 13 | 565 |
| C | 12 | 357 |
| D | 7 | 194 |
| E | 3 | 110 |
These are small local business sites. Their sitemaps list between 15 and 55 addresses. A site with 55 pages cannot have 565 of them unfetched.
Where the extra pages came from #
The check built its list of addresses from two places: the sitemap, and the pages that appear in the site's search performance data. That second source included addresses like the home page followed by a long query string. They came from links on the business's Google listing, the booking and ad links, which carry tracking parameters.
Each distinct parameter value looked like a distinct page. On one site, 494 of those rows had been added, and Google answered that 495 addresses were unknown to it. Which is true: those exact addresses are not pages, and Google does not index them.
Our second mistake #
We wrote the fix the same day and logged it as shipped. It had not reached production. Two more false alerts went out the next morning, one reporting a rise from 20 to 1,003, before we noticed and deployed it on 12 November. The record said done; the site said otherwise. We now read the live version before we mark a fix as live.
The fix #
Tracking parameters are removed before addresses are counted, so one page is one row. The alert itself now counts only addresses that came from the sitemap. Addresses seen only in performance data are kept for reference and do not raise an alert.
If you read index reports #
The same thing can inflate any report that mixes sitemap pages with pages seen in search data. If a small site suddenly shows hundreds of unknown or unindexed addresses, look at the addresses before you look for a cause. Parameters such as gsas, ahbb or rwg_token point to listing links, not to pages. Compare the count with your sitemap first; our sitemap audit guide covers how.
CrawlCheck’s dataset when this page loaded: 570,959 sites measured.
Share this finding:LinkedInXEmailFollow Emmanuel on LinkedIn
Questions this post answers
Why did my site suddenly show hundreds of unindexed pages?
Check the addresses. If they are the same few pages with long query strings, they are tracked links, such as booking or ad links from a business listing, counted as separate pages.
What are gsas, ahbb and rwg_token in a URL?
They are parameters Google adds to links from a business listing, such as booking and ad links. They identify the click, not a different page.
Was anything actually wrong with the five sites?
No. Their sitemaps list 15 to 55 addresses and those were unaffected. The alert was counting tracked versions of the same pages.
What did CrawlCheck change?
Tracking parameters are removed before addresses are counted, and the alert counts sitemap addresses only. Two false alerts went out before the fix reached production on 12 November 2026.
Related findings
The main product
Found this on your own site? We fix it for $100.
Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.
Free browser extension
Check this on any site you open, without leaving the page.
CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.
Write for the library
Measured something yourself? Submit an article.
Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.
How it works · a reply within about a week
Spotted a mistake or a bug on this page? Report an error. Confirmed errors are fixed and logged on the corrections page.
Comments
Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain (how). Those appear at once, marked verified.
Writing about this? Facts, live figures and marks — every number on that page is dated and traceable to a scan.