What these numbers mean
Every chart and stat on the board links here. Each entry explains what it measures,
how to read it, and where else it shows up.
Site score
A single number summarizing the site's SEO health. Higher is better. Watch the trend more than any one reading. A steady climb or a sudden drop tells you more than the number alone.
The score rolls up indexing, critical issues, and other signals the plugin checks into one number. It exists to answer "is this site getting better or worse" at a glance across many sites, not to be a precise grade. Treat a single day's score as noisy; treat a multi-day trend as signal.
Where this shows up
- Site board, Score column
- Site detail, Score stat and chart
Video walkthrough: not recorded yet.
Pages not indexed
Pages the plugin believes are useful but Google has not indexed. A page that cannot be found in search cannot earn any traffic, however good it is.
This counts pages the site's own indexing check has classified as worth indexing (not junk, not intentionally excluded) but that do not currently show up in Google's index. A rising count over time is worth investigating on the site itself. The plugin's indexing tools show which pages and why.
Where this shows up
- Site board, Not indexed column
- Site detail, Not indexed stat
Video walkthrough: not recorded yet.
Critical issues
Problems the plugin considers urgent, the kind that actively cost rankings or traffic, not minor polish items.
Critical is the plugin's own top severity tier, assigned per issue inside the site's audit. It intentionally does not include every recommendation the plugin has, only the ones judged worth interrupting someone's day for. Zero critical issues does not mean a perfect site; it means nothing urgent is currently flagged.
Where this shows up
- Site board, Critical column
- Site detail, Critical stat and chart
Video walkthrough: not recorded yet.
Cannibalization conflicts
How many queries have two or more of the site's own pages competing against each other, splitting traffic that one page could have won outright.
When two pages both rank for the same search, they usually rank lower than a single, clearly the best page would. This count is queries currently in that state. See the full list on the site's detail view. It names the competing pages and lets you resolve or dismiss each one.
Where this shows up
- Site board, Critical column (included when severe)
- Site detail, Cannibalization stat and list
Video walkthrough: not recorded yet.
How to read the score chart
The shaded band is the real range this score has moved in during the window shown. A red dot means the latest reading is a new high or low for that range, not just a normal wobble.
This chart plots the score over the history window (7 days free, 90 days licensed). The shaded band behind the line is the actual observed minimum to maximum for that window. It is not an external benchmark, it is this site's own recent normal. The most recent point is drawn larger; it turns red when it sits exactly at the top or bottom of that band, meaning the site just reached a new extreme rather than continuing a familiar pattern.
Where this shows up
Video walkthrough: not recorded yet.
How to read the critical issues chart
Same reading as the score chart, applied to the count of critical issues. The band is this site's own recent range, and a red dot marks a new high or low.
A rising line with a red dot at the top means critical issues are actively getting worse and just hit a new high for the window, worth investigating now rather than waiting for the next report. A falling line means whatever was fixed is holding.
Where this shows up
- Site detail, Critical issues chart
Video walkthrough: not recorded yet.
Recent column
A small bar per recent report, tallest where critical issues were highest. The rightmost bar is today. This shows direction at a glance without opening the site.
Each bar is one snapshot the site sent in, most recent on the right. Height tracks critical issue count, so a strip that climbs left to right is getting worse, and one that falls is improving. Useful for scanning many sites for which ones are trending the wrong way before opening any of them individually.
Where this shows up
- Site board, Recent column
Video walkthrough: not recorded yet.
Conflict severity and actions
HIGH, MEDIUM, or LOW reflects how much traffic is likely being split. "Mark resolved" and "Not an issue" tell the site what you decided. Both take effect within about 15 minutes; they don't happen instantly.
Severity is calculated from how close the competing pages are in impressions and ranking position. Two pages neck and neck for a lot of search volume is HIGH; a large gap or low volume is LOW. "Mark resolved" records that you fixed the underlying overlap (merged content, changed targeting, etc.); "Not an issue" records that the overlap is intentional and should stop being flagged. Both are sent to the site as a request, which it picks up on its own schedule, roughly every 15 minutes, rather than being applied the instant you click.
Where this shows up
- Site detail, Cannibalization list
Video walkthrough: not recorded yet.
Pages losing sales
Pages where the plugin's GA4 and Clarity analysis found conversions dropping, visitors leaving without engaging, or frustration signals like rage clicks. Sorted worst first.
Each card compares the page's current number against this site's own recent baseline, the same reference-range idea as the score chart, applied per page instead of site-wide. "Conversions/month estimated lost" is the plugin's estimate of what a return to baseline would be worth, not a guarantee. Six kinds of finding feed this list: no conversions at all, converting below average, a drop versus last period, high bounce rate, a failing script, and rage clicks.
Where this shows up
- Site detail, Pages losing sales list
Video walkthrough: not recorded yet.
Average position
Where this site typically ranks in Google search results, weighted by how many impressions each ranking got. Lower is better, a position of 1 means first result.
Pulled once a day from Google Search Console. Weighted by impressions rather than a flat average across queries, so a query that shows up constantly counts more toward this number than one that appears once. Only present for sites where Search Console is connected.
Where this shows up
- Site detail, Average position chart
Video walkthrough: not recorded yet.
Clicks from search
How many times someone clicked through to this site from a Google search result, for the most recent day Search Console has data for.
From the same daily Search Console pull as average position. A short history window means this will often look sparse for smaller sites, that is a real reflection of real traffic, not a display problem.
Where this shows up
- Site detail, Clicks from search chart
Video walkthrough: not recorded yet.
Impressions in search
How many times a page from this site appeared in Google search results, whether or not anyone clicked it, for the most recent day Search Console has data for.
A page can have many impressions and few clicks, that combination usually means the page is being shown but the title or snippet is not convincing people to click. Watched alongside clicks and average position rather than alone.
Where this shows up
- Site detail, Impressions in search chart
Video walkthrough: not recorded yet.
AI edits and suggestions
How many AI-proposed content changes were applied per day, and where every suggestion currently stands: applied, waiting for review, rolled back, or errored.
Every AI suggestion needs a human to confirm it before it goes live, this counts what has already been approved and applied, not what the AI merely proposed. Rolled back means someone applied it then reverted it, error means the change failed to save. A high pending count is not a problem by itself, it just means review has not caught up yet.
Where this shows up
- Site detail, AI edits applied per day chart
- Site detail, AI suggestions by status
Video walkthrough: not recorded yet.
Sessions per day
Total visits to this site, summed across every page, for each of the last two weeks.
From the same local analytics data the sales-losing findings above are built from, rolled up to one number per day for the whole site rather than broken out per page. Read alongside conversions per day to see whether a change in conversions tracks a change in traffic or happened independently of it.
Where this shows up
- Site detail, Sessions per day chart
Video walkthrough: not recorded yet.
Conversions per day
Total conversions across the whole site, for each of the last two weeks.
Same source and window as sessions per day. A conversions line that falls while sessions holds steady points at something on the site itself, not a traffic problem, the individual page findings above are the place to look for which page.
Where this shows up
- Site detail, Conversions per day chart
Video walkthrough: not recorded yet.
Confirmed indexing
Whether Google itself confirms a page is indexed, checked directly through Search Console rather than guessed from the plugin's own local signals.
A small batch of pages is checked against Google every day, prioritizing pages the plugin thinks are worth indexing but cannot confirm locally. Full site coverage builds up gradually rather than all at once, to stay well within Google's daily quota for this check. A page listed under not yet checked has not been asked about yet, it is not the same as confirmed not indexed.
Where this shows up
- Site detail, Confirmed indexing donut and findings list
Video walkthrough: not recorded yet.
Funnel
How many visitors made it through each step you defined, and how many were lost between steps.
Uses GA4's Funnel Exploration, an API Google itself labels alpha, still gathering feedback before it becomes a stable part of the platform. Steps are defined by the site owner in the plugin's settings, either a page path or a GA4 event name, since GA4 has no way to guess which pages or actions matter to a given business. Only sent once at least two real steps are configured.
Where this shows up
- Site detail, Funnel chart
Video walkthrough: not recorded yet.
Team
Who besides the owner can see or manage this site, and what they can do.
Viewer can see everything but change nothing. Editor can apply fixes and roll them back. Admin can also invite or remove other people. The person being invited needs an account on this platform already, an invite only grants access, it does not create the account for them.
Where this shows up
- Site detail, Team section
Video walkthrough: not recorded yet.
Broken links
Real 404s this site has actually served, worst (most-hit) first, not a guess or a crawl.
Every time a real visitor or bot hits a URL on this site that returns a 404, the plugin logs it locally. This list shows the ones hit most often, since those are costing the most real traffic. Type a destination path and add a redirect directly from here, the exact same 301 redirect the plugin's own Redirects screen would create.
Where this shows up
- Site detail, Broken links findings list
Video walkthrough: not recorded yet.
AI suggestions pending review
Real, already-generated suggestions from the plugin's own AI, waiting for a decision, not a live preview generated here.
The plugin generates these suggestions (title, meta description, ALT text, and more) on its own schedule, then holds them for review rather than applying anything automatically. Apply here does the exact same thing clicking Apply in the plugin itself would do, on the real page, immediately.
Where this shows up
- Site detail, AI suggestions pending review findings list
Video walkthrough: not recorded yet.
Toxic backlinks
Domains the connected data source itself flags as spam, not a guess the plugin makes on its own.
Only what the provider (currently Ahrefs) directly marks as spam appears here, a home-made toxicity score that gets a working link disavowed by mistake costs real traffic. Google has no API for the disavow tool: marking a domain here records the decision locally and adds it to the disavow file the plugin builds, uploading that file to Google Search Console is still a manual step, repeated whenever the list changes.
Where this shows up
- Site detail, Toxic backlinks findings list
Video walkthrough: not recorded yet.
Unanswered reviews
Real Google reviews with no reply yet, read from the same cache the plugin's own Reviews screen uses.
Suggest a reply calls the same AI draft generator the plugin itself offers, only when clicked, nothing is generated automatically. Post reply publishes whatever text is currently in the box, live, on the business's real Google profile, immediately visible to customers. Nothing is posted without a person reviewing the text first.
Where this shows up
- Site detail, Unanswered reviews findings list
Video walkthrough: not recorded yet.
Upcoming content
Real items still ahead in the plugin's own content plan: scheduled posts and drafts awaiting a real publish.
Read-only here, a cross-site view of what is coming, not a new editing surface. Manage drafts, reschedule, and approve from the plugin's own calendar screen on each site.
Where this shows up
- Site detail, Upcoming content findings list
Video walkthrough: not recorded yet.
Recommendations
Already prioritized by the plugin from 12+ real signals, not recomputed here.
Fixing here does the exact same thing clicking Fix in the plugin would do. Some fixes use AI and cost money per page or image, clearly labeled Fix with AI. A fix covering many targets (e.g. every image missing ALT text) may need more than one click: the button becomes Continue when work remains.
Where this shows up
- Site detail, Recommendations findings list
Video walkthrough: not recorded yet.
Broken template variables
Placeholders like {city} still visible on the live page, not filled in by whatever generated it.
The plugin can't know what value belongs in an unfilled placeholder, that's a template or data problem to fix by hand. Close from indexing keeps the page out of search results and stops it passing link equity through its own links until the real fix happens, the exact same action available on the plugin's own Broken template variables screen.
Where this shows up
- Site detail, Broken template variables findings list
Video walkthrough: not recorded yet.
Keyword clusters
Real clusters from the plugin's own keyword set, top by total search volume.
A cluster with no page assigned yet is flagged, but this is a planning view, not a findings list: deciding what to write and assigning it to a page happens in the plugin's own Keyword set screen.
Where this shows up
- Site detail, Keyword clusters findings list
Video walkthrough: not recorded yet.
Needs attention
Real problems the plugin detected on its own (tracking, indexing, and the like), not a static checklist.
An alert clears itself once the site reports the underlying problem is gone, the next time it checks in, usually within a day. Recheck now runs the same live check immediately instead of waiting for the next scheduled pass.
Where this shows up
- Site detail, Needs attention
Video walkthrough: not recorded yet.