On-Page Audit and Zone Architecture
The On-Page Audit is RankGear's fast, single-page tool: it scores a page out of 100 against the pages beating it for a query, lists fixes in priority order and reviews the rendered page against nine "zones" of responsibility[2] . It runs only on-page factors, so the maker says it takes about a minute and can be run live during a client call[2] . The Zone Architecture part is advisory and does not change the score[2] .
Overview
RankGear describes the On-Page Audit as "a fast, client-ready answer for one page"[2] . The user gives a keyword and page, a result depth from top 10 to top 100, country, language, an optional Near location, a deficit strategy and a Zone Architecture profile for the page type[2] . The audit uses no providers and writes no workbook, which is why it is faster than a full run[2] . RankGear's use-cases page describes walking a client through the score, first fix and Zone Architecture "in about a minute"[3] . The audit is one of the Analyse tools listed on RankGear's features page[1] .
How the audit is scored
The audit opens on a coverage score out of 100 and the single highest-impact fix, followed by a numbered list of priorities[2] . Below these are average and maximum diagnostics, keyword and contextual density, a content brief and a searchable competitive factor table that shows where the field's consensus is and where the page falls short[2] .
RankGear defines the coverage score as how well the page covers the on-page factors that track position in the field, and says it is "not a Google quality score or a probability of ranking"[2] . The target the score is measured against depends on the deficit strategy chosen, as explained in Deficits and target strategies. The factors themselves are listed in the RankGear factor catalog.
Zone Architecture (Z1 to Z9)
Zone Architecture is RankGear's advisory review of whether a page visibly fulfills nine semantic responsibilities, or zones, expected of its page type[4] . For each zone the audit reports the found state, a declared or inferred mapping, the location in the page's DOM, an evidence excerpt and required coverage[2] . Users choose a profile: Universal for the baseline every page should cover, Local service for a local service page with a contact, quote or booking path, or profiles for national service pages, editorial articles and ecommerce products[2] .
RankGear's glossary describes four zone states: present and substantive, present but weak, blocked or unrendered, and missing[4] . It advises reading each zone as two questions, whether the element is present and whether it is implemented well, since an element can exist in the markup yet be empty, duplicated or too generic[4] .
The nine-zone idea comes from Zone Theory, which RankGear's glossary describes as an external, MIT-licensed framework credited to Cory Hubbell[5] . RankGear says it applies the framework as advisory guidance, not as one of its scored factors[5] . The maker states that Zone Architecture "doesn't change BM25F, correlation, the deficit math, or the score"[2] , and that a page can satisfy all nine zones and still not rank[4] .
Fix lists
Every audit produces a branded, self-contained audit HTML file with the score, the fixes, the density figures and the Zone Architecture evidence[2] . An optional Strategic Summary adds a second client-ready report with up to ten factor charts built from the same measurements[2] . The maker suggests re-auditing after changes ship, then using Diff to separate the effect of those changes from movement in the field, as covered in Diff, Trends and Volatility[2] . Report formats are covered in Reports, workbooks and Action Planner.
On-Page Audit compared with Analysis Run
RankGear's feature page compares the two tools as follows[2] :
| On-Page Audit | Analysis Run | |
|---|---|---|
| Scope | On-page factors, one page | The full 928-factor catalog, including off-page and entities |
| Speed | About a minute | Longer; renders the whole field and writes the workbook |
| Output | Coverage score out of 100, fix list, Zone Architecture | Optimization score, roadmap and complete workbook |
| Best for | A fast read in a client call | The deep diagnosis and the deliverable |
The audit does not run backlinks, entities or the workbook export; those belong to the Analysis Run[2] . As with the full run, the maker says findings "flag priority, not a promise the fix will rank you"[2] .
Common questions
What does RankGear's On-Page Audit do?
It scores one page out of 100 against the pages beating it, gives the single highest-impact fix and a numbered priority list, and reviews the page's Zone Architecture[2] . It runs only on-page factors and takes about a minute[2] .
What is Zone Architecture?
It is RankGear's advisory review of whether a page fulfills nine semantic responsibilities expected for its page type[4] . It draws on Zone Theory, an MIT-licensed framework credited to Cory Hubbell[5] .
How is the On-Page Audit scored?
It uses a coverage score out of 100 that reflects how well the page covers the on-page factors that track position in the field[2] . Zone Architecture findings do not affect the score[2] .
When should I use an audit instead of a full run?
RankGear suggests the audit for a fast single-page answer, such as during a client call, and the Analysis Run for the full deliverable with off-page data, entities and the workbook[2] .
See also
- How RankGear works
- Analysis Run
- Content Intelligence and BM25 Drafts
- Local SEO grid
- Diff, Trends and Volatility
- Experiments
References
- ^ a b "RankGear Features". RankGear (rankgear.com). Retrieved November 2026.
- ^ 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 "On-Page Audit". RankGear (rankgear.com). Retrieved November 2026.
- ^ "RankGear use cases". RankGear (rankgear.com). Retrieved November 2026.
- ^ a b c d e "Zone Architecture". RankGear knowledge base. Retrieved November 2026.
- ^ a b c "Zone theory". RankGear knowledge base. Retrieved November 2026.