Fix a broken link at its source if the intended page still exists. If the page moved, redirect its old URL to a genuinely relevant replacement; if it was removed and no equivalent page exists, leave it returning a real 404 or 410. The right repair depends on what happened to the destination—not simply on the fact that a URL returns an error.
First, identify what is broken
Find the failing URL, then determine whether the destination is still live, has moved, or has been intentionally removed. Also identify where the link came from: a page on your site, a sitemap, or another source. This distinction prevents unnecessary redirects and helps separate links you can correct from URLs that should no longer exist.
If Google Search Console reported the URL, review the report’s discovery details to see where Google found it. Check your sitemap if the URL may have been submitted there. For links within your own site, locate the page containing the link and test the destination directly.
Choose the repair that matches the page
The intended page still exists: correct the link
Update the link on the page where it appears so its href points to the correct, live URL. Use a normal anchor element, such as <a href="https://example.com/page">Read the guide</a>. Google generally identifies links through anchor elements with an href; a script-only click handler or a non-anchor element may not be parsed reliably. Write concise, descriptive link text so visitors can tell where the link leads.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →The page moved: redirect to its replacement
If the old page has moved and a real, closely related replacement exists, redirect the old URL to that page. For a permanent move, use a server-side 301 or 308 redirect. For a temporary change, use a temporary redirect. The setup depends on your hosting platform and server environment; follow the host’s instructions for configuring redirects.
Do not send every old URL to the homepage. A redirect should take visitors to the closest relevant replacement, not merely to a page that loads successfully.
The page was removed without a replacement: return 404 or 410
When content is gone and there is no comparable replacement, leave the URL returning HTTP 404 or 410. Google currently treats 410 like 404. Do not invent replacement content or return a success response for a page that does not exist; Google may interpret a success response paired with a “not found” message as a soft 404.
You can still make the error useful to visitors. A custom 404 page can explain that the page is unavailable, retain your site’s navigation and visual identity, suggest useful destinations, or offer a way to report the broken link. It should continue to return HTTP 404.
Prioritize the 404s that need attention
Not every 404 is a problem. Google Search Console Help says, “In general, 404 errors won’t impact your site’s search performance, and you can safely ignore them if you’re certain that the URLs should not exist on your site.”
Start with URLs your site linked to or submitted in a sitemap, since those may indicate a mistake you can fix. Also investigate recurring misspellings or alternate spellings; if a repeated typo points to a clear intended page, a redirect may help. A removed page with no suitable replacement should remain a 404 or 410 rather than being redirected somewhere unrelated.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Verify the repair
- Check the source: Open the page containing the link and confirm its anchor points to the intended URL.
- Check the destination: Visit the destination and confirm it loads the expected page. If you configured a redirect, check that the old URL reaches the relevant replacement and behaves as intended.
- Use Google’s URL Inspection when relevant: In Search Console, inspect the URL to view the information Google has stored, then run a live test to check its current state. Stored index information and live-test results are different. Google says live-test information is not itself used to generate search results.
- Request indexing if appropriate: After correcting a crawl or indexing problem, you can request indexing in URL Inspection. A request does not guarantee a particular search appearance.
A site crawler or link-audit tool can help find URLs across a large site. Treat its findings as a starting point: decide whether each destination is live, moved, or gone before changing links or creating redirects.
Quick Recap
Google guidance for fixing 404 errors and links
- Google Search Console Help: 404 (Page Not Found) errors
- Google Search Central: Make your links crawlable
- Google Search Central: Redirects and Google Search
- Google Search Central: HTTP network errors
- Google Search Console Help: URL Inspection tool
- W3C WAI: Technique G127, identifying relationships between pages
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
