Check the HTML delivered to browsers for broken internal, external, anchor, and email links. Locate errors and unintended redirects, suggest URL updates or replacements, and help introduce automated checks and ongoing monitoring.
Use when reviewing templates, rendered HTML, or shared components related to Check for broken links. Validate the final browser-facing markup, not just the source framework abstraction.
Check whether internal and external links open correctly, and find 404 errors or redirects to unintended destinations. The review also covers anchors that point to locations within a page and mailto links that open an email draft. It identifies the elements, attributes, and routes involved in each problem by examining the final HTML delivered to browsers, alongside templates and shared components.
Use this skill to inspect links on documentation or e-commerce sites, or to review links generated by shared components. It also helps you prepare for external destinations disappearing after publication by setting up regular monitoring and automated checks in CI/CD.
The listed tools for automated checking are lychee, linkchecker, and broken-link-checker. Reviews cover the rendered HTML as well as the source code.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Broken links frustrate users, hurt SEO rankings (Google penalizes 404s), and damage credibility—especially for documentation and e-commerce sites.
Verify that all internal and external links are working properly and don't return 404 errors or redirect to unintended destinations.
Use automated link checking tools to identify and fix broken links, update redirected URLs, and remove or replace dead links.
Explain why broken links hurt user experience, SEO rankings, and credibility, and how to implement ongoing link monitoring.
Review templates, server-rendered HTML, and shared components that output markup related to Check for broken links. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/html/link-checker
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.