Diagnosing Drops: Query vs Page vs Technical

The diagnostic tree

When traffic drops, the cause falls into one of three categories. Identifying the correct category is the most important step because the fixes are completely different. Applying a content fix to a technical problem wastes time. Applying a technical fix to a query-level change wastes time.

This page gives you the diagnostic tree to classify any drop quickly.

Step 1: Determine scope

Open GSC Performance. Compare the last 28 days to the prior 28 days.

All or most pages declined. Go to the Technical branch.

A specific section or content type declined. Go to the Page branch.

Overall traffic is stable but specific queries lost volume. Go to the Query branch.

The Technical branch

A site-wide drop that affects most pages simultaneously is almost always technical or algorithmic.

Check immediately:

• GSC > Pages report for new crawl errors or indexing drops
• GSC > Security & Manual Actions for penalties
• Server uptime logs for downtime during the drop period
• Recent deployments for accidental robots.txt changes, noindex additions, or sitemap removal
• DNS and CDN configuration for recent changes

If you find a technical cause: Fix it. Technical recoveries are usually fast (days to 2 weeks) once the issue is resolved.

If no technical cause is found: Check timing against known Google algorithm updates. If the timing matches, the drop is likely algorithmic. Review your content against the update's stated focus area.

If no update matches: Check if competitors also dropped (use third-party tools or manual SERP checks). If the entire niche dropped, it is likely a SERP layout change or industry-wide algorithm adjustment. If only you dropped, investigate site-level quality signals.

The Page branch

When specific pages or a section drops while the rest of the site is stable, the issue is page-level.

For each affected page, check:

1. Is it still indexed? Use URL Inspection in GSC. If it was de-indexed, check for noindex tags, canonical issues, or quality-based exclusion.

2. Did the content become outdated? Compare your content to what currently ranks. If competitors have more current, more comprehensive content, your page decayed.

3. Is it being cannibalized? Filter GSC by the page's target queries. Are other pages from your site also appearing for those queries? If the ranking URL keeps switching, cannibalization is the cause.

4. Did it lose backlinks? Check the page's backlink profile. If significant links were removed or the linking pages lost their own authority, your page lost authority.

5. Did the SERP change? Check the current SERP for the page's target queries. Are new SERP features (featured snippets, AI overviews) taking space? Did a strong new competitor enter?

The Query branch

When specific queries lose volume but your pages are otherwise stable, the change is at the query level.

Check:

1. Did search volume change? Some queries are seasonal or trend-driven. A query that had 10,000 monthly searches last year might have 5,000 this year because interest in the topic declined.

2. Did Google change the SERP layout? New SERP features can absorb clicks that previously went to organic results. An AI overview answering the query directly reduces clicks to all organic results.

3. Did intent shift? Check the current SERP. If the result types changed (from articles to product pages, or from lists to videos), the intent Google assigns to the query may have shifted. Your page format may no longer match.

4. Did a dominant competitor enter? A major brand entering the SERP for a query can push everyone else down. Check if a new, authoritative result appeared.

After diagnosis

Once you have identified the category and specific cause:

• Technical issues: Fix immediately. Monitor for recovery over 1 to 2 weeks.
• Content decay: Update the affected pages. Monitor for 2 to 6 weeks.
• Cannibalization: Consolidate or differentiate. Monitor for 2 to 4 weeks.
• Algorithm update: Improve content quality across affected pages. Monitor for 1 to 3 months.
• Query-level changes: Evaluate whether the query is still worth targeting. If intent shifted, create new content in the expected format. If volume declined, find replacement queries.
• SERP feature changes: Optimize for the new SERP features if possible (structured data for featured snippets, video for video carousels). Accept that some click loss to SERP features is permanent.

Practical takeaway

Every traffic drop has a specific, diagnosable cause. The diagnostic sequence is: determine scope, follow the correct branch, check the specific causes in order, and apply the matching fix. Resist the urge to guess or apply generic fixes. Diagnosis first, always.