Issues, Page Explorer, and Internal Links

Investigate issue groups

Start with the rule definition, why it can matter, severity, category, affected count, and selected run. Search and filters narrow the evidence without changing the saved run.

• Read intentional exceptions.
• Inspect more than one affected URL.
• Separate template-wide and isolated cases.
• Use run history to distinguish persistent and new evidence.
• Copy agent guidance only with the relevant evidence attached.

Use Page Explorer

Page Explorer searches and filters the crawl inventory by status, discovery source, indexability, path, segment, and deeper technical fields. Saved views preserve a repeatable investigation, not a separate copy of the data.

• Clear stale filters before a new question.
• Name saved views by decision or owner.
• Use structure for directory-level orientation.
• Open the URL dossier when one page needs complete evidence.

Inspect site structure

Structure aggregates pages by path and directory so template or taxonomy patterns become visible. Folder counts reflect the selected run and scope; they are not a complete information-architecture model by themselves.

Investigate internal links

Internal Links connects source URL, target URL, anchor, relation, response and graph context. Link counts do not explain quality alone; inspect both endpoints and the wider navigation path.

• Broken targets need source and redirect context.
• Orphan status depends on crawl scope and eligible sources.
• Weak anchors need page intent and placement context.
• Link opportunities require relevance, not only graph distance.

Move from finding to verified fix