A self-contained HTML report is an analysis output whose styling, data, and interactive elements are all embedded in a single file, so it opens and behaves correctly without a running RankGear session or any external assets.
| Term | Self-Contained HTML Report |
|---|---|
| Category | Reports, Workbooks and Exports |
| Also known as | Offline HTML Report |
| Where it appears | Generated HTML reports |
What it means in RankGear
When RankGear finishes an analysis, it can produce an HTML companion to the workbook that packages everything the page needs to render on its own: the report markup, the CSS that styles it, the measured data, and any client-side interactions such as sortable tables or expandable sections. Because nothing is loaded from RankGear at view time and no network calls are required, the file can be emailed, dropped in shared storage, or opened months later on a machine that has never run the app. It is the shareable, read-only face of a run rather than a live view into the tool.
How to interpret it
Read the report the way it is laid out: start with the opening summary and any legend so you know what the columns and scores represent, then follow the internal links down into the supporting sections or sheets for detail. Treat the run metadata — the keyword, location, date, and settings recorded at the top — as part of the evidence, and keep it intact when you pass the file on so a recipient can see exactly which run produced these numbers. The report shows the state of one analysis at one moment; it does not update itself.
Example
You run an analysis for “commercial roofing contractor” in Dallas, then export the workbook together with a self-contained HTML report. You attach only the HTML file to an email for a client who has no RankGear login. They double-click it, the styled summary and sortable factor table render immediately with no missing images or broken layout, and they can drill into the sections offline — all from the single file, with the underlying measurements unchanged.
Important considerations
- A report is a snapshot of one run at fixed settings; when comparing reports, hold the keyword, location, and options constant so you are comparing like with like.
- Formatting and layout are presentation, not evidence — a cleaner-looking report is not a stronger result. Judge the findings, not the styling.
- Because the file is static, it will not reflect later re-runs or index changes; regenerate it when the underlying analysis is refreshed.
- The factor and provider metrics inside are comparative indicators drawn from the analyzed set, not Google ranking scores. Correlation is not causation, and a value in the report does not mean a term or setting caused a page to rank.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.