Working with Issues

Everything wrong with a client's site is tracked in one place: technical findings from site crawls, internal-link problems, and pages competing for the same keywords. Rather than checking three features separately, you work from the Pages table, sorted so the pages worth fixing first sit at the top.

The view is page-first. Each row is a page, and its Issues column counts the problems found on it. Click any row to open the page drawer and work through those issues one by one.

Where to find it

Open a client and click Pages in the sidebar. The Issues column sits between Cluster and Experiments.

To see only pages with problems, set the filter dropdown to Has issues, or Has errors for the most serious ones alone.

Issue counts stay empty until at least one crawl has run for the client. If every page reads as a dash rather than Clean, click Run crawl to start one. See Running an Audit.

What feeds the issue counts

Three features report in:

• Site crawl: technical findings from your latest audit crawl, including missing or duplicate titles and meta descriptions, thin content, redirect chains, slow responses, and missing structured data.
• Internal links: link problems detected from your link map, such as pages with no incoming in-content links (nav links don't count), pages that link to the same target more than once, and links pointing at removed pages.
• Keywords: keyword cannibalization, meaning two pages on the site ranking for the same non-brand queries in Google Search Console and splitting clicks between them. Requires a connected Search Console property. See Google Search Console.

Severity and priority

Every issue is an Error, Warning, or Info item. Errors are problems that hurt the page now, such as a missing title tag or a link to a removed page. Warnings are worth fixing when you get to them. Info items are usually deliberate choices worth confirming, like a redirect or a noindex tag.

Hover the Issues cell to see the breakdown by severity, the page's top issue, and its priority score.

Sorting by Priority weighs each page's issue severity against its traffic and key events. A page with one error and real visitors outranks a page with three errors and no traffic, because fixing the first one moves something. Use the sort button in the toolbar to cycle to priority, which appears once at least one page is ranked.

The stat cards above the table summarize the site at a glance: Open issues (with the number of pages affected), Errors (with keyword conflicts alongside, counted as page pairs so one conflict between two pages counts once), Live experiments, and Pending recommendations.

How to narrow the list

1. Type in the Search pages, titles, clusters… box to match a page URL, title, or cluster.
2. Use the filter dropdown for Has issues or Has errors.
3. Use the sort button to cycle to priority or issues, depending on whether you want the most impactful pages or simply the busiest ones.

How to work through a page's issues

1. Click a page row. The page drawer opens.
2. Open the Issues tab. Issues are grouped by category, with each one's severity, detail, and a guidance line explaining what to do about it.
3. Use the action link on each issue to jump to the right place: Details opens the crawl finding, and Fix opens Link Mapping for internal-link issues.
4. For keyword conflicts, the row is labeled Competing with the other page involved. Click Open that page → to inspect the counterpart.

Dismissing an issue

Some findings genuinely don't apply, such as a contact page flagged for thin content, or two pages that intentionally target overlapping queries. Dismissing removes an issue from the count without fixing it.

1. Open the page drawer and find the issue on the Issues tab.
2. Click Dismiss.

Dismissed issues stay hidden for that page, including on future crawls, until you restore them. To bring one back, click Show N dismissed at the bottom of the tab, then click Restore next to the issue.

Rechecking keywords

Keyword conflict detection refreshes nightly. If you've just changed something that affects the report, most commonly a client's brand terms, click Recheck keywords in the Pages toolbar to recompute conflicts now instead of waiting for the next nightly refresh.

Crawl history

The Pages table shows the current state of the site; it doesn't replace the crawl record. Click Site Audit in the sidebar to see every past crawl, each run's snapshot, and comparisons between runs. See Audit Reports & History.

Tips

• Sort by priority rather than raw issue counts. That order already accounts for which pages have traffic worth protecting.
• The keyword conflict count is the fastest health check after a content restructure: if it climbs, new pages may be stepping on old ones.
• Info items are often fine as-is. Confirm a noindex or redirect is deliberate, then dismiss it so the count only reflects real work.
• Because issues live on the Pages table, you can sort by clicks first and read the Issues column alongside traffic to spot high-value problems directly.

Troubleshooting

Every page shows a dash instead of a count. No crawl has run for this client. Click Run crawl, wait for it to finish, then check again.

No keyword conflicts appear. Conflict detection needs Search Console query data. Check that a property is connected and assigned to this client. See Google Search Console. If the site genuinely has no competing pages, an empty count is good news.

A conflict I fixed is still counted. The keyword report refreshes nightly. Click Recheck keywords to recompute it immediately.

An issue keeps coming back after I fix it. Crawl-based issues clear on the next crawl, not the moment you edit the page. Run a fresh crawl to confirm the fix, or dismiss the issue if it doesn't apply to that page.

Related

• Page Inventory
• Running an Audit
• Audit Reports & History
• Linking Plan Overview
• Google Search Console