One workflow, several different outcomes
A URL can be publicly reachable without being indexed, and a provider can accept a submission without a search engine crawling the page. The platform therefore records each stage separately instead of presenting one universal success label.
Technical preflight
The preflight evaluates the public response available at the time of the check. It can record the final HTTP status, redirect destination, robots access, page-level noindex directives, canonical URL, and detected title. A passed preflight means no supported blocker was found; it does not mean the URL will be indexed.
Provider response
When a configured provider is eligible for the URL, the system stores the provider name and returned response. “Submitted” or “accepted” describes that provider response only. It is not evidence that Google or another search engine crawled, indexed, retained, or ranked the URL.
Report status definitions
| Status | Meaning | Recommended next step |
|---|---|---|
| Ready | The URL passed the supported preflight checks, but no eligible provider accepted a signal. | Review provider configuration and the URL’s own crawl paths. |
| Submitted | An eligible provider accepted the discovery signal. | Allow time for recrawling and verify later with first-party search tools. |
| Blocked | A supported technical issue such as noindex, robots blocking, or an error response was detected. | Fix the blocker before resubmitting. |
Evidence and limitations
Results reflect the public URL and provider response observed during the run. A later server change, geolocation rule, authentication layer, JavaScript rendering difference, or search-engine decision can produce a different outcome. Search visibility should be verified with Search Console, server logs, analytics, and the search engine’s own inspection tools where available.
For a practical diagnostic sequence, read Why Google Is Not Indexing Your Page or start with the crawlability tools.