Skip to content
cccskills
FreePublished on GitHubEnglish overview

broken-external-links

Check external links for error responses and expired domains, then identify links to update or remove. Inspect rendered HTML and HTTP responses to locate affected pages and explain how to verify the corrections.

OriginalShow the original description

Use when auditing metadata, crawlability, structured data, or indexability related to Fix or remove broken external links. Verify the rendered HTML and HTTP response rather than relying only on source files.

AI rating90/ 100See how to install

Good for

  • Checking reference links in older articles
  • Updating or removing broken external links
  • Reviewing links to expired or repurposed domains

Overview

What it does

Checks external links on a page, finds destinations that cannot be opened, and fixes the links. It looks for HTTP errors in the 4xx and 5xx ranges, including 404 responses. When a correct URL is available, such as a resource’s new location, it updates the link. If the referenced material no longer exists, it covers removing the link. It also checks links to expired domains that may have been repurposed.

When it helps

Use it to review references in older articles or as part of regular website maintenance. It explains how link rot—the loss of linked resources over time—affects readers’ experience and their trust in a website. The review checks generated HTML and HTTP responses alongside source files, identifies affected page paths or templates, and explains how to verify the page output after corrections.

Example requests

  • “Check this article’s external links and list those returning 404 or other errors.”
  • “Update broken links to the correct URLs and remove links to resources that no longer exist.”
  • “Check destinations that may have expired or been repurposed.”

Notes

There are no special notes.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Objective evaluation

AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.

Clear instructionsIs it clear when to use it and what it does?
AGoodIt explicitly checks external links for errors and updates them to working URLs or removes them.
Concrete stepsAre steps, inputs, outputs, and examples spelled out?
AGoodIt specifies 4xx and 5xx checks, conditions for updating or removing links, and reporting affected routes or templates.
SafetyAre sending data, deleting files, and running commands disclosed?
BPartly lackingIt involves accessing external links and removing links, but provides no confirmation procedure before execution.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodChecking links and HTTP responses requires no specified service or API key.

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.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (2)

  • SKILL.md1.6 KB
  • references/rule.md2.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Fix or remove broken external links

Broken links provide a poor user experience and can signal to search engines that your content is outdated or poorly maintained.

Quick Reference

  • Regularly scan for external links returning 4xx or 5xx error codes
  • Update broken links to the new correct URL or remove them entirely
  • Avoid linking to expired domains that may have been repurposed

Check

Scan the page for any external links that lead to 404 pages or other error states.

Fix

Update the broken external link to a working URL or remove the link if the resource no longer exists.

Explain

Explain the impact of 'link rot' on a website's perceived quality and user trust.

Code Review

Review metadata generation, rendered HTML, structured data, and response headers related to Fix or remove broken external 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-external-links

Reviews

No reviews yet. Tell others what you thought.

Comments

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.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

404-page

FreeSummaryAI rating 100

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.

  • Creating a helpful custom 404 page
  • Adding search and navigation for broken links
  • Checking missing pages that return HTTP 200
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

about-page

FreeSummaryAI rating 90

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.

  • Reviewing a website’s About page
  • Creating a page about the organization and its mission
  • Checking how operator information appears in rendered output
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessibility-testing

FreeSummaryAI rating 80

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 accessibility coverage for shared components
  • Add accessibility checks to page flow tests
  • Run accessibility tests in CI
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessible-authentication

FreeSummaryAI rating 90

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.

  • Reviewing accessibility across the sign-in process
  • Checking verification code paste and autofill
  • Inspecting password reset and account recovery
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessible-notifications

FreeSummaryAI rating 100

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.

  • Reviewing form error announcements
  • Checking success message display duration
  • Auditing live update notifications
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

accessible-tables

FreeSummaryAI rating 100

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.

  • Reviewing tables for screen reader accessibility
  • Checking header relationships in tables with merged cells
  • Reviewing table patterns in a design system
thedaviddias/Front-End-Checklist74.5KUpdated Oct 6, 2026

See all skills by thedaviddias

Report a problem with this skill