Report Branding is custom header and footer HTML that replaces RankGear’s default presentation on the reports it generates, letting you stamp your own identity onto an exported workbook or companion file.
| Term | Report Branding |
|---|---|
| Category | Reports, Workbooks and Exports |
| Also known as | White-Label Branding, Branding |
| Where it appears | Settings → Branding |
What it means in RankGear
Report Branding lives in Settings → Branding, where you supply two blocks of HTML: one rendered at the top of a report and one at the foot. When RankGear builds a workbook or an HTML companion from a completed analysis, it drops your markup into those slots in place of its own default banner. The branding is presentation only — it wraps the output but never touches the measurements, factor scores, or run data underneath.
How to interpret it
Treat Report Branding as a template for the shell of the report, not part of its findings. Because the header and footer are raw HTML, you control the logo, agency name, contact block, or disclaimer that a client sees on a shared artifact. When you hand a report to someone, keep the run metadata intact alongside your branding so the reader can still tell which analysis, settings, and date produced the numbers.
| Slot | What it controls |
|---|---|
| Header HTML | The block rendered above the report body — typically a logo, agency name, or client title. |
| Footer HTML | The block rendered below the report body — typically contact details, a disclaimer, or copyright line. |
Example
A consultancy sets its header HTML to an inline logo and “Prepared by Northwind SEO” and its footer HTML to a confidentiality line. From then on, every workbook and HTML companion RankGear exports carries that framing, so a client receives a white-labeled document while the underlying factor measurements stay byte-for-byte the same as an unbranded run.
Important considerations
- Branding is cosmetic: it changes how a report looks, never what it measured. Do not read a polished header as extra evidence of quality.
- A report is a snapshot of one run. When comparing reports, match like-for-like settings rather than assuming two differently branded exports are otherwise identical.
- The fields accept raw HTML, so malformed markup can break a report’s layout — test a sample export after editing.
- Factor and provider figures inside a branded report remain comparative indicators, not Google scores; the wrapper does not change how those numbers should be read.
Related terms
Part of the RankGear glossary · how RankGear measures · the 870 factors.