Issues
Read the issue registry in the panel, filter affected pages, and bring a finding to the agent.
Open Issues next to the command bar after a crawl is loaded. The panel slides down under the bar. Esc closes the panel without clearing an issue filter that is already active.
The panel is the working view of the issue registry. Each active finding has a pillar, severity, evidence type, description, and affected page set. The reference page is the full lookup; the panel is where you act on it.
Read the panel
The Issues tab holds critical and warning findings, grouped under the five pillars. Info has its own flat list so lower-priority observations do not crowd the default view. If there are no critical or warning findings, the panel opens on Info.
The number beside a tab counts findings, not pages. The number on a finding is how many pages it affects. Hover for its severity, a short explanation, and its share of the crawl.
Within each pillar, severity sorts first. At the same severity, checks come before signals. Larger affected sets break the tie.
Filter affected pages
Click a finding and its chip appears beside the command bar. The table keeps only affected rows. On the map, affected pages stay clear and the rest dim so the surrounding clusters remain visible.
Click the active finding again, or use the × on its command-bar chip, to clear it. Click the body of that chip to invert the filter. Not Missing title, for example, keeps pages without that finding.
One issue filter can be active at a time. It can still stack with table filters and a map legend filter.
Filters and issues on the map →
Five pillars
| Pillar | The question it answers |
|---|---|
| Technical | Can search engines reach, render, and index this site? |
| On-Page | Does each page present itself well to engines and searchers? |
| Content | Is the substance worth ranking? |
| Architecture | Does the link structure route authority to the pages that should rank? |
| AI Search | Can machines extract, chunk, and cite this content? |
Checks vs signals
A check is a deterministic measurement: parsed HTML, an HTTP status, or a counted link. A signal is model-derived: embedding similarity, cluster fit, or a content-value score.
The panel does not add a Check or Signal badge to each pill. The distinction changes sorting and how you should read the evidence. The issue reference shows the evidence type for every finding.
From the inspector
The page inspector's Issues tab shows findings for one URL. On a multi-select, it rolls them up by rule and lists the affected pages underneath.
View all applies the same issue filter to the table and map. Attach to agent sends that finding as context instead. Finding attachments need a paid plan; filtering does not.
Ask the agent
On a paid plan, hover a panel finding and its count gives way to Ask agent. Select it to open the agent with that rule and its affected pages attached. You can also use + → Fix Issues from the composer.
Or ask in a sentence: which pages are missing meta descriptions, what the worst architecture issues are, or group the findings by pillar. The agent reads the same registry as the panel.