Google Page Speed Insights
Operated by Google
Quick Facts
- User-Agent:
- Google Page Speed Insights
- Category:
- SEO Tools
- Operator:
- Safety:
- Safe
- Blocking Impact:
- Varies - Evaluate before blocking
- SEO Impact Score:
- 0/10
- Official docs:
- developers.google.com
What is Google Page Speed Insights?
The specific User-Agent token used to control Google's PageSpeed Insights tool via robots.txt.
The specific User-Agent token used to control Google's PageSpeed Insights tool via robots.txt.
Google Page Speed Insights is a commercial SEO analytics crawler operated by Google. It builds backlink graphs, crawls for technical SEO issues, and tracks keyword rankings. The user-agent Google Page Speed Insights is well-known and respected in the SEO industry. Blocking it removes your domain from Google's index, preventing competitors from analysing your backlink profile via their platform. However, other Google users also lose visibility into links pointing TO your site - weigh this trade-off carefully.
What happens if you block Google Page Speed Insights?
How to block Google Page Speed Insights with robots.txt
<code>User-agent: Google Page Speed Insights</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Google Page Speed Insights safe to allow?
Google Page Speed Insights is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).What does Google Page Speed Insights do?
Understanding Google Page Speed Insights's purpose helps you decide whether to allow or block it.
- Analyzes website structure and SEO health
- Tracks backlinks and referring domains
- Monitors keyword rankings and competitor analysis
- Crawls sites for technical SEO audits
- Generates reports for SEO professionals
Frequently Asked Questions
What is the official user-agent string for Google Page Speed Insights?
Google Page Speed Insights. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Google Page Speed Insights by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.Is Google Page Speed Insights safe?
Google Page Speed Insights is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).Will blocking Google Page Speed Insights hurt my SEO?
How do I block Google Page Speed Insights in robots.txt?
/robots.txt file:
User-agent: Google Page Speed Insights Disallow: /This instructs Google Page Speed Insights not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g.,
Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.Does Google Page Speed Insights respect robots.txt?
How do I verify if Google Page Speed Insights is crawling my site?
Google Page Speed Insights (case-insensitive grep: grep -i "Google Page Speed Insights" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Google Page Speed Insights specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).What is the crawl frequency of Google Page Speed Insights?
User-agent: Google Page Speed Insights Crawl-delay: 10(10 second delay between requests).
Can I block Google Page Speed Insights from specific pages only?
Disallow: / you can restrict Google Page Speed Insights to specific paths:
User-agent: Google Page Speed Insights Disallow: /private/ Disallow: /staging/ Allow: /This allows Google Page Speed Insights everywhere except the listed paths. Path matching in robots.txt uses prefix matching -
Disallow: /private/ blocks /private/page.html but NOT /public/private/.