Menu and footer links resolve
Fix or remove the broken links.
Menu and footer links resolve
We open every header, menu and footer link on the pages we read, up to 80. Each one has to end on a working page.
A broken link sends a visitor to a page that no longer exists. The ones in your menu and footer matter most, because every visitor can reach them. Check that each link ends on a working page, that a missing address returns a real 404 status, and that the error page leads back into your site.
By the Neue World growth team · Updated November 2026
Navigation is how visitors move around your site: the menu, the footer, and the links between pages. Structure is what sits underneath: the address of each page, the redirects when a page moves, and what happens when someone opens an address that doesn't exist.
When it works, nobody notices. When it breaks, a visitor clicks your menu and lands on an error page, and search engines lose track of which pages are real.
People use your menu to find what they need. A broken link leaves them on an error page with nothing to do next.
Google takes pages that return an error out of search. It is also confused by an error page that looks like a normal page, which it calls a soft 404.
ChatGPT, Claude and Perplexity read websites with their own crawlers to find pages for their answers. A page they can't reach, they can't use, so a broken link hides part of your business from them.
Most broken links point to old pages that were renamed or removed. Once you know where they are, they're quick to fix.
These are the practices behind the checks, in plain words.
Every link in the header, menu and footer opens a working page. (Tools call this a broken link checker.)
A page for addresses that don't exist, in your own design, that also tells browsers and search engines the page is not found. The status matters as much as the words on the page.
A redirect sends a visitor from an old address to a new one. A chain is a link that passes through several redirects before it lands. Point the link straight at the final address.
The 404 page links to the homepage and the main sections, so a visitor who hits a dead link can carry on.
Old articles link to pages that moved, and other sites link to addresses you removed. Worth reviewing, but the analysis does not test them.
You can check all of this by hand in about ten minutes.
Open your site and click every link in the menu and the footer. Note any that show an error or land somewhere you didn't expect.
Type a made-up address after your domain, such as yoursite.com/this-page-does-not-exist. You should see your error page.
In your browser's developer tools, open the Network tab and reload: the first request should show 404. In Google Search Console, the Page indexing report lists pages Google sees as "Not found (404)" or "Soft 404".
On the error page, look for a link back to the homepage.
Or run the free analysis, which checks these for you. Check my links and 404 page
| Mistake | What it costs you | How to fix it |
|---|---|---|
| Menu or footer links lead to missing pagesThis usually happens after a page is renamed or removed and the menu is not updated. | Visitors who use your menu land on missing pages. | Fix or remove the broken links. |
| Some menu links go through redirect chainsA link that points at an old address and relies on a redirect to reach the new one. | Pages load slower through extra redirects. | Point these links straight at their final address. |
| Unknown addresses don't return a real 404 pageCommon when the site sends every unknown address to the homepage, or shows a normal page. The page looks fine to a visitor, but the status says it exists. | Search engines can treat error pages as real pages. | Return a proper 404 page for addresses that don't exist. |
| The 404 page gives visitors no way backThe error page is a bare message with no menu or link. | Visitors who hit a dead link have nowhere to go. | Add a link to the homepage and main sections on the 404 page. |
We check menu, header and footer links, up to 80 across the pages we read. We don't crawl every link in your content, and we don't check links from other sites. Code decides each of these, so the same pages always get the same result.
Menu and footer links resolve
Fix or remove the broken links.
We open every header, menu and footer link on the pages we read, up to 80. Each one has to end on a working page.
7 of the menu and footer links resolve directly and 1 after a single redirect; none go through a longer chain.
Point these links straight at their final address.
The same links, counting the redirects. Landing directly or after one redirect passes; more than one fails.
A made-up address on fieldnote.example returns HTTP 404, not a normal page or a redirect to the home page.
Return a proper 404 page for addresses that don’t exist.
We open a made-up address. It should say "not found" (404 or 410), not send visitors to the homepage or show a normal page.
The 404 page links back to the home page (2 links to the site in total).
Add a link to the homepage and main sections on the 404 page.
We read your 404 page for a link back to the homepage, so a visitor who hits a dead link can carry on.
A page that tells visitors it doesn't exist but returns a 200 "success" status. Google's documentation describes it this way. For a page you removed with no replacement, it recommends returning a 404 or 410; for a page that moved, a 301 redirect.
No. Redirecting every missing address to the homepage hides the error, and our analysis fails it. For a removed page with no replacement, Google's guidance is to return a 404 or 410.
Up to 80 menu, header and footer links across the pages we read. It does not check every link in your content, or links from other sites.
Some sites block or rate-limit automated visits. When we can't open a link we report it as not verified, never as broken. It costs a quarter of that check's points and is never counted as a failure.