🗺️ Overview
Search Atlas offers two distinct indexing features, and it is important to know which one you are using before troubleshooting a stuck queue. This article explains the difference between Instant Indexing and Dynamic Indexing, and walks you through what to check when URLs remain stuck in Indexing request pending status with no quota consumption.
⚡ Instant Indexing vs. Dynamic Indexing: Key Differences
These are two separate features. Confusing them is one of the most common reasons customers troubleshoot the wrong tool.
- Instant Indexing — Submits URLs directly to Google via the Google Indexing API. It is designed for JobPosting and BroadcastEvent structured data pages, but many users apply it broadly to accelerate Google crawling. Quota is consumed per successful API call.
- Dynamic Indexing — A Search Atlas automation layer that monitors your sitemap for new or updated URLs and triggers indexing requests on a schedule. It works alongside Instant Indexing but is a separate workflow.
Important correction: Instant Indexing is a Google feature. It has no connection to Bing. If you have seen guidance suggesting otherwise, please disregard it.
🚩 What a Stuck Queue Actually Looks Like
A queue is considered stuck when all of the following are true for more than 24 hours:
- One or more URLs show the status Indexing request pending.
- Your quota counter has not decreased since the requests were submitted.
- No error messages or rejection notices appear in the Instant Indexing log.
If only some URLs are pending but quota is being consumed normally, that is expected queuing behaviour and not a backend issue. The situation described above — zero quota movement over 24 hours or more — indicates a backend dispatch problem that cannot be resolved by switching to a different feature or running a manual reprocess.
🔎 Common Root Causes
- Dispatch job not running — The internal job that sends queued requests to the Google Indexing API may have stalled. This is a backend issue only the Search Atlas engineering team can resolve.
- Service account permission error — The Google service account connected to your property may have lost Owner-level access in Google Search Console, causing every API call to fail silently before it is dispatched.
- Google API quota exhausted at account level — If you share a service account across multiple properties, the daily 200-URL Google API limit may be consumed before your requests are processed.
- Service account JSON credentials expired or revoked — Credentials uploaded during initial setup can become invalid if the Google Cloud project settings have changed or the service account was modified.
📋 What to Have Ready When Escalating
Because a stuck dispatch queue requires backend investigation, please have the following information ready before contacting support:
- Your project name and the property URL affected.
- The exact URLs that are stuck in Indexing request pending status.
- The date and time when the requests were first submitted.
- A confirmation of whether your quota counter has moved at all since submission.
- Any error messages visible in your Instant Indexing log, copied exactly as they appear.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.