Overview
This article covers: URL submission workflows, Left sidebar → Authority → Indexer (URL Indexer), CSV imports, indexation delays, quota handling, pending URLs, Google Search Console verification issues, quota balance corruption, and schema deployment failures.
The URL Indexer submits pages to Google's indexing systems, but final indexation decisions are controlled entirely by Google. Because Google evaluates content quality, crawlability, authority, canonical structure, and technical SEO signals, successful submission does not guarantee immediate crawling, indexation, or rankings.
⚠️ Error 1: URL submission shows "Queued" for more than 24 hours
What's happening
The Indexer submits URLs through Google's Indexing API. When daily quotas are reached, submission volume spikes, or multiple properties compete for requests, URLs remain queued until the quota resets.
Steps to try
- Wait for the daily quota reset at midnight UTC.
- Refresh the queue status periodically.
- Avoid resubmitting the same URLs repeatedly.
- Prioritize critical URLs first.
- Submit urgent pages manually using Google Search Console → URL Inspection.
- Verify the domain is connected properly to GSC.
- Remove low-priority URLs from bulk queues.
- Break large submissions into smaller batches.
- Confirm the URLs are publicly accessible.
- Contact support if the queue remains frozen across multiple days.
Important Notes
Queued status does not mean failure. Processing resumes automatically after quota resets. If the quota balance itself appears corrupted (negative, doubled, or not updating after submissions), see Error 4 — this requires manual correction by support and will not self-resolve at the daily reset.
⚠️ Error 2: URLs show as "Submitted" but are not appearing in Google Search
What's happening
"Submitted" only confirms the request was sent to Google. Google still independently decides whether to crawl, index, delay, or ignore the page.
Steps to try
- Use Google Search Console → URL Inspection.
- Check the page's actual indexation status.
- Confirm the page is not blocked by robots.txt.
- Verify no noindex tags, canonical conflicts, or redirect loops exist.
- Improve thin or duplicate content.
- Add internal links pointing to the page.
- Build supporting backlinks to increase crawl priority.
- Ensure the page loads correctly in incognito mode.
- Wait several additional crawl cycles.
- Re-submit only after underlying issues are fixed.
Important Notes
Submission alone does not guarantee indexation. Google prioritizes quality and authority signals.
⚠️ Error 3: Bulk URL import from CSV is failing
What's happening
CSV uploads fail when formatting is invalid, unsupported characters exist, headers are included, or URLs are malformed. The importer expects strict formatting.
Steps to try
- Open the CSV file in a plain text editor.
- Ensure one URL per line, no headers, no blank rows, no extra columns.
- Confirm every URL begins with
https://. - Remove all
http://URLs. - Delete hidden formatting characters if present.
- Save the file as UTF-8 plain text.
- Avoid Excel auto-formatting whenever possible.
- Re-upload the cleaned file.
- Test with a smaller batch first.
- Contact support if correctly formatted files still fail.
Important Notes
CSV formatting errors are the most common import issue. UTF-8 encoding prevents hidden character corruption.
⚠️ Error 4: Quota balance is corrupted, negative, or blocks a valid batch submission
What's happening
In rare cases, the URL Indexer quota balance becomes corrupted — for example, showing a negative credit total, double-charged submissions, or a balance that does not update after Atlas Brain processes new activity. When this happens, even valid batch submissions (e.g., a 141-URL batch) may be blocked even though the user has sufficient credits. This is a back-end sync issue and will NOT self-resolve at the daily quota reset.
Steps to try
- Confirm the issue is not a normal quota exhaustion (see Error 1).
- Note the exact credit balance shown, the expected balance, and any recent submissions that may have been double-charged.
- Record a Jam or screen video showing the corrupted balance and the blocked batch attempt.
- Contact support and request a manual quota correction — this must be done by a senior agent.
- Once support confirms the total has been corrected, retry the batch submission.
Important Notes
Manual quota corrections are tracked and require senior-agent involvement. Do not repeatedly retry the batch while the balance is corrupted — this can compound the issue. Support has successfully restored credits in cases of double-charging (example: ~267 credits restored on a blocked 141-URL batch).
⚠️ Error 5: Schemas show "pending" and fail to deploy despite API success messages
What's happening
In some cases, the schema deployment API returns a success response, but schemas remain in a "pending" state and never actually deploy to the live site. This has been observed with large schema queues (e.g., 97 pending schemas) and is a back-end deployment issue, not a user configuration problem.
Steps to try
- Verify the site connection and authentication are still valid.
- Confirm the schemas appear as "pending" rather than "failed" or "error."
- Record a Jam video reproducing the deployment attempt and the pending state.
- Contact support and request escalation to the dev team.
- Reference the existing tracking ticket: Linear OTTO-1827.
Important Notes
This is a known, dev-tracked issue. An API success response does not always mean the schema deployed — always verify deployment on the live page. Do not bulk re-submit pending schemas, as this can compound the queue and complicate dev troubleshooting.