lintpage

CLI tool that audits websites for SEO, accessibility, performance, and AI visibility issues. Catch noindex tags, broken meta tags, missing alt text, slow pages, security problems, and AI crawler blocks before they hurt your rankings and AI search visibility.

Install

npm install -g lintpage

Or as a dev dependency:

npm install -D lintpage

Usage

lintpage https://example.com

The CLI automatically prepends https:// if no protocol is provided:

lintpage example.com

Output

✗ seo/title — Missing title tag
   Add a <title> tag

⚠ seo/meta-description — Meta description is too short
   Expand your meta description

ℹ accessibility/html-lang — Missing lang attribute

DEPLOY BLOCKED · 1 critical · 1 warning · 1 info

Exit codes:

• 0 — all checks pass
• 1 — critical issues found (or warnings with --fail-on-warning)
• 2 — runtime error

Options

| Flag | Description | | ------------------- | ------------------------------------------------- | | --format <format> | Output format: text (default), json, github | | --config <path> | Path to a config file | | --fail-on-warning | Exit 1 on warnings, not just criticals | | --ai-only | Run only the AI Visibility module (LP-050–LP-060) | | --skip-ai | Skip the AI Visibility module | | --quiet | Minimal output (counts only) |

Rules

LintPage checks 60 rules out of the box across five categories:

Pre-Launch

| Rule | Severity | What it checks | | ------------------ | -------- | ----------------------------------------------------- | | robots-noindex | CRITICAL | Robots noindex/nofollow directives | | ssl | CRITICAL | Site served over HTTPS | | x-robots-tag | CRITICAL | X-Robots-Tag HTTP header noindex/nofollow | | robots-txt-check | WARNING | robots.txt presence and validity | | sitemap-presence | WARNING | sitemap.xml presence and validity | | tracking | WARNING | Google Analytics, GTM, or Facebook Pixel | | mixed-content | WARNING | HTTP resources loaded on HTTPS page | | https-links | WARNING | Internal links use HTTPS instead of HTTP | | cors-policy | WARNING | Overly permissive CORS configuration | | security-headers | INFO | CSP, HSTS, X-Content-Type-Options, Permissions-Policy |

SEO

| Rule | Severity | What it checks | | ---------------------------- | -------- | ------------------------------------------------------- | | broken-internal-links | CRITICAL | Internal links resolve (no 404s or server errors) | | title | WARNING | Title tag presence and length (30–60 chars) | | meta-description | WARNING | Meta description presence and length | | heading-structure | WARNING | Single H1, valid heading hierarchy | | canonical-url | WARNING | Canonical URL tag | | og-title | WARNING | OpenGraph title | | og-description | WARNING | OpenGraph description | | og-image | WARNING | OpenGraph image | | og-url | WARNING | OpenGraph URL | | twitter-card | WARNING | Twitter Card meta tags | | twitter-image | WARNING | Twitter/X image meta tag | | viewport | WARNING | Viewport meta tag for mobile responsiveness | | favicon | WARNING | Favicon presence | | anchor-missing-href | WARNING | All <a> elements have a valid href | | duplicate-meta | WARNING | Duplicate title, description, or canonical tags | | og-image-size | WARNING | OG image dimensions (recommended 1200x630) | | og-image-type | WARNING | OG image format is widely supported | | social-preview-render | WARNING | Complete meta tags for social sharing previews | | title-keyword-stuffing | WARNING | Keyword stuffing in page title | | title-uniqueness | WARNING | Title is not generic or auto-generated | | description-uniqueness | WARNING | Meta description is not generic or auto-generated | | structured-data-validate | WARNING | JSON-LD structured data has required fields | | hreflang | WARNING | Hreflang tags for multi-language pages | | meta-refresh-redirect | WARNING | No <meta http-equiv="refresh"> redirects | | nofollow-audit | WARNING | rel="nofollow" usage on internal vs external links | | charset | WARNING | Character encoding declaration | | canonical-self-referencing | INFO | Canonical URL points to the current page | | structured-data | INFO | JSON-LD structured data presence | | thin-content | INFO | Sufficient text content for search engines (300+ words) | | content-to-html-ratio | INFO | Ratio of visible text to total HTML markup |

Accessibility

| Rule | Severity | What it checks | | -------------------- | -------- | ------------------------------------------------- | | html-lang | WARNING | lang attribute on <html> | | image-alt-text | WARNING | All images have alt attributes | | accessibility | WARNING | Buttons, links, inputs, and ARIA attributes | | semantic-structure | WARNING | Semantic HTML: landmarks, lists, tables, articles |

Performance

| Rule | Severity | What it checks | | ---------------------- | -------- | --------------------------------------------------------- | | ttfb | WARNING | Server response time (Time to First Byte) | | meta-render-blocking | WARNING | Render-blocking stylesheets and synchronous scripts | | lazy-load-lcp | WARNING | Above-the-fold images not lazy-loaded | | performance | INFO | Lazy loading, inline styles, and script count | | image-dimensions | INFO | Images have explicit width/height to prevent layout shift |

AI Visibility

Probes how AI assistants and crawlers (ChatGPT, Claude, Perplexity, Gemini) see your page — combining robots.txt directives with live per-bot fetches to catch silent edge blocks (e.g. Cloudflare's default AI-bot 403). Run these in isolation with --ai-only, or skip them with --skip-ai.

| Rule | Severity | What it checks | | ------------------------------- | -------- | ------------------------------------------------------------------- | | ai/all-crawlers-blocked | CRITICAL | Every tested AI bot is blocked — page is invisible to AI assistants | | ai/gptbot-silent-block | CRITICAL | robots.txt allows GPTBot but the live fetch is blocked (403/429) | | ai/claudebot-silent-block | CRITICAL | robots.txt allows ClaudeBot but the live fetch is blocked (403/429) | | ai/perplexitybot-silent-block | CRITICAL | robots.txt allows PerplexityBot but the live fetch is blocked | | ai/chatgpt-user-blocked | CRITICAL | ChatGPT-User (live retrieval) cannot reach the page | | ai/claude-user-blocked | CRITICAL | Claude-User (live retrieval) cannot reach the page | | ai/perplexity-user-blocked | CRITICAL | Perplexity-User (live retrieval) cannot reach the page | | ai/google-extended-disallowed | WARNING | Google-Extended (Gemini) disallowed in robots.txt | | ai/applebot-extended-disallowed | INFO | Applebot-Extended disallowed in robots.txt | | ai/empty-content-to-bot | WARNING | Bot receives near-empty HTML (content needs JS to render) | | ai/llms-txt-missing | INFO | No llms.txt file found |

Verdict

LintPage emits one of two verdicts after each scan:

• READY TO SHIP — no critical issues. Safe to deploy. Warnings and info findings remain for follow-up.
• DEPLOY BLOCKED — at least one critical issue. Fix before deploying. The CLI exits with code 1 so CI fails the build.

Issue severities:

• CRITICAL — production-breaking. e.g. noindex tag on prod, broken sitemap, broken SSL.
• WARNING — fix soon. e.g. missing meta description, oversized title, broken canonical.
• INFO — recommended. e.g. structured data missing, low content-to-HTML ratio.

Each rule has a stable identifier in the format <category>/<ruleId> (e.g. seo/title, accessibility/image-alt-text). The full registry of rules is at https://lintpage.com/checks.

Configuration

Generate a config file:

lintpage init

This creates .lintpagerc.json in the current directory. You can also use .lintpagerc or lintpage.config.json.

Disable a rule

{
  "rules": {
    "og-image": false
  }
}

Override severity

{
  "rules": {
    "meta-description": {
      "enabled": true,
      "severity": "CRITICAL"
    }
  }
}

CI / GitHub Actions

Use the github format for native annotations:

- name: Lint page
  run: npx lintpage https://your-site.com --format github --fail-on-warning

This outputs GitHub-compatible annotations that show up directly on your PR.

License

MIT