A Runtime-Minted Factor is a factor that RankGear creates on the fly from the current result set — a map token, a discovered term, or another signal that only exists because it surfaced in this run — so its presence depends entirely on the run data rather than a fixed factor list.
| Term | Runtime-Minted Factor |
|---|---|
| Category | Analysis and Optimization |
| Also known as | Dynamic Factor |
| Where it appears | Analysis engine and workbook |
What it means in RankGear
Most of the factors RankGear scores are predefined: they exist before a run starts and are measured the same way every time. A Runtime-Minted Factor is different. The analysis engine generates it while it processes the actual pages in your comparison set, so it only exists because something in this particular SERP produced it. Common cases are a map token pulled from local results or a term the engine discovered while reading the top-ranking pages for your keyword. Because these factors are minted from live run data, the exact set you see in the workbook can change from one analysis to the next, even for the same keyword, when the underlying results change.
How to interpret it
Read a Runtime-Minted Factor the same way you read any other factor in the workbook: against the target page, the comparison set, your selected deficit strategy, and the correlation the engine reports for it. Do not treat it as more or less important simply because it was generated at runtime. What matters is the evidence behind it — how the top pages use it and how strongly it tracks with position — not the fact that it was minted dynamically. Since these factors are tied to a specific run, expect the list to shift when you re-analyze after the results have moved, and judge each one on its own signal rather than optimizing any single value in isolation.
Example
You run an analysis for a plumbing keyword in a specific city. While reading the top-ranking pages, the engine repeatedly encounters a neighborhood name and a service term that were not on the standard factor list, so it mints them as runtime factors for this comparison. Your page never mentions the neighborhood, and the correlation for that factor is positive across the leading pages, so RankGear can turn that measured gap into a prioritized recommendation for this run. Change the city or the query and that neighborhood factor may not appear at all next time.
Important considerations
- The set of runtime-minted factors is tied to the current result set, so it can differ between runs of the same keyword when the SERP changes.
- A runtime factor is not inherently stronger than a predefined one — weigh it by its correlation and how the top pages actually use it.
- Correlation is not causation. These factors are comparative indicators drawn from the measured SERP, not Google ranking scores, and adding one does not by itself make a page rank.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.