Analytics
Overview
RndrKit's analytics give you visibility into how search engine bots and social media crawlers interact with your site. Every bot request is logged, giving you data on which pages are being crawled, which bots are visiting, and how your cache is performing.
Accessing Analytics
Analytics are available at two levels:
- Account-wide -- From the main dashboard, view aggregated data across all your domains.
- Per-domain -- Click a specific domain and navigate to the Analytics tab for domain-specific data.
Crawler Activity Over Time
The main chart shows bot request volume over time. You can view this data at different granularities:
- Daily -- Render counts for each day
- Weekly -- Aggregated by week
- Monthly -- Aggregated by month
This chart helps you understand trends in crawler activity. A sudden spike might indicate that a search engine is recrawling your site after you submitted a new sitemap. A gradual increase suggests improving discoverability.
Top Pages
The top pages table shows which URLs on your domain receive the most bot visits. Each entry includes:
- URL path -- The page being crawled
- Total visits -- Number of bot requests for this page
- Unique bots -- How many different crawlers have visited this page
- Last visited -- When the most recent bot visit occurred
Use this data to:
- Identify your most crawled pages and ensure they are properly optimized
- Spot unexpected pages that bots are visiting (404 pages, redirect chains)
- Prioritize which pages to warm in the cache
Bot Distribution
The bot distribution chart shows which crawlers are visiting your site and how often. RndrKit organizes crawlers into four categories so you can see at a glance where your renders are being used:
Search Crawlers
The bots that actually get your pages into search results. These are the ones you care about most.
- Googlebot -- Google Search
- Bingbot -- Microsoft Bing
- Applebot -- Apple / Siri
- DuckDuckBot -- DuckDuckGo
- YandexBot -- Yandex
AI Crawlers
AI companies crawling the web for training data and search augmentation.
- ClaudeBot -- Anthropic
- GPTBot -- OpenAI
- Amazonbot -- Amazon
- Bytespider -- ByteDance / TikTok
Social Crawlers
These fetch your pages to generate link previews when someone shares your URL on social media.
- FacebookBot -- Facebook / Meta
- TwitterBot -- Twitter / X
- LinkedInBot -- LinkedIn
SEO Tool Crawlers
Professional SEO tools that analyze your site.
- AhrefsBot -- Ahrefs
- SemrushBot -- Semrush
- DotBot -- Moz
- MJ12bot -- Majestic
- PetalBot -- Aspiegel (Petal Search)
Excluded Bots
Some bots are not counted as renders and do not show up in your analytics. RndrKit excludes these because they are monitoring or research tools that would waste your render quota:
- DotBot (Moz) -- Proxied directly to your origin, not pre-rendered
- UptimeRobot -- Uptime monitoring service, proxied to origin
These excluded bots hit your origin server directly instead of going through the rendering pipeline, so they never consume any of your monthly renders.
Understanding which bots visit helps you:
- Confirm that major search engines are crawling your site
- See if social media crawlers are fetching your Open Graph tags
- Identify SEO tool crawlers that might be consuming your render quota
Cache Performance
The cache performance section shows:
- Hit rate -- Percentage of bot requests served from Redis cache
- Hits -- Number of requests served from cache (fast, under 50ms)
- Misses -- Number of requests that required a fresh Puppeteer render (2-5 seconds)
- Hit rate over time -- Chart showing cache efficiency trends
A healthy cache hit rate is typically above 70%. If your hit rate is low:
- Bots may be crawling many unique pages that have not been cached yet. Use cache warming to pre-render popular pages.
- Your cache TTL (1 hour by default) may be expiring before bots revisit the same pages.
Render Logs
The render logs table shows individual bot requests with full details:
| Column | Description |
|---|---|
| Timestamp | When the request was received |
| Path | The URL path that was requested |
| User Agent | The bot's user-agent string |
| Cache Status | HIT (served from cache) or MISS (fresh render) |
| Render Time | How long the render took in milliseconds (MISS only) |
You can filter and search logs by path, user agent, or cache status.
Usage Tracking
Your render usage is tracked against your plan's monthly limit. The usage section shows:
- Current period's render count
- Monthly render limit
- Percentage of limit used
- Estimated usage based on current trends
If you are approaching your limit, consider upgrading your plan or optimizing your cache hit rate.
Next Steps
- Cache Management -- Improve your cache hit rate
- SEO Audit -- Audit the pages bots are crawling
- Bot Detection -- Learn which bots RndrKit identifies