incident report · ongoing
One <meta> tag.
47 days of lost
organic traffic.
LintPage is a pre-launch linter for websites. Paste a URL, get 60 automated checks in ~30 seconds — the kind of checks that would have caught a stray <meta name="robots" content="noindex"> before it cost someone their quarter. Plus: AI crawler accessibility, OG regression detection, and the checks Lighthouse CI doesn't do.
traffic lost−90%organic, over 30 days
time to detect14dmedian, no monitoring
time to fix2mwith LintPage, pre-deploy
~/lintpage — zshv1.4.2
# paste any URL · 60 checks · ~30s · no signup
lintpage@prod~$scan --url
✓ free✓ no signup✓ all 60 checks✓ results in ~30s
§ 02 · The kill list
Every issue we catch. Every dollar it costs you.
60 automated checks across indexability, crawlability, meta tags, Open Graph, structured data, SSL, performance, accessibility, and AI visibility. Each one includes a severity and a one-minute fix.
LP-009pre-launch/robots-noindexChecks for noindex/nofollow in the robots meta tagPre-LaunchCORE
LP-046pre-launch/robots-txt-checkFetches and validates robots.txt for proper directivesPre-LaunchPRO
LP-015pre-launch/sslChecks that the site is served over HTTPSPre-LaunchPRO
LP-047pre-launch/sitemap-presenceChecks for the existence and validity of sitemap.xmlPre-LaunchPRO
LP-008seo/canonical-urlChecks for a canonical link tag and validates the URLSEOCORE
LP-045seo/broken-internal-linksChecks that internal links on the page resolve successfully (no 404s or server errors)SEOPRO
LP-002seo/meta-descriptionChecks for the presence and length of the meta description tagSEOCORE
LP-025performance/performanceChecks for inline styles, lazy loading, and script countPerformancePRO
LP-005seo/og-imageChecks for the og:image meta tagSEOCORE
LP-010seo/heading-structureValidates H1 tag presence, count, and heading hierarchySEOCORE
LP-037seo/structured-data-validateValidates JSON-LD structured data for required fields based on schema typeSEOPRO
LP-051ai visibility/ai/gptbot-silent-blockrobots.txt allows GPTBot but live fetch returns 403/429 (likely Cloudflare or WAF block)AI VisibilityPRO
# and 48 more. full rule table at /checks
§ 03 · ships everywhere you ship
Three surfaces. One linter.
Paste a URL in the browser. Pipe the CLI into your deploy hook. Block PRs in CI. Same engine, same rules, same report.
lintpage.com — scan~30s
# paste a URL, hit scan
▸
✓ 4 passed · 1 failed · 2 warnings · (27 / 30)
§ 04 · post-mortem
Same deploy. Two outcomes.
The meta tag took 4 seconds to write. What came next took 47 days.
⚠ without lintpage
Day 0
Deploy to productionnoindex tag ships unnoticed
Day 14
Traffic starts droppingGoogle removes pages from index
Day 30
Team notices−90% organic, root cause unknown
Day 47
Root cause foundOne meta tag. One line. That's it.
Day 90
Partial recoveryStill −40% below baseline
✓ with lintpage
Pre-launch
Paste staging URL60 checks run in ~30 seconds
+5s
Issue detectednoindex flagged CRITICAL
+2m
Fix appliedTag removed, rescan passes
Launch
Deploy with confidenceClean report. No surprises.
Outcome
0 days of lost traffic0 dollars wasted
§ 05 · free tools
Check one thing at a time.
When you just need to verify one thing — no signup, no scan history. Just an answer.
01Meta Tag CheckerCheck your page title, meta description, viewport, charset, and robots tags.02Robots.txt ValidatorValidate your robots.txt file for syntax errors and blocking rules.03AI Crawler CheckerTest if ChatGPT, Claude, and Perplexity can actually read your page — not just whether your robots.txt says they can.04Open Graph Tag PreviewCheck your Open Graph and Twitter Card tags for social media sharing.05Sitemap ValidatorValidate your sitemap.xml file format and URL count.06Heading Structure CheckerAnalyze your H1-H6 heading hierarchy for SEO best practices.
§ 06 · don't be next week's post-mortem
Every hour you wait is another hour your site could be invisible.
Run your first scan now. It takes 30 seconds. No signup. Nothing to install.
~/lintpage — zshv1.4.2
# paste any URL · 60 checks · ~30s · no signup
lintpage@prod~$scan --url
§ 07 · faq
Questions, answered.
How is LintPage different from Lighthouse CI? +
Lighthouse CI runs Google's Lighthouse audits in your pipeline — performance, basic SEO, accessibility, best practices. LintPage focuses on the deployment disasters Lighthouse misses: AI crawler accessibility (does ChatGPT/Claude/Perplexity actually receive your page?), staging URL leaks into Google's index, OG tag regressions across redesigns, schema markup breakage. Plus the catastrophic basics — that stray noindex tag — caught BEFORE they ship. We complement Lighthouse CI; we don't replace it.
What exactly does it check? +
60 rules across indexability (noindex, robots.txt, sitemap), crawlability (redirects, broken links, canonicals), meta (title, description, Open Graph, Twitter cards, structured data), SSL, performance budgets, and accessibility essentials. Every check has a severity level and a short fix.
Do I need to be an SEO expert? +
No. We explain everything in plain English with the exact one-minute fix. Most issues take 2–5 minutes; the catastrophic ones take seconds.
Is my data private? +
Yes. We fetch publicly accessible pages — the same content Google sees. No crawling behind auth, no data shared with third parties, no retention beyond your scan history.
Can I run it in CI? +
Yes. `npx lintpage scan $DEPLOY_URL --fail-on-error` in any CI. Fails the build on critical issues, writes a JUnit-style report.