Broken Link Checker
Scan a page for internal links, anchor text, follow status, and responses.
Broken Links Checker for Internal URLs and Response Codes
The broken link checker scans a submitted page and lists the internal links found on that page. The result table includes each URL, link text, status, link type, follow status, and server response. On smaller screens, additional information can be available through the More dropdown so the table remains readable without hiding important details.
This tool is useful when you need to find internal navigation problems before users or crawlers encounter them. A broken internal link can send visitors to an error page, waste crawl paths, weaken content quality, and create avoidable maintenance work. Checking one important page at a time is a practical method for launches, edits, migrations, and routine SEO cleanup.
How to Scan a Page for Broken Links
- Enter the full page URL in the visible URL field.
- Select the Get Broken Links button.
- Wait while the page extracts and checks internal links.
- Review the URL and link text columns to understand where each link points.
- Check status, follow status, and server response as the table completes.
The tool validates the submitted URL, fetches the page, extracts links, and focuses the visible table on internal destinations. That makes it especially useful for navigation, content links, category links, tool links, and other same-site references.
Understanding the Result Columns
| Column | What it shows | How to use it |
|---|---|---|
| URL | The internal destination found on the submitted page. | Open or fix any URL that returns an error response. |
| Link text | The visible anchor text or linked content. | Improve vague anchors that do not explain the destination. |
| Status | A loading or result indicator for the link check. | Wait until checks finish before making decisions. |
| Link type | Whether the link is internal or external in the result context. | Separate same-site cleanup from outbound review. |
| Follow status | Whether the link is marked nofollow or dofollow. | Confirm important internal links are handled as expected. |
| Server response | The HTTP response returned by the destination. | Investigate 404, 500, timeout, or unusual responses. |
A response code by itself does not always tell the whole story. A redirect may be intentional, a temporary failure may need retesting, and a blocked request may depend on server rules. Still, the table gives a clear starting point for cleanup.
Prioritizing Server Responses
Not every response deserves the same urgency. A 404 on a main navigation link should usually be fixed immediately. A 500-level response suggests a server-side problem that may need developer or hosting attention. A redirect may be acceptable if it is intentional, but repeated or unnecessary redirects can slow navigation and make link maintenance harder. A timeout may need retesting because it can be temporary.
Use the response column as a triage guide. First fix errors on important internal links, then review redirects and unclear statuses. If a link is important to users or search crawlers, it should resolve cleanly and predictably.
Cleaning Anchor Text While Fixing URLs
Broken link cleanup is a good time to improve anchor text. If a link says “here,” “read more,” or repeats the same vague label across many destinations, users may not understand the target before clicking. Clear anchor text makes the page easier to scan and helps technical reviewers understand the purpose of each link in the result table.
- Use descriptive anchor text for important internal links.
- Replace outdated URLs with the final canonical destination.
- Remove links that no longer support the page topic.
- Retest the page after fixes to confirm the response changed.
When a Broken Link Scan Is Worth Running
- After editing navigation: confirm that menu, footer, and content links still point to valid pages.
- Before publishing: check a new page’s internal references before it receives traffic.
- After changing URLs: find older internal links that still point to retired paths.
- During SEO maintenance: reduce crawl friction caused by 404 pages or stale destinations.
- After content imports: catch copied links that no longer match the final URL structure.
If the page has many links, start with the highest-value pages first: homepage, category pages, landing pages, documentation pages, and pages that receive search traffic.
Follow-Up Checks After Link Cleanup
If link text or crawlable page content looks suspicious, inspect the same URL with the Spider Simulator. If search results still show an older version after fixing links, compare the page with the Google Cache Checker. If visitors report loading or response issues, test delivery with Check GZIP Compression to see headers and page-size details.
Broken link cleanup is not only about removing 404s. It is also about keeping internal paths clear, making anchor text understandable, and reducing avoidable dead ends in the user journey.
Retesting After Fixes
After changing links, run the same page through the checker again instead of assuming the edit solved the problem. A replacement URL can still redirect, time out, return a soft error, or point to a page that is no longer relevant. Retesting confirms the final response and catches accidental mistakes introduced during cleanup.
For larger edits, keep a short before-and-after note with the page URL, broken destination, chosen replacement, and new server response. That makes future maintenance easier because you can see whether a link was intentionally redirected, removed, or replaced with a canonical destination.
Creating a Link Maintenance Routine
For a small site, run the checker on the homepage, main category pages, and any page that receives regular traffic. For a larger site, prioritize pages that are linked from navigation, promoted in campaigns, or updated often. This keeps the review practical. The goal is not to check every URL manually every day; the goal is to catch the internal links that would create the most visible problems if they fail.
After each scan, group the results by action. Some links need direct replacement, some need removal, some need a redirect update, and some need a second test because the response may have been temporary. Anchor text improvements can be handled at the same time, especially when vague labels make the table hard to understand.
Keep a simple record of the submitted page, the broken destination, the fix applied, and the final response after retesting. That record is useful during migrations and content cleanups because it shows which internal paths were intentionally changed.