50 articles
A 301 tells Google the new URL should be canonical; a 302 asks Google to keep showing the old one. How to choose, which server and CMS defaults send 302s by accident, and how to confirm the move in Search Console.
Trace server errors from Search Console to the failing layer. Use Crawl Stats request times, incident templates, and checks for robots.txt, maintenance, and stable recovery.
A blocked page can still appear in Google. Decide when to leave it alone, unblock it, remove it with noindex, or consolidate a duplicate, then verify the change in Search Console.
Find what refused crawler access, choose the right server or security-rule fix, and verify public pages while keeping private content restricted.
Decide which 4xx responses need action, find the code Google received, and validate repaired public pages while leaving expected endpoint errors alone.
Copy Google Search Console regex patterns for questions, brand terms, and page groups. Check false positives, use the right filter logic, and keep long-query analysis separate from AI visibility.
Choose the right response for a soft 404: remove, redirect, restore content, or use noindex. Then confirm the fix in the current Search Console report.
Decide which uncrawled pages need attention, separate crawl capacity from demand, and verify your fixes. Includes a diagnosis worksheet and developer ticket.
Most crawled - currently not indexed URLs don't need fixing. Use the sitemap filter to find the ones that do, rule out look-alike statuses, and fix the real cause on Google's own timelines.
Check which canonical Google selected before fixing duplicates. Use a decision table, pattern worksheet, and validation checklist to prioritize the pages that matter.
Decide when an alternate URL can stay excluded and when its canonical needs a fix. Use a status comparison, inspection worksheet, facet policy, and developer ticket to guide the change.
