Within your site
A relative link such as /blog/guide usually leads to another page you control. Fix broken internal links at their source.
Check every link on a page in one go. Find broken links and redirects, and see which links are internal, external or nofollow.
One page at a time. Every link is listed; repeated destinations share one HTTP check.
Sample results show how statuses and rel attributes appear. They are not live checks.
Paste a public page URL and run the check. The report lists every HTML link on that page, groups internal and external destinations, reads each link’s rel attribute, then checks unique public HTTP or HTTPS destinations on standard ports for status codes and redirects.
An internal link points to the same website as the page you checked; an external link points to another site. This tool compares hostnames, treating the www and non-www forms as the same site. Other subdomains are shown as external.
A relative link such as /blog/guide usually leads to another page you control. Fix broken internal links at their source.
A link to a different domain can break or change without your site changing. Check external references after publishing.
A link such as #pricing points within the current page. It has no separate HTTP response, so the tool checks whether its target exists in the HTML.
A normal HTML link is followable by default; rel="dofollow" is unnecessary. rel="nofollow" asks search engines not to treat the link as a standard endorsement. sponsored identifies paid placements, and ugc identifies user-generated links.
The report shows the exact rel tokens, including combinations such as rel="ugc nofollow". A page-level robots nofollow directive appears separately so you can distinguish it from a link attribute.
A 2xx code means the request succeeded. A 3xx code redirects; check where it ends. A 404 or 410 means the destination is missing. A 5xx code points to a server problem. A 403 or 429 may mean the server blocked or rate-limited this checker, so confirm it manually.
| Response | What the report shows | Next step |
|---|---|---|
| 200–299 | Success | Check that the destination still says what you expect. |
| 301, 302, 307, 308 | First status → final status and destination | For links you control, update the href to the final page. |
| 404 or 410 | Missing destination | Replace the URL, restore the page, or remove the link. |
| 403 or 429 | Restricted check | Open the link in a browser before calling it broken. |
| 500–599 | Server error | Retry later, then investigate if it persists. |
| No response | Could not verify | Check DNS, TLS or a network block manually. |
Start with internal 404 and 410 links because you control both the source and destination. Then update internal redirects to their final URLs, review server errors, and verify external links that appear blocked to the checker.
Change the href to a working page, restore the missing page, or remove the link if the destination no longer exists.
Use the final URL directly where you can, especially in navigation and prominent content links.
Do not treat a 403 or 429 as proof of a broken page. Open it manually, then decide whether to keep the link.
Review the link’s purpose. A regular editorial link usually needs no rel attribute; paid and user-generated links need appropriate qualification.
The checker lists every <a href> link in the submitted HTML and checks each unique public HTTP or HTTPS destination on a standard port. Repeated link instances keep their own anchor text and rel attributes. On-page anchors and email or telephone links appear without HTTP codes.
It reads the server-returned HTML rather than rendering JavaScript. A target may also block automated checks while loading normally for a person. For site structure beyond one page, try Pineable’s Sitemap URL Extractor.
The report shows what the page links to and how those destinations responded during this check. Rel attributes and status codes answer different questions, so review both before making changes.
rel="dofollow". The tool labels links without nofollow, sponsored or ugc as Follow.Explore design references for clearer, more useful pages.
Browse the design library