IndexChex scheduled index checks

Purpose

Submitting a URL and checking it are two separate moments, and checking too early is the most common way to misread a submission. A page crawled in minutes may take hours or days to show up in results. The scheduled check in IndexChex fixes the check date at submission time so the follow-up happens without anyone having to remember it.

The feature was added on 22 December 2025, as recorded in the changelog.

How it works

1. When creating a standard or instant submission, the user chooses a re-check delay of 1 to 5 days, or none.
2. The check's credits, 1 per URL, are deducted together with the submission credits.
3. The delay clock starts when the submission begins processing. The check is scheduled for that moment plus the chosen number of days.
4. On the due date, IndexChex creates an ordinary index-check job for every URL in the submission and runs it with the standard index checker method: four live Google query forms per URL.
5. Results appear like any other check, with indexed, not indexed and failed lists, and the not-indexed URLs can be resubmitted in one click.

A pending check can be cancelled from the dashboard. Cancellation is atomic: once cancelled, it cannot also run, and the reserved credits go back to the balance. If the submission itself fails, the scheduled check is cancelled and refunded automatically.

Cost example

Credit prices per plan and pack are on the pricing page; every limit involved is in the specifications.

Choosing the delay

The right delay depends on the mode and on what the result will be used for.

IndexChex's product documentation describes the standard timeline as: Googlebot crawl within minutes, first pages indexed 5 to 12 hours after the job completes, most eventually indexed URLs visible 24 to 48 hours after the crawl, and indexation typically as complete as it will get by day 5. IndexChex's weekly measurements on recurring URL sets put average time to first Googlebot crawl under 2 minutes as of October 2026. A crawl is the start, not the outcome; Google's crawler overview covers fetching only, and indexing is a later decision.

Restrictions

• Not with drip feed. A job cannot use both. For a drip job, run a manual index check after the drip period ends.
• Range is 1 to 5 days. Longer gaps are handled by running a manual check later.
• One check per submission. For a second look, start a new check from the results.

Through the API

Both API versions expose the same option as an integer field named checker:

• API v1: POST /api/v1/index-submit/jobs with "checker": 3. The job status then reports scheduled_check_days, scheduled_check_status, scheduled_check_at and, once the check starts, scheduled_check_run_id.
• API v2: POST /api/v2/task/google/indexer/create with "checker": 3. An indexer task is only marked complete, and its report only served, after the scheduled check has finished.

A value of 0 or no value means no scheduled check.

Why it matters for evidence

Published indexation rates are only meaningful if the check that produced them happened at a consistent point after submission. The same reasoning applies to a user's own records: a fixed delay makes this month's batch comparable with last month's. How IndexChex applies that to its own figures is set out in the measurement methodology.