An Active Task is the single processing job RankGear is running right now — the one job that currently holds the application’s shared analysis and page-rendering resources.
| Term | Active Task |
|---|---|
| Category | Product and Workflow |
| Also known as | Active Work, Running Job |
| Where it appears | Software-wide work coordinator |
What it means in RankGear
RankGear runs heavier operations — fetching and rendering pages, scoring a keyword against the factor set, building a report — through a shared pool of analysis and rendering resources. Because that pool is finite, the work coordinator promotes one job at a time to the foreground and marks it the Active Task. Everything else you have queued waits behind it. When you watch progress in the coordinator, the Active Task is the row that is actually moving: pulling data, computing, or writing its result.
How to interpret it
Read the Active Task as a state, not a score. It tells you which job owns the engine at this moment and how far along that job is — nothing about the quality of your page or its ranking. To judge whether a run is healthy, look at three things together: the inputs the task was given, the state the coordinator reports for it (queued, running, complete, or failed), and the artifact it says it produced. If those three line up, the task did its job; a stalled or failed Active Task points to a run problem, not a content verdict.
Example
You start a full analysis on the keyword “managed IT services” while a sitemap crawl from an earlier session is still finishing. The coordinator keeps the crawl as the Active Task and shows your keyword analysis as queued. Once the crawl completes and releases the rendering resources, your analysis is promoted to the Active Task, its progress bar begins to move, and when it finishes the coordinator links you straight to the saved report.
Important considerations
- Only one job is the Active Task at a time; a long-running job upstream can hold everything behind it, so a "stuck" analysis is often just waiting its turn rather than failing.
- The Active Task describes RankGear’s own behavior and navigation — which job holds the engine — not a ranking signal. It says nothing about how a page will perform in search.
- If a task never leaves the running state or ends in failure, check its inputs and the reported artifact before rerunning; the coordinator’s state is the reliable place to diagnose it.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.