Ignoring Domains and Using Ignore Patterns
Not every link in your Markdown documents needs active validation. Development URLs, local references, staging environments, or third-party services with frequent downtime can clutter results with false warnings. The Markdown Link Checker solves this with flexible ignore patterns that let you exclude specific links from checking.
The ignore patterns feature lives in the configuration panel and accepts comma-separated values. Each pattern matches against the full resolved URL, giving you precise control over what gets skipped.
Common Use Cases
Local development servers often use localhost or 127.0.0.1 addresses that are unreachable outside your machine. Adding localhost or 127.0.0.1 to ignore patterns prevents unnecessary failed attempts during collaborative reviews.
Staging or preview deployments typically live on temporary subdomains. Ignoring patterns like staging.example.com or *.vercel.app keeps validation focused on production links only.
Internal company wikis or documentation behind authentication walls return errors when checked from outside the network. Patterns matching your intranet domains ensure smooth validation for public-facing content.
Pattern Syntax
Simple domain matches work directly: enter example.com to ignore all links to that domain and subdomains. For broader coverage, use wildcard prefixes like *.example.com to catch any subdomain.
Path-specific ignores are possible too. Adding /admin/ ignores any URL containing that path segment, useful for skipping protected areas.
Multiple patterns combine seamlessly. Separate them with commas: localhost, 127.0.0.1, staging.mysite.com, *.github.io/wiki.
How Ignored Links Appear
Matching links receive Ignored status in the results table. They display with grayed styling, the original URL, and line number for reference, but do not affect overall validation metrics or trigger warnings.
This clear distinction helps reviewers understand why certain links were skipped without removing them from the report entirely.
Best Practices
Start with common development domains in your personal workflow. For team projects, document agreed ignore patterns in project guidelines to ensure consistent results across members.
Review ignored links periodically. As staging sites go live or local references move to production, update patterns accordingly to maintain accuracy.
Combine ignore patterns with external-only validation mode when you want to focus solely on public HTTP links while completely bypassing internal references.
Ignore patterns turn a universal validator into a targeted quality tool that respects your project structure and development stages.
By excluding known-safe or irrelevant links, you streamline reviews and concentrate effort where it matters most.
Clean results start with smart ignore patterns.