Back to Blog
Lesson 18 of the SEO Foundations: Rank Your First Pages course
SEOJuly 31, 20264 min read

Fixing Basic Technical Issues: 404 Errors and Redirects

Master technical SEO basics by finding and fixing 404 errors, detecting redirect chains, and maintaining a proactive site health checklist.

404 errorsredirectstechnical SEOsite maintenancesite healthSEO courseseosearchorganic-traffic
Close-up of a computer screen displaying an authentication failed message.

Previously in this course, we looked at how to check page speed, mobile responsiveness, and HTTPS security in Essential Site Health Checks: Technical SEO Foundations. In this lesson, we take the next step by finding and fixing 404 errors, untangling redirect chains, and updating your ongoing technical maintenance checklist to keep your project site healthy.

Broken links and tangled redirects act like road closures on your website. When search engine crawlers hit dead ends or bounce endlessly between URLs, they waste crawl budget and lose context on your site architecture. Fixing these basic technical issues ensures that both human visitors and web spiders reach your valuable content without friction.

Finding and Resolving 404 Errors

A 404 error occurs when a user or search engine requests a URL that your server cannot find. While finding a 404 is normal for deleted content, leaving unaddressed 404 errors—especially those receiving incoming links or internal references—frustrates users and leaks link equity.

You can uncover 404 errors using two primary methods:

  1. Google Search Console (GSC): Navigate to the "Pages" report under the Indexing section, then look for URLs marked with the reason "Not found (404)."
  2. Sitemap Crawl Tools: Run a local crawl using tools like Screaming Frog SEO Spider to scan your domain for broken internal links.

Once you have your list of 404 URLs, apply this decision framework:

SituationRecommended Action
Old URL with external links or search trafficImplement a permanent 301 redirect to the most relevant live page.
Outdated URL with zero traffic and no linksLet it return a proper 404 (or 410 Gone status if permanently deleted).
Typo in an internal linkEdit the source page code to point to the correct, existing URL.

Detecting and Fixing Redirect Chains

A road closed by barriers and a traffic sign in Geesthacht, Germany.

Redirects tell browsers and crawlers that a page has moved. A single 301 redirect is completely fine, but problems arise when you chain multiple redirects together (e.g., URL A points to URL B, which points to URL C).

Redirect chains introduce latency, slow down page rendering, and can cause search engine crawlers to stop following the path altogether after a certain number of hops.

How to Detect Redirect Chains

  • Screaming Frog: Run a crawl, select the "Redirects" tab, and filter by "Redirect Chain" to see every multi-hop path on your site.
  • Browser Extensions: Use tools like Redirect Path to inspect individual URLs as you click through your site.

Fixing a Chain

To fix a redirect chain, update the initial source URL (URL A) so that it points directly to the final destination (URL C). Eliminate the intermediate step (URL B) entirely.

[Broken or Old URL A] ---> (Old Redirect) ---> [Intermediate URL B] ---> (Old Redirect) ---> [Final URL C]
                                      │
                                      ▼
                   [Update A to point directly to C]
                                      │
                                      ▼
                        [Clean URL A] ---> [Final URL C]

For deeper server-side routing strategies and complex canonical setups, refer to our guide on Advanced Canonicalization and Redirect Strategies for SEO.

Updating Your Site Health Maintenance Checklist

Technical SEO is not a one-time setup task; it requires routine auditing. As you build out your running project site, incorporate these items into your monthly maintenance checklist:

  1. Check GSC Coverage Weekly: Review the Indexing report for sudden spikes in 404s or server errors (5xx).
  2. Audit Internal Links Monthly: Run a crawler to verify that all internal navigation links return a 200 OK status.
  3. Review Redirect Maps: Ensure newly retired pages are immediately assigned a single 301 redirect to a relevant live equivalent rather than stacking onto legacy rules.

Hands-on Exercise

Log into your Google Search Console or open your preferred crawling tool. Find at least one 404 error and one redirect on your project site. Map out their current state, decide whether to redirect or update the internal link, and execute the fix.

Common Pitfalls

  • Redirecting everything to the homepage: Sending all broken 404 links to your homepage creates "soft 404s," confusing search engines about page intent. Always redirect to a topically relevant page.
  • Using 302 (temporary) redirects for permanent moves: Always use a 301 redirect when a page has moved permanently so that link equity passes correctly.
  • Ignoring internal 404s: Fixing external broken links is important, but leaving broken internal links means you are actively breaking your own site architecture.

Recap

Fixing 404 errors and untangling redirect chains clears out crawl roadblocks, preserves link equity, and keeps your site health score high. By maintaining a regular audit checklist, you ensure your project site remains pristine as it grows.

Up next: Building a Maintenance Workflow.

Similar Posts