Bot intelligence record
Google Business Link Verification
Review firstUse the Google-BusinessLinkVerification identifier to separate Google security scanning or verification traffic from normal visitor requests in server logs.
- Operator
- Family
- Type
- Security
- Source type
- Official
- Last checked
- 2026-05-20
User-Agent Pattern
GoogleGoogle-BusinessLinkVerification
User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.
Robots.txt Snippet
Click snippet to copyUser-agent: Google-BusinessLinkVerification Disallow: /Click the snippet to copy it, or highlight the text manually.
Handling Guidance
DependsUse this record as bot intelligence, then verify the request source and behavior before allowing, blocking, or rate limiting.
Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.
Record Details
Structured data- Operator
- Family
- Type
- Security
- Purpose
- Security
- Identity type
- Official Documented
- Confidence
- High
- Last verified
- 2026-04-19
- Last checked
- 2026-05-20
- Source type
- Official
- Verification
- Use the documented Google-BusinessLinkVerification user-agent. Google states these verification crawlers do not follow robots.txt.
- Spoofing risk
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Notes
Google Business Link Verification is listed in the Botcrawl directory as a security scanner from Google. The primary identifier for log review is Google-BusinessLinkVerification.
Identification
- User-agent pattern:
Google-BusinessLinkVerification - Family: Google
- Type: Security
- Kind: Scanner
Common use
Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.
Verification and handling
Use the documented Google-BusinessLinkVerification user-agent. Google states these verification crawlers do not follow robots.txt.
Directory guidance marks the risk level as Neutral and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.
Robots.txt handling: No.
Evidence and Source
- Use the documented Google-BusinessLinkVerification user-agent. Google states these verification crawlers do not follow robots.txt.
- Match `Google-BusinessLinkVerification` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Do not treat a user-agent match alone as proof of identity for allow-listing.
- Security scanning, malware checks, abuse prevention, compliance review, or vulnerability monitoring.
- User-agent strings can be spoofed. For allow-listing or low-friction rules, pair the published identifier with operator documentation or cryptographic verification when available.
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.