site-checker

Crawl an index URL and validate links, media, SEO tags, and console errors.

1|Updated Jun 3, 2025
One-click install
npx skills add https://github.com/jaysoo/dot-ai-config --skill site-checker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: site-checker
Source: https://github.com/jaysoo/dot-ai-config/tree/main/dot_gemini/skills/site-checker
Command: npx skills add https://github.com/jaysoo/dot-ai-config --skill site-checker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate all pages reachable from an index URL for broken links, missing images, SEO gaps, and console errors. Crawls index links shallowly (no recursion) and validates each page. Works with localhost, preview deploys, staging, and production. Optional compare mode diffs DOM against a reference URL.

Core Features & Use Cases

  • Check HTTP status, media health, SEO tags, accessibility basics, and console errors for each page.
  • Validate internal links health and detect mixed content on HTTPS pages.
  • Compare against a reference site to surface structural or content differences.

Quick Start

Run the site-checker on your index URL to validate links, media, SEO, and console errors.

Frequently Asked Questions about site-checker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my website for broken links and missing SEO tags?

To check for broken links and SEO gaps, crawl an index URL to validate HTTP status, media health, SEO tags, and console errors for each page automatically. This shallow crawl reports health metrics without recursion.

Can I run a site health check on localhost or staging preview deploys?

Yes, site health checks work with localhost, preview deploys, staging, and production URLs. The crawler validates pages reachable from the provided index URL across all these environments.

How do I detect mixed content and console errors on HTTPS pages?

Detect mixed content and console errors by running a validation crawl on your HTTPS pages. The checker reports mixed content issues alongside JavaScript console errors for each URL.

What is the best way to compare DOM differences between a staging and production site?

The best way to compare DOM differences is using the optional compare mode to diff a target site against a reference URL. This surfaces structural or content differences between the two sites.

Does shallow crawling validate accessibility basics and media health?

Yes, shallow crawling validates accessibility basics and media health. It checks each page linked from the index URL without recursion, enforcing deterministic checks with parallel processing.