Analysis Run

The Analysis Run is RankGear's full competitive workflow, which the maker calls "the heart of RankGear"^[2] . It defines the field of pages ranking for a keyword, measures a target page against them across the factor catalog, and returns an optimization score, a single first fix, an ordered roadmap and a workbook^[2] . The maker describes the result as a reason to prioritize a change, not a guarantee that it will rank^[2] .

Overview

RankGear's feature page says a run starts by defining "this query, right now" rather than "SEO in general"^[2] . Once the field is set, the shared engine renders each page and calculates the factor catalog, then tests each factor for how it correlates with position^[2] . The six stages behind this are described in How RankGear works, and the factor families in the RankGear factor catalog.

Inputs and settings

The user sets the following before a run^[2] :

• Keyword and target: a domain or a specific Target URL, or a pasted manual ranked list whose order RankGear keeps as the rank order^[2] .
• Depth: top 10 through top 100^[2] .
• Localization: country, language, device and an optional Near city or state for organic results^[2] .
• Deficit strategy: the statistical target gaps are measured against^[2] .
• Providers and variants: optional off-page and entity sources on the user's own accounts, plus variant keywords^[2] .
• Reports: which HTML companions to write beside the workbook^[2] .

The field can come from live Google organic results (the default), from Google Maps, or from a manual list^[2] . In manual mode, RankGear appends the Target URL once if needed, without moving the pasted ranks^[2] . The strategies are compared in Deficits and target strategies.

What a run measures

The engine calculates the 928-factor catalog, covering keywords, headings, content, entities, structure, schema, media, links, technology and authority; how many factors return a value depends on the field^[2] . Each factor is tested with Spearman and Pearson correlation, alongside competitor usage, distributions, BM25F and topical coverage^[2] . The two correlation measures are explained in Spearman and Pearson correlation.

RankGear's glossary defines a Significant Deficit as a gap on a factor whose correlation with rank in the current comparison set is strong enough to pass the run's significance rule^[3] . The glossary says the label separates gaps the measured results support from small differences "that carry no evidence behind them"^[3] . It also warns that a small or unusual comparison set can make gaps look significant or hide them^[3] .

Outputs: score, first fix and roadmap

The dashboard opens with the optimization score against the field, shown in degrees, the field's average and the Do-This-First fix, defined as "the single highest-correlation, lowest-effort change"^[2] . Below that come quick wins, an ordered roadmap and a work order that can be handed to a writer or developer, followed by a competitive factor table^[2] . Opening any factor shows its usage across the field, the page's value, the goal and the deficit^[2] .

The optimization score measures how much of the supported deficit the page has closed against the field and the chosen strategy^[2] . RankGear's glossary describes it as a 0 to 100 coverage summary, "not a grade of writing quality and not a prediction of a specific position"^[4] . Because a stricter strategy raises the bar, the same page scores lower under it^[4] .

Every full run writes a timestamped, color-coded XLSX workbook that opens on a Start Here tab, plus optional HTML companions such as the Analysis Summary and a Strategic Summary with up to ten statistically significant factor charts^[2] . These are covered in Reports, workbooks and Action Planner.

Excluding your own page from the benchmark

The tracked page is excluded from its own benchmark, "so nothing is ever graded against itself"^[2] . The methodology page says this stops the page from skewing the comparison^[5] . RankGear's glossary adds that the target page is plotted against the field so users can see where it sits instead of having its value folded into the average^[6] .

Limits

The maker lists several boundaries^[2] . Off-page and entity results depend on the providers a user has saved; a top 100 run takes longer than a top 10 run because there are more pages to fetch and render; and some pages stay unreadable after a retry, in which case rendered HTML can be pasted manually^[2] . Slow or blocked pages get one longer safety attempt, and other failures stay rank-aligned while the run continues^[2] .

The deficit strategy changes the goal and the deficit but never the measured page values^[2] . The glossary says the score covers only on-page factors RankGear can measure and "says nothing about off-page signals"^[4] . It also cautions against chasing 100 on every factor, since some gaps are trivial^[4] . Why correlation cannot prove a factor works is explained in Correlation and causation in SEO.

Common questions

See also

• How RankGear works
• On-Page Audit and Zone Architecture
• Content Intelligence and BM25 Drafts
• Local SEO grid
• Diff, Trends and Volatility
• Experiments

References

1. ^ ^{a b} "RankGear Features". RankGear (rankgear.com). Retrieved November 2026.
2. ^ ^{a b c d e f g h i j k l m n o p q r s t u v w x y z 26 27 28 29 30 31 32 33 34 35 36} "Analysis Run: measure the ranking field for a keyword". RankGear (rankgear.com). Retrieved November 2026.
3. ^ ^{a b c} "Significant deficit". RankGear knowledge base. Retrieved November 2026.
4. ^ ^{a b c d} "Optimization score". RankGear knowledge base. Retrieved November 2026.
5. ^ "Methodology: What RankGear measures". RankGear (rankgear.com). Retrieved November 2026.
6. ^ "Competitor field". RankGear knowledge base. Retrieved November 2026.
7. ^ "RankGear: Evidence-Led SEO Software for Mac & Windows". RankGear (rankgear.com). Retrieved November 2026.