NewSiteCheckFind obvious broken paths from a public homepage. See exactly which links were sampled and what each request returned.
Enter a public domain or page URL. No account or email required.
The tool fetches the public homepage, extracts a bounded set of same-host links and tests up to six. It tries HEAD first and falls back to GET when the server rejects HEAD with a method-not-supported status. The table shows the sampled URL and response status or fetch failure. A result of zero errors means only that the tested sample did not show an error.
An HTTP 404 or 410 on a navigation link is a concrete task. A fetch failure needs verification because security rules, temporary network conditions and timeouts can affect an automated request. Also review the link text and final destination: a technically successful link can still lead to an unrelated page. If the same broken link appears in a shared menu, fix the component that emits it and recheck a representative page.
This tool samples links from one fetched homepage; it is not a complete crawl. Links injected by JavaScript or exposed only after interaction may not appear in the fetched HTML. External links, buttons without link URLs and form submissions are outside this sample. Test the primary visitor journey manually and use a broader crawl when the website has many sections or templates.
A completed check is saved to this browser's workspace, where you can view the snapshot or run it again. Export the result as JSON or CSV for a release record. Browser snapshots do not trigger automatic monitoring, and clearing browser data removes them.
No. It means the sampled internal homepage links responded without a detected error. Other pages, links and interactive flows still need review.
No. It reads public information and shows what was observed. Review the next step before changing site or DNS configuration.
The free launch scan runs 40 checks and shows the top three findings. The paid report unlocks all detailed results and a priority action plan.