Understanding the Track overview

Learn the difference between the client-level Track workspace and individual tracking projects, then trace each metric to its supporting evidence.

Track has two levels: a client-level workspace that combines projects and keywords, and an individual tracking project with deeper reports. Use the client view to find where attention is needed, then open the relevant project or keyword for evidence.

Before data appears

Select a client and create at least one tracking project with a keyword. Visibility requires a usable terminal scan: either Complete, or Partial with successful data for the metric being shown. A partial run does not imply that every requested platform succeeded. Google Search Console (GSC) and Google Analytics 4 (GA4) are optional connections and only populate their related views after the correct property is connected and data is available.

Client-level Track workspace

Overview — Aggregates Search Performance Index (SPI) and available performance signals across the client. Competitor comparisons and Serena analysis appear when the required data and permissions are available.
Keywords — Reviews tracked keywords across projects and helps you filter and compare their current performance.
Traditional search — Consolidates supported organic ranking results across tracked keywords for the selected client.
GSC — Shows connected Google Search Console evidence for the client.
GA4 — Shows connected Google Analytics 4 evidence for the client.
Production — Shows website activity from the client’s connected GitHub repository, with new pages and significant content updates counted separately.

PDF in the Track workspace’s More actions menu, and Download PDF in an individual report’s More actions menu, build a client-ready PDF report for a client update or a file you keep. Rankability generates the document from the report’s latest completed scan rather than capturing the screen, so on-screen filters and date ranges do not change it. By default a report PDF covers the performance summary, an AI platform summary, channel results, competing domains, AI answer excerpts, and cited sources, and the workspace PDF covers the performance summary, the workspace’s reports, and an AI platform summary. Both carry your Report branding logo, name, and color.

Choose Customize PDF in the same menu to pick which of those sections to include and, if you want, limit the document to selected platforms. Platform choices change the exported detail only, not the saved visibility scores, and nothing you choose here changes your tracking or shared-report settings; the next download starts from the full report again.

Tracker competitors controls who appears in this workspace’s comparison charts. Open it with Competitors in the Track workspace’s More actions menu, or with Manage competitors in an individual report’s More actions menu. By default Rankability picks them from the scans. Turn on Add my competitors and list up to ten business names or domains, one per line — business names for AI and local results, domains for organic. Matching additions are prioritized, then Rankability fills the remaining comparison spots with automatically discovered competitors. Only competitors that actually appear in scans are shown, so an entry you add appears once a scan finds it. Choosing competitors changes the comparison charts only; the raw search results and your own rankings are never hidden.

Client portal viewers can have a reduced set of tabs and actions.

Website production history

Open Track → Production to review the work reaching your connected website repository’s default branch. If GitHub is not connected, choose Connect GitHub and select the website repository in workspace Settings. Once connected, Start tracking imports the previous year of supported page history and enables daily read-only checks. It does not publish content or change repository files.

Wait for the initial import to complete before interpreting totals. A later history update can preserve existing results while recovering missed pages; the view explains when those totals are still changing. Check the last-checked time and any connection notice before treating the report as current.

Use Activity to switch between New pages and Significant content updates. Compare weekly or monthly output in Bars or Table, or choose Cadence for a daily view. Current-period comparisons run through today. An existing campaign can be overlaid, with a baseline when enough earlier history is available. The evidence table links each new page to its commit and each qualifying update to its diff and reason.

A shipped page means a supported page file first reached the default branch; it does not prove that the page is deployed. Supported new pages include Astro and HTML pages, Pages Router pages, static Next.js App Router pages, and Markdown posts in an Astro blog collection with a verified public blog route. Removed pages, dynamic templates, and unrecognized content collections are excluded.

Significant updates count changes to authored Markdown body text or static main/article text in HTML and Astro pages. At least 100 added or removed words and 20% of the previous body, or 300 changed words, must qualify. Dates, metadata, formatting, code, link targets, and word reordering alone do not count. New pages and updates are separate activity measures, not an SEO quality score or proof of campaign impact. Expand About this history for the tracked period and detection limits.

Individual tracking project

Open a project or keyword when you need its scan history and platform-specific evidence. Available views vary with the project configuration and can include Overview, Keywords, Local, Traditional search, AI answers, AI citations, Compare, Video search, GSC, and GA4. From an individual report, select the keyword name in the header to search the workspace’s other tracked keywords and switch to one.

Ask Serena about the exact report

When a non-portal report has usable results, choose Ask Serena in the report header to open a dedicated Serena conversation grounded in the selected client, project, keyword, and report. Use it to interpret a change, compare evidence across tabs, or decide what to investigate next without having to restate the report context.

Review the destination shown in the conversation before asking Serena to act. The handoff supplies report context; it does not give Serena permission to change a project or an external site. Client portal viewers do not see this internal action.

Read empty and historical states correctly

No scan means there is no current usable complete or partial scan for that metric.
No history means an earlier comparable usable scan is not available.
Not tracked means that search engine or surface was not selected for the keyword.
Not ranked means a completed scan exists but the target did not rank within the tracked range.

Do not interpret a dash, blank field, or delayed connected-data value as zero without checking the state, date, and connection.

A load failure is reported as a failure rather than as empty data. When the overview cannot be loaded at all, it says so and offers a retry; when it cannot refresh but earlier results exist, it shows the most recent data available and tells you the refresh did not succeed. Neither state means the client’s numbers dropped — check the notice before reading the figures as current.

History views collapse comparable same-day results to the newest usable result for that UTC day. A partial run contributes only the platforms that returned usable data.

Move from summary to evidence

Confirm the selected client, comparison period, last completed scan, and connected-account status.
Open the SPI breakdown or the platform tab behind the change.
Compare the same dates and keyword scope before connecting visibility to GSC or GA4 performance.
Use annotations where available to record launches, migrations, campaigns, or outages.

Troubleshooting

If Overview is empty, confirm that a tracked keyword has a completed scan.
If GSC shows an authorization error, reconnect the client’s Google Search Console account and confirm the property.
If GA4 is missing, confirm the client connection, property, permissions, and source-data date.
If a ranking looks wrong, open the individual keyword report and verify the engine, location, latest scan, and ranking URL.