A Bulk Run is a queue that carries out the same audit or analysis workflow — an On-Page Audit or a Full Analysis Run — across many keyword-and-target rows at once, so you configure the batch once instead of starting each row by hand.
| Term | Bulk Runs |
|---|---|
| Category | Product and Workflow |
| Also known as | Bulk Run, Batch Run |
| Where it appears | Analyse → Bulk Runs |
What it means in RankGear
Bulk Runs live under Analyse → Bulk Runs. Instead of pointing RankGear at a single keyword and URL, you hand it a list — each row pairing a keyword with the target page you want scored — and pick the workflow to apply to every row: an On-Page Audit or a Full Analysis Run. RankGear then processes the rows as a queue, working through them without you having to launch each one. When the batch finishes you get a run per row, each with its own report link, rather than one blended result.
How to interpret it
Treat a Bulk Run as a workflow container, not a metric. There is nothing to read on a scale of good-to-bad; what matters is that each row ran against the inputs you intended. Before you kick it off, check the keyword-and-target pairing on every row, and confirm which workflow the batch is set to run — an On-Page Audit and a Full Analysis Run produce different depth of output. While it runs, watch the per-row state so you can see which rows are queued, in progress, done, or failed. When it is finished, judge success row by row against the report each one produced.
Example
You are optimizing a cluster of twelve service pages, each aiming at its own primary keyword. Rather than open twelve separate analyses, you load all twelve keyword-and-URL pairs into a Bulk Run, set the workflow to On-Page Audit, and start it. RankGear works down the queue and, when it settles, hands back twelve individual audit reports — one per page — that you can open in turn to see where each target stands.
Important considerations
- A Bulk Run describes how RankGear processes work — it is navigation and batching, not a ranking signal. The batch itself has no effect on how any page ranks.
- Every row is only as good as its inputs. A mis-paired keyword and target will still run; it will just produce an audit for the wrong intent.
- The output is one artifact per row, not a single combined score. Compare rows against each other using the individual reports the run retained, not the fact that they were run together.
- Any scores inside the resulting audits are comparative indicators drawn from the pages analyzed, not Google’s own measurements — correlation with what currently ranks, not proof of cause.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.