The RankGear Report Template is the shared editorial shell that every generated HTML report is built from — it supplies the report masthead, responsive spacing, linked-keyword behavior, and footer rules so each export looks and reads consistently.
| Term | RankGear Report Template |
|---|---|
| Category | Reports, Workbooks and Exports |
| Also known as | Report Template |
| Where it appears | All generated HTML reports |
What it means in RankGear
When RankGear writes an analysis out to a shareable HTML report, it does not lay out each report by hand. Every export is poured into one common template: a masthead that identifies the run, spacing rules that keep the layout readable from a desktop down to a phone, keyword references rendered as working links into the relevant sections, and a footer that carries the run’s context. Because the same shell wraps every report, two reports from different runs sit side by side and follow the same visual grammar — the same header placement, the same link behavior, the same footer conventions — so a reader always knows where to look.
How to interpret it
Read a report top-down: start with the opening summary and any legend the template presents, get your bearings from that, then follow the linked keywords into the supporting sections rather than scrolling blindly. The template is presentation, not measurement — it arranges the findings a run produced, it does not add to them. When you share a report, keep the run metadata the footer and masthead carry intact; that context is what lets a recipient tell which run, settings, and moment the report describes.
Example
You finish an analysis and export it as an HTML companion to the workbook. The Report Template renders it with the project name and run details in the masthead, each tracked keyword as a link that jumps to its section, and the run’s metadata in the footer. You email the file to a colleague; because it uses the same shell as every other RankGear report they have seen, they immediately know to read the summary first and click a keyword to drill in — without any explanation from you.
Important considerations
- A report is a snapshot of one run. Compare like-for-like settings across reports, and do not read a difference in wording or layout as a difference in the underlying data.
- The template controls formatting only. Styling — colors, spacing, link treatment — is not evidence and should never be treated as a signal about a page’s quality or ranking.
- The figures a report presents are comparative indicators drawn from the pages a run examined, not Google ranking scores; the template’s job is to display them clearly, not to strengthen or endorse them.
- Preserve the masthead and footer metadata when sharing an artifact — stripping the run context makes a report harder to interpret and easy to mistake for a different run.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.