How to Fix 404 Errors on Your Business Website

A 404 error means a visitor clicked a link or typed a URL and your server had nothing to show them. Instead of your product page, your pricing table, or your review collection form, they got a dead end. For businesses that depend on their website to generate leads, collect reviews, and build trust, every 404 is a small crack in the foundation.

The fix is usually straightforward once you know where to look. This guide walks through what causes 404 errors, how to find them on your site, and how to fix each type without breaking anything else.

What a 404 Error Actually Means

HTTP status codes are how web servers talk to browsers. A 200 means everything worked. A 301 means the page moved permanently. A 404 means the server understood the request but couldn't find the page.

From a visitor's perspective, they clicked something and hit a wall. From your server's perspective, someone asked for a file that doesn't exist at that address.

This happens more often than most business owners realize. A study by Ahrefs found that 66.5% of links to websites on the internet are completely dead. Your site isn't immune to that trend.

There's also a lesser-known variant called a soft 404. This is when your server returns a 200 status code (technically "success") but the actual page content is empty, broken, or just an error message. Google treats soft 404s as worse than real 404s because they send conflicting signals — the HTTP header says everything is fine while the page tells a different story.

Why 404 Errors Hurt Your Business

A single 404 won't tank your business. But a pattern of them creates real problems across three areas.

Lost Customers

When a potential customer clicks your Google listing, an ad, or a link from another site and lands on a 404, they're gone. They won't hunt for the right page. They'll hit the back button and click on your competitor's link instead. If that dead link was your Google review page or your contact form, you just lost both the lead and the review.

This matters even more for businesses actively working to increase their Google reviews. Every broken page between a customer and your review form is friction that kills conversion rates.

Search Ranking Damage

Google crawls your site regularly. When Googlebot hits repeated 404s, it signals that the site isn't well-maintained. While Google has said that 404s themselves aren't a direct ranking penalty, they do waste your crawl budget. If Googlebot spends half its time hitting dead pages, it has less budget to discover and index the pages that matter for your rankings.

More importantly, external sites that linked to your pages — valuable backlinks that took months or years to earn — are now pointing to nothing. That link equity evaporates with every 404.

For local businesses competing in Google's map pack, this is especially painful. Your Google Business Profile links directly to your website. If those pages return 404s, Google may reduce the confidence score it assigns to your business listing.

Reputation Damage

Your website is part of your brand. A visitor who encounters a dead page forms an instant opinion: this business doesn't keep things up to date. For service businesses where trust is the sale — dentists, lawyers, financial advisors, consultants — a broken website undercuts the credibility you've worked to build through reviews and testimonials.

This perception compounds over time. If a customer hit a 404 on your site last month, they're less likely to trust your review request email when it lands in their inbox next week.

Common Causes of 404 Errors

Before you can fix 404s, you need to understand what creates them. Here are the most common causes.

Changed or Deleted Pages

This is the number one cause. Someone redesigned the site and the old URLs didn't carry over. Maybe you switched from /services/teeth-whitening to /dental-services/whitening without setting up a redirect. The old URL now returns a 404, and every external link pointing to it is broken.

Typos in Internal Links

A developer or content editor typed /about-su instead of /about-us in a navigation menu or blog post. The link looks right at first glance but points to a page that doesn't exist.

Broken External Links

Other websites, directories, and social media profiles link to your site. If those links were entered with a typo, or if you've changed your URL structure since they were published, those inbound visitors hit 404s. You can't control what other sites link to, but you can redirect those URLs to the right destination.

Deleted Products or Services

If you discontinued a product or stopped offering a service and deleted the page without redirecting it, anyone who bookmarked it, shared it, or found it in search results will get a 404.

CMS or Platform Migration

Switching from WordPress to Shopify, or from Squarespace to a custom site, almost always changes URL structures. Without a redirect map, every old URL becomes a 404 overnight.

Review Platform Link Changes

This one catches many business owners off guard. If you've switched review management platforms, your old review collection links, testimonial pages, and widget embed URLs may all go dead. Customers who bookmarked your review page — or businesses that linked to your testimonials — now hit a 404.

Broken Asset and Media URLs

Not all 404 errors involve web pages. Image files, PDFs, video files, and downloadable documents generate 404s when they go missing, and these often do not show up in standard site crawls because most crawlers focus on HTML pages.

This happens most often when you move images from one folder to another without updating every reference to them, when you delete a PDF that is still linked from multiple pages or included in an email campaign, when migrating to a new hosting provider that changes your file upload paths, or when a WordPress media library cleanup removes files that are still referenced in older posts.

Asset 404s matter for two reasons. First, a page with broken images creates a poor experience for visitors who see empty boxes where content should be. Second, if you have linked to a PDF in an email campaign and that PDF returns a 404, every click from that campaign delivers nothing.

Finding asset 404s requires checking your server logs directly rather than relying on crawl tools alone. Most crawlers skip binary files by default. In Google Search Console, asset 404s occasionally appear in the Coverage report but are easy to miss because the filenames end in .pdf, .jpg, .png, or .mp4 rather than a clean URL path.

Filter your server error logs by file extension and set up 301 redirects or restore any files that are still getting active requests. For a quick check on a specific file, the same curl command used for pages works just as well on asset URLs.

How to Find 404 Errors on Your Site

You can't fix what you can't see. Here are four ways to identify 404s.

Google Search Console

Google Search Console is free and shows you exactly which pages Googlebot tried to crawl and got a 404. Log in, go to Pages in the left sidebar, and filter by "Not found (404)." Google also reports soft 404s — pages that return a 200 status code but display error content.

This is the single most important tool because it shows you what Google actually experiences when crawling your site, not what you think it experiences.

Site Crawl Tools

Tools like Screaming Frog, Ahrefs Site Audit, or Sitebulb crawl your entire site the way a search engine would and report every 404 they find. Screaming Frog's free version handles up to 500 URLs, which is enough for most small business sites.

Run a crawl monthly. It takes five minutes to set up and catches problems before they compound.

Server Logs

Your web hosting provider logs every request to your server, including the ones that return 404. If you have access to your server logs (usually through cPanel, Plesk, or your hosting dashboard), filter for 404 status codes to see what visitors and bots are requesting that doesn't exist.

Google Analytics 4

Unlike Google Search Console, GA4 doesn't automatically report 404 errors — you have to configure it. The most reliable method uses a custom event triggered when your 404 page loads.

If your site uses Google Tag Manager, create a new Tag with Trigger type "Page View" and a condition where the page title contains "404" or "Page Not Found." Set the Tag to fire a GA4 event named page_not_found with a parameter capturing the page path ({{Page Path}}). Once it's live, broken URL attempts appear in your GA4 Events report under page_not_found.

If you don't use GTM, add this snippet directly to your 404 page template, after the existing gtag.js script load:

<script>
  window.addEventListener('load', function() {
    gtag('event', 'page_not_found', {
      page_location: window.location.href,
      page_referrer: document.referrer
    });
  });
</script>

After a few days of collection, go to GA4 under Reports > Engagement > Events, filter for page_not_found, and expand the event parameters to see which URLs are generating errors. The referrer data tells you which pages or external sites are sending visitors to broken links — useful for deciding where to focus your redirect work.

Manual Testing

Click through every page on your site. Click every navigation link, every button, every link in your footer. Open your site on your phone. This sounds tedious, and it is, but it catches things automated tools miss — like JavaScript-generated links that don't appear in static crawls.

Prioritizing Your 404 Fix Queue

After an audit, it's common to find dozens — sometimes hundreds — of broken URLs. You don't have to fix them all at once, and they're not equally important. Work through them in this order.

First priority: 404s with inbound backlinks. Use Google Search Console's Links report or a tool like Ahrefs to find which broken URLs have external sites pointing to them. These are your highest-value fixes. Every inbound link pointing at a 404 is wasting link equity that could otherwise pass to your live pages. A single backlink from a relevant directory or industry site can be worth far more than fifty broken pages with no external links.

Second priority: 404s in Search Console's Not Found report. These are URLs Googlebot actively tried to crawl and couldn't reach. Google is spending crawl budget on dead pages instead of your real content. Fixing them keeps your crawl budget focused on pages that matter.

Third priority: broken internal links. A site crawl tool shows you which pages on your own site link to non-existent URLs. These create dead ends for visitors and signal to search engines that your content isn't well maintained.

Last priority: random probe 404s. Some 404s come from bots testing common paths like /admin, /wp-login.php, or /xmlrpc.php. Real users never visit these. Look at the referrer data — if there's no referrer and the path looks like a vulnerability scanner, you can ignore it.

This order means the first ten or twenty redirects you set up likely recover the majority of the value. You can address the rest over time rather than blocking yourself on a list of low-importance fixes.

How to Fix Each Type of 404 Error

Once you've identified your 404s, here's how to handle each one.

Set Up 301 Redirects

A 301 redirect tells browsers and search engines that a page permanently moved to a new address. This is the right fix when the content still exists somewhere on your site, just at a different URL.

If you moved /services/review-management to /features, set up a 301 redirect from the old URL to the new one. Every visitor and every search engine bot that hits the old URL gets sent to the new page automatically. The backlink equity transfers too.

How you set up redirects depends on your platform:

• WordPress: Use the Redirection plugin. Install it, go to Tools > Redirection, and add your old URL and new URL.
• Shopify: Go to Settings > Navigation > URL Redirects and add each redirect.
• Next.js: Add entries to your next.config.js redirects array or your middleware.
• Apache (.htaccess): Add Redirect 301 /old-path /new-path to your .htaccess file.
• Nginx: Add rewrite ^/old-path$ /new-path permanent; to your server block.
• Wix: Go to Settings > SEO > URL Redirect Manager. Add the old URL slug in the "Old URL" field and the destination in "New URL." Wix also supports CSV bulk import for batches of redirects, which is useful after a site restructure.
• Squarespace: Go to Settings > Advanced > URL Mappings. Each mapping uses the format /old-path -> /new-path 301 — one per line, typed directly into the text area. There's no visual form, so double-check your syntax before saving.
• Webflow: In the Webflow Designer, open Project Settings > Hosting > 301 Redirects. Add the old path and new path, then publish your site. Redirects don't take effect until you publish.

WordPress-Specific 404 Issues

WordPress is the most common website platform for small businesses, and it has a few failure modes that produce 404 errors without any obvious cause.

The Permalink Settings Reset

WordPress maps friendly URLs like /services/tax-preparation to their database content using rewrite rules. When WordPress loses those rules after a plugin update, a server migration, or a permissions change, every page on the site except the homepage returns a 404.

The fix takes about ten seconds. Go to Settings > Permalinks in your WordPress admin and click Save Changes without changing any setting. WordPress regenerates its rewrite rules on save. If your site suddenly shows 404s on all pages, try this before investigating anything else.

The .htaccess File Problem

On Apache hosting, WordPress URL rewriting depends on specific rules in the .htaccess file in your site's root directory. If another plugin overwrites that file or a server update resets it, the same mass-404 problem appears.

Access your .htaccess file via FTP or your hosting control panel's file manager. WordPress requires these lines:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$
- [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

If those lines are missing or corrupted, add them back manually, then go to Settings > Permalinks and save to regenerate the rules.

Plugin Conflicts with Redirects

Cache plugins, security plugins, and URL management plugins can interfere with each other's redirect handling. A redirect you set up correctly in a plugin like Redirection may fail silently when your cache plugin is active because the cache is serving a stored version of the old response.

When a redirect you configured does not fire consistently, test it in a private browser window to bypass your local cache. If it works in private mode but not normally, the problem is in your cache configuration. Add the old URL to your cache plugin's exclusion list to prevent it from storing a response for that path.

These three scenarios cover the most common WordPress-specific 404 failures. Once you have ruled them out, the redirect fixes described elsewhere in this guide apply regardless of platform.

Fix Typos in Internal Links

For internal link typos, correct the link at the source. Search your site's code or CMS for the broken URL and update it to the correct one. No redirect needed — just fix the link.

Restore Deleted Content

If you deleted a page that was getting traffic or had inbound links, consider bringing it back. Check the Wayback Machine at archive.org for a cached version of the content if you don't have a backup.

If the content is genuinely outdated and shouldn't come back, redirect the URL to the closest relevant page on your current site.

Build a Useful 404 Page

Even after fixing every known 404, new ones will appear. Visitors will mistype URLs. External sites will link incorrectly. Your 404 page should help visitors find what they're looking for instead of just showing an error message.

What to include on a 404 page that actually helps:

• A plain-language message that the page wasn't found — no error code numbers as the headline, no technical jargon
• A search bar, which is the single highest-value element because it lets visitors self-rescue without guessing where to go
• Links to your three to five most visited pages — check GA4 for which pages actually get traffic before picking
• Your site's standard navigation so visitors can browse to the right section
• A single back-to-homepage link as a last resort, clearly labeled

What to skip:

Don't redirect all 404s to your homepage. Google treats mass homepage redirects from unrelated broken URLs similarly to leaving the 404 in place — there's no content connection between what the visitor wanted and where they land. Don't fill the page with jokes or overly casual copy. A visitor who hit a dead end is already mildly frustrated, and making them read through a pun before they can navigate away just adds friction.

Platform-specific setup:

On WordPress, your theme's 404 template lives in a file called 404.php. If you're using a page builder like Elementor or Divi, you can design the 404 template visually without touching code. Most managed WordPress themes include a default 404 template you can edit directly from the WordPress editor under Appearance > Theme Editor.

On Shopify, the 404.liquid file in your theme's templates directory controls what visitors see when they hit a broken URL. Edit it from your theme editor under Online Store > Themes > Edit Code. Shopify's 404 page has full access to your theme's standard sections, so you can add a featured collection, the main navigation, or a working search bar using built-in Liquid components.

On Squarespace, go to Pages > Not Linked and look for a page labeled "404 Error Page." Click into it and edit it like any other page. Add a search block, a summary block pointing to your most popular content, and a button linking back to your homepage.

Tracking 404 visits in Google Analytics:

Knowing how often visitors hit your 404 page — and which pages sent them there — tells you whether new broken links are appearing faster than you're catching them. In GA4, your 404 page already shows up in the Pages and Screens report if it has a consistent URL path like /404 or /not-found. Create a custom exploration filtered to that page path and sort by sessions over a 90-day window. If 404 page visits are rising month over month, new broken links are appearing faster than you're fixing them. The referrer dimension shows which pages are sending visitors to dead ends, which is exactly where to look for your next batch of internal link typos.

Skip the jokes. A visitor who just hit a dead end doesn't want to read a clever pun. They want to get where they were going.

Handling Bulk 404 Errors After a Site Migration

A site migration — moving from one domain to another, switching CMS platforms, or restructuring URLs during a redesign — is the fastest way to generate hundreds of 404 errors at once. Instead of one broken page at a time, you have an entire architecture that no longer matches what search engines and visitors have stored. The process for handling bulk 404s after a migration is different from fixing individual errors.

Build a URL mapping before you migrate

The most important step happens before the migration, not after. Export a full list of every URL on your current site — either from your CMS, an XML sitemap, or a crawl tool like Screaming Frog. This becomes your migration mapping sheet. For each old URL, you decide: does it redirect to an equivalent page on the new site, does it consolidate into a nearby page, or is it retired with no equivalent?

If you're moving a fifty-page site, this takes an afternoon. If you're moving a five-hundred-page e-commerce store, it takes a week. But having the mapping done before go-live means every redirect is in place the moment traffic starts hitting the new site, rather than playing catch-up while customers hit dead ends.

Set up redirects in bulk instead of one at a time

Most platforms let you import redirects from a CSV file rather than entering each one manually.

WordPress with Redirection plugin: Export your mapping to a CSV with columns for "Source URL" and "Target URL." In the Redirection plugin, go to Tools > Import/Export, choose your file, and import. This handles hundreds of redirects at once without manually adding each row.

Shopify: Go to Settings > Navigation > URL Redirects, click "Import," and upload a CSV with the columns "Redirect from" and "Redirect to." Shopify's limit is 1,000 redirects per import file, so split larger files into batches.

Squarespace: Squarespace doesn't support bulk CSV import for redirects. You'll need to enter each URL mapping individually under Settings > Advanced > URL Mappings. For large migrations, this is the main argument for handling redirects at the server level (through your CDN or host) rather than inside Squarespace.

Webflow: Webflow also handles redirects one at a time in Project Settings. For large-scale migrations off Webflow, consider handling the redirect layer through Cloudflare or your hosting provider for bulk imports.

At the server/CDN level: If you have access to Nginx, Apache, or Cloudflare's redirect rules, you can manage bulk redirects outside any CMS. This is faster, adds no plugin dependency, and handles every request before it even reaches your application. For Cloudflare, use Bulk Redirects under the dashboard's Rules section.

Prioritize which 404s to fix first after migration

After a migration, GSC typically flags dozens to hundreds of 404 errors within the first week as crawlers re-index the new site structure. Trying to fix everything at once is inefficient. Prioritize in this order:

Pages with existing backlinks — check the Links report in GSC for external sites pointing to the old URLs. These carry link equity you're actively losing. A broken URL with five inbound backlinks is worth far more attention than a page that was only crawled internally.

High-traffic pages — check GA4 or your analytics to see which old URLs were receiving regular visitors before the migration. These represent real user journeys being interrupted.

Review and contact pages — any URL that appeared in your outgoing review requests, email campaigns, QR codes, or printed materials. These are time-sensitive: a customer who got a broken review link won't come back and try again.

Category and navigation pages — these link to many other pages, so a broken navigation URL cascades into lost access to multiple content areas.

Everything else — low-traffic, orphaned, or purely duplicate pages — can be left as clean 404s or pointed to a broadly relevant page.

Use crawl tools to verify coverage after the redirect deployment

Once your redirects are in place, re-crawl your old URL list with a tool like Screaming Frog or Ahrefs to confirm that every redirect resolves as a 301 (not 302) and reaches the intended destination URL with a 200 status code. Spot-check ten to twenty redirects manually — run the curl test covered below — to catch any configuration issues before assuming the bulk import worked correctly.

After the crawl confirms the redirects are working, submit your new sitemap to Google Search Console and use the URL Inspection tool on a sample of your most important migrated pages to request re-indexing. GSC will continue showing the old 404s for some time while crawlers work through the list — that's normal. The "Validate Fix" button on the 404 report in GSC can speed the process up for specific URLs.

Preventing Future 404 Errors

Fixing existing 404s is half the battle. Preventing new ones is the other half.

Create a Redirect Map During Site Changes

Before any site migration, redesign, or URL structure change, export a complete list of your current URLs. Map each one to its new equivalent. Implement all redirects before the new site goes live, not after.

Keep a URL Change Log

Anytime you change a URL on your site, log it. Note the old URL, the new URL, and the date. This makes troubleshooting much easier six months later when someone reports a broken link.

Monitor Search Console Monthly

Set a calendar reminder to check Google Search Console's coverage report once a month. New 404s will appear — that's normal. Catching them within a week or two limits the damage.

Audit External Links

Use Ahrefs, Moz, or Google Search Console's Links report to see which external sites link to you and what URLs they're linking to. If you spot links pointing to pages you've moved, set up redirects for those specific URLs.

Don't Delete Pages Without a Plan

Before removing any page from your site, check its traffic in Google Analytics, its backlink profile in Search Console, and whether any internal pages link to it. If it has traffic or links, redirect it. If it has neither, you can safely remove it.

Protect Your Review and Reputation Pages

Your review collection pages, testimonial displays, and social proof sections are some of the most-linked assets on your site. Other businesses, directories, and happy customers often link directly to them. Before touching any URL that involves reviews, testimonials, or reputation content, check its inbound links first. These pages tend to accumulate more external links than the average blog post, so a broken URL here causes disproportionate damage.

Real-World Scenario: The Review Link That Quietly Died

Here's what this looks like in practice. A dental office sends 200 review request emails per month using an automated sequence. Each email contains a direct link to their Google review page on their website — something like yourdentist.com/leave-a-review.

During a routine WordPress update, the plugin that handles the review redirect breaks. The page starts returning a 404 instead of forwarding to Google.

For three weeks, those 200 monthly emails land customers on a broken page. The office loses roughly 30-40 reviews they would have received (assuming a typical 15-20% conversion rate on review requests). They don't notice because the emails themselves still send fine. The automation looks healthy. The pipeline quietly bleeds.

When they finally catch it — usually because someone mentions it in person — they've lost a month of social proof they can't get back. Those customers won't click the link a second time.

The fix takes five minutes. The damage took three weeks to accumulate.

How to Prevent This Specific Failure

Set up a simple uptime check on every URL you send in automated emails or print on physical materials. Free tools like UptimeRobot or Better Uptime will ping a URL every five minutes and alert you the moment it stops returning a 200 status. For your most important review collection URLs, this one check prevents the entire failure mode described above.

How 404 Errors Affect Your Review Pages

For businesses using online reviews to build trust and attract customers, 404 errors on review-related pages are especially damaging.

If your Google review link sends customers to a 404, they won't leave a review. Period. They tried, they hit a wall, and they moved on. You don't just lose one review — you lose the social proof that review would have generated for every future visitor. If you've invested time setting up a QR code that points to a review page and that page breaks, every printed sign, receipt insert, and table tent in your location is now useless until you fix it.

Similarly, if your testimonial page, case studies, or review collection widget lives at a URL that returns a 404, all the trust signals you've built are invisible. Internal links pointing to those pages from your blog or service pages lead nowhere.

There's a subtler problem too. If you're using review management software that sends automated review requests via email or SMS, those messages contain links back to your site. A 404 on the landing page means your entire automated review pipeline is broken — and you might not notice for weeks because the requests are still going out. The emails look fine. The links just don't work.

Praising's review management platform helps prevent this by giving you stable, permanent links for review collection that don't change when you redesign your site. The review widget embeds directly on your pages rather than relying on a separate URL that could break during a migration.

Advanced: Handling 404s for Multi-Location Businesses

If you operate multiple locations, 404 errors multiply in complexity. Each location may have its own page, its own review links, and its own Google Business Profile pointing to location-specific URLs.

A common scenario: you consolidate your website from /locations/downtown-office and /locations/westside-clinic into a single /locations page during a redesign. Both old URLs now return 404. Every location-specific backlink — from local directories, newspaper features, and the Google Business Profiles themselves — is broken.

The fix for multi-location businesses requires a redirect for every old location URL, not just the main ones. Build a spreadsheet mapping every old location-specific URL to its new equivalent before making any structural changes. If you're merging pages, redirect each old URL to the combined page. If you're removing a location entirely, redirect to the nearest remaining location or your main locations index.

This is also where having a reputation monitoring tool pays for itself. Automated monitoring catches broken links across all your locations before they compound into a multi-week SEO problem you only discover when rankings drop.

Quick Reference: 404 Fix Checklist

1. Run a Google Search Console check for 404s under the Pages report
2. Run a crawl with Screaming Frog or Ahrefs Site Audit
3. Categorize each 404: moved page, deleted page, typo, or external link
4. Set up 301 redirects for moved and deleted pages
5. Fix typos in internal links at the source
6. Audit your review collection links and Google review link to confirm they still resolve
7. Build a helpful 404 page with search and navigation
8. Create a redirect map before your next site change
9. Check Search Console monthly for new 404s

Frequently Asked Questions

What is a 404 error and why does it happen on my business website?

A 404 error means a visitor tried to reach a page on your site that doesn't exist at that URL. The most common causes are pages that were moved or deleted without a redirect, typos in links, and URL changes from a site redesign or platform migration. Every website gets 404 errors eventually. The problem isn't that they happen — it's leaving them unfixed. Each broken page is a missed customer interaction, a wasted backlink, and a signal to search engines that your site isn't well-maintained.

How do 404 errors affect my Google search rankings?

Google has said that 404 errors aren't a direct ranking penalty. However, they do waste your crawl budget — the number of pages Google will crawl on your site in a given period. If a significant portion of your URLs return 404, Googlebot spends time on dead pages instead of indexing the ones that matter. More damaging is the loss of backlink equity. When an external site links to a page that returns 404, the ranking value of that link is lost. Setting up a 301 redirect preserves most of that equity and passes it to the new destination page.

What is the difference between a 404 error and a soft 404?

A standard 404 returns an HTTP 404 status code, telling browsers and search engines the page doesn't exist. A soft 404 returns a 200 status code (which means "success") but the actual page content is an error message or a mostly empty page. Google treats soft 404s as a bigger problem because they send mixed signals. The status code says the page is fine, but the content says otherwise. Check for soft 404s in Google Search Console under the Pages report. Fix them by either restoring real content to the URL or returning a proper 404 status code.

How often should I check my business website for 404 errors?

Monthly is a good baseline for most business websites. Check Google Search Console's Pages report and run a site crawl tool like Screaming Frog. If you're making frequent changes to your site — adding pages, updating URLs, publishing blog posts — check every two weeks. After a major site redesign or platform migration, check daily for the first week and weekly for the first month. New 404s surface quickly when crawlers re-index your changed site structure.

Can I just delete a page without creating a redirect?

You can, but you should only do it if the page has zero traffic and zero backlinks. Check Google Analytics for the page's traffic over the past 12 months, check Google Search Console's Links report for external sites linking to it, and check your internal links to make sure no other page on your site points to it. If the page has any traffic, backlinks, or internal links, set up a 301 redirect to the most relevant existing page on your site. The redirect preserves the link equity and sends visitors somewhere useful instead of a dead end.

How do 404 errors on review pages affect my reputation?

Broken review pages are uniquely damaging because they disrupt a time-sensitive action. When a customer finishes a great experience and taps your review link — whether from an email, a QR code, or a text message — they're motivated right now. A 404 kills that motivation instantly, and you almost never get a second chance. Unlike a broken product page where the customer might search for the product elsewhere on your site, a broken review page means the review simply doesn't happen. Over weeks and months, this invisible leakage can mean dozens of lost reviews that would have bolstered your online reputation and local search rankings.

What is the difference between a 301 and 302 redirect?

A 301 redirect means the move is permanent. A 302 redirect means the move is temporary. The practical difference: with a 301, search engines transfer link equity from the old URL to the new one and update their index to use the new address. With a 302, they keep indexing the old URL and don't transfer equity, expecting the original to return.

For fixing 404 errors on a business site, use 301 redirects in almost every case. A 302 is only appropriate when you've temporarily taken a page down — for a seasonal campaign or an A/B test — and you're certain the original URL will come back. When in doubt, 301 is the right choice.

Is it better to redirect a 404 to my homepage or to a relevant page?

Always redirect to the most relevant page you have. Redirecting all 404s to your homepage is a recognized problem — Google treats homepage redirects from unrelated URLs similarly to leaving the 404 in place, because there's no content relationship between the broken URL and the destination.

More practically, it doesn't help visitors. Someone who followed a link to your old pricing page doesn't benefit from landing on your homepage. They benefit from landing on your current pricing page, or the closest equivalent.

If you genuinely have no relevant destination for a particular broken URL, a clean 404 page with clear navigation to your main sections is more honest than a homepage redirect that doesn't answer the visitor's question.

Auditing Your Review Request Pipeline for Broken Links

Fixing 404s on your general website pages is one thing. Protecting the specific links that feed your review collection pipeline is a separate task — and one most businesses skip entirely.

Your review request pipeline includes every URL in your outgoing emails, text messages, QR codes, and printed materials. Each one is a potential failure point. Unlike a broken product page, a broken review link doesn't just lose a visitor. It loses the review, the social proof that review would have generated, and often the customer's motivation to try again.

Here's a simple audit that takes about twenty minutes.

Start with your email templates. Open each active review request email and click every link in it. Don't stop at the main review link — test the unsubscribe link, the business logo link, any "view in browser" option, and social media icons. Any of these returning a 404 creates a broken experience even when the core review link is intact.

Test every QR code you have in circulation. Scan each code on printed materials, table tents, receipts, and display stands. If the QR code redirects through your website to a review platform, trace the full redirect chain and confirm it resolves correctly. A QR code that printed fine six months ago may point to a URL that no longer exists — you won't know until someone scans it and gets nothing.

Check your Google Business Profile. Log into your GBP dashboard and click the website URL you've listed. Then use the "Share review form" option and actually test the generated URL in a private browser window. Getting your customers to share your Google review link effectively starts with making sure that link actually goes somewhere when they click it.

Verify your review widget embed. If you display customer reviews on your site using a widget or embed code, confirm it's loading correctly and the data source still returns results. A broken widget goes silent rather than throwing an error — the social proof disappears without any visible sign that something went wrong.

Check your automated review request sequences. Look at your active automation settings and manually click the links in a test send. Automated sequences are exactly the failure mode in the scenario above — they run perfectly while delivering customers to broken pages, because the automation itself is healthy even when the destination is broken. Part of mastering Google review management is confirming that every link in your outreach chain resolves correctly before it goes to real customers.

Set a calendar reminder to repeat this audit monthly. It takes fifteen minutes once you have a checklist. And unlike most monthly maintenance tasks, this one has a clear payoff: every broken link you catch before a customer hits it is a review you don't lose.

Why Google Search Console Still Shows 404 Errors After You Fixed Them

You fixed the broken URL. You set up the redirect. You refreshed the page and it works. But Google Search Console still shows that URL as a 404 in the Coverage or Page Indexing report. This is one of the most frustrating parts of 404 error management, and it's very common.

The reason is simple: Google does not re-check every URL the moment you make a change. It crawls URLs on its own schedule, which can be anywhere from a few days to several weeks depending on how frequently your site is crawled. When you fixed the 404, Google had no way of knowing until one of its crawlers happened to revisit that URL.

How to speed up the process

The URL Inspection tool in Google Search Console is the fastest way to tell Google a URL has changed. Open GSC, paste the old (previously broken) URL into the search bar, and click "Test Live URL." This forces Google to fetch it right now. If the URL now redirects or returns 200, you'll see it immediately in the inspection results.

After confirming the live URL is healthy, click "Request Indexing." This queues the URL for a fresh crawl ahead of the normal schedule. It doesn't guarantee instant removal from the 404 report, but it typically moves things along within a few days.

Using "Validate Fix" in the coverage report

If the 404 appeared in GSC's Page Indexing report under the "Not found (404)" category, there's a second step worth taking. Click into that section, select the affected URL, and look for the "Validate Fix" button. Clicking it tells Google you believe the issue is resolved and asks it to re-evaluate those specific URLs.

GSC will show a "Validation in progress" status while it works through the list. Once it confirms the URL no longer returns a 404, it will move out of the error category. This process typically takes a few days to a few weeks depending on crawl frequency.

What if the 404 keeps coming back?

If a URL keeps reappearing in GSC's 404 report even after you've fixed it, check two things. First, confirm the redirect is set up correctly on the server side, not just in a plugin or CMS setting that might be inconsistent. Run a curl test (covered below) to verify the server itself is returning the redirect. Second, check whether the URL appears in any XML sitemaps. If an old, broken URL is still listed in a sitemap, Google will keep trying to crawl it and keep recording the 404 in reports.

---

How to Confirm a 301 Redirect Actually Worked

Setting up a 301 redirect in your CMS, .htaccess file, or server config does not always mean it's working correctly. Caching, configuration errors, and plugin conflicts can silently prevent a redirect from firing. Before assuming a redirect is working, run a quick server-level test.

The curl method

The most reliable way to test a redirect is with curl from a terminal:

curl -sI https://example.com/old-page | head -5

This sends a request and returns just the response headers without downloading the page content. Look for two things in the output:

1. The first line should show HTTP/1.1 301 Moved Permanently (or HTTP/2 301)
2. There should be a Location: header pointing to the destination URL

If the first line shows 200 OK instead of 301, the redirect is not configured. If it shows 302 Found, it's a temporary redirect rather than a permanent one, which means Google won't pass full link equity to the destination.

To follow the redirect chain all the way to the final URL, add the -L flag:

curl -sIL https://example.com/old-page | grep -E "^HTTP|^Location"

This shows the status code at every hop. What you want to see is a single 301 followed by a final 200. If you see multiple redirects in a chain (301 to 302 to 200, for example), that's a redirect chain, which adds latency and can dilute the link value passed to the final URL.

Testing in a browser

Chrome's DevTools give a visual way to check the same thing. Open DevTools (F12), click the Network tab, and check "Preserve log." Then navigate to the old URL. You'll see each request in the list. If the redirect is working, you'll see the old URL show a 301 status with a Location header pointing to the new URL, followed by a 200 request for the destination page.

If you only see a single 200 request for the destination URL without the 301 entry, it may mean a browser or intermediary cache already resolved the redirect before the request hit the server. Test in a private/incognito window to avoid cached results.

Validating from Google Search Console

After setting up a redirect and verifying it with curl or DevTools, the URL Inspection tool in GSC gives one more confirmation from Google's perspective. Paste the old URL, click "Test Live URL," and GSC will show you what Google sees when it crawls that URL right now. If the redirect is working, you'll see the destination URL listed under "Redirect" in the inspection results.

This is worth checking because some server configurations redirect browsers correctly but don't redirect Googlebot correctly, particularly when server rules apply different logic based on the User-Agent header. The "Test Live URL" function simulates Googlebot, so it catches this class of problem that curl and browser testing miss.

Once you've confirmed the redirect returns a 301, Google discovers it via the URL Inspection request, and the old URL stops appearing in GSC as a 404, the fix is complete.

404 vs 410: When to Use a "Gone" Status Code

Most discussions of 404 errors treat them as the default response for any missing page. That is mostly correct — but there is a second status code worth knowing when you are cleaning up permanently deleted content: the 410 Gone.

A 404 tells Google "this page doesn't exist right now," which could mean the page was moved, deleted, or temporarily unavailable. Google will continue recrawling the URL periodically in case the content comes back. A 410 tells Google "this page has been intentionally and permanently removed, and it is not coming back." Google typically deindexes a 410 URL within a few days versus the one to four weeks a 404 often requires.

When 410 Is the Right Choice

Use 410 when a page is genuinely gone and will never return:

• A discontinued product or service you are permanently removing from your catalog
• A time-limited promotion page that has expired and will not be repeated
• A review collection link tied to a platform you have stopped using entirely
• A blog post that contained inaccurate information you have taken down for accuracy reasons
• A staff member profile page after they have left the company

Do not use 410 for a page you might restore later, or for a page you are moving to a new URL. Use a 301 redirect for that case.

How 410 Affects Crawl Budget

Google allocates a finite amount of crawl capacity to your site each week. Pages that return 410 are marked as permanently removed and dropped from the crawl queue much faster than 404s, which Google continues to probe periodically in case the content reappears. For sites with large volumes of expired content — e-commerce stores that regularly discontinue products, or businesses that run seasonal campaigns — switching from 404 to 410 on truly dead URLs reduces wasted crawl capacity and can help newer, higher-value pages get discovered faster.

How to Return 410 on Different Platforms

Returning 410 requires telling your server or CMS to send a different HTTP status code than the default missing-page response.

WordPress (Redirection plugin): Go to Add Redirect, enter the old URL in "Source URL," set the HTTP Code dropdown to 410, and leave the Target URL blank. The plugin returns a 410 response without redirecting the visitor anywhere.

Apache (.htaccess): Add this block to your configuration, replacing /old-page with the specific path:

<Location /old-page>
  Redirect 410
</Location>

Nginx: Add to your server block:

location /old-page {
  return 410;
}

Shopify: Shopify does not natively support 410 responses — the admin interface only creates 301 redirects. Leaving Shopify's built-in 404 for discontinued products is acceptable, since the practical difference is small for most product catalogs.

Next.js (App Router): Return new Response(null, { status: 410 }) from a route handler. In the Pages Router, use res.status(410).end() in an API route or pass notFound: true via getStaticProps for a page that should never be regenerated.

When to Stick With 404

If you are unsure whether a page will return, leave it as a 404. The practical difference in how Google handles 404 vs 410 is real but rarely significant enough to justify configuration overhead unless you are managing large volumes of dead URLs — hundreds or thousands — where crawl budget genuinely matters. For most small business websites with a handful of deleted pages, a 301 redirect for any page that has backlinks or existing traffic, and a plain 404 for everything else, is the right approach.

Quick-Fix Reference: 404 Error Types and Solutions

Running a 404 audit often surfaces several distinct types of broken URLs at once. Use this table to quickly categorize what you're dealing with and choose the right fix without overthinking it.

Most fixes land in one of two buckets: fix the source (for typos and links you control) or set up a 301 redirect (for everything else). The redirect is almost always the right call when you don't control where the original link lives.

---

For related reading, see our guides on how to get a Google review link, Google Business Profile setup, review management tools, and how to monitor your online reputation.