Is this your problem?
- Pages show "404 Not Found" or "Page not found" after a rebuild or a move
- Links from Google, other sites or old bookmarks lead to a 404
- Search Console reports a jump in "Not found (404)" pages
- The home page works but inner pages, or old blog posts, do not
- Menu links work but direct links to old addresses fail
What usually causes it
How to tell: The new site uses different URLs, so every old link points to an address that no longer exists.
How to tell: A change to how addresses are built (dates, categories, slugs) moves every page at once.
How to tell: Content was dropped or retitled, and nothing redirects the old address.
How to tell: The new site still links to old paths that were not updated.
How to tell: On some stacks, pretty URLs need a rewrite config that was not carried over, so every deep link 404s.
Before you touch anything
- Get the list of old addresses from Search Console (Pages, then Not found) or from a crawl of the old site.
- Map each important old address to its new one before you start, so redirects are deliberate.
How to fix it, step by step
-
1
Confirm the pretty-URL rules exist
If every deep link 404s but the home page works, the rewrite rules are missing. On WordPress, re-save Permalinks; on other stacks, restore the rewrite config (an .htaccess or server rule).
-
2
List the broken addresses
Use Search Console and a link checker to collect the old addresses that now 404, especially ones with traffic or links.
-
3
Redirect each old address to the new page
Set a permanent (301) redirect from each old address to its closest new page. A redirect plugin, the platform redirect tool, or a server rule all work.
-
4
Send dropped pages somewhere sensible
For a page that no longer exists, redirect it to the nearest relevant page or the parent section, not the home page, which Google treats as a soft 404.
-
5
Fix internal links
Update menus and in-content links to the new addresses so the site does not rely on redirects for its own navigation.
-
6
Give Google the new map
Submit an updated sitemap and let Search Console recheck. The 404 count falls as it recrawls.
Stop and get help if
- There are hundreds of changed addresses and the redirects need a pattern rule, not one by one.
- The site earns from search and the 404s are on pages that used to rank.
- Every page 404s and you are not sure whether it is rewrite rules or a deeper server problem.
Stop it happening again
- Before a redesign, export the old URL list and plan redirects as part of the launch.
- Keep the same addresses where you can; change them only on purpose.
- After launch, watch Search Console for a 404 spike and fix it quickly.
- Use a custom 404 page that offers search and top links, so a miss is not a dead end.
Questions people ask
Should I redirect everything to the home page?
No. Google reads that as a soft 404 and it frustrates visitors. Redirect each page to its nearest match.
Will 404s hurt my Google ranking?
Old links that now 404 lose the value they passed. Redirecting them to the right page keeps most of it.
What is a 301 versus a 302?
A 301 is permanent and passes ranking value; use it for a moved page. A 302 is temporary. For a redesign, use 301.