Skip to main content
The editor is where a report is built. Open a report from the Reports list.

​
Widgets

Content is added as widgets on a grid. Click to open the Add widget panel, choose one, and it’s placed on the canvas.

​
Widget types

Every widget renders as one of six visual forms:

​
Presets

Rather than building each widget from scratch, the panel offers presets that already know which metric to pull. They cover the whole platform: Rankings — Ranking Overview, Ranking Changes, Ranking History, Total Keywords, Avg. Position, Top 3 Keywords, Top 10 Keywords, Visibility Score, Position Distribution, the individual position bands (1–3, 4–10, 11–20, 21–50, 51–100, Not Ranking), Improved, Declined, Top Gainers, Top Losers, All Keywords Backlinks — Backlink Summary, Backlink History, Anchor Texts, Total Backlinks, Referring Domains, Domain Rating Audits — Audit Summary, Audit Issues, Audit Pages AI and GEO — GEO Overview, GEO Trend, GEO Topics Other — Web Vitals, Local SEO Overview, Domain Overview Picking a preset creates the widget with a sensible default visual type, which you can then change.

​
Text widgets

Text / Note is the widget most often skipped and most worth using. A report of charts without commentary makes the reader do the interpretation — which, for a client report, is the part you’re being paid for. Put a short summary at the top and a note under any chart that needs explaining.

​
Configuring a widget

Select a widget to open its configuration panel, where you set its type and options. Changes preview live against real project data.

​
Layout

Widgets are moved and resized on the grid. Arrange top-down in the order you want the story read: headline numbers first, then trends, then detail tables. Keep in mind the report will be read as a PDF as often as in the browser. Wide tables and dense charts survive that transition poorly; a few well-chosen widgets read better than a comprehensive dashboard.

​
Date range

The editor has a date range that applies to the whole report. Every widget reads its data for that range. This is what makes a report reusable: duplicate last month’s report, move the range forward, and every widget re-reads. It’s also what to check first when a report shows unexpected figures — a range that hasn’t been advanced is the usual cause.

​
Live data

Widgets read from the project when the report is viewed. They aren’t snapshots — a report opened next month shows current data for the configured range. Because widgets read stored project data, a widget for a feature that hasn’t been collected shows nothing. An audit widget on a project whose last crawl was months ago shows that old crawl. See How data collection works.