Skip to main content

Try Base free for 14 days, no card or M-Pesa needed See pricing

Guide

How to find and fix broken landing pages that still get traffic

Last updated
Page tools
Agent setup

A page that earned traffic now returns an error. Compare its traffic with its current response, then restore it, redirect it or leave it removed.

A tour page earned 1,200 Google clicks in September and October. In early November someone renamed its URL. Search results, bookmarks and old links still send people to the old address, and they get a 404.

The traffic report still looks healthy, because it describes the past. The page is already broken.

The short version. Put two facts side by side: the traffic a URL earned in a stated period, and what it answers today. Then choose one of three actions: restore it, redirect it to a page that genuinely replaces it, or leave it removed with a 404 or 410.

Two facts, each with a date

FactWhere to get itWrite it as
Traffic it earnedSearch Console Performance → Pages; GA4 landing pages.“1,240 Google clicks, 1 Sep–31 Oct.”
What it answers nowA status check of the exact URL, or a fresh crawl.“404, checked 18 Nov.”
When it brokeAudit history, server logs, CMS revisions, deploy notes.“404 since about 4 Nov.”
What it was forThe page itself in an archive, a backup or your CMS.“The 3-day Maasai Mara tour.”
What still points at itInternal links, sitemaps, ads, emails, other sites.“Linked from 2 blog posts and the sitemap.”

Keep the dates apart. Traffic from before the break shows demand, not current visits. Once Google sees a 404 or 410, it removes a previously indexed URL from its index (Google), so the clicks fade and the evidence goes with them.

Find the candidates

  1. Export pages with clicks from Search Console for a period before the problem began, such as the last three months.
  2. Export GA4 landing pages for the same period. Pages from ads or email may not show in Search Console.
  3. Check what every URL answers today. The free Bulk HTTP Status Checker checks up to 25 URLs at once and shows where redirects end.
  4. Keep the rows that return 4xx or 5xx, or that redirect somewhere you didn’t intend.

Restore, redirect or leave removed

SituationActionWhy
Removed or broken by mistake, still wanted.Restore it at the same URL.Visitors and links already point there.
Server error (5xx).Restore: fix the error.The page still exists; the server fails to deliver it.
Moved, or a clear replacement exists: same product, same article, merged page.301 redirect to the replacement.Google advises a redirect when a page has moved or has a clear replacement, and prefers permanent server-side redirects (Google, Google).
Gone, with no page of similar content.Leave removed: 404 or 410.Google advises 404 or 410 when there is no replacement with similar content (Google).
The only redirect target is the homepage or a loosely related page.Leave removed.Google warns against sending old URLs to one irrelevant page such as the homepage; it may be treated as a soft 404 (Google).

404 or 410? Google treats all 4xx responses except 429 the same (Google). Use 410 if you want your own records to say the removal was deliberate. A custom error page is fine, as long as it returns the error status, not 200 (Google).

Example: a safari operator after a site update

Illustrative example, not real data. An invented Nairobi safari operator on example.co.ke. Traffic is from 1 September to 31 October; statuses were checked on 18 November.

URLTraffic, 1 Sep–31 OctStatus on 18 NovOriginal purposeReplacement optionsAction
/tours/maasai-mara-3-days/1,240 Google clicks404 since ~4 NovThe 3-day Mara tour/tours/maasai-mara-3-day-safari/: the same tour, renamed301 to the renamed page.
/contact/380 Google clicks500 since ~12 NovEnquiriesNone neededRestore: a form plugin update broke it.
/blog/safari-packing-list-2024/650 Google clicks301 → homepage since ~6 NovPacking list/blog/safari-packing-list/: the updated listChange the redirect to the updated list.
/tours/lamu-dhow-weekend/180 Google clicks404 since ~2 NovA Lamu trip no longer run/tours/ (all tours); /tours/lamu-old-town-walk/Leave removed (410). Neither is the same trip.
/tours/amboseli-day-trip/?ref=newsletter90 GA4 sessions, none from search404Newsletter link to a live tour/tours/amboseli-day-trip/ answers 200Fix the link in the newsletter template.

Google clicks each broken URL earned before it broke

  • Fix: redirect or restore
  • Leave removed
/tours/maasai-mara-3-days/404 since ~4 Nov1,240 · 301 redirect
/blog/safari-packing-list-2024/301 to homepage since ~6 Nov650 · Fix redirect
/contact/500 since ~12 Nov380 · Restore
/tours/lamu-dhow-weekend/404 since ~2 Nov180 · Leave removed

Google clicks from 1 September to 31 October; statuses checked on 18 November. The three URLs to fix earned 2,270 of the 2,450 clicks. The newsletter URL is left out: its 90 visits are GA4 sessions, none from search.
Source: Illustrative example: invented figures, not real data.

Copy linkDownload SVG
Embed

The Lamu row is the trap. Redirecting it to the walking tour would land people who wanted a dhow weekend on a different trip. If you want those visitors, add a coastal-trips section to /tours/ and link to it from relevant pages, not through a redirect.

Finish the job

  • Point internal links and sitemap entries at the final URL, not at the redirect.
  • Redirect in one hop. If the old URL already redirected, update the first rule to go straight to the final page.
  • Keep redirects in place. For site moves, Google says to keep them as long as possible, generally at least a year (Google).
  • Tell whoever runs ads, emails or partner links that still use the old address.

In Ndovu

Site Audit crawls pages with Search Console or Analytics traffic first, and raises these issues:

IssueWhen it appears
Page with search traffic now returns an errorCritical. Search Console reports clicks in the last 28 days, but the crawl got a 4xx or 5xx.
Analytics landing page now returns an errorCritical. GA4 recorded organic sessions landing there in the last 28 days.
Page with search traffic now redirectsFine after an intended move; otherwise check the target.
Missing page known only from outside data (404)Nothing on the site links to it; it is known from Search Console, Analytics or your import.
Retired page (410 Gone)A record of a deliberate removal. No action if intended.
  • The last 28 days can miss an older break. Paste the older URLs into Import URLs to audit first (up to 5,000).
  • Changes shows URL status changes against the previous audit, which dates the break. URLs filters by status and traffic.
  • Search Performance → Pages and Analytics → Content give the traffic side, for any period you choose.
  • Inspect URL shows one URL’s Google clicks, organic visits and, with server logs connected, which crawlers requested it and what they got.

Check the fix

  • Each URL answers what you chose: 200 when restored, one 301 to the right page, or 404/410.
  • Re-run the audit. These issues come from Search Console and Analytics data, so a new audit, not a recheck, confirms them. The issue becomes Verified resolved once a complete audit no longer finds it.
  • Over the following weeks, the replacement URL gains impressions and landing-page sessions while the old one fades.
  • Crawlers in Inspect URL get the new answer.

A worksheet you can copy

URL:
Traffic (clicks / sessions) and period:
Status today, and date checked:
Broken since (date, source):
Original purpose:
What still links to it:
Replacement options:
Does a replacement serve the same need? (yes / no):
Action (restore / 301 to … / 404 / 410 / fix the link):
Done on (date):
Verified on (date, how):
When you need to…Read
Run and verify an auditRun a site audit and verify fixes
Decide what to fix firstPrioritise a technical audit
Check pages after a plugin or theme updateCheck SEO after a WordPress update

Sources

Next steps

Was this helpful?