The Batch Index is the HTML summary page RankGear generates for a Bulk Run — a single index that lists every row, its current state, its target location, and links out to each completed row’s artifacts.
| Term | Batch Index |
|---|---|
| Category | Reports, Workbooks and Exports |
| Also known as | Bulk Index, Batch Report |
| Where it appears | Bulk Runs |
What it means in RankGear
When you launch a Bulk Run, RankGear processes many keyword-and-location rows in one pass. The Batch Index is the landing page for that whole run: rather than opening each row separately, you get one HTML document that catalogs every row in the batch, shows whether each finished, is still processing, or failed, records the location each row was run against, and provides a link into the per-row output — the individual report or workbook produced for that keyword. It is the table of contents for the run, not a new analysis of its own.
How to interpret it
Read the Batch Index top-down: start with the opening summary and the state legend so you know what each status marker means, then use it as a hub — follow the links into the row-level reports and supporting sheets where the actual measurements live. Treat the index itself as navigation and provenance, not as findings. When you share or archive a run, keep the run metadata intact so a reader can see the settings, locations, and timing that produced the rows; that context is what makes the linked artifacts comparable to one another.
Example
You queue a Bulk Run of forty local keywords across three cities. When it finishes, RankGear writes a Batch Index that lists all one hundred and twenty rows: thirty-eight show a completed state, one is marked failed because a SERP fetch timed out, and one is still processing. From that page you click “plumber near me — Denver, CO” and land directly on that row’s report, then step back to the index to open the next one — without re-running anything.
Important considerations
- The Batch Index reflects one run at a fixed point in time. It is a snapshot; re-running the same batch later can produce different states and links as SERPs and provider data change.
- Compare rows like-for-like. Rows share meaning only when they were run with the same settings; a row’s location and configuration are part of how you read it.
- Formatting is not evidence. The index organizes and links results — it does not add signal. The measurements in the linked artifacts are the data; the index is how you get to them.
- Any provider metrics surfaced through the linked reports are comparative indicators, not Google’s own scores, and correlation across rows is not causation — the index does not imply that any factor makes a page rank.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.