Submit URLs for indexing

A job is a list of URLs submitted together. You can submit up to 2000 URLs in one job and create as many jobs as you like. Every page is checked before it is sent, and only URLs that are sent use credits, so a job costs at most one credit per URL with standard indexing, or more with the Fast and Bing add-ons. Processing begins as soon as a funded URL is sent. If your balance runs out part way through a job, the URLs already sent keep running; only the remaining URLs wait for credits and are sent once the balance is topped up. The job page says which is which, and what happens next.

Checks before sending

Each URL goes through a few quick checks first. Nothing is charged while a URL is being checked.

• Skipped URLs are not sent or charged by default. A URL is skipped when it redirects, when robots.txt blocks Googlebot, when it carries a noindex or expired unavailable_after rule, when it returns an error such as 404, or when its canonical points to a different page or conflicts. A page that could not be checked (an unsupported file type, or repeated fetch errors over a bounded number of attempts) is also skipped rather than sent. Each skipped URL shows its reason on the job page. A skip is a sending rule of this service, not proof that Google cannot index the page.
• Skipped URLs are not checked again on their own. After you fix the page or allow our crawler, choose Check again on the job. You do not need to submit the URLs again. The check is free; a URL that passes is sent and uses the job’s credits per URL.
• A blocked page checker can be bypassed. If a site returns HTTP 403 to our checker, the job links to the crawler allow guide. You can allow the crawler and choose Check again, or submit the affected URLs from the existing job without checks. The page makes clear that we could not confirm redirects, crawl rules, noindex or canonicals. Each URL uses the job’s credits per URL when it is sent.
• A URL already in progress is not sent twice. If another of your jobs, in any project, already holds the same URL and it has not had its first indexing check yet, the new entry is skipped and links to the earlier submission. Once that check has happened (a completed Google search or the first report), you can submit the URL again deliberately, for example after a meaningful update.
• Pages with little main content wait for your review. When the check reads little or no main text on first load, the URL shows Needs review with the word count it found. A page that appears to load its content with JavaScript is also shown for review, because this check does not run JavaScript and so could not measure its content. Google can read such pages. Nothing is sent or charged until you choose to approve some or all of those URLs on the job page.

A pass or approval that is more than an hour old is checked again before the credit is reserved, so a page that started redirecting or gained a noindex rule while waiting is not sent. Your approval of a content warning is kept across that recheck; a new technical block still wins.

Submit from the web app

You can also submit from the CLI, an AI client over MCP, or the API.

URL statuses

Every URL in a job has its own status.

Timing starts when each URL is sent, not when you create the job, so a URL waiting for credits has no timing yet. We search Google after 24 hours, with additional searches around days 3 and 7 only if no earlier exact-URL match or report has confirmed indexing. Searches stop once found or confirmed indexed. This is a check, not a promise that the page is indexed by then. A page found in Google at any of these searches shows Indexed straight away and counts towards the job’s progress. Your full report follows around day 5, with final checks around day 14, and those checks continue in the background for every URL. If a later report does not find the page, its status returns to Not indexed yet. A URL without an early match can show In progress until its first report appears.

Following each URL

Each sent URL shows when it was last checked and when the next check is due, for example Checked 24 Sept · next ~28 Sept. The ~ means the report comes around that day. Hover over the line to see which check it was and its exact time.

The link icon next to each sent URL opens a Google site: search for that exact URL in a new tab, so you can see the current results yourself. Google’s results vary by location and change over time. A page missing from a Google search, ours or yours, does not prove Google has not indexed it; the scheduled reports decide the result and any refund.

Indexing is not guaranteed. Google decides what it adds to the index, so pages still need to be worth indexing.

What works best

Not sure a page is ready? Run it through the free indexability checker first. It shows crawl access rules, noindex tags, and content concerns without using a credit.

• The pages that matter: product, feature, documentation, comparison, and collection pages, and posts you have just published or updated.
• Public URLs that load without signing in. No Search Console access or site ownership is needed, so pages on other sites that mention you work too.
• Pages with real content that is not duplicated elsewhere.
• Pages that are not blocked by robots.txt or a noindex tag.
• The canonical version of the URL, rather than a redirect or a tracking variant.

Duplicate URLs

If the same URL appears more than once in a job, it is submitted once and charged once; the job page says how many entries were folded. A URL already in progress in another of your jobs is skipped until that URL has had its first indexing check (see Checks before sending).

Refunds

When a URL is confirmed as not indexed after the final check, around day 14, its status changes to Refunded and one credit is returned to your balance. Fast and Bing credits are not returned. Refunds follow confirmed results, so they can take a little longer than 14 days. See Credits for the full rules.