What is checked before credits are charged
Each line is normalized as an HTTP or HTTPS URL. Exact duplicates are removed within the batch. Invalid lines are returned to the user before the database transaction is committed.
Credits are deducted only for accepted unique URLs. The transaction stores the batch, URL rows and credit movement together so partial submissions do not silently consume a balance.
- HTTP or HTTPS URL format
- Duplicate URL hash inside the batch
- Maximum batch size
- Available account credits
- Rate-limit and anti-abuse checks
Meaning of every processing status
Statuses describe the operational workflow, not a promise from Google. The provider and verification fields are kept separate so a green processing state cannot be mistaken for an indexed result.
- Received: saved safely in the account
- Validated: format and duplicate checks passed
- Processing: owner or provider work has started
- Provider submitted: an external workflow accepted the URL
- Verification pending: waiting for an independent check
- Indexed: a configured verification method detected the canonical URL
- Not detected: the verification method did not detect it at that check time
- Failed: the workflow returned a technical failure
Public reporting rules
Public aggregate statistics remain hidden until the account has enough completed samples to avoid misleading percentages from a tiny dataset. The threshold is editable by the owner.
No testimonial, success percentage or processing-time claim is generated automatically. The owner must publish only evidence supported by actual order and URL records.
What users should check on the page itself
A submission system cannot repair blocked crawling, a noindex directive, a conflicting canonical, a soft 404 or low-value duplicate content. Those checks belong to the page and site.
- HTTP response and render stability
- robots.txt and robots directives
- Canonical consistency
- Internal links and sitemap coverage
- Unique helpful page content
- Search Console inspection for owned URLs
Frequently asked questions
Does “Provider submitted” mean the URL is indexed?
No. It only means a configured provider accepted the workflow request.
When is a URL labelled indexed?
Only when an independent configured verification method detects the canonical URL.
Why might public success statistics be hidden?
The owner can require a minimum completed sample so a tiny dataset is not presented as meaningful proof.
Can FastIndexingBot force Google to index a page?
No. Google controls crawling, canonical selection and indexing.