83
B
Alert
No urgent crawler access problem was found in this audit.
Advise
Your most important bots appear to be reaching the site normally, so the main opportunities are lower-priority hardening and polish.
Action Step
Keep monitoring crawler access and focus next on response headers, caching, and small technical improvements.
Key Findingswhat failed first
Warnings
COEP is not set.
ETag is missing.
Passed
HTTPS is enabled.
HSTS is valid.
robots.txt is present.
Fix Priorityrecommended next steps
1Add a COEP header if cross-origin isolation is needed.
2Add ETag or validator headers for better cache revalidation.
3Review the detailed sections below for lower-priority hardening opportunities.
4Review the detailed sections below for lower-priority hardening opportunities.
Speed
83
Excellent response path
Security
95
core protections are present
SEO
95
crawl assets are discoverable
Bot Access
36
bot responses need attention
Result Integrity98% measurement confidence · 1 conflict
LOWCSP contains 'unsafe-inline' — inline script execution is permitted, which is the most common CSP bypass vector
Replace 'unsafe-inline' with nonce-based or hash-based script allowlisting. This single change has more XSS-protection impact than any other CSP improvement.
Main fetch: ok
Security: ok
SEO: ok
20/20 bot probes succeeded
Bot Importance Hierarchy
all ranked bots stable
Ranks crawlers by practical impact so users can tell whether a failure is mission-critical, growth-related, or lower-priority.
Tier 1
Mission Critical
Search and AI discovery bots that most directly affect visibility and retrieval.
stable tier
Google
Stable
OAI Search
Stable
GPTBot
Stable
Vertex AI
Stable
ChatGPT
Stable
Perplexity
Stable
Claude
Stable
Tier 2
Growth & Distribution
Bots that influence secondary reach, ecosystem visibility, and social preview distribution.
1 issue
Amazon
Blocked
Bing
Stable
Meta AI
Stable
Mistral
Stable
Apple
Stable
Facebook
Stable
Twitter
Stable
LinkedIn
Stable
Tier 3
Reference & Baseline
Supportive or baseline agents useful for comparison and lower-priority monitoring.
1 issue
ByteDance
Blocked
CommonCrawl
Stable
DuckDuck
Stable
Chrome
Stable
BotWatcher
Stable
consistent access caution anomaly / blocked
Anomaly Detection
peak Bot/Crawl spike
Asset Discovery
6/8 public assets visible
HTTPS
TLS active
Cloudflare
DYNAMIC
Compression
none
robots.txt
crawl rules live
Sitemap
1 URLs
llms.txt
missing
Structured Data
7 schema blocks
Analytics
tracking visible
Map routes are derived from bot simulation responses and compliance checks. This board is audit-driven, not global telemetry.
Bot Access & Consistency36▾
✕
Bot Access & Consistency 36
Your site appears to respond differently to some crawlers, which can reduce AI search visibility and trigger cloaking concerns.
ℹ
Why this matters
AI search visibility, social previews, and crawler trust can drop when some agents receive different responses or are blocked.
✕
Different bots received different responses
Mixed status code classes: 2xx, 4xx
✕
Status codes stayed consistent
Mixed status code classes detected
ℹ
AI crawler guidance
Add /llms.txt for AI crawler guidance
Bot Status Strip
Google
Bing
DuckDuck
Apple
GPTBot
Claude
Perplexity
Facebook
Twitter
LinkedIn
Chrome
BotWatcher
amazonbot
bytespider
ccbot
chatgptuser
oaisearchbot
mistralaiuser
googlevertexbot
metaexternalagent
| Bot | Result | HTTP | robots.txt | Notes |
|---|---|---|---|---|
| amazonbot | Review | 403 | unspecified | HTTP 403 |
| bytespider | Review | 403 | unspecified | HTTP 403 |
| Googlebot 2.1 | Accessible | 200 | allowed | 14ms |
| Bingbot 2.0 | Accessible | 200 | allowed | 14ms |
| DuckDuckBot | Accessible | 200 | unspecified | 7ms |
| Applebot | Accessible | 200 | unspecified | 14ms |
| GPTBot (OpenAI) | Accessible | 200 | allowed | 14ms |
| ClaudeBot (Anthropic) | Accessible | 200 | allowed | 11ms |
| PerplexityBot | Accessible | 200 | unspecified | 14ms |
| Facebook External Hit | Accessible | 200 | unspecified | 18ms |
| Twitterbot | Accessible | 200 | unspecified | 19ms |
| LinkedInBot | Accessible | 200 | unspecified | 19ms |
| Chrome (baseline) | Accessible | 200 | unspecified | 21ms |
| BotWatcherAudit/1.0 | Accessible | 200 | unspecified | 20ms |
| ccbot | Accessible | 200 | unspecified | 24ms |
| chatgptuser | Accessible | 200 | unspecified | 27ms |
| oaisearchbot | Accessible | 200 | unspecified | 24ms |
| mistralaiuser | Accessible | 200 | unspecified | 33ms |
| googlevertexbot | Accessible | 200 | unspecified | 26ms |
| metaexternalagent | Accessible | 200 | unspecified | 27ms |
Performance83▾
TTFB
103ms
Total Time
104ms
Body Size
96.2 KB
Status
200
Compression
none
CF Cache
DYNAMIC
✓
HTTPS
Secure TLS
✓
TTFB: 103ms
Excellent
✓
HTTP 200
OK
✕
Compression
Enable gzip or Brotli
Note 1: Uncompressed responses waste bandwidth and slow down page load times for all visitors.
Note 2: Crawlers see increased latency and may deprioritize your site in crawl schedules.
Note 3: Enable gzip or Brotli compression in your web server config (nginx: gzip on; Apache: mod_deflate).
✓
Cache-Control
max-age=600
ℹ
ETag
Consider adding ETag
✓
Redirects: 0
No redirects
✓
Cloudflare CDN
CF-Cache-Status: DYNAMIC
Security Headers95▾
✓
HTTPS / TLS
Secure
✓
HSTS
max-age=31536000; includeSubDomains
✓
Content-Security-Policy
default-src 'self'; base-uri 'self'; object-src 'none'; script-src 'self' https:…
✓
X-Content-Type-Options
nosniff
✓
Clickjacking protection
Via CSP frame-ancestors
✓
Referrer-Policy
strict-origin-when-cross-origin
✓
Permissions-Policy
camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()
✓
Cross-Origin-Opener-Policy
same-origin
ℹ
Cross-Origin-Embedder-Policy
Not set
SEO & Crawlability95▾
✓
Meta title
btcminergpt.ai | Bitcoin Mining Intelligence, Mempool Fee Tracker & R&…
✓
Meta description
AI-powered intelligence platform for home Bitcoin miners. Real-time Bitcoin mempool fee gauge, live …
✓
Canonical URL
https://btcminergpt.ai/
✓
Viewport meta
width=device-width, initial-scale=1.0, maximum-scale=5
✓
robots.txt
1 sitemap(s)
✓
Googlebot access
Allowed
✓
Sitemap.xml
1 URL(s)
✓
Open Graph
og:title = "btcminergpt.ai | Bitcoin Mining Intelligence &…"
✓
JSON-LD Structured Data
WebSite, Article, Article, SoftwareApplication, FAQPage, Organization, WebApplication
ℹ
llms.txt (AI compliance)
Not found - add for GPTBot, Claude etc.
Third-Party & Privacy▾
Analyzes raw HTML source for third-party domains, consent tooling, render-blocking scripts, and tracking pixels. Tools injected at the edge (Cloudflare Zaraz, CF Web Analytics) or loaded dynamically via JS after page load will not appear here — use your browser's Network tab for a complete runtime picture. Results are informational and do not affect your score.
19 third-party domains
·
0 render-blocking scripts
·
✗ No consent tool
Third-Party Domains in Source
| amboss.space |
| amboss.tech |
| btcminergpt.ai |
| buymeacoffee.com |
| chatgpt.com |
| creditcard.exchange.gemini.com |
| fonts.googleapis.com |
| fonts.gstatic.com |
| forms.zohopublic.com |
| google-analytics.com |
| googletagmanager.com |
| lightningnetwork.plus |
| llmadvisor.ai |
| lnrouter.app |
| mempool.space |
| + 4 more |
Platforms Detected in Source
✓ Google Analytics 4✓ Cloudflare Web Analytics○ Universal Analytics (UA)○ Google Tag Manager○ Cloudflare Zaraz○ Plausible○ Fathom○ Matomo / Piwik○ Hotjar○ Microsoft Clarity○ Segment○ Mixpanel○ Heap○ Amplitude○ HubSpot○ Intercom○ Adobe Analytics○ Meta (Facebook) Pixel○ TikTok Pixel○ Crisp Chat
Domain Surface▾
Probes common subdomains and non-standard HTTP/HTTPS ports to map the visible attack surface of this domain. Results are based on network-layer responses only. Informational — does not affect your score.
!
Wildcard DNS detected — subdomain results are not meaningful
A probe of a guaranteed-nonexistent subdomain (
wildcardtestconfirmationbotwatcherai.btcminergpt.ai) returned HTTP 530, definitively confirming a wildcard DNS record (*.btcminergpt.ai) is active and answering all subdomain requests. Individual subdomain scan results are unreliable when wildcard DNS is present and have been suppressed.Non-standard Ports
| Port | Status | HTTP | TTFB |
|---|---|---|---|
| http:8080 | Responded | 301 | 83ms |
| https:8443 | Not open | closed | — |
| http:3000 | Responded | 301 | 89ms |
| http:8000 | Responded | 301 | 89ms |