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.

To fix a 404 error on a business website: Open Google Search Console, go to Pages → Not found (404), and download the list of broken URLs. For each one, create a 301 redirect pointing the dead URL to the closest live page. If the broken URL appeared in a review request email or QR code, update that source too — the redirect stops new visitors from hitting a wall, but the original broken link keeps circulating until you change it. Most fixes on small business sites take under five minutes once you have the broken URL list.

How to Fix 404 Errors: Quick Overview

Every 404 fix follows the same five steps, regardless of which platform or CMS your site runs on:

1. Find broken URLs — Log into Google Search Console and go to Pages → Not found (404). This shows the URLs Googlebot couldn't load. For broken internal links that real visitors hit before Googlebot caught them, run Screaming Frog's free version against your domain.

2. Prioritize by impact — Fix review links, booking pages, and contact forms first. A broken link in your review request email kills every conversion in that 48-hour post-visit window. Old blog posts and archived pages can wait.

3. Set up 301 redirects — Point each broken URL to the closest matching live page. Use the specific destination page, not your homepage. Google treats generic homepage redirects from unrelated content as invalid and won't pass any ranking value through them.

4. Update internal links — Search your CMS for any references to the old URL and update them. Redirects catch the incoming traffic; updating the link source prevents the same break from sending future visitors to the redirect chain indefinitely.

5. Test, then schedule a monthly check — Verify each redirect with curl -sIL <old-url> and confirm the response chain shows a 301 followed by a 200. Set a monthly calendar reminder to re-run the Google Search Console check and catch new breaks before they compound.

The rest of this guide goes deeper on each step, with platform-specific instructions for WordPress, Shopify, Wix, Squarespace, Webflow, Apache, and Nginx.

The 404 Errors That Hurt Local Businesses Most

Not every broken page costs the same. A 404 on a retired blog post from two years ago barely registers — Googlebot notes it, nobody else does. A 404 on your review collection link is a different problem: it cuts off customers at the exact moment they're ready to help you.

Here's how broken pages actually rank by business damage:

1. Review request links. The link you paste into every post-visit email or hand to customers at checkout. When it breaks, every customer who clicks it during the 24-72 hours after a job — the window when they're most willing to write a review — hits a dead end. They don't hunt for an alternative. They close the tab. A link that quietly breaks and stays broken for a month can wipe out 15-30 reviews for a service business that sends 50 request emails a week. You won't see it coming because open rates look normal and nobody sends a complaint about a 404 they got while trying to do you a favor.

2. Your Google Business Profile website link. If your GBP listing points to a page that returns 404, Google sees a business pointing people to nothing. That matters for your local pack ranking — Google's systems infer business health partly from whether the signals in your profile (website, phone, address) actually resolve to real destinations.

3. QR codes at your location. A printed QR code scans perfectly whether or not the URL behind it works. The customer scans it, sees an error, and assumes something is wrong with your business — not with a URL they never saw. Unlike a broken email link, you can't swap a static QR code without reprinting it.

4. Booking pages and contact forms. A broken appointment page loses you a job. At least customers can call or Google you for an alternative way in. A broken review link has no fallback — there's no other route to leaving you a Google review, and most people won't look for one.

5. Old citation links. Local directories, chambers of commerce, and industry association sites link directly to specific pages on your site. If those pages moved without redirects, that inbound link equity evaporates and any customer who follows the link gets an error.

--- The reason this ordering matters: most 404 fixes start with the Search Console report, which lists pages Googlebot couldn't crawl. Googlebot never crawls your review request email or the QR code at your register. By the time a broken review link shows up anywhere you can see it, it's been leaking customers for weeks.

If you manage your reviews through a platform like Praising.ai, broken review links surface faster because the tool watches your review collection rate, not just your sitemap. A sudden drop in completed reviews is a signal that something in the funnel broke — even when all your pages technically return 200.

---

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.

When the Broken Page Is Your Review Link

Not every 404 costs the same. A broken archive page from 2021 that gets no traffic is a nuisance. A broken review request link is a revenue problem — and a reputation problem.

Here's the dynamic: when a customer just finished an appointment, wrapped up a service call, or checked out of your shop, they're at peak willingness to help you. That's exactly when most businesses send a review request — by email, text, or a QR code at the register. If that link returns a 404, the customer runs into a wall at the worst possible moment. They don't hunt for another way to leave you a review. They close the tab.

The damage usually stays invisible for weeks. Your review request emails keep going out. Open rates look normal. But responses stop. Nobody files an error report on a 404 they hit while trying to do you a favor. They just leave. You'd typically find out when someone mentions it in passing, or when you notice your review count hasn't moved in a month.

The Review Links Most Likely to Break

Your Google Business Profile review link. The short URL in your GBP dashboard — the one you paste into email templates and print on business cards — is a redirect that Google manages. Its format has changed at least twice in the past few years. A link generated in 2022 or 2023 may still work today, or it may silently fail for some users depending on their location and device. Test it from an incognito browser every few months; don't assume it's fine because you set it once.

Your review platform's hosted landing page. If you use a tool that gives you a custom landing page for review collection (something like yourdomain.com/reviews or a branded short URL), that page can break when:

• Your subscription lapses or you change plans
• The platform updates how it routes URLs
• You rename the campaign or change the landing page slug
• You migrate to a different tool and forget to redirect the old URL

A platform migration is especially dangerous here. The old URL stays in circulation — in emails you sent months ago, in printed QR codes, in your GBP listing — long after the page itself is gone.

QR codes at your location. A QR code is just a URL encoded in a square. If the URL behind it stops working, the code still scans perfectly — it just takes customers to a 404 page. Since most businesses print QR codes once and never update them, any URL change silently breaks every QR code you have displayed until you reprint them.

How to Check Your Review Links Without Search Console

Google Search Console catches broken pages that Googlebot crawled. It won't catch a review request link that customers click directly from their email inbox. For those, you need to test manually:

1. Your GBP review link. Copy the URL from your Google Business Profile dashboard, paste it in a private/incognito browser window, and confirm you land on Google's review form — not an error page.

2. Your platform landing page. Visit the URL from outside your home or office network (use your phone's cellular connection), so you're not hitting a cached version.

3. Your email templates. Open the last review request you sent yourself as a real recipient. Click every link, including secondary CTAs. Confirm each one loads the right page.

4. Your QR codes. Scan the physical QR codes posted at your location using your phone's camera. A ten-second test catches months of silent failure before it compounds.

When you find a broken review link, the fix is the same as any other 404: create a 301 redirect from the broken URL to the working one, and update every place you've hardcoded the old link — email sequences, automation triggers, printed materials. The redirect protects customers who click old links; updating the source stops new links from pointing to the wrong place.

The Complete Review Link Audit: A Step-by-Step Checklist

Most 404 audits focus on website pages. The harder-to-catch breaks live in your review collection funnel — the links you send to customers, the QR codes on your counter, and the URLs embedded in your automation sequences. These don't show up in standard crawls because they're not part of your website's internal link structure. Google never follows them. Screaming Frog never finds them. They only break when a real customer tries to use them.

This checklist runs through every surface where a broken review link can hide.

Step 1: Test Your Google Business Profile Review Link

Open your Google Business Profile dashboard and find your short review link — it usually looks like g.page/r/your-business-name/review or starts with maps.google.com. Copy it.

Open a private browsing window (Chrome's incognito mode, Firefox's private window, or Safari's private browsing). Paste the link and go. Don't test from a regular browser where you're signed into Google — you need to see what a new customer sees.

The link should land directly on Google's review form with your business already selected. If it redirects to a general map page, shows a Google search, or returns any kind of error, the link needs to be regenerated from your GBP dashboard.

Google has changed the format of short review links at least twice in recent years. A link you generated in 2022 may produce different behavior than one created today. Regenerate your link every six to twelve months even if you think it's working, then replace it everywhere you've used the old format.

Step 2: Audit Your Email Templates

Collect every email template your business sends that contains a review link. This includes your main review request email, follow-up sequences (day 3, day 7, day 30 reminders), automated post-purchase emails from your e-commerce platform, thank-you emails from your booking system, and any survey follow-ups that include a review ask at the end.

Open each template and click every link. Don't copy the URL and paste it — actually click as a real customer would, because link-tracking redirects sometimes break separately from the underlying destination.

For each link, record where it goes, what HTTP status it returns, and whether it lands on the correct destination. Use Chrome's developer tools → Network tab to see the actual status code. A link that redirects through multiple steps before reaching the destination is a red flag even if it ultimately works — broken redirect chains are common after platform changes, and each hop adds latency that discourages click-through.

Step 3: Test Every QR Code at Your Location

Pull out your phone and scan each physical QR code displayed at your business. Test the QR code at your front desk or register, any codes on receipts or packaging, QR codes on table cards or menus, and codes on business cards or flyers.

For each one, record the URL it encodes (most phones show it before you open the link), the destination you land on, and whether the destination is the correct review platform.

If any QR code leads to a 404, you have two options. If the QR code generator you used supports dynamic codes — where you can change the destination URL without reprinting — update the destination URL through the generator's dashboard. If you used a static QR code that encodes the URL directly, you need to reprint.

Going forward, use a QR code generator that supports dynamic, editable destinations. The minor monthly cost is worth it for the ability to update destination URLs without reprinting every card and sign.

Step 4: Check Your Printed Materials

Printed materials stay in circulation for months or years after you've updated your digital assets. Business cards, receipt footers, in-store signage, product inserts, and menus can all carry review links that went dead when you changed platforms.

For each printed piece, note the URL it contains. Then visit that URL — not the one you think is printed there, the one that's actually on the page. Type it in manually, exactly as a customer would. A 404 there means every customer who reads that piece and tries to act on it hits a dead end.

If a printed piece is still in active use and contains a broken link, create a 301 redirect from the broken URL to the correct destination right away. That protects anyone who types the old URL into a browser. Then schedule a reprint within 30 days.

Step 5: Check Your Social Media Profiles

Visit each of your social media profiles and click the review link in your bio or pinned post. On Instagram, this means testing the single clickable link in your bio. On Facebook, click the "Write a review" button destination. On Google Business Profile, test the review shortcut separately from the link you share manually. If you use a link-in-bio service like Linktree or Later, click through every individual link in your page.

Social media links get set once and forgotten. If you've changed your review platform, changed your business name, or updated your Google Business Profile since you last set these links, they may be pointing to a 404 that none of your followers have mentioned because they assumed the link was fine.

Step 6: Audit Automation and CRM Sequences

If you use a CRM, email automation platform, or reputation management tool that sends review requests automatically, log in and audit every template and sequence that contains a review link.

The problem with automation is that it runs without anyone watching. A link can break and silently stop working for months while the sequence keeps firing. You only notice when someone mentions they couldn't leave a review, or when your review count stops growing despite healthy request volumes.

For each automation template: open it in edit mode, find every URL in the message body, footer, and CTA buttons, then manually visit each URL and confirm the correct HTTP status and destination.

If you use a review management platform that handles request delivery, it may have built-in link health monitoring. Check your settings or dashboard for any broken link alerts or delivery failure reports — the best tools catch broken review links before they silently kill your collection rate.

Step 7: Set a Monitoring Schedule

One-time audits catch existing problems. A recurring schedule catches new ones before they compound.

Monthly: Run Google Search Console's Pages report (Not found 404). This shows every URL Google found broken since your last check. Also test your main Google review link from an incognito window — it's your most important asset, and a manual check takes thirty seconds.

Quarterly: Run through the full checklist above. Quarterly checks catch problems in printed materials, automations, and social profiles that monthly checks miss because those surfaces change less often.

After every platform change: Migrate from one review tool to another, redesign your website, change your GBP settings, or update your email sequences? Run the full checklist the day after the change. Platform migrations are the single biggest source of sudden 404 spikes in review collection funnels.

What to Do When You Find a Broken Review Link

The fix depends on where the link lives. For an email template, update the URL immediately — if you use a link tracker or URL shortener, update the destination at the shortener level so all past emails auto-update. For a QR code, update the destination in your generator's dashboard if it's dynamic; schedule a reprint and add a 301 redirect if it's static. For social media, update the link directly on the platform. For printed materials, add a 301 redirect from the broken URL and schedule reprinting within 30 days. For an automation sequence, update the template URL and check whether any queued messages can also be updated.

The principle throughout: fix the source AND add a redirect. The redirect protects current traffic. Fixing the source stops future traffic from relying on the redirect chain indefinitely.

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.

URL Inspection Tool

The Pages → Not found (404) report shows broken URLs that Googlebot found while crawling. The URL Inspection tool does something different: it lets you check the index status of any single URL and see exactly what Google knows about it.

Use it this way:

1. In Google Search Console, type any URL into the search bar at the top of the screen.
2. Click REQUEST INDEXING if the page exists and should be indexed.
3. Check the Coverage section to see if Google has indexed the page, excluded it, or flagged it as a 404.

This is useful when you've just added a 301 redirect and want to confirm Google has processed it. It's also useful if a page appears in your 404 report but seems to load fine when you visit it — URL Inspection will show whether Google is actually seeing the correct content or hitting a soft 404.

For small business owners, the most common use case is checking a Google review request link after updating it. If your review link changed format and you set up a redirect, URL Inspection confirms whether Google has processed the redirect and updated its index entry. That usually takes a few days to a few weeks, but you can speed it up by requesting indexing through the tool.

One limitation: URL Inspection only checks one URL at a time. For bulk checks, use the Pages report or a crawl tool.

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.

404 Errors After a WordPress Core Update or Theme Switch

WordPress core updates and theme switches are two of the most reliable ways to break pages that were working fine the day before.

Why Core Updates Cause 404 Errors

WordPress stores its URL rewrite rules in the database and writes them to your server's .htaccess file (on Apache) or Nginx config. A major WordPress update can flush the rewrite cache without regenerating it correctly, leaving all URLs except the homepage returning 404 errors.

The fix is the same as for the permalink reset issue: Settings → Permalinks → Save Changes. No need to change anything — clicking Save forces WordPress to regenerate the rewrite rules immediately. Do this within five minutes of a major update if you notice page-level 404s appearing.

Theme Switches That Break Custom Post Types

If you switch themes, your new theme may not register the same custom post types or taxonomies that your old theme did. This happens most often when you're using a theme that bundles its own portfolio, testimonials, or services post types. After the switch, URLs like /portfolio/website-redesign return 404 errors because the post type no longer exists in WordPress's registry.

To check if this is the cause: Go to Settings → Permalinks → Save Changes. If 404s persist after that, install a plugin like Query Monitor and load a broken URL. Look under "Rewrite Rules" — if there is no rule matching your URL pattern, the post type isn't registered.

The fix options:

• Switch back to the old theme temporarily, export the content, then rebuild it in the new theme using a supported post type
• Install a standalone plugin that registers the same custom post type so the URLs survive independently of the theme
• If the content isn't being actively used, redirect the old URLs to a category page or related content

Plugin Conflicts After a Core Update

When WordPress updates, some plugins break. The worst case is a redirect plugin that stops functioning silently — redirects you set up no longer fire, and the 404 errors come back without warning.

After a major WordPress update, test your five most critical redirect rules: your review collection page, your contact form, your booking link, and any review platform redirect pages you're maintaining. Use curl -sI on each URL and verify the chain still shows a 301 followed by a 200.

If a redirect has stopped working, deactivate and reactivate the redirect plugin. Most redirect plugins rebuild their internal rule cache on activation. If the problem persists, check whether the plugin has released a compatibility update for the new WordPress version.

Checking for Update-Related 404 Spikes

The fastest way to catch update-related breaks before customers do: check Google Search Console's Coverage report the day after any major WordPress update. Filter for "Not found (404)" and sort by detection date. A cluster of newly discovered 404s appearing on the same day as your update is a clear signal that something in the update broke URL routing.

---

WooCommerce 404 Errors: Product Pages, Categories, and Checkout Links

WooCommerce adds its own layer of URL complexity on top of WordPress, and that means its own specific 404 failure modes. If you run an online shop alongside your review collection or service offering, these issues show up regularly.

The WooCommerce Permalink Setting

WooCommerce has its own permalink structure separate from WordPress's main permalink setting. When you first install WooCommerce or after a major update, shop URLs like /shop, /product-category/, and /cart may return 404 errors even though the WordPress permalink setting is correct.

Fix: Go to WooCommerce → Settings → Permalinks. Click Save Changes without modifying anything. WooCommerce rebuilds its endpoint registry on save. Also go to Settings → Permalinks in the main WordPress admin and click Save Changes there too — both rewrite tables need refreshing.

This two-step save is the first thing to try whenever WooCommerce URLs break after an update.

Product Page 404s After Reorganizing Categories

If you change a product's category, slug, or product type in WooCommerce, the old URL stops working. Because WooCommerce uses the category as part of the URL path by default (for example /product-category/services/consultation/), moving a product between categories changes its URL.

Old search results, customer bookmarks, and review request links pointing to the old product URL will hit a 404.

Fix: Use the Redirection plugin to create a 301 redirect from the old URL to the new one. If you've moved multiple products, check each one individually or run a crawl with Screaming Frog to find all the broken product URLs at once.

For businesses that frequently reorganize their product catalog, consider setting WooCommerce permalinks to the simple /product/[slug]/ format, which doesn't include the category path and doesn't break when you move products between categories.

Out-of-Stock Products: 404 vs Visible-But-Unavailable

WooCommerce gives you a choice when products go out of stock. You can hide them from the shop, set them as out-of-stock (still visible with a notice), or delete them entirely. Each approach has different 404 implications.

Deleting the product creates a 404 at the product URL. If that URL appeared in review request emails, on a pricing page, or in any external link, those visitors now hit a dead end.

Hiding from shop (the WooCommerce "Hidden" catalog visibility setting) keeps the URL active — it still returns 200 — but removes it from category pages and search results. This is usually the right choice for temporarily unavailable items.

If you need to delete a product permanently, redirect its old URL to the nearest equivalent active product page, to its category page, or to your main shop page. Don't redirect to the homepage.

Checkout and Cart 404 Errors

WooCommerce creates page objects for the cart (/cart), checkout (/checkout), and account (/my-account) paths automatically during installation. If someone deletes these pages from WordPress's Pages admin without realizing WooCommerce depends on them, those paths return 404 errors.

Check: Go to WooCommerce → Settings → Advanced and confirm that the Cart Page, Checkout Page, and My Account Page fields are set to actual WordPress pages. If any show "(no page selected)" or a deleted page title, re-create the page using the WooCommerce shortcode format or the WooCommerce block, then update the setting.

Review Link 404s on Product Pages

Many businesses embed review links on individual product pages — either as a direct Google review URL or as a link to a review collection landing page. When those links break, every customer who buys that product stops being prompted to leave feedback.

After any WooCommerce product update or theme change, test your review CTAs by loading each product page and clicking the review link. A broken review link on your ten best-selling products is a continuous drain on your review collection rate that compounds quietly week over week. A review management platform that generates consistent review request links from a stable URL makes this problem much less likely — your request URL doesn't change when you reorganize WooCommerce product categories.

Wix-Specific 404 Issues

Wix is one of the most popular platforms for small business websites — salons, restaurants, service businesses, local shops. It has several 404-producing quirks that the dashboard never warns you about.

The URL slug change trap

Every time you change a page's URL slug in Wix — the part of the address after your domain — the old URL stops working immediately. If you renamed /services to /our-services to match a rebrand, anyone who bookmarked the old link, clicked a Google result indexed before the change, or received a business card pointing to the old URL now hits a 404.

Wix has a built-in 301 redirect manager, but it doesn't create redirects automatically when you change a slug. You have to add the redirect manually. Most site owners skip this step because Wix doesn't require it or warn that the old URL is now dead.

To add a redirect: go to Settings > SEO > Redirects and add the old path → new path mapping. Test it immediately by pasting the old URL into a private browser window and confirming it lands on the correct page.

The multilingual URL problem

Wix sites with multilingual content use a language-prefix structure: /en/page-name for English, /es/page-name for Spanish. When you change language settings, add a new language, or remove one, the URL structure for existing pages can shift. If you had shared the non-prefixed URL — the default for single-language sites — and then switched to a multilingual configuration, all those old unprefixed URLs now return 404.

The fix is a redirect for every page whose URL structure changed. For a large site, use Wix's bulk-import option in the redirect manager — you can upload a CSV with the old and new paths rather than adding each redirect by hand.

Deleted app pages

Wix apps — Bookings, Events, Stores, Blog — each create their own URL patterns. If you remove an app and reinstall it later, the new installation can generate different URL patterns. A Wix Bookings page that lived at /bookings might reappear at /book-now after reinstallation. Every existing link — Google My Business posts, social bios, email signatures — that pointed to the old URL breaks silently.

Before uninstalling any Wix app, note its current URL and add a redirect from that path to whatever replaces it. If you don't know what will replace it yet, redirect to your homepage temporarily and update it once the new URL is live.

Squarespace-Specific 404 Issues

Squarespace handles URLs differently from WordPress and Wix, and has its own failure patterns that only show up after you've moved things around.

The URL slug lock

When you create a page in Squarespace, it generates a slug from the page title at that moment. If you later rename the page — say, from "Services" to "What We Do" — Squarespace does not automatically update the URL slug. The visible page title changes while the URL path stays the same. When you then go into page settings and manually update the slug to match the new title, the old slug breaks immediately.

Before changing a slug, note the current URL under Pages > (Page name) > Settings > URL Slug. After updating, add a redirect under Settings > Advanced > URL Mappings using the format:

/old-slug -> /new-slug 301

Test by visiting the old URL in a private browser window to confirm the redirect fires correctly.

The folder move problem

Moving a page in Squarespace's navigation sidebar can change its URL path depending on whether you're moving it into or out of a folder. A top-level page at /pricing that you drag into a resources folder now lives at /resources/pricing. The old URL 404s the moment you save the navigation change.

Before moving any Squarespace page, note its current URL. Make the move, then immediately add a redirect from the old path to the new one in URL Mappings. Two minutes of work prevents weeks of dead-link damage.

Squarespace store product 404s

Squarespace commerce product pages use their own URL structure (/store/product-name). Deleting a product, switching it to draft status, or changing its slug all immediately break any incoming links. Squarespace doesn't create automatic redirects for products that are removed or hidden.

If you're pulling a product permanently, redirect the old product URL to your store's main page or the closest relevant category. If it's a temporary draft while you update content, redirect it to a "coming soon" page or the store index so customers land somewhere useful instead of a dead end.

Shopify-Specific 404 Issues

Shopify handles some 404 scenarios differently from WordPress, Wix, and Squarespace — mainly because it automatically creates 301 redirects when you change a product or page URL handle. That sounds helpful, and it usually is. The problem is there are several situations where Shopify does nothing automatically, and those are exactly where businesses get caught off guard.

Product URL changes vs. product deletion

When you edit a product in Shopify and change its handle (the URL slug), Shopify prompts you to create a redirect from the old URL to the new one. Always accept this offer. It takes one click and prevents every existing link to that product — bookmarks, backlinks, email campaigns, QR codes — from delivering a 404.

Shopify creates automatic redirect offers for: edited product handles, edited page handles, edited blog post handles, and edited collection handles. It does NOT automatically redirect: deleted products, archived products, deleted blog posts, and deleted collections.

If you delete a product instead of archiving it, anyone with a saved link to that product hits a dead end. That includes customers who bookmarked the product, any external site that linked to it, and every email or text you've sent that contained the product URL.

The safer option for most cases is to archive the product rather than delete it. An archived product stays accessible at its URL (returns 200) but doesn't show up in your storefront collections or search results. This is the right move for products you might reintroduce, or for anything with meaningful backlinks or traffic history worth preserving.

If you're genuinely discontinuing a product, delete it — but first create a manual redirect via Settings > Navigation > URL Redirects. Point it to the closest alternative product or a relevant category page.

App pages that go dead after uninstalling

Shopify apps often create public-facing pages on your store — review display widgets, loyalty portals, booking calendars, referral landing pages. When you uninstall the app, those pages return 404 immediately. There's no warning and no automatic redirect.

Before uninstalling any Shopify app, check your store's sitemap at yourdomain.myshopify.com/sitemap.xml for URLs the app created — they often include the app's name or a recognizable slug. Then look in your analytics for traffic to those URLs. Any page with meaningful traffic or external links pointing to it needs a redirect before you uninstall.

After uninstalling, create manual redirects in Settings > Navigation > URL Redirects for any affected pages. This step is easy to skip in the moment and hard to catch weeks later when the 404s start appearing in Search Console.

The collection URL inconsistency

Shopify generates two URL formats for product pages: the direct path (/products/handle) and the collection-scoped path (/collections/category/products/handle). Both display the same product, but only one is canonical.

If you've linked to the collection-scoped URL in emails, QR codes, or on external sites, changing or deleting that collection can break those links even if the product still exists at /products/handle. Shopify doesn't automatically redirect from the old collection-scoped URL to the new one.

For any links you control — email templates, printed materials, social media bios — use the direct /products/handle format. It stays stable regardless of which collections the product belongs to. For links you don't control, create a manual redirect from the old collection-scoped URL to the direct product URL.

Verifying Shopify redirects

Shopify's redirect interface works, but confirm any redirect is actually firing before trusting it. The same curl test used for other platforms applies:

curl -sI https://yourdomain.com/products/old-handle | head -3

A working redirect shows HTTP/1.1 301 Moved Permanently with a Location: header pointing to the correct destination. If you see a 404 instead, check whether the redirect was entered with or without a leading slash — Shopify's interface handles this inconsistently, and a redirect entered as products/old-handle won't match a request for /products/old-handle. Always test immediately after creating any manual redirect.

How to Fix 404 Errors in Webflow

Webflow has become the platform of choice for professional services firms, agencies, and growing businesses that want more design control than Wix or Squarespace without managing a WordPress installation. It handles 404s and redirects differently from every other CMS covered in this guide — and the differences trip up even technically capable users.

The publish-first requirement

Every change you make in Webflow — including redirect rules — lives in staging until you hit Publish. This creates a frustrating loop: you add a redirect, test it, and the old URL still returns a 404. The redirect is saved correctly. You just haven't published yet.

Unlike Apache's .htaccess (which takes effect the moment you save the file) or the WordPress Redirection plugin (which applies changes instantly), Webflow holds everything in its own environment until publication. Always publish after adding or editing any redirect, then test. If you test before publishing, you're measuring the staging environment, not the live site.

Setting up redirects in Webflow

In the Webflow Designer, open Project Settings → Hosting → 301 Redirects. Add the old path in "Old Path" and the destination in "New Path." Include only the path — no domain, no https://. A redirect from /old-service to /services/what-we-do would go in exactly that way.

One hard limitation: Webflow doesn't support wildcard patterns or regex. If you restructured a blog from /articles/<slug> to /blog/<slug>, you can't write a single pattern rule — you need one redirect entry per post. For small restructures this is fine. For large migrations, use Webflow's CSV upload option: build a spreadsheet with columns for old path and new path, export as CSV, and import it under the same redirects screen. This saves hours compared to manual entry.

CMS collection page 404s

Webflow's CMS manages dynamic content like blog posts, portfolio entries, case studies, and testimonials. When you archive a CMS item, Webflow removes it from the published site but doesn't set up a redirect. The old URL returns a 404 — for bookmarked visitors, for any external links that referenced it, and for search engines that indexed it.

The fix: before archiving a CMS item, copy its slug from the item's settings. Then add a redirect in Project Settings from that slug to the most relevant live page. You can delete the CMS item afterward — the redirect you created is a separate record that survives item deletion. One redirect entry per archived item, added before you archive.

The slug change trap

Webflow auto-generates a URL slug from your page or CMS item name. When you rename something — say, from "Our Dental Services" to "Services" — Webflow may or may not update the slug, depending on whether you've manually locked it. If the slug changes, the old URL becomes a 404.

To avoid this: before renaming any page that's been live more than 30 days, open the page settings panel and copy the current slug. After renaming, check whether the slug changed. If it did, add a redirect from the old slug to the new one in Project Settings.

For pages that have earned backlinks or have been referenced in client-facing materials, the safer approach is to lock the slug permanently. In Webflow's page settings, you can type a slug directly into the slug field and leave it unchanged even when the page display name changes. Rename the page; leave the slug alone.

When Webflow's redirect limit becomes a problem

Webflow caps the number of redirect rules per site (the limit varies by plan tier). If you're migrating a large site into Webflow — say, 500 pages from a previous CMS — you may hit this ceiling before you've mapped every old URL. When that happens, handle the overflow at the DNS or CDN layer instead. If your domain runs through Cloudflare, Cloudflare's Page Rules or Transform Rules can handle pattern-based redirects without touching Webflow's settings, and they don't count toward Webflow's limit. This also handles the wildcard pattern problem — Cloudflare supports regex matching, which Webflow doesn't.

Testing Webflow redirects

After publishing, run the same curl test you'd use for any other platform:

curl -sI https://yourdomain.com/old-path | head -3

The response should show HTTP/2 301 with a location: header pointing to the new path. If it shows HTTP/2 404, the redirect either wasn't published or wasn't saved correctly in Project Settings. If it shows HTTP/2 200 for the old path, you may have a caching issue — test from a private browser window on a cellular connection to bypass local DNS and CDN cache.

One scenario to watch for: a Webflow site served through Cloudflare where the CDN has cached the old 404 response. Cloudflare's default behavior is not to cache 4xx responses, but some configurations do. If the redirect is correct in Webflow's settings and returns 301 in curl but shows a cached 404 in the browser, purge the Cloudflare cache for that URL specifically from the Cloudflare dashboard.

How to Fix 404 Errors in GoDaddy Website Builder

GoDaddy's Website Builder (distinct from GoDaddy hosting running WordPress or a custom site) is one of the most widely used platforms for small business websites in the US. It handles redirects entirely through its own settings interface — there's no .htaccess file, no plugin, no code to edit. The interface is buried deep enough that "how do I set up a redirect in GoDaddy" is one of the more consistently searched questions among small business owners.

Where redirects live in GoDaddy Website Builder

Log in to your GoDaddy account, go to My Products, and open your Website Builder. In the editor, look for Settings → SEO → Redirects. In some account versions this appears as Marketing → SEO → Redirects after a 2024 interface update.

Add the old path in "Original URL" and the destination in "Forwarding URL." GoDaddy's builder applies these as permanent (301) redirects by default, which is what you want for any page that was indexed or linked. Use the path only — no protocol, no domain. Moving /old-page to /services means entering those two paths exactly as written.

One thing GoDaddy Website Builder does NOT support: wildcard or pattern-based redirects. Every broken URL needs its own entry. If you restructured from /services/1 through /services/20 to a single /services page, that's 20 redirect entries to add by hand. There's no CSV import in the Website Builder product (that's available in GoDaddy Managed WordPress, but not the drag-and-drop builder).

The URL restructure trap on GoDaddy

GoDaddy Website Builder auto-generates page URLs from page names. If you rename a page — say, from "Contact" to "Get a Quote" — the URL may change from /contact to /get-a-quote without any warning and without creating a redirect. Your old URL, which may appear in your email signature, your Google Business Profile, printed business cards, and anywhere you've ever shared your site, now returns a 404.

Check this before renaming any live page: go to Settings → SEO → URL Slug for that specific page and copy the current slug. After renaming, check whether the slug changed. If it did, add a redirect from the old slug to the new one immediately.

Checking 404 status on GoDaddy sites

GoDaddy Website Builder doesn't have a built-in 404 log or crawl report. Your best external tools:

• Google Search Console: Free, shows what Googlebot found broken. Check Pages → Not Found (404).
• Screaming Frog: Free up to 500 URLs, crawls your live site and reports every 4xx response.

After any redirect you set up in the builder, test it by pasting the old URL in a private browser window. You should land on the new destination automatically. If you still see a 404, go back into Settings → SEO → Redirects and verify the rule saved — GoDaddy's builder has a known issue where rules occasionally don't persist on the first save. Clicking Save a second time fixes it.

Review links and GoDaddy sites

If you built a review collection page in GoDaddy Website Builder — a page at /reviews or /share-your-experience — treat its URL as permanent from day one. Put that URL in every review request email, QR code, and printed material, and never move the page without adding a redirect first. If you restructure your navigation and the review page shifts to a new URL, every piece of outreach you've ever sent now points to a 404. GoDaddy gives you full control over page URLs — use that control to keep the review page stable.

How to Fix 404 Errors in BigCommerce

BigCommerce is the platform many merchants migrate to when they outgrow Shopify or need more built-in catalog features. Its 404 handling is more capable than most SMB platforms, but it has specific failure patterns worth knowing before you hit them.

BigCommerce's URL Redirects manager

In your BigCommerce admin, go to Server Settings → URL Redirects. This is a dedicated redirect management tool with both manual entry and CSV import — more capable than most competing platforms at this price point. Add individual redirects manually or upload a CSV with two columns (old path, new path) for bulk imports after a migration.

BigCommerce supports both static redirects (exact URL to exact URL) and dynamic redirects (pattern-based, matching URL structure). The dynamic option handles most migration scenarios — if you moved all products from /products/[slug] to /[slug], one dynamic rule covers the entire catalog without individual entries.

For most 404 fixes on an established BigCommerce store, the root cause isn't a missing redirect rule — it's a deleted product or category that wasn't redirected when it was removed.

Deleted products and out-of-stock pages

BigCommerce gives you a choice when you delete a product: redirect visitors to another page, or simply remove the product and let the URL return a 404. Most store owners click "delete" without reading that prompt carefully, and the product URL — which may have backlinks from review aggregators, comparison sites, or social shares — goes dead immediately.

The fix going forward: whenever you delete a product or category, BigCommerce shows the redirect prompt. Always accept it and point it to the closest alternative in your catalog — same brand, same category, similar price point. For products already deleted without a redirect, find the old URLs in Google Search Console's "Not found (404)" report, then add manual 301 redirects through URL Redirects.

URL change after editing product names

BigCommerce generates product URLs from product names by default. If you edit a product name, the auto-generated URL slug may change, creating a 404 for anyone who bookmarked the original URL or for any external site that linked to it.

To prevent this: in your product settings, go to SEO → Custom URL and lock the slug before editing the product name. Once the slug is set manually, BigCommerce won't change it when the display name changes. For any product that's been live more than 30 days, locking the slug before a name edit is the safer habit.

Checking BigCommerce 404 errors

BigCommerce's native analytics don't include a 404 log. Use Google Search Console (Pages → Not found (404)) as your primary source, supplemented by a Screaming Frog crawl of your storefront. For a post-migration check, the CSV import option in URL Redirects handles bulk fixes efficiently — map old URLs to new destinations in a spreadsheet, import in one operation, then run a second crawl to confirm the list is clear.

How to Fix 404 Errors in Duda

Duda is the website builder behind many agency-built small business sites. If your site was built by a marketing agency rather than by you directly, there's a reasonable chance it runs on Duda. The platform handles 404 fixes through a URL Redirects panel inside the site settings, so you don't need developer access or file editing to create redirects.

To add a redirect in Duda:

1. Log into your Duda account and open the site editor at my.duda.co.
2. Click Settings in the top navigation bar.
3. Select SEO from the left sidebar menu.
4. Scroll down to URL Redirects and click Add Redirect.
5. In the From URL field, enter the broken path — start with a forward slash, like /old-page or /services/old-name.
6. In the To URL field, enter the correct destination — either the full URL or just the new path.
7. Click Add to save. Duda applies 301 redirects by default.

The most common Duda 404 cause is page renaming. When you rename a page in the Duda editor, the URL changes immediately but no redirect is created automatically. Anyone who bookmarked the old URL or clicked an external link hits a 404. The fix is adding the redirect manually in the panel right after you rename the page — ideally before publishing the change.

Review and booking links on Duda sites sometimes break when an embedded third-party widget is updated or a review management tool changes its URL format. The break often shows up as a blank area on the page rather than a visible 404 error — the page shell loads fine but the embedded content fails silently. In that case, the fix is replacing the embed code in the Duda editor rather than adding a URL redirect.

For businesses whose Duda sites are managed by an agency, ask your agency to add a URL Redirect whenever any page is renamed, deleted, or restructured. Keeping a shared log of active redirects prevents the same broken links from reappearing after each site update cycle.

How to Fix 404 Errors in HubSpot CMS

HubSpot CMS (part of Content Hub) is common among mid-size businesses running inbound marketing alongside their website. Unlike most drag-and-drop builders, HubSpot's redirect manager is capable enough to handle complex URL patterns — but it has a few specific behaviors that reliably cause 404 errors if you don't know to look for them.

Navigate to Settings → Website → Domains & URLs → URL Redirects. Click "Add URL redirect" in the top right. In the "Original URL" field, enter the broken path with a leading slash — like /old-page or /blog/old-post-title. In the "Redirect to" field, enter the destination. HubSpot defaults to 301 redirects, which is correct for permanent content moves.

HubSpot also supports pattern-based redirects through "Flexible match" mode. Toggle from Standard to Flexible, then use a regex pattern to catch an entire group of broken URLs at once. A single rule matching ^/old-section/(.*)$ and redirecting to /new-section/$1 handles every URL under a renamed category without adding individual entries for each one.

The most common HubSpot-specific cause of 404 errors: auto-generated slugs change when you edit page titles. When you publish a page or blog post, HubSpot builds the URL from the title. If you edit the title after publishing, HubSpot sometimes updates the slug automatically — and if you dismiss the redirect prompt that appears, the old URL goes dead with no redirect in place. After any title edit, open URL Redirects and confirm a rule was created. If it wasn't, add one manually pointing the old path to the new URL.

Deleted blog posts are a separate problem. When you delete a HubSpot blog post, its URL returns a 404. HubSpot does not auto-create a redirect on deletion. For any post that's been live for more than 30 days — particularly one with inbound links or search traffic — add a redirect before or immediately after deletion. Point it to the closest live post, or to your blog index (/blog). Avoid redirecting deleted posts to your homepage; Google treats a homepage redirect from unrelated content as an invalid redirect and won't pass ranking value through it.

To fix broken links inside HubSpot email templates, open Marketing → Email, open the email in the editor, and update the href on any link that's changed. Send a preview to yourself and click through every link before the next campaign runs — HubSpot wraps your links in its own tracking redirect layer, which can make a destination 404 invisible until an actual click happens.

Checking HubSpot for 404 errors: HubSpot's built-in analytics don't include a dedicated 404 error report. Connect your HubSpot domain to Google Search Console and use GSC's Pages → Not found (404) report as your primary detection tool. For internal broken links that Googlebot hasn't flagged yet, run Screaming Frog against your live HubSpot site — it catches href attributes pointing to dead destinations that the GSC crawl hasn't reached.

One workflow that works well for HubSpot blogs with frequent updates: before publishing any post deletion or URL restructure, export your current sitemap and run it through a quick curl check to confirm your top twenty or thirty pages all return 200. HubSpot's URL Redirects panel handles the fix; the crawl confirms it landed correctly.

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

How to Build a Helpful Custom 404 Page

Most business sites ship with a default 404 page that says "Page not found" in plain text against a white background. That's it. No links, no search bar, no reason for the visitor to stay. The default is a dead end. A well-designed 404 page doesn't fix the broken link — nothing does except a redirect — but it gives the visitor somewhere to go instead of hitting the back button and landing on a competitor.

What a useful 404 page includes

A plain-language explanation, not a technical apology. Visitors don't know what HTTP error codes mean. Write one sentence that says the page couldn't be found, not a formal error message. Keep the tone consistent with the rest of your site.

A working search bar. If you run a content site, a services directory, or a local business with multiple pages, a search box lets visitors find what they were probably looking for. On WordPress, most themes include a search widget you can drop into the 404 template. On Shopify, the built-in search component works in any Liquid template.

Links to your three or four most important pages. These are usually your homepage, your main service or product page, your contact or booking page, and your review or testimonial page. Don't list everything — pick the pages that match the most common visitor intentions. A dental office might link to "Book an Appointment," "Our Services," "Patient Reviews," and "Contact Us." An e-commerce store might link to its three top categories.

Your phone number and contact info. If a visitor hit your 404 because they were trying to reach you, a visible phone number on the error page saves the interaction.

No autoplay video or distracting animations. A 404 page is not the place to show off. Visitors are already frustrated. Keep the layout simple.

How to implement a custom 404 page by platform

WordPress: Most themes have a 404.php file in the theme directory. Open it in your theme editor or FTP, and add your content there. If you're on a block theme, the Full Site Editor (Appearance > Editor) lets you create a 404 template visually. Third-party page builders like Elementor and Divi have dedicated 404 page settings under their theme builder sections.

Shopify: Create a file called 404.liquid in your theme's templates folder. Shopify automatically serves this file when a URL can't be found. Add navigation links, a search bar using Shopify's built-in {% form 'search' %} tag, and your contact information.

Next.js (App Router): Create a not-found.tsx file in your app directory. This file renders when the notFound() function is called from any page or layout, and also as the default fallback when a route doesn't match. Keep it in your root app/ directory for site-wide coverage.

Wix: Go to Settings > Custom Error Pages. Wix provides a visual editor for your 404 page where you can add navigation links, a search bar, and contact info. Wix handles the HTTP 404 status code automatically — you're editing only the visual content.

Squarespace: Add a page to your site and name it "404." Squarespace recognizes this as the custom error page and serves it for all 404 requests. Design it in the normal page editor.

What not to do

Don't redirect all 404s to your homepage. This is a common shortcut that creates its own problem — Google treats homepage redirects from unrelated URLs similarly to leaving the 404 in place, because the content relationship isn't there. It also confuses visitors who clicked a specific link and end up on your homepage with no explanation.

Don't use your 404 page to apologize at length. One brief sentence is enough. Everything else on the page should help the visitor get where they need to go.

Don't skip the custom 404 page just because 404s should be redirected. Even with a solid redirect strategy in place, some broken URLs will always slip through — old campaign links, misspelled URLs, external links you don't control. A helpful 404 page is your last line of defense.

How HTTPS Migration Causes 404 Errors

Switching your website from HTTP to HTTPS sounds like a routine security upgrade. Install the SSL certificate, flip the setting in your hosting panel, done. What most businesses don't realize until too late is that the switch creates a new category of 404 errors — ones that affect URLs that were working perfectly the day before.

Here's what happens: Google's index, your email campaigns, customer bookmarks, directory listings, and external backlinks all contain your old HTTP URLs. The moment your site switches to HTTPS without a proper redirect layer in place, every one of those HTTP requests hits a 404 instead of loading your page. Your site is technically live, but anyone arriving via an old link gets nothing.

The missing redirect is almost always the culprit

The fix for an HTTPS migration 404 is a server-level redirect that forwards all HTTP traffic to the HTTPS equivalent. This is a single rule, and it covers every page on your site at once — you don't have to set up individual redirects for each URL.

On Apache, add this to your .htaccess file:

RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

On Nginx, add this to your server block (before the HTTPS server block):

server {
    listen 80;
    server_name yourdomain.com www.yourdomain.com;
    return 301 https://$host$request_uri;
}

If your site runs on a managed hosting platform, the setting usually lives in your control panel rather than a config file. GoDaddy calls it "HTTPS Redirect" under your hosting settings. Bluehost has an "SSL/TLS Status" toggle. Cloudflare handles this under SSL/TLS → Edge Certificates → "Always Use HTTPS."

After enabling the redirect, test it with curl rather than your browser — browsers cache redirects aggressively, which can make a broken redirect look like it's working when it isn't:

curl -sI http://yourdomain.com | head -3

A correct result shows HTTP/1.1 301 Moved Permanently with a Location: https://yourdomain.com/ header. If you see a 404 instead, the redirect rule isn't in place or isn't firing for that server.

Mixed content 404s: a different problem

Once HTTPS is running correctly, you may still see 404 errors in your browser's developer console even though the page itself loads. These are mixed content errors — the main page is served over HTTPS, but it's trying to load images, stylesheets, or scripts from HTTP URLs that no longer exist.

The most common source is older blog posts or product pages that embed images with hardcoded HTTP URLs. When the browser requests an HTTP image URL on an HTTPS page, it either returns a 404 or gets blocked by the browser's security policy before the request reaches your server. The image slot on the page goes empty, the console logs an error, and if enough resources fail, the whole page experience breaks.

Fix these by searching your content database for any hardcoded HTTP references to your own domain and updating them to HTTPS. On WordPress, the Better Search Replace plugin handles this across your entire database in a few clicks. On Shopify, mixed content images from external sources need to be re-uploaded to Shopify's CDN and re-referenced in the product or page content.

Test for mixed content using your browser's developer tools (Network tab, filter by status 4xx) or a tool like Why No Padlock, which scans a URL and reports every non-HTTPS resource the page tries to load.

What to check after any HTTPS migration

Run your site through Google Search Console's URL Inspection tool on two or three key pages immediately after switching. If Googlebot can reach the HTTPS versions correctly, the inspection shows the canonical URL as https://. If it still shows http://, the redirect isn't reaching Google's crawler. This usually means the redirect rule is in your CMS but the server itself — often a caching layer or CDN — is serving the cached HTTP response instead.

Clear your CDN cache and any site-level caching after making changes to HTTP redirect rules. Server caches don't expire immediately. A redirect change that looks broken for the first hour may simply be the cache serving the old response while the new rule takes effect underneath it.

The timeline for Google to catch up after fixing an HTTPS redirect is typically one to four weeks for a small business site. Once it does, the HTTP URLs in Google's index get replaced with the HTTPS equivalents, and the old 404 reports in Search Console clear themselves. You can speed this up by using the URL Inspection tool to request reindexing of your key pages directly.

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.

Tools like Praising.ai track your active review request links and flag when a destination URL stops responding — turning a problem you'd normally discover weeks later into something you catch the same day.

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.

When Your Review Request Link Breaks Mid-Campaign

Discovering that your review link has been returning a 404 for days — or weeks — while an active campaign was running is one of the more sinking feelings in local business marketing. The automation kept going, customers kept opening emails, and nobody left a review. Here's how to contain the damage quickly.

Step 1: Confirm the break and find when it started

Before doing anything else, run a curl test to confirm the exact status the URL is returning right now:

curl -sI https://yourdomain.com/your-review-link | head -3

Then open Google Analytics and pull the traffic report for that specific page path over the last 30 days. Look for the date when visits dropped sharply or stopped entirely — that's roughly when the link broke. Google Search Console's URL Inspection tool can show you when Googlebot last crawled the page and what it found.

Knowing the break date tells you how many customers were likely affected. If your campaign sends 50 emails per week and the link broke 10 days ago, roughly 70 people hit a dead end.

Step 2: Get a working link in place first

Fix the broken destination before you do anything else. If your review redirect page broke, the fastest fix is usually one of:

• Restore the redirect in your CMS or server config so the old URL sends visitors to your Google review form again.
• Use a new direct link. Google's review form link for your business can be grabbed fresh from your Google Business Profile settings. If your old redirect page is gone, a direct link to the Google form sidesteps the broken redirect entirely.
• Update your campaign template. If the root cause was a URL you can't restore (your old review platform changed the link format, for example), update the link in every active email sequence and automation before sending another message.

Test the new link from your phone on cellular data — not from your office computer where cached DNS might make a broken link appear to work.

Step 3: Re-engage the customers who hit the broken link

This is the step most businesses skip. If you have access to open and click data from your campaign tool, you can see who clicked the broken link. Those customers had enough motivation to act — they opened the email and clicked. They're warm, and they just got unlucky with the timing.

A simple follow-up works here. You don't need to explain that your link was broken. Send a short review request email with a subject line like "Quick question about your recent experience" and a fresh, tested link. Keep it under four sentences. The customers who clicked but didn't complete a review are your highest-conversion follow-up audience.

For customers who opened the email but didn't click, a normal re-send with a working link is appropriate.

Step 4: Fix the root cause and add a monitor

Once the link is working again, add it to a free uptime monitor like UptimeRobot. Set the check interval to five minutes. The monitor will alert you within minutes if the URL stops returning a 200 — before any more customers encounter the dead end.

Also audit your other campaign links at the same time. If one link broke silently, others might be at risk for the same reason. Check every URL in your active automated review request sequences, including the unsubscribe link, your business logo link, and any secondary CTAs.

A broken review link mid-campaign is recoverable. Most of the customers who clicked will respond to a clean, well-timed follow-up. The goal is to move quickly enough that you're re-sending within a few days of the break, not a few weeks.

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.

How to Set Up Automatic 404 Alerts

Monthly manual checks are better than nothing, but they're slow. A 404 that appears after a site update could send customers to a dead page for three to four weeks before you spot it in Search Console, and then another week or two before Google recrawls the fixed URL. For high-traffic pages — your homepage, your contact form, a review collection link in your email campaigns — three weeks of silent failures means a lot of missed customer interactions.

The better approach is monitoring that tells you within minutes or hours, not weeks.

Google Search Console email notifications

GSC doesn't have a simple "alert me when a 404 appears" toggle, but it does email you when new issues are detected in the Page Indexing report. To enable this, open Search Console, go to Settings, and confirm that notifications are turned on for your property. GSC will email you when it discovers a meaningful new batch of errors on your site. The limitation: this only catches what Googlebot has already crawled, so there's a built-in delay of several days to weeks.

Uptime monitoring for your most important pages

Free tools like UptimeRobot and Freshping (both free for up to 50 monitors) let you watch specific URLs and alert you by email or text when they stop returning 200. This is different from a whole-site crawl — you're watching individual high-value URLs continuously, not scanning your entire site once a month.

Set up monitors for:

• Your homepage
• Your contact or booking page
• The active review collection link you use in email campaigns, QR codes, and text messages
• Any page that has significant external backlinks

Configure alerts to fire immediately when a monitored URL stops returning 200. If your review link breaks at 2 a.m. after a CMS update, you'll know by morning instead of discovering it three weeks later when a customer mentions it.

Scheduled crawl automation

If you want a complete picture rather than watching individual URLs, schedule a monthly crawl with a free tool. Screaming Frog's free version (up to 500 URLs) and Ahrefs' free Webmaster Tools both surface 404s without requiring you to do anything once configured — Ahrefs runs periodic crawls of your verified property automatically and drops the results into Site Audit.

For most small business websites, combining one uptime monitor on your review collection link with monthly GSC review covers 90% of the real failure scenarios. The uptime monitor catches same-day breaks on your most critical URL. GSC catches broader issues across the rest of the site. Neither requires ongoing work once set up.

How Many Reviews Are You Losing to Broken Links?

There's a calculation most businesses never run. If you send 200 review requests per month and your link is broken for three weeks before you notice it, roughly 150 of those requests sent customers to a dead page instead of a review form.

Not all 150 would have left a review. Typical conversion rates on review request emails land somewhere between 5% and 15% depending on timing, industry, and how the email is written. At 10%, those 150 broken deliveries represent 15 reviews that didn't happen. At scale, or across multiple months before detection, that's a measurable gap in your review volume and a real slowdown in your rating trajectory.

The math matters less than the timing. A customer who just had a great experience and taps your review link is at peak motivation. They haven't forgotten you yet, they're not distracted by the next task, and they had a specific intention when they opened the message. A broken link doesn't delay that review — it eliminates it. Most customers won't try again. They'll close the message and move on, and the impulse won't come back.

This is why a broken review link is categorically different from a broken blog post or a missing product image. Those failures are annoying. A broken review link is a one-time permanent miss.

What compounds the damage

Online ratings operate on a curve. If your current Google rating is 4.3 stars, adding 15 reviews with a 4.8 average moves your overall score less than you'd expect, because those new reviews average against your existing total. But stopping the flow of positive reviews — which is exactly what a broken link does — means your rating is only moving based on whatever reviews come in organically. Organic reviews tend to skew negative, because customers with a complaint are more motivated to find a way to leave a review than customers with a good experience.

Three weeks of a broken review link can halt positive review velocity, let one or two negative experiences nudge your rating down, and create a gap in your review count timeline. Platforms that rank local businesses on review volume and recency — including Google Maps — notice that kind of gap.

A quick pipeline health check

Once a month, before anything else:

1. Paste your main review collection link into a private browser window and click through to the destination — confirm it resolves correctly on both desktop and mobile.
2. Open the last review request email your system sent and click every link in it, not just the main CTA.
3. Scan any active QR codes with your phone — the target URL may have changed even if the QR code still scans.
4. If you use a review management platform, check the delivery dashboard for unusual drops in click-through rate. A broken link causes clicks to fall to near zero while delivery rates stay normal — that's a diagnostic signal.

Catching a broken link takes under five minutes. Recovering reviews you missed while the link was broken isn't possible.

What to Do After Sending Review Emails with a Broken Link

The hardest part about a broken review request link isn't fixing the link — it's the emails already sitting in customers' inboxes.

Most review platforms send request emails on a delay after a transaction closes. If your link was working when the emails were queued but broke before they were opened, some percentage of those opens will hit a dead page. Email open rates tend to cluster in the first three to five days after send, but a meaningful tail continues well past that. Every day the link stays broken, more opens convert to frustration instead of reviews.

You can't recall emails that have already been delivered. But you can limit the damage:

Fix the destination immediately. Even if hundreds of emails went out with the broken link, fix the target URL now. Every customer who opens after the fix gets a working experience. If you use a stable proxy URL — your own domain redirecting to Google or your review platform — updating one redirect fixes all remaining future opens at once. No changes to individual email templates required.

Identify who was affected. In your email platform or review management tool, find the send batch that contained the broken link. Look for campaigns with an unusual drop in click rate while delivery and open rates stay normal. That specific pattern — normal opens, near-zero clicks — is the diagnostic signal for a broken link in a live campaign, not a subject line or audience problem.

Send a follow-up to the unclicked list. If you can export contacts who received the email but didn't click, a brief follow-up within 48 hours recovers some missed opportunities. Don't mention the broken link. "We noticed we sent you a review request recently and wanted to make it easy to find" with the correct link clearly visible is enough. Three or four sentences, nothing more.

This only works if you move quickly. The motivation to leave a review fades fast. A customer who had a good experience three days ago is still in a positive frame of mind. That same customer two weeks from now has mostly moved on, and the impulse to share their experience publicly won't return without a fresh trigger.

Check your SMS sends too. Review request texts are read almost immediately after delivery, which means a broken link in an SMS sent during the outage reached nearly every recipient in real time with no recovery window. Check your SMS delivery logs for any sends during the affected period. Some platforms let you filter by click status and resend to unclicked recipients — use it if yours does.

Going forward, include your review link in a monthly five-minute check: paste it into a private browser window, click through, and confirm the form loads correctly on both desktop and mobile. That's the cheapest insurance you can buy against this problem.

---

404 Errors in JavaScript Apps and Single-Page Sites

Traditional websites serve a new HTML document for each URL. When a page doesn't exist, the server returns a 404 status code and the browser shows an error page. Straightforward.

JavaScript-heavy sites — anything built with Next.js, React, Vue, or a similar framework — handle routing differently. The browser loads a single HTML document on the first request, and JavaScript handles all subsequent navigation client-side by swapping content without making new server requests. The problem: when a visitor lands directly on a URL that doesn't exist (from a Google result, an email link, or a bookmarked address), the server may return a 200 response with an empty page or a generic shell — not a proper 404.

This is a soft 404 at the infrastructure level. Google receives a success signal from the server, crawls the page, sees little or no useful content, and either skips indexing it or classifies it as thin. You can't tell from Google Search Console alone whether a 404 in the report is a server-level 404 or a soft 404 produced by a client-side routing miss.

How to catch it

If you're on Next.js and your deployment platform (Vercel, Netlify, or a custom server) isn't configured to handle Next.js routes, a URL like /services/accounting that exists as a Next.js route may be served as a 200 with the index HTML instead of the correct page content. Run the curl test against your live domain for a known missing URL:

curl -sI https://yourdomain.com/this-page-does-not-exist | head -3

The first line should show HTTP/1.1 404. If it shows HTTP/1.1 200, your server is silently swallowing 404s.

Platform-specific fixes

Next.js (App Router): Call notFound() from your page or layout when a data fetch returns null or empty. This renders your not-found.tsx file and sends a proper 404 response to the browser and to crawlers.

import { notFound } from 'next/navigation';

export default async function Page({ params }) {
  const data = await fetchPageData(params.slug);
  if (!data) notFound();
  return <div>{data.content}</div>;
}

Next.js (Pages Router): Return { notFound: true } from getStaticProps or getServerSideProps for any path that doesn't have real content:

export async function getServerSideProps({ params }) {
  const data = await fetchPageData(params.slug);
  if (!data) return { notFound: true };
  return { props: { data } };
}

React with a standalone server (Express): Add a catch-all route after all your defined routes that sends a proper 404 status with your 404 page HTML:

app.get('*', (req, res) => {
  res.status(404).sendFile(path.join(__dirname, 'build', '404.html'));
});

Static hosting (Netlify, Vercel, Cloudflare Pages): Create a 404.html file in your build output root. Netlify and Cloudflare Pages automatically serve this file for unmatched routes with a 404 status. On Vercel, the 404.html file is served for routes that don't match any serverless function or static file — though for Next.js specifically, the framework's built-in not-found.tsx takes precedence.

Why this matters for your business site

Most small business websites aren't full single-page apps. But many are built on frameworks that use client-side routing for performance (faster navigation between pages). If your developer or website builder used a framework without configuring the server correctly for unmatched routes, every broken URL on your site is returning 200 to Google while displaying nothing useful. That's worse than a real 404, because Google keeps indexing the empty shell.

If you're unsure whether your site handles this correctly, the curl test takes thirty seconds and gives you a definitive answer.

When Google Changes Your Review Link Format

Google has updated its review URL structure at least three times in recent years. If you generated your review link more than 18 months ago, there's a reasonable chance it either dead-ends or redirects to your Google Business Profile listing rather than opening the review form.

The current format for a Google review link looks like this:

https://search.google.com/local/writereview?placeid=ChIJ...

Older links often went through the g.page/r/SHORTCODE/review format or the maps.app.goo.gl redirect service. Both of those formats have broken for some businesses over time.

You won't always get an explicit 404. Sometimes the old link redirects to your GBP profile page with no review prompt. Sometimes it loads a generic Google search result. The customer sees something — just not what they expected — and closes the tab. You never know unless you test it yourself.

How to get your current working review link

1. Log into your Google Business Profile at business.google.com.
2. Click your location.
3. Find the "Ask for reviews" section — Google labels it slightly differently depending on when your dashboard was last updated.
4. Copy the link Google provides directly from that section. This is the URL format Google maintains and updates when structures change.

Test it: paste the link into a private browser window and confirm it opens the review form, not a profile page or search result. If it opens the form, you're good. If it doesn't, that's your answer.

The stable proxy approach

Every time Google changes its URL format, you have to track down every place the old link lives — email templates, text message templates, printed QR codes, table tents, receipts, business cards, email signatures. Missing even one means some of your customers hit a dead end.

A more resilient setup uses a URL you control as the link customers see. Something like yourdomain.com/review redirects to Google's current URL. When Google changes its format, you update one redirect — and every place that sends customers to your domain keeps working without changes.

Setting this up:

• WordPress: Install a redirect plugin like Redirection and add /review → [current Google URL] as a 301.
• Shopify: Go to Settings > Navigation > URL Redirects and add the mapping there.
• Squarespace: Add the mapping under Settings > Advanced > URL Mappings using the format /review -> [URL] 301.

Test the proxy the same way you'd test the direct link — private browser, click through, confirm the review form loads.

Updating stale links across your materials

After getting your current working link, check everywhere the old one lives.

Email templates. Open each active review request template and search for the old URL. If you're using a review management platform, update the link stored in your account settings — the platform embeds that URL in every outgoing request, so fixing it there fixes all future sends in one step.

SMS templates. Some platforms embed the full URL; others use a short link that redirects to whatever you've configured. Check both.

QR codes. If you used a dynamic QR code service, log in and update the destination URL. The QR image stays the same; only the destination changes. If you used a static QR code, you'll need to generate a new one and replace any printed materials.

NFC tags. Most NFC tag apps let you update the stored URL from the app without physically replacing the tag.

Physical materials. Receipts, table tents, signs, and business cards with printed review links are the hardest to fix quickly. If you're redoing any of them soon, switch to your stable proxy URL so future format changes don't require reprinting.

Your Google Business Profile. Check the website URL field in your GBP — some businesses point it to their review link. It should point to your actual website.

One broken link in any of these spots means some percentage of motivated customers hits a dead end. Catching it takes five minutes and a private browser window. Missing it costs you reviews you'll never recover.

404 Errors in Business Citations and Directory Listings

When another website links to your business, that link is an asset. But many of those links don't point to your homepage — they go straight to specific pages: your services page, your team page, a product listing, or a page that no longer exists.

Business directories are especially vulnerable to this problem. Yelp, BBB, Angi, Houzz, Thumbtack, and hundreds of industry-specific directories collect a website URL when you first create or claim your listing. That URL gets embedded in a link and stays there indefinitely, long after you've redesigned your site, changed your domain, or updated your URL structure. Directory editors rarely check whether the links they host still resolve.

Why citation links matter more than you might expect

Local SEO depends in part on citation signals — mentions of your business name, address, and phone number across the web. Search engines use these mentions to verify that your business is real, established, and operating at a specific location. When citation profiles also include a link to your website, that link becomes part of the signal.

A dead link on a Yelp or BBB profile doesn't just frustrate the occasional visitor who clicks it. It creates an inconsistency between what the directory claims about your business and what Google finds when it checks. A directory that links to a working page signals that the listing is current and maintained. One that links to a 404 signals the opposite.

This is distinct from the backlink equity loss that happens with any broken external link. Citation health specifically affects your local authority signals, which feed into map pack rankings and local organic results. For brick-and-mortar businesses and service-area businesses competing in Google's local results, the difference between clean citation links and broken ones can show up in rankings.

Finding broken citation links

Start with the directories where your business already has a presence. Log into each profile and look for a "Website" or "Business URL" field. Paste that URL into a private browser window and confirm it loads — not just that the domain resolves, but that the specific page they're linking to still exists and returns a real page.

Free tools like Moz Local, BrightLocal (paid, but with a free trial), and Google's own Business Profile dashboard can surface a list of directories where your business appears. Cross-reference these with the URL they have on file and add any dead links to your 404 fix queue.

For a faster audit, pull a list of your external backlinks from Google Search Console (under Links → External Links) or Ahrefs' free Webmaster Tools and filter for any that return 404. Directory links tend to show up in these reports, and you can identify which directories have your old or broken URL in a single pass rather than logging into each one manually.

Updating directory profiles

Unlike internal links, which you can fix with redirects, directory links require updating each profile individually. Log into each directory, navigate to the website URL field, and update it to your current working URL.

For the most important directories — Google, Yelp, BBB, and any industry-specific platforms where customers actively look for businesses like yours — update the links directly. For smaller directories where you no longer have login credentials, the 301 redirect approach is more practical: set up a redirect from the old broken URL to its correct destination, and the directory link will resolve cleanly without needing to contact anyone.

Document every change. Add it to your URL change log, noting which directory was updated and what the new URL is. If you ever migrate your site again, you'll have a ready list of directories that need updating before you flip the switch — not after you start seeing 404 reports.

Keeping an eye on your online reputation includes more than review ratings — it includes the structural health of every path a customer might take to reach you. A broken citation link is one of the quieter ways to lose business you never knew was available.

For further reading, see our complete guide to what online reputation management actually involves and our comparison of the best review management tools available.

404 Errors in Your Google Business Profile Website Link

Your Google Business Profile has a website URL field. Most business owners set it once during initial setup and never touch it again. But if you've redesigned your site, changed your domain, or restructured your URLs since then, there's a real chance that link now points to a 404.

This matters in a specific way that goes beyond ordinary backlink equity. When someone finds your business on Google Maps or in the local pack, they can click straight to your website from your GBP listing. If that click lands on a 404, you've lost a high-intent visitor — someone who searched for your type of business, found you, and decided to learn more. That's about as warm a lead as you can get before they're already a customer.

There's a secondary effect as well. Google's local algorithm considers the consistency of signals attached to your business. A GBP that links to a working page is one piece of that picture. A profile linking to a dead page doesn't trigger a hard penalty, but it creates a discrepancy between what your listing claims and what a crawler finds when it checks. Over time, that kind of inconsistency accumulates.

How to check your GBP website link

Log into your Google Business Profile at business.google.com. Click the profile you want to check, then go to Edit profile → Business information. Scroll to the website field and look at what's saved there.

Then open a private browser window — not your regular browser, where cached pages and auto-logins can hide problems. Paste the URL and load it. If you get a 404, a redirect loop, or any error, that's what your potential customers see when they tap your listing.

While you're there, check any appointment booking URLs, menu links, or service links you've added to the profile. These can all silently break after a website migration and they're easy to overlook because they don't appear in your normal site crawl tools.

Fixing a broken GBP website link

Update the website field in your GBP to the correct current URL. If you've moved to a new domain, use the new domain. If a specific page moved, use the new path. After updating, test the link again from a private window to confirm the URL resolves correctly and lands on a real page — not a redirect chain that ends in another 404.

One mistake worth flagging: some businesses point their GBP website field to their Google review link instead of their actual website, thinking it makes it easier for customers to leave a review. The problem is that review links are among the URLs most likely to change when Google updates its format. If that happens, your GBP's website field points to a dead URL and you find out only when a customer complains or you happen to click it yourself.

Your GBP website field should point to your actual domain or a stable landing page you control — not a third-party URL that can change without warning. For the review link specifically, your better move is to use the review link sharing options built into GBP rather than hardcoding the raw URL into your profile fields.

If you're managing Google Business Profile setup across multiple locations, add a website-field check to your monthly audit routine. It takes under a minute per location and catches a broken link before your customers do.

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.

Testing 404 Fixes From a Smartphone

Most guides on 404 errors show you how to verify fixes from a desktop browser. But for local businesses — restaurants, salons, medical offices, trades — the majority of customers who click your links are doing it from a phone. A redirect that works perfectly in Chrome on your laptop can still break on iOS Safari, and you won't know unless you test it the same way your customers experience it.

Why mobile testing is different

Three things commonly cause 404 fixes to behave differently on mobile:

App redirect conflicts. On iOS, tapping a Google Maps link sometimes opens the Google Maps app instead of a browser, bypassing your redirect entirely. If your review link goes through your website (e.g., yourdomain.com/review redirecting to Google's review URL), the redirect may fail silently when the Maps app intercepts the link. Test by pasting the URL directly into Safari's address bar rather than tapping from another app.

Cached DNS on mobile networks. Phones connected to carrier networks cache DNS lookups differently than your home or office Wi-Fi. A domain migration may show correctly on Wi-Fi but return a 404 on cellular data for hours after the change. If a redirect works in the office but customers are still hitting a 404, test on LTE with Wi-Fi disabled.

Phone-formatted URLs. Some review request platforms send review links formatted for phone screens — sometimes with a shortened URL or a click-tracking wrapper. The tracking URL resolves to your review page, which resolves to Google's form. Each hop can fail independently. Send yourself a test review request and tap the link from your phone, not from your email client on a computer.

How to test redirects from a smartphone

Open your phone's browser in a fresh tab. On iPhone, use Safari (iOS's default, and the one with the most quirks). On Android, use Chrome. Type or paste the URL manually into the address bar — do not tap a link from another app, which can trigger app interception logic.

If the redirect works correctly, you'll land on the destination page. If it doesn't, you'll see a 404 or an error message that tells you where in the chain the break is.

For your review link specifically: after fixing the redirect, paste the link into your phone's browser, let it resolve, and confirm you land directly on the review-entry form — not on your Google Business Profile's overview page, and not on a generic Google search result. The form is the only outcome that actually results in a review. The other two outcomes look like success and aren't.

Checking QR codes from the physical world

If you have printed materials — table tents, receipts, business cards, window stickers — with QR codes pointing to a review page or your website, scan them from your phone's camera app. Scan from across the room, not right up close. A QR code that only works when the phone is two inches away won't be scanned by most customers.

When the QR redirects, confirm it lands on the correct destination. If the QR's destination URL has changed (because you updated your review link or moved to a new platform), the physical materials are broken until you reprint them or update a dynamic QR's destination. Add QR code testing to your monthly audit routine — it takes 30 seconds and catches breaks in your physical review pipeline before they quietly drain your review count.

Setting Up 404 Monitoring Without a Technical Team

Most 404 monitoring guides assume you have a developer available to set up scripts, configure server logs, or run Screaming Frog crawls on a schedule. If you're running a small business without IT support, those setups either require technical skills you don't have or tools that cost more than the problem warrants.

There are two free approaches that work without any technical knowledge.

Google Search Console already tracks 404 errors because Googlebot reports them when it crawls. What most business owners miss is that Search Console can email you when new coverage errors appear. Go to Settings (the gear icon in the left sidebar) → Notifications → tick "Email notifications for your site." This won't alert you in real time, but it gives you a weekly digest of new crawl errors, including 404s that Googlebot hit during its most recent visit. You see problems within days instead of weeks.

UptimeRobot's free tier monitors up to 50 URLs every five minutes and sends an email or SMS when any of them returns a non-200 status. You don't need to monitor your entire site — just the pages that matter: your review request landing page, your contact form, your most-linked service pages, and your booking URL if you take appointments. Set these up once and you'll know within minutes if a page goes down. You find out before a customer does, not after.

For review-related pages specifically, this setup is worth doing even if you skip everything else. A broken review link can drain an entire campaign silently. Customers hit the dead page and close the tab without saying anything. UptimeRobot catches it in five minutes. Google Search Console might surface the same issue three weeks later, after dozens of customers have already encountered it.

Neither tool replaces a full monthly crawl. But together they cover the breaks that cost you real business — broken review flows and downed landing pages — with no ongoing effort on your part. The only thing they ask is that you actually fix the link when they notify you.

404 Errors in Email Marketing Automations

Your website's pages and your email marketing sequences age at different speeds. You might update a service page, delete an old promotion, or move your booking link — and fix every redirect on the site — while three automated email sequences continue sending visitors to the old URL from six months ago.

This is one of the most common 404 sources for service businesses, and it's almost completely invisible. Email platforms track opens and clicks, but they don't tell you whether the destination URL returned a 200 or a 404. From your dashboard, a broken link looks identical to a working one — both show click counts, neither shows what happened after the click.

Which automations to check first

Most small businesses run four or five automations that contain URLs worth checking: a welcome sequence for new contacts, a post-appointment follow-up, a review request series, a re-engagement campaign for inactive contacts, and a seasonal promotion that was supposed to run once but never got turned off. Open each one and look at every link.

Pay particular attention to links that were added more than six months ago. Anything pointing to /services/, /promotions/, or /book/ has a real chance of having moved at least once since the automation was built. Review request emails deserve their own pass — the Google review link format has changed at least twice in the past few years, and an email sequence built on the old format may still be sending thousands of messages to a broken link each month.

How to fix links in a live sequence without breaking the flow

Most email platforms let you update template links without pausing the automation. Log into each sequence, click into the link element, and update the destination URL. Save the template. The change applies to any future sends — it won't affect emails already in someone's inbox, but it stops new sends from hitting the broken link.

After updating, send yourself a test of each email from inside the platform and click every link manually. Email clients render HTML differently than browsers, and occasionally a link that looks correct in the template editor resolves to a slightly different URL when the email client processes it. Clicking from an actual test email is the only way to confirm.

One gotcha: some platforms use tracked links that wrap your destination URL in a click-tracking redirect. If the tracking redirect caches the destination, updating the template link doesn't immediately update the cached destination. Check the platform's documentation for how to force a cache refresh, or use the platform's built-in link validator if one exists.

Building a link review into your campaign calendar

Checking active automation links takes about 15 minutes twice a year. Add it to the same calendar slot as your automated review request audit. The combination — live sequences, active campaigns, and review request flows — covers the three places where a broken link costs you real customer contact. You don't need a full site crawl for this check; you only need to open each active automation, click each link, and confirm it lands somewhere useful. That's it.

Your 10-Minute Monthly 404 Audit

A full site crawl takes time and tools. What most business owners actually need is a shorter routine that checks the pages most likely to cost them customers when broken. This takes under 10 minutes and catches the failures that matter.

1. Open Google Search Console → Indexing → Pages → "Not indexed" → look for "404 (Not Found)" in the reason breakdown. Note any URLs that weren't there last month. These are pages Googlebot flagged as broken since your last check.
2. Open a private browser window and paste your Google review link. Confirm it opens the review form directly — not a general profile page, not a search result. If it doesn't open the form, your review requests are broken.
3. Log into business.google.com → Edit profile → Business information and paste your saved website URL into a private window. Confirm it loads a real page, not a redirect chain or an error.
4. Pull a list from Google Analytics of your five most-visited landing pages. Open each in a private window and click the main call-to-action link on each page — whatever that page is asking visitors to do. These are the paths your customers follow most often.
5. Open your most recently sent review request email in your email platform's template editor. Copy the destination URL and paste it into a private window. Confirm it lands on the review form.

If any of these fail, fix the redirect the same day. The customer who hit that broken link during the past month didn't get a second chance — but every customer after you fix it will.

For a wider look at your online reputation and review pipeline, Praising's review management platform runs these checks automatically so you don't have to do them manually each month. Broken review links, response-rate drops, and new review alerts — all in one place without the monthly checklist.

How to Fix 404 Errors in Apache with .htaccess

Apache is the server software running behind a large chunk of small business websites — often hidden inside shared hosting accounts at GoDaddy, Bluehost, DreamHost, and similar providers. If your site runs on Apache, you control redirects through a file called .htaccess, which lives in your site's root directory.

Enabling mod_rewrite

Before redirect rules work, Apache needs mod_rewrite enabled. On most shared hosting, it's already on. If it isn't, redirect rules silently fail — the URL returns 404 instead of redirecting. Test by adding any redirect rule; if it has no effect, ask your host to enable mod_rewrite or add Options +FollowSymLinks near the top of your .htaccess.

Redirecting a single page

The most common fix: you moved a page and need to send visitors from the old URL to the new one.

Redirect 301 /old-page/ https://yourdomain.com/new-page/

The 301 tells browsers and search engines this is a permanent move. Replace /old-page/ with the path after your domain name — no domain included, just the path. Test by visiting the old URL in a private browser window; it should land on the new page.

Redirecting multiple pages with a pattern

If you restructured a whole section — say, moving from /articles/ to /blog/ — you don't want to add one rule per post. Use RewriteRule instead:

RewriteEngine On
RewriteRule ^articles/(.*)$ /blog/$1 [R=301,L]

This matches any URL starting with /articles/ and redirects it to the same path under /blog/. The (.*) captures everything after the prefix; $1 drops it into the new URL. The [R=301,L] flags mean "301 redirect, stop processing other rules."

Setting up a custom 404 page

ErrorDocument 404 /404.html

Add this to .htaccess and create a 404.html file in your root directory. The server sends the file content with a real 404 HTTP status code. If your 404 page shows up but returns a 200 in curl -sI, the ErrorDocument is pointing to a script that strips the status code — fix by returning the 404 status explicitly in that script.

The most common .htaccess mistake

Editing .htaccess while your site runs behind a CDN or caching plugin means the cache keeps serving the old response for minutes or hours after your rule is in place. Clear your site cache and any CDN cache right after adding redirect rules. Test from your phone on cellular data — a connection that doesn't share your office's cached DNS — to confirm the redirect actually resolves.

Multiple .htaccess files can trip you up too. Apache processes them from the directory of the requested file upward to the root, so a rule in a subdirectory .htaccess can override the root file. If a redirect "works everywhere except one section of the site," check whether a subdirectory .htaccess is intercepting the request first.

How to Fix 404 Errors in Nginx Server Config

Nginx handles redirects differently from Apache. There's no .htaccess — instead, redirect rules go into the server block configuration, usually at /etc/nginx/sites-available/yourdomain or inside /etc/nginx/nginx.conf.

Redirecting a single page

location = /old-page/ {
    return 301 https://yourdomain.com/new-page/;
}

The = modifier means this block only matches the exact path /old-page/. Use it for individual page redirects. After editing the config, run nginx -t to check for syntax errors, then systemctl reload nginx to apply changes without dropping active connections.

Redirecting a URL prefix

location /old-section/ {
    rewrite ^/old-section/(.*)$ /new-section/$1 permanent;
}

Without the =, the location block matches any URL starting with /old-section/. The rewrite directive captures the path after the prefix and appends it to the new destination. permanent is equivalent to a 301.

Setting up a custom 404 page

error_page 404 /404.html;
location = /404.html {
    internal;
}

The internal flag means the 404 page can't be requested directly — it only loads when Nginx itself invokes it. Without this, someone could request /404.html directly and get a 200 response, which creates a soft 404 in Search Console.

Testing Nginx redirects

After reloading Nginx, test with curl:

curl -sI https://yourdomain.com/old-page/ | head -3

You should see HTTP/2 301 with a location: header pointing to the destination. Then follow the full chain:

curl -sIL https://yourdomain.com/old-page/ | grep "HTTP"

The -L flag follows redirects. The output should show HTTP/2 301 then HTTP/2 200. If you see two 301 lines before the 200, you have a redirect chain — collapse it into a single redirect going directly to the final destination. Each extra hop loses a small amount of link equity and adds latency.

Tracking 404 Errors in Google Analytics 4

Google Search Console shows which 404s Googlebot hit. Google Analytics 4 shows which 404s your actual visitors hit — including ones from email links, social posts, and manually typed URLs that never showed up in Search Console because a bot never crawled them. The two data sets overlap but aren't the same.

GA4 doesn't have a dedicated 404 report. But if your 404 page has a consistent title or URL path, you can filter for it in Explore.

Building the report

Check what your 404 page's browser tab shows — visit a non-existent URL on your domain and read the tab title. Most sites show something like "Page Not Found" or "404 Error." In GA4:

1. Go to Explore → Blank exploration.
2. Add the dimension Page title (or Page path + query string if your 404 page has a specific path like /404).
3. Add the metric Views.
4. In Filters, add: Page title contains "Not Found" — or whatever your error page's <title> tag says. If the 404 loads at a fixed path, filter on page path instead.
5. Set the date range to the last 90 days and sort by Views descending.

The result is a list of URLs your real visitors hit and found broken — sorted by how often it happened.

What to do with the data

Focus on the top 10 by views. For each URL:

• If a relevant live page exists, set up a 301 redirect.
• If the URL was part of a campaign email, update the link in any still-active automated sequences.
• If the same broken URL appears across multiple traffic sources (organic, direct, social), it probably has external links pointing to it — check Search Console's External Links report for who's sending traffic there.

URLs at the bottom with one or two views are usually typos or bots probing your server. Ignore them — the redirect effort costs more than the traffic is worth.

Setting up a spike alert

In GA4, go to Insights (under Advertising) and create a custom alert: filter by page title containing "Not Found," set a views threshold, and turn on email notification. A spike in 404 views often means a broken link went out in a large email send or a popular account shared an old URL. Catching it the same day lets you fix the redirect before most visitors hit it.

Search Console and Analytics together give you the complete picture: Search Console shows what Google found, Analytics shows what your visitors experienced. Run both reports monthly — they take under 10 minutes combined and catch different failure modes.

When Your Review Management Platform Changes Your Link Format

Most businesses set up a review request link once — they paste it into an email template, add it to their signature, or load it into an automated campaign — and then forget about it. The problem is that review management tools sometimes change their URL structure when they release new features, switch subdomain configurations, or migrate between platform versions. When that happens, every link you sent in the past silently becomes a 404.

This is different from a normal broken page. Your website didn't change. Your platform changed something on their end, and now the link you've been sending to hundreds of customers over the past year goes nowhere.

How to spot it

The clearest signal: your review click rate drops noticeably while your open rate stays the same. People are opening the email, but nothing happens when they tap the review link. Most of them won't report it — they'll just close the email and move on.

A secondary signal: in Google Analytics 4, you see referral traffic that ends up on your 404 page, coming from your email ESP's tracking domain (Mailchimp, Klaviyo, Constant Contact, etc.). The link was clicked, forwarded to your domain, and landed on nothing.

What to fix

Before anything else, click your own review request link from a fresh private browser window. Don't test from an admin account — test the same link your customers receive. If it returns a 404, you have work to do in three places:

Active email automations. Log into your email tool and update the review link in every automated sequence that contains it. For most businesses, this means welcome emails, post-purchase follow-ups, and feedback requests. Update the link, save the template, then send yourself a test email and click through to confirm it resolves to a real page.

Scheduled campaigns. If you have upcoming campaigns queued with the old link, edit them before they go out. A 404 in a one-time campaign is a fixable mistake; a 404 in an evergreen automation is a slow drain that continues losing reviews every day until someone catches it.

External references. Check your website's contact page, your email signature, any social media bios that link to your review page, and any PDF materials you've distributed. These are easy to miss because they're not in your email tool.

Preventing it going forward

Test your own review request flow at least once a month — it takes under two minutes. When a review management platform announces an update, check the changelog for any mention of URL format changes before the update goes live. If your platform generates a short tracking link rather than a direct URL to the review platform, those are generally more stable across migrations because they're a redirect layer you control.

The best protection is knowing that this failure mode exists. Most business owners assume the tools they set up continue working exactly as configured indefinitely. Review links break more often than any other outreach link — because they point to third-party platforms that change independently of your own site. Building a monthly click-test into your routine catches these breaks within 30 days instead of discovering them six months later when a Google review audit reveals your collection rate quietly collapsed.

404 Errors That Hit Service Businesses Hardest

Technical guides about 404 errors usually talk to developers. But the businesses that get hurt most by broken links aren't the ones with in-house engineering teams — they're restaurants, dental offices, contractors, gyms, and salons. These businesses have websites maintained by a mix of whoever set them up two years ago, the owner's cousin who "knows computers," and a stream of different marketing tools that each add links you might not even know exist.

The bad part: service businesses also have the most time-sensitive conversion moments on the web. A customer just finished a great meal, or walked out of a great haircut, or had a painless dental cleaning. They're inclined to leave a review right now, while the goodwill is fresh. A broken link in that moment doesn't just cost you one review — it cost you the goodwill that won't still be there tomorrow.

Restaurants and food businesses

Restaurant websites break in specific ways that other businesses don't see.

Online menu links in Google Business Profile: Restaurants often link their menu directly from their Google Business Profile. When the menu PDF gets reorganized or the menu page URL changes during a website refresh, that GBP link breaks. Customers searching for your hours and menu on Google see a "Menu" button that goes nowhere. Most of them don't bother navigating to your main site — they close the tab and look at a competitor.

Check this by opening an incognito window, searching your restaurant name, and clicking every link in the Knowledge Panel on the right side of the results page. Menu, reservations, order online — click each one and confirm it loads.

Reservation embed dead links: Third-party reservation platforms (OpenTable, Resy, Yelp Reservations) generate embed codes with specific URL parameters. When the platform updates their embed format or you switch between systems, every page where you embedded the old code now shows a broken widget — or worse, an invisible broken element that just renders blank. Customers who try to make a reservation and see nothing will assume you don't accept online reservations, not that you have a technical problem.

Delivery platform redirect pages: Some restaurants build a page on their site that redirects to their DoorDash or Uber Eats menu. Those pages often get forgotten. The delivery platform listing changes, the redirect breaks, and the "Order Online" button on your website goes to a 404. Your own website is actively losing you orders.

Review request emails with season-specific content: Restaurants frequently link to seasonal pages or limited-time offer pages in review request emails. After the promotion ends, the page gets deleted. Six months later, review request automations are still sending with a dead link inside.

The fix for restaurants: after any website update, click every button in your Google Business Profile, your reservation system, and your online ordering links from an incognito window before reopening for dinner service. It takes four minutes.

Healthcare and dental practices

Healthcare websites carry a specific 404 risk: the wrong broken page can violate patient trust in a way that's very hard to recover from.

Patient portal login links: Healthcare practices often link their patient portal from multiple places — their website's header, the footer, a dedicated page. When the portal provider updates their login URL or the practice switches to a new EHR system, those links break. A patient trying to access their test results or appointment history hits a 404. They're not going to assume it's a technical issue. They're going to wonder whether the practice is professionally run.

New patient form URLs: Dental offices and medical practices link intake forms from their appointment confirmation emails. These forms often live on the EHR system's domain, not the practice's own website, which means the practice has zero control over whether those URLs stay stable. When the EHR provider updates their form infrastructure, your old links break. New patients arrive at their appointment without having completed paperwork, creating delays for everyone.

Appointment booking page after switching booking systems: This is the most common healthcare 404. A practice was using one scheduling system, switched to another, and someone updated the main "Book an Appointment" button on the website — but not the appointment links in email signatures, the Google Business Profile, the Facebook page bio, or the old blog posts that mentioned booking. All of those still point to the defunct system.

The review collection angle: healthcare reviews depend almost entirely on post-appointment outreach. A patient who had a good experience is sent a follow-up email asking for a review. If the review link in that email returns a 404, the request has failed invisibly. The practice sent the email, the patient opened it, nobody left a review, and no one knows why. Monthly testing of the review link in your actual post-appointment email template is the only way to catch this.

HIPAA compliance pages: Practices are required to link their Notice of Privacy Practices from their website. When these pages get updated or moved, old links from external sources (insurance company referral pages, Google Business Profile) go dead. It's not just a ranking issue — it's a compliance documentation gap.

Home service contractors

Contractors — plumbers, electricians, roofers, HVAC companies — have a pattern of 404 errors that comes from how they manage seasonal content and location-specific pages.

Expired seasonal service pages: A roofing company publishes a page for "Spring Roof Inspection Specials" with a form to book a free inspection. The season ends and someone deletes the page. The page got indexed by Google, was linked from their social media, and picked up a few backlinks from local directory sites. Now it returns a 404, the backlinks are dead, and anyone who bookmarked it after the promotion ended gets nothing when they try to book the following spring.

Don't delete seasonal pages. Either redirect them to a permanent service page or leave them live year-round with the promotion removed.

Location pages after scaling back service areas: A plumber expands service areas, builds location-specific landing pages for each city, and runs ads to those pages. Two years later, they pull back from three markets. The pages get deleted. The local links that were built to those pages, the customers who bookmarked them, and the Google cache of those URLs all now hit 404s.

Before-and-after portfolio pages: Contractors live and die by project portfolios. When they reorganize their website, individual project pages often change URLs or get consolidated into gallery slideshows. Every external link to an old "Bathroom Remodel in Naperville" page now hits a 404.

Estimate and quote request form pages: Contractors often use standalone form pages from tools like JotForm, Typeform, or their CRM's form builder. These URLs are not on the contractor's own domain, which means the contractor has no visibility into whether those URLs are still valid. When the form provider restructures their URL system or the contractor's subscription lapses, the quote request form stops loading. Customers who want to get an estimate hit a dead link and call a competitor instead.

For review collection, contractors are especially dependent on post-job outreach because their customer relationships are transactional and seasonal. A homeowner who just had their roof replaced won't be thinking about leaving a review six months later — they need to be asked within a week of the job finishing. If that review request email contains a broken link, the window closes permanently.

Fitness studios and gyms

Fitness businesses have high member turnover and frequent schedule changes, which creates a constant churn of links that go stale.

Class booking embed links: Studios embed booking widgets from platforms like Mindbody, ClassPass, or Vagaro. These widgets use session tokens and platform-specific URLs. When the platform updates their embed system — which happens more often than most studio owners realize — the embed stops working and the class schedule page shows either nothing or an error state that's easy to mistake for a deliberate design choice.

Intro offer pages: Gyms and studios frequently build landing pages for first-month offers, trial memberships, or summer specials. These pages are advertised on social media, in Google ads, and in referral emails from existing members. When the promotion ends and the page gets deleted, the referral links sent by members and the ad campaign URLs all go to 404s. The gym loses new member sign-ups because the landing page worked fine when the offer was active, but nobody redirected it to the regular membership page when the offer ended.

Member portal links after switching CRM systems: When a studio switches from one member management system to another, every link sent to existing members in the past — class reminders, billing notices, account management links — now points to the old system. Members trying to update their payment method or check their attendance history hit dead pages.

For review collection: gyms and studios often send review requests immediately after a member hits a milestone (first month completed, first class attended). If the review link in that message returns a 404, the studio loses the review and the member moves on without ever knowing there was a problem.

The principle behind all of this

Every type of service business has the same underlying 404 pattern: a link was created at a point in time, something changed (platform, season, content strategy, service area), and nobody traced back all the places the old link was still living.

The links that matter most for a service business are the ones sitting inside its review request flow. Your review collection depends on motivated customers clicking through in the 24-to-48-hour window after a positive experience. A 404 in that flow kills the conversion at exactly the moment your customer was most likely to follow through.

Fix whatever 404s are blocking the action closest to revenue first. For most service businesses, that's the review request link. After that, fix the booking form. Then the menu or portfolio. Then work backward through the rest.

Fixing 404 Errors on Custom Review Collection Pages

Many businesses build a dedicated page on their own domain to collect reviews — a simple page at something like /leave-a-review or /share-your-experience, with a headline and buttons linking out to Google, Yelp, or Facebook. You control the URL, the copy, and the hosting. Which also means you control whether it breaks.

The common failure pattern: the page was created for a specific campaign or as part of a site launch, lived at one URL, then got swept up in a redesign. A new designer built a fresh review page at a different URL, but nobody redirected the old one. Every QR code ever printed, every email ever sent, every table tent ever made — they all point to the old URL, which now returns a 404.

What to check on your current review landing page

Visit it from a private browser window — not your regular browser where caching can mask problems. Confirm it loads cleanly and loads fast. Then click each button on the page (the Google link, Yelp link, any others) and confirm each destination actually loads the review form, not an error page or an empty screen.

After that, check mobile. Scan your own QR code on your phone, or manually type the URL on a mobile device. A page that renders fine on desktop but wraps its layout incorrectly on a phone functions as a de facto 404 for most customers — they won't scroll to find a broken button, they'll close the tab.

After a site redesign, run this check before anything else

Search your CMS for the old review page URL. Update every internal link pointing to it. Then check the places that live outside your CMS: email templates, SMS automations, your Google Business Profile, any print materials you've distributed, and your social media bio links. These references survive site changes because they're not in your CMS — nobody thinks to update them when the site gets rebuilt.

If the URL changed but the content is the same, set up a 301 redirect from the old path to the new one immediately. Don't wait to see if anyone notices the break.

Short redirect pages are more durable than platform-generated links

Some businesses use the long, platform-generated review link from Google or Yelp directly in their outreach. Those links work, but they're not stable — Google's review link format has changed at least twice in recent years, and any time the format changes, old links stop working. A short redirect on your own domain (yourdomain.com/review) that points to your current Google review link is far more resilient: when Google changes the format, you update one redirect and every printed card, email, and QR code in circulation is fixed instantly.

When Third-Party Review Widgets Return 404 Errors

Many businesses embed review widgets on their websites — a carousel of five-star quotes, a floating badge showing their average rating, a live feed of recent Google reviews. These widgets pull data from an external service and render it on your page. When that connection breaks, the widget goes silent.

The silence is the problem. A review carousel whose data source returns a 404 doesn't throw a broken image or an error message — it typically renders nothing, or collapses to zero height. Visitors above and below that area on the page see normal content. Nobody knows anything is missing. But you're losing the social proof the widget was supposed to deliver, on every page where it appears.

The four most common causes

Your review management platform subscription lapsed or your plan tier changed, and the widget feature is no longer included. The platform updated its embed URL format, and your old script tag or iframe no longer matches the current URL structure — this happens after platform migrations, version upgrades, or domain changes. The platform migrated to a new subdomain, which is common after acquisitions. Or your SSL certificate expired and the page is serving mixed content — the widget script is still referenced via http:// in an otherwise https:// page, and the browser blocks the mixed-content request.

How to confirm a widget is actually broken

Right-click the area where the widget should appear and open your browser's developer tools. Check the Elements panel — if the widget container has zero height or is entirely empty, something went wrong. Then open the Network tab, reload the page, and filter for status codes in the 400 range. If any request from the widget's domain shows a 404 or 403, that's the source of the problem.

Fixing each cause

For a lapsed or downgraded subscription, restore the plan and the widget should resume on its own. For a URL format change, log into your review platform and regenerate the embed code — most platforms automatically update the embed to the current URL format, so replacing the old code with the new one fixes the break. For an SSL mixed-content issue, update the script tag from http:// to https://, or contact the platform if they haven't enabled SSL on their widget domain.

For a platform that went out of business or substantially changed its feature set, you'll need to switch widget sources entirely. Any review management tool that pulls directly from your live Google Business Profile data rather than a cached snapshot will be more stable across platform changes — the widget renders from your actual reviews, not from a hosted dataset on the platform's own servers.

Check widget load status monthly

Load your page, open the browser developer tools, go to the Network tab, and confirm no 404 responses appear for widget-related requests. Do this for every page on your site that embeds a review widget or rating badge. It takes about three minutes per page and catches breaks before they drain weeks of social proof from your site without anyone noticing.

Monitoring 404 Errors with Bing Webmaster Tools

Google Search Console handles most 404 monitoring for the majority of business websites, but Bing Webmaster Tools gives you a separate crawler's view of broken pages — and it's worth checking, particularly if your business serves customers who skew toward desktop search, where Bing holds a larger share of the market than most analytics dashboards suggest.

Setting up Bing Webmaster Tools takes under five minutes if you're already verified in Google Search Console. Bing supports a Google Search Console import at webmaster.bing.com — authenticate with a Microsoft account, click "Import from Google Search Console," and Bing pulls your verified properties without requiring any new code on your site.

Once verified, navigate to Reports then Page Not Found (404) in the left sidebar. The report lists URLs Bing's crawler tried to load and received a 404 response for, with crawl attempt counts alongside each entry. A high attempt count on a specific URL usually means an external link or an unupdated sitemap entry is still pointing there — the same root causes you'd fix for Google, but sometimes surfaced on a different schedule by Bing's crawler.

What's different about Bing's 404 report

Bing classifies broken pages by how it discovered them: crawl, sitemap submission, or manual URL submission. This categorization speeds up triage. A URL listed under "sitemap" means you explicitly told Bing to crawl it — usually because you removed the page without updating your XML sitemap. Fix the sitemap entry first, then set up the redirect.

Bing also flags soft 404s: pages that return a 200 status but contain no substantive content. If your CMS generates empty category archive pages, discontinued product listings, or tag pages with zero posts, Bing may classify those as soft 404s. Google does too, but the two crawlers sometimes surface different pages because they visit on different schedules and weight content signals differently. Comparing both reports each month gives you a complete map that neither tool produces alone.

After setting up a redirect for any URL Bing flags, use the URL Inspection tool in Bing Webmaster to request recrawl rather than waiting for Bing's natural crawl schedule. On small business sites, Bing's revisit frequency can be lower than Google's, so a manual recrawl request shortens the time between your fix and the report clearing.

The practical benefit of checking both tools: a 404 that disappeared from Google's report may still be active in Bing's, or vice versa. Keeping both clean takes about five extra minutes per month and gives you the full picture of how customers find your site — not just through one search engine.

How Fixing 404 Errors Affects Your Review Collection Rate

Most businesses tackle 404 errors for SEO reasons: recover link equity, clean up crawl budget, improve rankings over time. Those outcomes matter. But for any business actively collecting customer reviews, a broken link in your review request flow has an immediate, countable impact on review volume — one that shows up in your review count long before it shows up in search rankings.

The math is direct. If you send 150 review request emails per month and 20% of recipients click through, that's 30 potential reviews per month. If your review link has been returning a 404 for 90 days, you've lost roughly 270 reviews — customers who were ready to leave feedback, hit a wall, and moved on. You don't get to recover those. Each customer is a one-time window for an unprompted public review.

Measuring the gap before and after

To put a number on the damage after you fix a broken review link, run a quick before-and-after comparison:

1. Find when the link broke. Check your review platform's activity log, your email tool's click-rate history, or Google Analytics for the date your review-related click rate dropped while open rate stayed flat. That's your break point.
2. Calculate your pre-break baseline. Take total reviews collected in the 90 days before the break point and divide by
3. That's your monthly rate when things were working.
4. Calculate your during-break rate. Divide total reviews during the broken period by the number of months affected.
5. Compare. The gap between those two numbers is the review volume the broken link cost you.

Most businesses find the loss runs 40 to 70 percent of their baseline during a broken-link period. Customers still leave the occasional unprompted review, but the systematic request-driven flow stops almost entirely.

Measuring the recovery

After fixing the link, expect two to four weeks before your collection rate returns to baseline. Customers who received requests during the broken period have already moved past the moment of motivation — you're starting a fresh cycle from the fix date forward.

Track weekly review counts for the first month after the fix. If the rate doesn't rebound to pre-break levels within six weeks, check two things: whether your active automation sequences have the updated link (old templates may still be sending with the broken URL), and whether your review platform account has any service interruption. A slow recovery usually means the fix was applied to new sends but existing automations are still running with the original broken destination.

For ongoing visibility into your review request pipeline — including automatic checks that your destination URL resolves correctly — Praising's review management platform monitors your active flows and flags a broken review link in hours, not weeks later when a review audit reveals the gap.

When Your Google Review Link Returns a 404

Google review links break more often than most business owners expect. The link you set up six months ago — embedded in email templates, printed on customer receipts, shared in QR codes — may have quietly stopped working. Google updates its review link format periodically, and an old link that redirected fine last year can return a 404 this year with no warning.

Here's how to confirm the problem, get a fresh working link, and prevent the same break from repeating.

How Google Review Links Break

Google has changed its review link format multiple times since it launched Google My Business. Links containing g.page, plus.google.com, or older patterns like maps.google.com/?cid= may stop resolving correctly as Google retires legacy formats. Three situations account for most broken Google review links.

Google deprecated your link format. If your review link was set up more than two years ago, the format it used may no longer be supported. Google's current review link format resolves to https://search.google.com/local/writereview?placeid=XXXXXXXX. Older formats either redirect inconsistently or return a 404 outright.

Your Google Business Profile was suspended and reinstated. A suspension sometimes breaks the place ID tied to your listing. After reinstatement, the link may need to be regenerated from your current GBP dashboard rather than using a saved link from before the suspension.

You have duplicate or merged listings. If Google merged two listings for your business, the old place ID may point to a deactivated entry. Customers who tap the old link hit a 404 or land on a profile that no longer corresponds to your active business.

Getting a Fresh Review Link

Log into your Google Business Profile at business.google.com. Select the profile you want a review link for. Click Ask for reviews in the dashboard. Google shows a short URL in the format https://g.page/r/XXXXXXXXXXXXXXXX/review. Copy it.

Open a private browser window and paste the link. It should open the Google review form directly — the star selector and a text box. If you land on your profile's overview page instead of the form, the link is routing incorrectly. If you get a 404, there's a deeper issue worth checking with Google Business Profile support.

Once you have a working link, update it everywhere it appears:

• Email and SMS review request templates
• Automated review request sequences
• Your Google Business Profile website field and booking button
• QR codes on receipts, table tents, menus, and signage
• Your website's review widget, footer CTA, and any dedicated review page
• Social media bio links

QR codes need separate treatment. A QR code encodes the URL at the moment it's printed. Changing your Google Business Profile settings does nothing to codes already in circulation — they still point to whatever URL was embedded when they were generated. The most resilient approach is to encode a short URL you control (yourdomain.com/review) that redirects to your current Google review link. When Google's format changes, you update one redirect and every card, receipt, and sign in circulation works again without reprinting anything.

Verifying the Fix

After updating your links, confirm any redirect on your own domain is working:

curl -sIL https://yourdomain.com/review | grep -E "HTTP|Location"

This follows the full redirect chain and shows each hop. You should see a 301 from your domain to Google's URL, then a 200 from the review form endpoint. A 302 instead of a 301 means change it — a temporary redirect doesn't pass link equity and can behave inconsistently in some email clients.

For email templates, send yourself a test from an address not signed into Google. Tap the link on your phone. Confirm you land on the review form with the star selector visible and the text box responsive. That full path — on a phone, not signed in as the business owner — is what your customers experience. A link that opens the right page but doesn't load the form input is still a broken experience from a conversion standpoint.

Why Review Links Keep Breaking

The fundamental problem is that Google controls the link format, not you. Every link that goes directly to a Google URL is one update cycle away from breaking. Building a durable review link means routing all outreach through a short URL you control.

Set up a simple redirect: yourdomain.com/review points to your current Google review link. That becomes the one address you put in email templates, on printed materials, and in every automation. When Google's format changes, you update one redirect destination and everything downstream updates automatically. For multiple locations, create one redirect per location — /review-downtown, /review-eastside — each pointing to that location's current link.

Review management tools like Praising.ai take this further by actively monitoring your review request endpoints. Instead of discovering a broken link because a customer mentions they couldn't leave a review, you get an alert on the day the link breaks — while the damage is still limited to a few hours rather than weeks of missed reviews.

How to Check If Your Review Request Links Are Working Right Now

Most businesses find out their review link is broken when a customer mentions it — which means the link was already broken for days, weeks, or longer before anyone caught it. A simple check takes under five minutes and should happen any time you update your website, switch platforms, or notice that response rates have dropped without an obvious reason.

The 5-Minute Link Audit

Step 1: Open a private browser window. This clears cached sessions and auto-redirect behavior that can make a broken link look fine on your own device. Incognito mode in Chrome or Private mode in Safari both work.

Step 2: Test your Google review link directly. Paste the URL you send in review request emails — the one starting with g.page/r/ or search.google.com/local/writereview — into the address bar. A working link opens the Google review form: a star rating selector and a text field. If you land on a generic profile overview instead of the form, the link is alive but not routing correctly. If you get a 404, the link is dead.

Step 3: Check your short redirect if you have one. If you set up yourdomain.com/review as a shortcut, test that URL too. A short redirect can work while the underlying Google URL it points to is broken. Open the short URL in the same private window and confirm you land on the review form.

Step 4: Test from a phone. Google's review links behave differently on mobile than on desktop. A link that works in Chrome on a laptop may open the Google Maps app on a phone, landing customers on your profile overview instead of the prompt to write a review. Text the link to yourself and tap it to confirm the behavior matches what you expect.

Step 5: Click through from the actual email. Open the email template you send customers and click the review link from inside it. Many email clients and marketing platforms apply tracking wrappers that can break redirect chains. The only reliable test replicates exactly what your customer does — clicking a link in a delivered email, not previewing a template.

What to Do When a Test Fails

If any step above fails, the fix depends on where the link breaks:

• Google URL is dead: Log into your Google Business Profile, generate a fresh link via Ask for reviews, test it in a private window, then update it everywhere it appears — email templates, automated sequences, QR codes, and your website.
• Short redirect is broken: Log into your redirect manager (your website's plugin, Bitly, or whichever service you use) and update the destination URL. One change fixes every place the short link appears.
• Email link fails: Update the link inside your email platform's template and send a test to a real inbox before turning campaigns back on. Template previews don't always reproduce real delivery behavior.

Scheduling This Check

A review link that worked last month can break this month without you changing anything. Google updates its link formats without warning. Building the check into a routine costs less time than a single customer complaint costs in reputation.

• Add a calendar reminder for the first of each month: "test review link."
• After any website update or platform migration, add link testing to your post-deploy checklist.
• Use a review management platform that monitors your review endpoints automatically and alerts you when one stops working — the only approach that catches the break on day one, not after a customer reports it.

For businesses running active review campaigns, broken links aren't a minor inconvenience. A week of broken links during a busy period means dozens of reviews that never happened. Those reviews don't come back after the link is fixed. Catching the break fast — through a reputation management strategy that includes link monitoring — is the difference between a brief gap and a permanent hole in your review history.

404 Errors You Did Not Create: Noise vs. Real Problems in Search Console

One of the more confusing things that happens when you start digging into your Google Search Console 404 report: you find URLs that clearly were never pages on your site. Not old pages that got deleted or moved — just random paths, like `/wp-admin/` or `/phpmyadmin/` or strings like `/page/undefined`. Your site returns 404 for all of them, which is correct behavior. But they show up in your error report, and you're not sure whether you need to do anything about them.

The short answer is: in most cases, no.

What creates "noise" 404s

Most sites receive thousands of automated requests from bots and crawlers every month. Security scanners probe for common vulnerability paths. Content scrapers hit random endpoints. Old search engine crawlers try URLs based on patterns they have seen on other sites. WordPress bots try `/wp-login.php` on every domain they find, regardless of whether WordPress is involved.

Every one of these hits creates a 404 on your server. Most of them never reach Search Console because Googlebot does not generate them. But some do appear in GSC because of:

Stale backlinks with typos. A site that linked to you years ago may have mistyped your URL. If that external site has decent authority, Googlebot follows the link and hits a 404 on your end. The URL looks strange — maybe a doubled path like `/services/services/remodeling` or a slug that is close but wrong.

Old sitemap entries cached by third parties. If your site was listed in a directory that cached your old sitemap, their crawlers may still be hitting URLs from the old structure. You redirected those pages long ago, but the third-party crawler keeps flagging the original path anyway.

Social media crawlers following broken links. When someone shares a broken URL on social media, those platforms crawl the URL to generate a preview card. The 404 shows up in your server logs and sometimes in linked-site data in GSC.

How to tell signal from noise

The practical test: would a real customer ever type or click that URL?

• `/wp-admin/` on a site that does not run WordPress — noise. Ignore it.
• `/services/plumbing` on a site that had a plumbing services page before a redesign — real. Fix it with a redirect.
• `/contact-up` from a directory that mistyped `/contact-us` — worth checking. One redirect fixes the directory link and Googlebot stops flagging it.

In Search Console's page indexing report, filter the 404 list by the "Discovered by" column. URLs Googlebot found by following links on other sites are worth investigating. URLs with no linking source are usually bot noise and safe to ignore.

If you see hundreds of unfamiliar 404 paths, pull the external links list from GSC (Links → Top linking sites), check Ahrefs Webmaster Tools, or run a quick export. Real customer-facing 404s almost always trace back to a real source: a citation directory, an old email campaign, a QR code in print, or a social post. Random paths with no linking source are bot traffic.

When noise 404s are worth addressing anyway

Two situations where even noise 404s deserve a second look:

When the path matches a common customer expectation. If a significant number of visitors type `/book` or `/schedule` expecting a booking page but you do not have one at that path, setting up a redirect to your actual booking page is low-effort and captures real intent. Check your analytics for 404 exits on those paths to see whether real people are hitting them.

When a high-authority site has the wrong URL for one of your pages. That 404 quietly drains link equity you earned. The path shows up in GSC with a recognizable referring domain. One redirect to your most relevant current page recaptures that value — and you never have to contact anyone.

For review collection specifically: if your old review page URL (`/reviews`, `/testimonials`, or a custom path) shows up in your 404 report with real referring links or real traffic, treat it like any other high-priority broken page. Review request emails that were sent months ago may still be driving clicks to the old address. A redirect makes every past email still functional — potentially recovering requests that have been bouncing unnoticed for months.

What you do NOT need to do

You do not need to create pages for every 404 path in the report. You do not need to contact websites that have the wrong URL and ask them to update it — a 301 redirect handles this automatically. You do not need to block bots from hitting 404 paths, because blocking legitimate crawlers causes more problems than it solves.

The one thing worth doing monthly: filter the GSC 404 report to "Discovered: Googlebot" and sort by impressions. Any URL with more than a handful of impressions got there because real searches matched it, which means real searchers saw a 404 result in their search results. That is your highest-priority fix list.

404 Errors and Local SEO: The Hidden Cost for Small Businesses

Local businesses face a specific version of the 404 problem that national brands rarely deal with. When a plumber in Austin or a dentist in Charlotte has a broken URL, the damage shows up in places that directly hurt their Google Maps ranking and their ability to collect reviews.

Why local citations make broken links more expensive

Your business is listed across dozens of directories: Google Business Profile, Yelp, Bing Places, Apple Maps, local chamber directories, HomeAdvisor, Angi, and the rest. Most of those listings include a link to your website. If you redesign your site and forget to set up redirects, every one of those directory links breaks at the same time. That's not one 404 — it's dozens of referral sources all dead-ending at once.

Search engines use citation consistency as a local ranking signal. A directory linking to a dead page on your site sends a different signal than one linking to a working, relevant page. It doesn't mean Google will immediately drop your rankings, but over time, dead citation links mean missed referral traffic and a weaker signal on the pages those links were supposed to support.

Google Business Profile website links break silently

When someone finds your business on Google Maps and clicks "Website," they're using the URL you entered in your Google Business Profile settings. If you changed your URL structure and didn't update GBP, that click goes to a 404.

This is invisible from inside GBP — there's no warning that the website field contains a broken URL. You have to test it manually. Open Google Maps, search for your business name, click the Website button, and confirm you land on a working page. Do the same for the appointment link if you have one configured.

If either URL is broken:

1. Log into your Google Business Profile at business.google.com.
2. Click Edit Profile, then Contact.
3. Update the website URL to the correct current page.
4. Save and test the link from Google Maps within a few minutes.

Also check your "Book an appointment" or "Order now" link if you use them — these are set separately from the main website field and break independently.

Local landing pages after a redesign

Many local businesses have city-specific or neighborhood-specific landing pages: /plumbing-services-austin, /emergency-dentist-brooklyn, /catering-chicago. These pages accumulate backlinks from local directories and often rank in local searches. When a site migration or redesign removes them without redirects, all that local authority disappears.

Before any redesign, export your full URL list from Google Search Console. Filter for URLs with more than 10 impressions in the past 90 days. Every URL on that list needs either a redirect to the updated equivalent page or confirmation that the new URL is already live. This matters especially for service-area pages, which rarely get a second chance once local citation sources move on.

Your review request link is a local ranking signal too

The link you send customers to leave a Google review is almost always a fixed URL — either a short link to your Google review form or a custom-branded URL that redirects to it. When this URL breaks, it doesn't just stop reviews from coming in. It cuts off a stream of traffic that is specifically high-intent: people who already had a good experience with your business and were willing to take action.

A customer who just visited your shop and clicked your review link is as motivated as any visitor you'll ever send to your site. A 404 at that moment is a broken promise to someone who was already doing you a favor. Check this link weekly if you're actively running a review collection campaign. If you use an automated tool like Praising.ai to send review requests, confirm that the destination URL it uses resolves to a live page — broken destination links in automated campaigns can quietly drain your response rate for weeks before anyone notices.

The NAP consistency check most businesses skip

NAP stands for name, address, and phone number — but citations also include your website URL. If your address changed, your URL structure changed, or you moved from HTTP to HTTPS, your citations may point to a mix of old and new URLs. Run your business name through a free citation checker like BrightLocal's listing scan or Moz Local and look at which URL each directory has on file. Any directory pointing to a 404 is worth updating directly, not just redirect-patching, because some directories display a "Website" button that uses the stored URL even after you've redirected it.

This takes about 20 minutes once a year and prevents a slow accumulation of dead citation links that most local businesses never know they have.

What a Broken Review Link Actually Costs You in Star Ratings

Most business owners think of a broken review link as a technical inconvenience. Fix it, move on. But the damage doesn't disappear when you restore the link — it accumulates over the weeks or months the link was down, and it shows up directly in your star rating.

Here's how to calculate what you've actually lost, and why catching breaks early matters more than most SEO guides let on.

The 48-Hour Window (and Why Missing It Costs More Than You Think)

Customer motivation to leave a review follows a predictable decay curve. Research across hospitality, healthcare, and local services consistently shows the same pattern: the highest willingness to write a review happens within the first 24–48 hours after a positive experience. By day 7, that motivation has dropped sharply. By day 14, the chance of converting a satisfied customer into a written review is a fraction of what it was right after the visit.

When your review link returns a 404 during that window, you're not delaying the review — you're losing it. Customers who hit a dead link in the first 48 hours almost never circle back once the link is fixed, even if you send a follow-up. The moment passed. They moved on.

A restaurant that serves 150 customers per week and sends automated review requests might normally convert 12–18% of those into reviews. That's 18–27 new reviews per week on a working pipeline. A broken link for two weeks doesn't pause that count — it removes it. Roughly 36–54 reviews just don't exist that month.

Running the Numbers for Your Business

The calculation isn't complicated, but most businesses never do it:

Step 1: Find your baseline conversion rate. Look at your last three months of review volume (new reviews per month) divided by the number of customers you served. For a dental practice doing 300 appointments per month and gaining 45 reviews, that's 15%.

Step 2: Estimate the break duration. If you discover the link was down for 21 days, and you normally serve 300 customers per month, roughly 210 customers received a broken link during that period.

Step 3: Calculate missed reviews. 210 customers × 15% baseline rate = 31–32 reviews that should exist but don't.

Step 4: Translate that into star-rating impact. Here's where it gets uncomfortable. If your current listing has 80 reviews averaging 4.5 stars, adding 31 reviews at your typical quality (let's say 90% of them would have been 5-star) takes you from 80 reviews to 111 reviews — and potentially pushes your average up to 4.6 or 4.7. The reverse is also true: you're not just missing the count, you're missing the positive signal those reviews would have sent to Google's local ranking algorithm.

What Platform-Specific Review Volume Looks Like

The calculation above uses percentages, but it's useful to know what real review accumulation rates look like by business type. These aren't invented — they're compiled from publicly available case studies and industry benchmarks across thousands of small businesses:

Restaurants and cafes: 8–15 reviews per 100 transactions when active review collection is running. A busy brunch spot doing 500 covers on a weekend can realistically gain 20–30 reviews per week with a working collection pipeline.

Dental and medical practices: 12–20 reviews per 100 appointments, with post-appointment text requests outperforming email by roughly 2:1. A four-chair dental practice with 40 appointments per day can generate 40–60 reviews per month on a healthy pipeline.

Auto repair and service businesses: 10–18 reviews per 100 vehicle-out events. Customers are often more motivated to leave reviews after repair work than after routine maintenance — a pattern worth understanding for scheduling review requests.

Retail and specialty stores: 3–8 reviews per 100 transactions, with the variance explained almost entirely by whether customers receive a prompt. Unprompted retail reviews are rare; prompted reviews convert at close to the same rate as service businesses.

When your review link breaks, multiply your daily customer volume by the low end of these ranges, multiply by the number of days the link was down, and you have a conservative estimate of reviews you can't recover.

The Star Rating Math That's Easy to Overlook

Star ratings don't move uniformly. Because Google's local algorithm weights recency, a period of 0 new reviews isn't just neutral — it's slightly negative compared to a period of steady inflow.

Here's a concrete example. A plumbing company with 60 reviews averaging 4.4 stars breaks its review link in September. By the time they notice in October (a six-week break), they've missed approximately 24 reviews that would have arrived based on their historical rate. Their nearest competitor, who has 45 reviews but has been gaining consistently, now has 63 reviews and averaging 4.6 stars. The plumber's listing is stagnant; the competitor's is growing. Google's local search algorithm, which considers review velocity as a ranking signal, begins surfacing the competitor more frequently for service-area searches.

None of this happens because the competitor is better. It happens because the plumber's review pipeline had a silent 404 in it for six weeks.

The math is worse for businesses that are earlier in their review journey. If you have 20 reviews averaging 4.2 stars and you miss 15 reviews that would have been five-star, your trajectory toward the 4.5+ threshold that unlocks better local pack visibility is simply delayed. You can't recapture those reviews from the past.

How to Measure the Actual Break Date

When you discover a broken review link, your first instinct might be to fix it and move on. Don't. Spend five minutes figuring out when it broke — this tells you how much damage was done and whether a re-engagement campaign makes sense.

Check your email campaign click reports. Most email tools track clicks by link. Open the campaign report for your review request sequence and look for the date when clicks on the review link dropped to zero (while open rates stayed roughly the same). That's your break date. The difference between the break date and today, multiplied by your daily review rate, is your estimated loss.

Check Google Analytics 4. Pull the traffic report for your review landing page path (e.g., /leave-a-review or /reviews). Filter for the date range you're investigating. A sharp cliff in sessions on a specific date confirms the break. If your review link goes directly to Google's review form rather than through a page on your own site, GA won't have this data — use the email click report instead.

Check Google Search Console. Pull the URL Inspection report for any pages in your review collection flow. If Googlebot found a 404 on a specific date, you'll see it in the crawl history. This also confirms whether the broken state was indexed.

Once you know the break date and duration, you have an estimate of affected customers. That number drives the next decision: whether to send a recovery campaign.

Running a Review Recovery Campaign After a Broken Link

Not every 404 break warrants a recovery campaign. If the break lasted less than a week or your customer volume is low, the cost of a campaign (in time, potential unsubscribes, and spam-filter risk) may outweigh the return.

The threshold worth crossing: if you estimate you missed 15 or more reviews, a targeted re-engagement is worth running.

Who to contact. Customers who received a review request email during the broken period and clicked the link are your highest-priority segment — they showed intent. Contact them first, within the same week you fix the break if possible. Customers who opened the email but didn't click are your second tier. Customers who never opened the email are your lowest priority (they didn't engage the first time, and an additional message may just generate unsubscribes).

What to say. Don't explain that your link was broken — this rarely helps and sometimes creates negative associations. Instead, frame it as a simple follow-up: "We wanted to circle back and ask about your experience." Keep it short. One sentence describing your business, one question about whether they'd be willing to share feedback, one clean link to your review form. Under 100 words works better than a long explanation.

When to send. Mid-week, mid-morning in the customer's time zone. Tuesday, Wednesday, and Thursday between 9 AM and 11 AM consistently outperform other send windows for service business review requests.

One follow-up only. Sending more than one recovery message risks harming your deliverability and irritating customers who already decided not to leave a review. One clean re-engagement, sent promptly after you fix the link, is the appropriate response.

Setting Up a Permanent Monitor So This Doesn't Repeat

Free uptime monitoring tools like UptimeRobot and Better Uptime will check a URL every five minutes and alert you within minutes if it stops returning a 200 status. Adding your review collection URL — and every other URL you send in automated emails — takes about two minutes. The alert arrives before any significant damage accumulates.

If you use a review management platform, look for built-in link monitoring rather than relying on a separate tool. Praising.ai tracks the endpoints in your active review request campaigns and flags broken destinations as part of the dashboard — turning a problem you'd normally catch in a customer complaint into something you see before customers do.

The calculation from earlier in this section works in reverse for setting a monitoring threshold: a business that gains 30 reviews per month loses roughly 1 review per day when the pipeline is broken. At that rate, even a weekend-length outage costs 2–3 reviews. For any business where review velocity is actively managed, five-minute uptime monitoring on the review collection URL is the minimum viable safety net.

Switching Review Platforms: The 404 Risk Most Businesses Miss

When a business moves from one review management tool to another — from a platform like Birdeye or Podium to something newer — the broken links that follow are almost never noticed until customers start complaining or response rates quietly drop. This is one of the most predictable 404 patterns in reputation management, and it's almost entirely avoidable.

Here's what typically breaks and how to handle each piece before you switch platforms.

What breaks when you switch

Your review collection short links. Most review platforms generate their own short URLs for sending customers to your review form. A link like getreviews.example.com/YourBusinessName or a custom short URL configured through the old platform stops working the moment you deactivate that account. If those links are embedded in email templates, stored in your SMS platform, printed on table tents, or encoded in QR codes on receipts, every single one becomes a 404 overnight.

Embedded review widgets on your website. Platforms that display your reviews through an embed code usually pull from their own servers. Once you close the account, the widget endpoint returns a 404 or stops loading entirely. Customers who visit your website see a blank box, a broken frame, or a loading spinner that never resolves. Review-heavy pages — your homepage, a testimonials page, or a service-specific landing page — can look broken to both visitors and Googlebot.

Review landing pages. Some platforms create hosted pages for your business (like platform.com/reviews/yourbusiness). If you shared or linked to those pages from your site's footer, your email signature, or your Google Business Profile, those links now return a 404. You didn't create the page, but you own the broken link to it.

Reply confirmation emails. If the old platform sent customers a confirmation after you replied to their review, those emails may include a link back to the platform's review view — which no longer exists after migration.

The pre-switch audit (takes 20 minutes)

Before you deactivate anything:

1. Search your website for the old platform's domain. Run a site crawl or use your CMS search to find every link pointing to the old platform's URLs. That covers embedded widgets, linked pages, and any direct URLs in content.

2. Export your email and SMS templates. Pull every template from the old platform and scan it for review collection links and any links to hosted pages. Copy or note every URL.

3. Search your CMS and email platform. Many businesses have old review request templates in their email marketing tool (Mailchimp, Klaviyo, ActiveCampaign) that still point to the old platform's link format. These are easy to miss because they're not in the review platform itself.

4. List every QR code in circulation. If you have QR codes on physical materials — menus, receipts, business cards, lobby signage — photograph or note what URL each one encodes. If they encode the old platform's short URL directly, those QR codes need to be reprinted unless you set up a redirect layer.

The redirect-first migration approach

The cleanest migration replaces old platform URLs with a short URL on your own domain before the switch. Instead of the old platform's branded link, you use yourdomain.com/reviews and point it at the new platform from day one.

This means every email template, QR code, and physical material keeps working. When you move from the old platform to the new one, you update the redirect destination — not every individual use of the link. One change propagates to everything in circulation.

If you're already past this point and you're dealing with broken old-platform links, create 301 redirects from any URLs you control to the equivalent new destinations. For hosted pages you don't control (the old platform's own domain), you can't redirect — but you can update every place on your own site that linked to those pages.

Tools like Praising.ai are built to handle this migration cleanly. The review collection links it generates route through your account rather than a platform-specific domain, so they stay stable across changes to the underlying routing. If the destination format changes, the short link stays consistent. That's particularly useful if you're migrating away from a platform that gave you a custom short domain tied to their infrastructure — the domain dies when the account does, and there's no redirect path.

For the full process of monitoring Google reviews after a migration, run a complete crawl of your site the first week after switching. Broken widgets and dead platform links are easiest to catch while you still remember every place the old platform's URLs appeared.

Fixing 404 Errors in Google Business Profile Posts

Google Business Profile lets businesses publish posts — updates, offers, events, and product highlights — that appear directly in Google Search and Google Maps results. Each post can include a link to your website. When that page returns a 404, the click goes nowhere.

GBP posts aren't permanent. Google deletes standard posts after seven days, and some post types expire sooner. But the underlying SEO problem is that during the time a post is live, a broken link wastes the click while also sending a weak trust signal — Google can follow those links, and what it finds (or doesn't find) affects how it evaluates your profile's content quality.

Why GBP post links break

The most common cause is a landing page that was updated or replaced after the post was published. An offer post created in June might link to /summer-sale, which was replaced with /sale in August. The post is still visible in your profile (or was recently re-published), but the link goes to a 404.

The second cause is tracking parameters. Some marketing tools append UTM parameters to URLs when scheduling GBP posts. If the URL was malformed during scheduling — a double question mark, a missing ampersand, or a broken encoding — the resulting link returns a 404 even though the base page exists fine.

The third cause is platform-specific redirect rules. Some hosting setups strip trailing slashes or enforce HTTPS strictly, causing posted URLs with slight formatting differences to fail on click.

Finding broken GBP post links

You can't see your GBP post click data in Search Console unless you've set up UTM parameters. The most direct check is manual: open Google Maps, find your business listing, and tap or click each active post to verify its link works. Do this after any website update.

For historical posts, check the Google Search Console URL Inspection tool for any page paths that appeared in your GBP post history and now show 404 in the Coverage report.

Fixing it

If the post is still live and the original destination page was replaced:

1. Edit the post in your Google Business Profile dashboard (Posts, then Edit).
2. Update the button URL to point to the current live page.
3. Publish the updated post.

If the post has expired but the underlying 404 was captured by Googlebot, set up a 301 redirect from the old URL to the current equivalent. This matters most for product or service URLs that appear across multiple posts over time.

For ongoing management, keep a simple list of every URL you use in GBP posts. Before posting a link, paste it into a browser to confirm it returns 200. One minute of testing prevents a situation where a post runs for a week pointing at nothing.

If your business posts frequently or manages multiple locations, a local SEO guide for Google Maps covers the broader context of keeping your GBP signals clean — post link quality is one part of a larger pattern that Google uses to evaluate profile trustworthiness and local ranking eligibility.

Third-Party Scheduling Tools and the 404 Errors They Create

Most 404 error guides focus on pages you built yourself. But for service businesses, a significant portion of customer-facing traffic goes through third-party scheduling tools — Calendly, Acuity Scheduling, HubSpot Meetings, SimplyBook.me, Square Appointments — hosted on the provider's own domain and embedded or linked from your site and emails.

When these links break, the 404 isn't on your server. But the customer sees a dead end from your email or your website, and the blame lands on you.

Why third-party scheduling links break

Plan changes. Downgrading or canceling a scheduling subscription often deactivates booking links immediately, or after a short grace period. If you shift from a paid plan to a free tier, or pause a subscription while comparing alternatives, your old booking URL may stop working overnight. This is especially common with tools that tie the booking URL to account-level permissions rather than just the calendar configuration.

Workspace or subdomain changes. Calendly links follow the format calendly.com/your-workspace/event-name. If you rename your workspace, change your personal URL, or move to a team plan under a different handle, every existing link to the old workspace becomes a 404 immediately. Acuity, SimplyBook, and HubSpot Meetings have similar patterns — a workspace rename or account restructure silently breaks every link you've ever sent.

Event type deletion. Deleting a specific meeting type doesn't redirect its URL — it just kills it. If you removed a "30-minute consultation" event and someone clicks the direct link from an email you sent three months ago, they get a 404. The booking page may still be active for other event types; the specific link isn't.

Embedded widget failures. Scheduling tools embedded as iframes or JavaScript widgets can fail silently when the underlying account URL changes. Your page returns HTTP 200 because the page shell loads. But the widget inside it hits a 404 from the scheduling provider's servers. Visitors see a blank space or a spinner that never resolves. Standard site crawl tools miss this entirely because they don't render JavaScript-loaded content.

Outdated GBP appointment links. Google Business Profile accepts a direct booking URL from your scheduling tool. When you switch providers or change your workspace URL, the old booking link stays in your GBP until you manually replace it. Your profile continues showing an "Appointments" button — it just routes customers to a dead page without any visible warning.

How to find broken scheduling links

Unlike your own website's 404s, scheduling tool breaks won't appear in Google Search Console unless Googlebot has followed those specific links. You need to check them manually:

1. Send yourself the most recent review request email and click every link from a private browser window with no cached sessions. If any link shows a 404, note the URL and find the correct current destination.
2. Test your website's "Book" or "Schedule" buttons. Click each one from a private browser. Confirm the scheduling page loads — not an error, not a blank iframe.
3. Check your GBP profile. Open your Google Business Profile from an incognito window, click the booking or appointment link, and confirm it opens an active scheduling page.
4. Search your email marketing tool for links. Filter all templates and automation sequences that include a URL from your scheduling provider's domain. These are highest-risk — they're automated, they go out continuously, and a broken link quietly drains your response rate for weeks before anyone notices the pattern.

The fix for any broken scheduling link follows the same logic as any other 404: set up a redirect from the old URL to the new one where you control the domain, and update every place the old URL appears directly.

For links you don't control (the calendly.com/ or acuityscheduling.com/ portion), you can't set up a server-side redirect — but you can replace them and update every active automation referencing the old address.

The most durable long-term approach is a short redirect on your own domain pointing to your scheduling tool. Using yourdomain.com/book in all your emails, QR codes, and website buttons means that when you switch providers or change your workspace handle, you update one redirect destination. Every existing reference in circulation — emails from six months ago, printed table tents, your GBP listing — automatically routes to the correct page.

Why Your Google Review Shortlink Shows "Page Not Found"

There's a specific 404 scenario that trips up small business owners who've done everything right: your website is fine, your hosting is working, but the link you're sending customers to leave a Google review shows a "Page not found" error. This isn't a problem with your website — it's a problem with the Google-side link itself, and it requires a different fix.

Google issues two types of links for collecting reviews. The first is a long URL that includes your full business name and a Place ID, something like https://www.google.com/maps/place/Your+Business+Name/@lat,lng,17z/data=.... The second is a short redirect in the format https://g.page/r/xxxxxxxxxxxxxxxx/review. The short version is what Google provides in your Business Profile dashboard under "Get more reviews," and it's what most businesses copy into email templates and QR codes because it's clean and easy to share.

The short link is where 404s happen most often.

Why Google Review Shortlinks Break

Google's review shortlinks (g.page/r/) aren't permanent in the way a page on your own website would be. They're managed redirects that Google can and does change, particularly when:

• Your Google Business Profile was transferred to a new email. When ownership transfers, Google sometimes regenerates the shortlink. The old short URL that the previous owner shared — in printed materials, old email sequences, or on the physical location — no longer routes correctly.

• Your business profile was suspended and reinstated. A suspension (even a brief one that was resolved) can cause Google to reassign the profile identifier that the short link depends on. The fix works fine; the link doesn't come back automatically.

• You claimed a different profile for the same location. Duplicate profiles are common, especially for businesses that have been around for a few years. If you claimed a second listing and merged or deleted the original, any review links tied to the original profile now go nowhere.

• Google updated its link format. Google has changed how review shortlinks are structured at least twice. Old-format links that were working perfectly in 2022 may have started returning 404s when Google deprecated that format. If you haven't tested your review link recently, this is worth checking.

• Your Google Business Profile category changed substantially. Less common, but some category changes trigger a re-generation of the profile's associated URLs.

How to Get Your Current Working Review Link

The only reliable source of your current review link is your own Google Business Profile dashboard — not a saved bookmark, not a link you forwarded from an email two years ago, not a link a previous employee set up.

Here's how to get it:

1. Sign into Google Business Profile using the account that manages your listing.
2. Find your location in the list and click on it to open the dashboard.
3. Look for the "Get more reviews" button or card — it's usually on the Home tab.
4. Google will show you a link to share with customers. Copy it.
5. Open a private/incognito browser window and paste the link. Confirm it loads Google's review prompt — you should see your business name and the option to leave a star rating.

If step 4 produces a link that still returns 404 when you test it in step 5, the issue is on Google's side, not yours. In that case, use the URL Inspection tool in Google Search Console to check whether Google has any indexing issues flagged for your business listing URL. More commonly, though, regenerating the link from the dashboard produces a working new one immediately.

Every Place the Old Link Is Probably Hiding

Once you have a working replacement link, the fix isn't done until you've updated every place the old broken version is in use. For most businesses, that's more places than they expect:

In email templates: Check your email marketing platform (Mailchimp, Klaviyo, ActiveCampaign, or whatever you use) for any automated sequences that include the review link. This includes one-time campaigns AND automated flows — post-purchase follow-ups, appointment confirmation emails, after-service thank-you sequences. Update every instance.

In text message templates: If you're sending SMS review requests, the link in those messages was set when the template was created. Check your SMS platform and update the template before the next send goes out.

In your email signature: If you've ever put a "Leave us a Google review" link in your email signature, it's still in there. Go to your email settings and update it.

In printed QR codes: A QR code is just a URL encoded into a square. If you have QR codes on menus, receipts, business cards, lobby signs, or table tents that link to your Google review form, those QR codes are now broken. You'll need to generate new QR codes pointing to the working link and reprint or replace the physical materials — or, better, set up a redirect from your own domain (yourdomain.com/reviews) so future link changes only require updating one redirect rather than reprinting everything.

In your website's "Leave us a review" section: Many businesses add a review button to their website footer, contact page, or testimonials page. Check each of these locations and update the href.

For more on getting a clean, working Google review link and distributing it effectively, the core process is the same regardless of whether your old link was a 404 or just outdated.

The Verification Step Most People Skip

After updating everything, verify that the link actually works the way customers will experience it — not just on your own computer, where Google might be pulling from a session cache.

Test from three different surfaces: an incognito window on your desktop, your phone's browser on cellular data (not your office wifi), and if possible, a phone belonging to someone who has never visited your Google profile before. A link that appears to work when you're logged into your Google account can still fail for customers depending on how the redirect is configured.

For businesses actively working to increase their Google review count, a broken review link is the single fastest way to undo months of effort. Getting a hundred customers to open your request email and click a link that returns 404 is worse than not sending the email at all — it trains customers to ignore future requests.

How to Test Review Request Links Before Every Campaign Sends

Broken review links typically go unnoticed for days or weeks because the failure happens silently — your email automation sends messages on schedule, open rates look normal, but nobody clicks through to leave a review because they're hitting a 404 instead of your review form. By the time the problem surfaces — usually when a customer mentions it or when you notice your review count stalled — you've already lost dozens of conversion opportunities.

The fix is testing before you send, not after customers report a problem. This takes about ten minutes and should happen before any new review request campaign goes live.

The Pre-Send Link Test (Do This Every Time)

1. Open an incognito or private browser window. Your regular browser caches pages and you may be logged into accounts that let you see things customers can't. Testing in private mode replicates what a first-time visitor experiences.

2. Test your main review link. Paste your Google review link — the one from your GBP dashboard's "Get more reviews" section — into the address bar. Confirm it loads the review prompt for your specific business, not a 404, not a general Google Maps page, and not a "find this business" screen. If you can see the star rating form for your business, the link is working.

3. Test every link in the email template. Most review request emails have more than one link: the primary CTA button, possibly a text link below it, an unsubscribe link, your website link in the footer, and sometimes a "click here if the button doesn't work" fallback. Click every single one from the incognito window. A broken unsubscribe link is a compliance issue; a broken CTA means every motivated customer hits a wall.

4. Test from a mobile browser. Open a private tab in Safari on an iPhone or Chrome on an Android device and repeat the test. Some redirect chains that work on desktop fail on mobile because of how carriers handle certain URL schemes, or because the destination page itself has a mobile-specific 404 that doesn't appear on desktop. If you don't have a second device handy, use your browser's built-in device emulation in DevTools.

5. Test from your phone on cellular data. Your office wifi may have cached DNS responses for recently changed URLs that make a broken link appear to work. Switching to cellular data bypasses those caches. A thirty-second test from your phone on LTE catches a category of link failures that other tests miss entirely.

What to Check for Multi-Location Businesses

If you're managing review requests across more than one business location, each location typically gets its own Google review link — and each link needs to be tested independently. Businesses that share a template across locations and swap in the review link using merge fields need to verify that every location's link resolves correctly, not just the first one.

The failure mode that catches multi-location businesses is a bad merge field substitution. If the variable that holds a location's review link is empty, misconfigured, or pointing to a deactivated profile, every customer in that segment hits the fallback — which might be the wrong location's review page, an empty string that produces a malformed URL, or a plain 404. Check the preview rendering for each location before the campaign goes out rather than spot-checking one and assuming the rest are fine.

Catching Broken Links in Running Automated Sequences

The pre-send test works well for new campaigns. For sequences that have been running for months — post-purchase follow-ups, after-service thank-you emails, drip sequences triggered by customer actions — the review link was probably tested when the sequence was first set up and never checked again. If the link changed since then, every message in the sequence is silently failing.

Check running sequences every 60 days: pull up the email template in your marketing platform, click through every link in preview mode, and confirm each one still resolves to a live page. If you find a broken link in an active sequence, fix the template immediately. The broken link stops affecting future sends the moment the template is updated. Customers who already received the broken version can't be reached again through the same message, but you can send a follow-up to the affected segment with a corrected link and a brief note.

This is the highest-leverage monthly maintenance task for businesses where automated review requests are part of the customer experience — the automated review request best practices that matter most are the ones that keep your pipeline from running broken for months undetected.

Using Your Platform's Link Monitoring

Manual testing every 60 days is the minimum viable approach. A better setup is monitoring that catches broken links automatically, the moment they break, rather than the next time someone remembers to check.

Some review management platforms include link monitoring as part of their dashboard — checking the destination URLs in active campaigns and flagging broken ones without requiring a manual test. Praising.ai monitors the links in your active review request campaigns and surfaces broken destinations on the dashboard before customers encounter them.

For businesses not on a platform with built-in monitoring, free tools like UptimeRobot can watch a URL on a five-minute interval and send an alert when it stops returning a 200 status. Adding your Google review link and your review collection landing page costs two minutes to set up and removes the "I forgot to check it" failure mode entirely.

The review reminder email templates that produce the most responses are the ones where every link consistently works — customers who click once and hit a broken page rarely try again.

When Review Links Break in SMS Campaigns

Email gets most of the attention in review link audits — email platforms wrap your links in click-tracking redirects and flag broken destinations in delivery reports. SMS works differently, and the failure stays invisible longer.

When you send a review request by text, the link goes out as a raw URL or through your SMS platform's shortener. Your delivery report shows "delivered" no matter what the link does afterward. Customers who tap it and get a 404 don't reply to tell you — they just don't leave the review. The only signal is silence.

Three failure modes specific to SMS review links:

Carrier-level link shortening. Many SMS platforms shorten URLs to stay inside the 160-character limit, routing them through third-party shortening services. If that service changes its domain, updates its pricing structure, or shuts down, every shortened link that ran through it stops resolving — silently and permanently. The texts keep delivering. The links stop working.

Deep link routing on mobile. A Google review link should open inside the Google Maps app and land the customer directly on the review form. This only works when the link format matches what the Maps app on that specific device recognizes. Google has changed its review link URL format at least once. Old format links may resolve fine in a desktop browser but fail to trigger the Maps app on newer Android or iOS versions. The customer gets a profile overview instead of a review form — or a browser 404 depending on the device — and assumes something went wrong on their end.

Template set-and-forget lag. SMS review request templates are typically written once, then sent hundreds of times without anyone checking the destination URL again. A link that worked when you created the template may have since been through a Google format change, a platform migration, or a shortening service change. The template still fires. The destination no longer exists.

How to test before the next send:

Text the review request to your own phone exactly as customers receive it. Use a cellular connection, not office WiFi — some carrier shorteners resolve differently by network. Open the message in your Messages app and tap the link; don't copy-paste the URL into a browser, since the browser path skips the deep link routing that actual recipients use. You should land inside Google Maps on a form with star ratings visible. If you land on a profile overview, the link resolves but routes wrong. If you see a 404, it's broken.

For campaigns already running: check your SMS platform's link-click report. A drop in clicks on an unchanged template isn't a slow week — it's usually a broken link.

Preventing Review Link 404s: A Monthly Checklist

A broken review link is the most damaging 404 a local business can have, and it fails without any warning. Your emails deliver. Customers open them. The link just goes nowhere. This checklist takes about 10 minutes each month and catches the most common failure points before they show up as a dip in your review count.

Every Month (10 minutes)

Open Google Search Console → Pages → Not found (404). Sort by "Impressions" descending. Any URL with recent impressions that now returns 404 is sending real visitors to a dead end — fix those first, before anything else.

Test your primary review link directly. Paste your Google review URL (the one starting with https://search.google.com/local/writereview?placeid= or g.page/r/) into a private or incognito browser window. You should land on a review form with a star rating selector. If you see a profile overview instead, the link is alive but not routing to the form. If you get a 404, the link is dead.

Test your short redirect separately. If you use yourdomain.com/review as a shortcut, paste that into the same private window. A redirect pointing to a broken destination still returns 200 at the short URL level — the only way to catch it is to follow the chain to the end.

Check from a phone on cell data. Google review links behave differently on mobile than desktop. Text the link to yourself and tap it. You should land on the review form inside the Google Maps app, not on your profile overview page.

Click through from an actual sent email. Open the last review request email you sent, find the review link, and click it. Email platforms often wrap links in tracking redirects. The only way to test this faithfully is to click a link in a real delivered email — template previews don't reproduce the full redirect chain.

After Any Website Change

Run these checks any time you update your platform, change your domain name, switch themes, or modify your redirect configuration:

1. Retest your short review redirect — site migrations and platform switches silently wipe custom redirect rules more often than any other change
2. Check Google Search Console's Coverage report within 48 hours for any new 404 spikes
3. Open your CRM or email platform and click every link in your review request template
4. Scan any QR codes at your location to confirm they route to the review form, not a 404 or a generic Google profile

After Switching Review Platforms

Switching from one reputation management tool to another invalidates every link the old platform generated. Most businesses don't realize the break has happened until a customer mentions it weeks later. The transition protocol:

1. Export your old platform's link formats before you cancel. You need to know what URLs were embedded in outgoing emails and printed on cards.
2. Set up 301 redirects from old destination URLs to new ones — not just update your short link, but redirect the actual destination pages so any customer who already has the old URL in their inbox still lands somewhere useful.
3. Update your Google Business Profile's posted review link if the old platform had placed a custom URL there.
4. Send a short recovery email to customers who received a broken link during the gap. A brief "we fixed a broken link from our last message" email typically recovers a meaningful share of those missed reviews within 48 hours — the window is short, but it is not fully closed.

Quarterly (30 minutes)

Once a quarter, run a broader audit that catches the less-obvious breaks:

• Run Screaming Frog's free version (covers up to 500 URLs) against your domain to catch internal broken links that Search Console hasn't flagged yet
• Check Ahrefs Webmaster Tools free tier for external sites linking to pages on your domain that now return 404
• Review every piece of printed material — business cards, receipts, table tents, window signage — that includes a review URL or QR code
• Check every social media bio and pinned post that links to your review page
• Run your automated email sequences in preview or test mode and click every link before the next campaign sends

The businesses that maintain healthy review counts aren't the ones with the most aggressive outreach — they're the ones whose collection infrastructure actually works every time a customer tries to use it.

The Review Velocity Method: Catching Broken Links Without Logging Into Anything

Most 404 detection methods require you to log into Search Console, run a crawl, or check a monitoring dashboard. All of those work — but they all require you to remember to check them.

There's a simpler signal that runs automatically: your weekly review count.

For any service business sending review requests, the number of new Google reviews that arrive each week is a direct function of whether your review link is working. When the link breaks, that number drops. When it drops to zero on a week you sent 30-40 requests, the link is broken until proven otherwise.

How to use this without any tools:

At the end of every Monday, check two numbers:

1. How many new Google reviews did you receive last week?
2. How many review requests went out last week?

If number 1 is significantly lower than usual — especially if it's zero when your baseline is 3-5 per week — check your review link before anything else. Don't start with Search Console. Don't start with a crawl tool. Start by clicking the exact URL you use in your emails and confirming it loads.

This works because the failure pattern is specific: when a review link breaks, your open rate stays the same (people still open the email), your send rate stays the same (your automation keeps running), but your conversion rate hits zero. The disconnect between sends and reviews is the signal.

Setting a baseline:

If you don't know your baseline, pull the last 8 weeks of review arrivals from your Google Business Profile and average them. You're looking for a number to compare against each week. For most small businesses actively requesting reviews, this is somewhere between 2 and 15 per week. Any week that comes in at less than half the average deserves a link test before any other explanation.

Why this matters more than Search Console:

Search Console shows you what Googlebot couldn't reach. Googlebot never crawls a URL from your review request email — it crawls your site. So a broken review link can stay completely invisible in Search Console for months while it silently kills every campaign you run. The review velocity method catches it within a week of the break, because you're measuring the outcome (reviews received) rather than the symptom (a Googlebot error).

This is the check that runs without effort if you already monitor your online reputation weekly. If you're using a review management platform that tracks both sends and arrivals, the gap shows up automatically in your dashboard — you don't have to do the mental math. For businesses doing it manually, a five-minute Monday morning habit is enough.

One practical note: review velocity dips are not always caused by broken links. A seasonal lull, a patch of customers who don't check email, or a week of lower-than-average traffic can all push the number down. The test is whether the link works when you click it — the velocity drop is the prompt to test, not the diagnosis.

Using Review Management Software to Catch Broken Links Early

The manual methods described above all require you to remember to run them. That's the weak link in any monitoring plan — and most small business owners have a dozen other things competing for their attention, so the link tests get skipped until a customer mentions they hit a wall. A broken review link that returns a 404 error for three weeks while you're running a post-visit outreach campaign can silently wipe out dozens of reviews you'd otherwise receive.

A review management platform shortcuts this by tracking both sides of the equation: requests sent and reviews received. When reviews stop arriving at roughly the rate you expect, the platform's dashboard shows the gap before you'd notice it yourself. That's the review velocity check from the previous section, except you're not doing the mental math — the software does it automatically.

The diagnostic that adds real value is click-through data. If your review request emails are being opened and the links clicked, but reviews aren't materializing, there's almost certainly a 404 error or redirect failure at the destination. That pattern is invisible in Google Search Console — Googlebot never crawls a URL from your email sequence. It shows up only when a tool tracks both the send and the outcome.

Online reputation monitoring platforms like Praising.ai track your inbound review rate across Google, Trustpilot, and other connected platforms. A sudden drop — say, your two-week rolling average falls by half — is an automatic signal to fix broken links before the next campaign goes out.

The same logic applies to review collection automation sequences. When a 90-day email drip stops converting, the first thing to check isn't the subject line — it's whether the link in the email still works. Automated campaigns are particularly vulnerable because the link gets set once at campaign creation and rarely checked again, even as platforms update their URL formats on the back end.

Setting a monthly calendar reminder works if you're disciplined about it. An automated monitoring system works whether you remember or not — and catches the break within days rather than the weeks or months a manual check might miss.

How to Fix Broken Links vs. 404 Errors: Two Different Problems

Most guides treat "broken links" and "404 errors" as synonyms. They're related, but the fix for each is different — and confusing them is how businesses spend time chasing the wrong problem.

A 404 error is what your server returns when someone requests a URL that doesn't exist. The problem lives on your server. You fix it by either restoring the page at that URL or setting up a redirect so requests to the old URL land somewhere useful.

A broken link is a link on a page — your page, or someone else's — pointing to a URL that no longer works. The problem lives at the source of the link. You fix it by editing the href to point somewhere that actually exists.

When your own page has a broken link pointing to your own missing page, you have both problems at once: a broken link (the href is wrong) and a 404 error (the destination doesn't exist). Fix the destination first with a redirect; then update the source link so future visits go direct instead of through a redirect chain.

When an external site has a broken link pointing to your deleted page, you can only fix the 404 side — add a redirect on your server. You can't change the href on a site you don't control.

This distinction matters when you're prioritizing. To fix broken links on your own site: export your GSC coverage report, filter for 404 errors, then search your CMS for any internal hrefs matching the broken URLs and update them. To fix 404 errors that come from external sources: add 301 redirects pointing the dead URLs to your best-matching live pages.

Both steps together — fix broken links in your own pages, add redirects for the rest — close the loop that most cleanup routines leave open.

The Bottom Line on 404 Errors

Most business owners discover their 404 problem the wrong way — a customer mentions they couldn't leave a review, a team member tests an old link and finds nothing there, or Search Console surfaces a batch of broken URLs during a routine check. By that point, you've already lost traffic, links, and probably some reviews.

The good news is that fixing 404 errors doesn't require a developer or a technical deep dive once you know the pattern. Most business websites have three to five recurring causes — and most fixes take under ten minutes each once you have a redirect set up.

Here's what matters most if you take nothing else from this guide:

Set up Google Search Console if you haven't already. It's free, and its Pages report is the most accurate view of which URLs are broken on your site. Check it monthly. The whole review takes about five minutes once you know where to look.

Fix review-related links first. Not all 404s cost the same. A broken product archive from 2019 with no traffic is a low-priority nuisance. A broken review request landing page means every email you send asking customers for feedback leads to a wall — and customers who hit that wall don't come back to try again. Prioritize any URLs that are part of your review collection flow, your Google Business Profile, or your automated outreach sequences.

Never delete a page without a redirect. This is the single rule that prevents most future 404s. Every time a page goes away — whether you're cleaning up old content, rebranding a service, or migrating platforms — the old URL needs a 301 pointing somewhere relevant. It takes two minutes. Skipping it means months of silent traffic loss.

Test after every site change. A CMS update, a theme switch, or a plugin conflict can quietly break redirect rules that were working the week before. A ten-minute crawl after major changes catches these immediately, before Googlebot flags the broken URLs and before real customers hit the dead ends.

If you're running an active review collection campaign, broken links in your outreach are often the invisible reason response rates are lower than expected. Your emails are delivering, your customers are opening them — the link they tap just goes nowhere. Automated review request tools solve part of this by standardizing the links in outgoing messages, but you still need the destination URL to actually work. A review management platform like Praising.ai goes a step further — it keeps tabs on your review collection endpoints so a broken redirect doesn't quietly drain your campaign results for weeks before anyone notices.

For ongoing maintenance, monitoring your online reputation includes keeping your review-related pages accessible. A monthly check of your Google Business Profile listing's website link, review link, and any embedded widgets takes less time than a single customer service email — and prevents a category of loss most businesses never think to measure until a customer mentions it.

404 errors are fixable. They're preventable once you put basic monitoring in place. Start with Search Console, fix your highest-traffic broken URLs this week, and set a monthly calendar reminder to run the 10-minute audit from earlier in this guide. That's enough to stay ahead of most of what breaks.

Combining Google Search Console and curl: A Diagnosis Workflow

Google Search Console tells you which URLs Googlebot couldn't reach. curl tells you exactly what a browser gets when it visits. Using them together takes about ten minutes and produces a definitive answer for every broken page on your list.

Step 1: Export your 404 list from Search Console

Sign into Google Search Console and go to Pages in the sidebar. Click the Not found (404) filter under "Why pages aren't indexed." You'll see every URL that returned 404 when Googlebot crawled it.

Click any URL for context: when it was detected, how many times it appeared in crawl data, and whether Google found it via a sitemap or a discovered internal link. The detection count matters. A URL flagged 50 times is a crawled page Googlebot kept coming back to; one flagged twice is probably a stale reference from a single old link. Fix the high-count ones first.

Export the full list by clicking the download icon above the table. You get a CSV with one URL per row.

Step 2: Validate each URL with curl

Open a terminal and run this for any URL from your export:

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

The flags: -s suppresses progress clutter, -I fetches headers only (no body, so it's fast), -L follows any redirects. The grep keeps just the status codes and destinations. A properly working redirect looks like:

HTTP/2 301
Location: https://yoursite.com/new-page
HTTP/2 200

That output means: the old URL returns 301, the browser lands on a page returning 200. Done.

A URL still returning 404 looks like:

HTTP/2 404

No Location line — no redirect exists yet. One that redirects but ends on another 404 or a non-200 means the redirect target is also broken.

Step 3: Match fixes to your platform

Once you've categorized each URL, fix in bulk:

• Still returning 404 directly — Add a 301 redirect in your CMS's redirect manager (WordPress Redirection plugin, Shopify's URL Redirects, Wix's 404 & Redirects panel, or your Nginx/Apache config).
• Redirecting to the wrong destination — Update the redirect target directly. Don't stack a second redirect on top of the first; update the original entry in your redirect manager.
• Returning 200 but blank or showing an error message — That's a soft 404. Either put real content on the page or have your server return a proper 404 status code.

Step 4: Request re-indexing after fixing

In Search Console, open the URL Inspection tool and paste each fixed URL. Click Test Live URL to confirm the server returns the right status. Once it passes, click Request Indexing to queue it for a fresh crawl. On a small business site, this brings fix detection from weeks down to a few days — you don't have to wait for Googlebot's next scheduled pass.

Testing a batch at once

If you have more than ten broken URLs, a shell loop saves time:

while IFS= read -r url; do
  echo "Testing: $url"
  curl -sIL "$url" | grep -E "^HTTP|^Location"
  echo "---"
done < broken_urls.txt

Paste your exported URLs into broken_urls.txt (one per line) and run it. Pipe the output to a file to save a dated audit record you can compare month over month:

while IFS= read -r url; do
  echo "Testing: $url"
  curl -sIL "$url" | grep -E "^HTTP|^Location"
  echo "---"
done < broken_urls.txt > audit_$(date +%Y-%m).txt

This workflow pairs well with a monthly calendar reminder — ten minutes once a month, and you catch broken links before they compound into weeks of silent customer losses.