Index Reporting stuck at 0% or in queue
If your Index Reporting shows "In queue for processing" or "Progress 0%" for longer than you expected, you're probably wondering whether something's wrong. Here's how to tell the difference between normal processing and a genuine issue—and what to check if it seems stuck.
What the queue states mean
When you set up Index Reporting, you'll see one of these states in the UI:
"In queue for processing" — Your request is accepted and waiting to begin. This is normal immediately after setup or after adding new sitemaps.
"Progress 0%" or "The indexing process has not started yet" — The system has your sitemaps but hasn't started fetching page data. This can last from a few minutes to a few days depending on queue load and sitemap complexity.
A percentage (e.g., 45%, 78%) — Processing is actively running. The percentage reflects how many of your submitted pages have been checked so far.
How long should it take?
There's no fixed timeline—processing speed depends on the size of your sitemaps, how many pages you're tracking (up to 5,000 per Super Site), and current queue demand. For most sites, you'll see progress within 24–72 hours after setup.
If you've hit the 5,000-page limit, Index Reporting will only track the pages you've selected. Larger sites should prioritize your most important sitemaps or use additional Super Sites for subfolders or subdomains.
When 0% might mean something's wrong
If your report has been stuck at 0% or "in queue" for more than a few days with no movement, it's worth checking a few things:
1. Re-validate your sitemaps
Go to Settings → Super Site Page Selection and click Validate Sitemaps. If validation fails, the report can't start. Common issues:
The sitemap URL is incorrect or returns an error.
The sitemap format isn't readable (XML works best).
Fix the issue, save, and re-validate. Once validation passes, the queue will pick up your request.
2. Use a domain-level XML sitemap
Index Reporting works best when you provide an XML sitemap served at the domain level. If you're using a sitemap hosted elsewhere or relying on automatic discovery, try submitting the direct sitemap URL instead.
3. Check your property connection
If you connected your site as an sc-domain: property in Google Search Console (e.g., sc-domain:example.com), but your sitemaps reference https://example.com/..., the mismatch can block discovery. Make sure your sitemap URLs match the property type you connected in SEO Gets.
What about a percentage that never changes?
If Index Reporting shows a percentage (like 78% indexed) and it stays the same for a while, that doesn't necessarily mean the feature is broken. Some pages may be:
Published but not yet discovered by search engines.
Crawled but not indexed, which means Google knows they exist but hasn't added them to the index.
Intentionally excluded by robots.txt or noindex tags.
That's normal SEO behavior, not a reporting error. Use the indexed/not indexed breakdown to spot patterns, and check how to detect decaying content if you're concerned about pages dropping out of the index.
Still stuck?
If you've validated your sitemaps, confirmed your property connection, and waited several days with no progress, reach out via in-app chat. We can take a look at your setup and help get things moving.