Find and fix internal links that lead to missing pages or server errors. Check rendered pages and HTTP responses, then identify URLs to update or remove and explain how broken links affect search engine crawling.
Use when auditing metadata, crawlability, structured data, or indexability related to Resolve internal broken links. Verify the rendered HTML and HTTP response rather than relying only on source files.
Run score Not tested
See how to installbroken-links finds broken internal links and helps update them to the correct URL or remove links that are no longer needed. It targets links returning 404, meaning the page cannot be found, or 5xx, meaning a server error. It checks rendered HTML and HTTP responses instead of judging source files alone, and identifies the specific pages or templates with problems.
Use it after moving or deleting pages to check whether links in menus and page text still work. It also explains crawl budget: the amount of work or time a search engine can spend crawling a site. This helps you understand how broken links affect the efficiency of getting pages indexed for search.
Verification requires the target pages' actual HTML and HTTP responses. Implementation details and code examples are provided through the accompanying references/rule.md.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. 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.
Internal broken links frustrate users and waste crawl budget by sending search engine bots to non-existent pages, potentially harming your site's SEO.
Scan the website for any internal links that lead to 404 pages or server errors.
Update the broken link to the correct URL or remove it if the destination page no longer exists.
Explain the concept of 'crawl budget' and how broken links can negatively affect a site's indexing efficiency.
Review metadata generation, rendered HTML, structured data, and response headers related to Resolve internal broken links. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/broken-links
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.