Lighthouse Audit
Operated by Google
Quick Facts
- User-Agent:
- Chrome-Lighthouse
- Category:
- SEO Tools
- Operator:
- Safety:
- Safe
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- None published by Google
Reported, not operator documented
Google has not published a crawler page that names Chrome-Lighthouse. It is listed here because a credible public source does: GitHub (GoogleChrome/lighthouse source). Lighthouse audit runner appends Chrome-Lighthouse to its user agent. It is a testing tool, not a crawler; sites see it when someone runs PageSpeed Insights or a Lighthouse audit.
What that means for you: the robots.txt rule on this page is the best available spelling, and a well-behaved crawler using this string will honour it, but there is no vendor statement of purpose, crawl rate or robots.txt compliance to rely on. Treat a matching request in your logs as a detection clue, not proof of who sent it, and combine the rule with a firewall rule if the traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.
What is Lighthouse Audit?
Lighthouse Audit is a monitoring and validation agent operated by Google. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Lighthouse Audit is a monitoring and validation agent operated by Google. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Lighthouse Audit uses the user-agent token Chrome-Lighthouse. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
What happens if you block Lighthouse Audit?
How to block Lighthouse Audit with robots.txt
<code>User-agent: Chrome-Lighthouse</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Lighthouse Audit safe to allow?
What does Lighthouse Audit do?
Understanding Lighthouse Audit's purpose helps you decide whether to allow or block it.
- Validates pages, ads, or policy compliance
- Performs automated quality and safety checks
- Does not collect training data
- No impact on search rankings
- Generally safe to allow
Frequently Asked Questions
What user-agent string does Lighthouse Audit use?
Chrome-Lighthouse. That spelling comes from GitHub (GoogleChrome/lighthouse source), not from Google, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.Is Lighthouse Audit safe?
Will blocking Lighthouse Audit hurt my SEO?
How do I block Lighthouse Audit in robots.txt?
/robots.txt file:User-agent: Chrome-Lighthouse Disallow: /
This instructs Lighthouse Audit not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Lighthouse Audit respect robots.txt?
Chrome-Lighthouse will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.How do I verify if Lighthouse Audit is crawling my site?
Chrome-Lighthouse (for example grep -i "Chrome-Lighthouse" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Google sent it.