Help & Documentation

Introduction

LogLens is a real-time web analytics and security monitoring platform. Unlike traditional analytics tools that rely on JavaScript tracking, LogLens analyzes your server logs to provide accurate, privacy-friendly insights into your website traffic.

What makes LogLens different?

• Server-side analytics — Captures all requests, including those from bots, scrapers, and users with ad blockers
• Real-time monitoring — See traffic as it happens with sub-second latency
• Bot detection & verification — Automatically identifies bots and verifies legitimate crawlers against their official IP ranges
• IP address analysis — Deep dive into individual IPs and IP ranges to identify patterns
• Smart alerts — Get notified instantly when traffic anomalies, errors, or suspicious bot activity occur
• Privacy focused — No cookies, no personal data collection, GDPR compliant by design
• Data export — Export any data table to CSV for further analysis
• CDN integration — Native support for AWS CloudFront, Cloudflare, and Vercel

Quick Start Guide

Get up and running with LogLens in just a few minutes.

Step 1: Create an Account

Sign up at app.loglens.ai using your email address. You'll automatically be set up with a personal organization.

Step 2: Add Your Website

From the dashboard, click on the website selector and choose "Add Website". Enter your domain name and a friendly name for your site.

Step 3: Connect Your Logs

You have several options to send logs to LogLens:

• AWS CloudFront — Use real-time logs with Kinesis Firehose (recommended for AWS users)
• Cloudflare — Use Cloudflare Workers to forward logs
• Vercel — Use Vercel Drains for instant setup (recommended for Vercel users)
• Import — Upload historical log files directly

Step 4: Configure Alerts

Navigate to the Alerts page to set up monitoring for traffic anomalies, error spikes, and suspicious bot activity. LogLens will automatically build a baseline over 24 hours and start detecting anomalies.

Step 5: View Your Analytics

Once logs start flowing, your dashboard will populate with real-time data. It typically takes 1-2 minutes for the first data to appear.

Key Concepts

Requests vs Visitors

LogLens tracks requests, not unique visitors. A single page load typically generates multiple requests (HTML, CSS, JS, images). This gives you a more complete picture of server load and resource usage.

Human vs Bot Traffic

LogLens automatically classifies traffic as either human or bot based on user agent analysis. Bot traffic is further categorized into:

• Search engines — Google, Bing, etc.
• Social media — Facebook, Twitter, LinkedIn crawlers
• AI crawlers — GPTBot, ClaudeBot, etc.
• Monitoring — Uptime monitors, health checks
• SEO tools — Ahrefs, SEMrush, etc.
• Scrapers — Generic or malicious bots

Verified vs Unverified Bots

Many bots claim to be legitimate crawlers (like Googlebot) but are actually impersonators. LogLens verifies bots by checking if their IP address matches the official IP ranges published by Google, Microsoft, OpenAI, and other major bot operators.

• ✓ Verified — IP matches official published ranges
• ⚠ Unverified — Claims to be a known bot but IP doesn't match

Time Periods

All analytics can be filtered by time period. Available options include:

• Last hour, 6 hours, 24 hours
• Last 7 days, 30 days, 90 days
• Last year
• Custom date range

Dashboard Overview

The main dashboard provides a high-level summary of your website traffic.

The main dashboard showing traffic overview, top bots, and live feed

Key Metrics

Dashboard Widgets

The dashboard includes several widgets:

• Traffic over time — Bar chart showing requests per time interval
• Top countries — Geographic distribution of traffic
• Top bots — Most active bot user agents with verification status
• Top paths — Most requested URLs
• Live feed — Real-time stream of incoming requests with bot verification badges

Time Filters

Use the time filter dropdown in the top-right corner to change the analysis period.

Preset Periods

Quick selection options include Last hour, 6 hours, 24 hours, 7 days, 30 days, 90 days, and 1 year.

Custom Date Range

Select "Custom" to specify exact start and end dates. This is useful for analyzing specific events or campaigns.

Country Filters

Filter your analytics by country to focus on specific geographic regions.

How to Use

1. Click the "All Countries" dropdown in the header
2. Select one or more countries from the list
3. All analytics will update to show only traffic from selected countries

This is particularly useful for:

• Analyzing traffic from your target markets
• Identifying suspicious traffic from unexpected countries
• Comparing behavior across different regions

Live Mode

Live mode shows requests as they happen in real-time.

Enabling Live Mode

Click the "Live" toggle in the top-right corner of the dashboard. When enabled, the dashboard will automatically refresh every 10 seconds and show a live feed of incoming requests.

Live Feed

The live feed shows the most recent requests with details including:

• Timestamp
• Request path
• HTTP method and status code
• Country of origin
• Human/bot classification
• Bot verification status (verified ✓ or suspicious ⚠)

Traffic Analysis

The Traffic page provides detailed analysis of your website requests.

Traffic Over Time

A stacked bar chart shows human traffic (cyan) and bot traffic (amber) over time. Hover over any bar to see exact counts for that time period.

Status Code Breakdown

See the distribution of HTTP response codes:

• 2xx (Success) — Successful requests
• 3xx (Redirect) — Redirects
• 4xx (Client Error) — Not found, forbidden, etc.
• 5xx (Server Error) — Server errors

Exporting Traffic Data

Click the "Export CSV" button to download the traffic data for further analysis in spreadsheets or other tools.

Bot Detection

LogLens automatically identifies and categorizes bot traffic based on user agent strings and behavior patterns.

Bot detection showing verified and unverified crawlers with request counts

Bot Categories

Bot Detail View

Click on any bot to see detailed information including:

• Total requests and percentage of traffic
• Verification status (verified or suspicious)
• Most requested paths
• Activity over time
• Response code distribution
• Full request history with status codes and IPs

Bot VerificationNEW

LogLens verifies that bots claiming to be from major providers (Google, Microsoft, OpenAI, etc.) are actually from their official IP ranges.

How Verification Works

When a request claims to be from a known bot (based on user agent), LogLens checks the client IP address against the official IP ranges published by that bot's operator:

• Google — googlebot.json (Googlebot, Google-Extended, etc.)
• OpenAI — openai.com/gptbot-ranges.json (GPTBot, ChatGPT-User)
• Microsoft — bingbot.json (Bingbot, MSNBot)
• Meta — facebookexternalhit, Facebook ranges
• Apple — Applebot
• Anthropic — ClaudeBot
• And many more...

Verification Badges

Bot requests are marked with verification badges throughout the interface:

• ✓ Verified — The IP address matches official published ranges. This is a legitimate bot.
• ⚠ Suspicious — The bot claims to be from a known provider but the IP doesn't match. May be an impersonator.

Where Verification Shows

Bot verification status is displayed in:

• Live Feed on the dashboard
• Bots list page
• Bot detail pages
• Request history tables

IP Range Updates

LogLens automatically fetches the latest official IP ranges from bot operators daily to ensure accurate verification.

IP AddressesNEW

The IP Addresses page provides detailed analysis of traffic by individual IP addresses and IP ranges.

IP address analysis showing top IPs and ranges with request counts

IP Tabs

The page has two tabs:

• IPs — Individual IP addresses with request counts
• Ranges — IP ranges (e.g., 192.168.1.x) with aggregated request counts

Traffic Graph

A line chart shows traffic over time. When no IP is selected, it shows all traffic. Click on an IP or range to filter the graph to show only requests from that source.

Viewing Request Details

Select an IP or range and click "View Requests" to see a detailed, paginated list of all requests including:

• Timestamp
• Request path
• HTTP method and status code
• User agent
• Referrer
• Country
• Bot classification

Exporting IP Data

Use the "Export CSV" button to download the IP list or request details for further analysis.

Path Analysis

Understand which pages and resources are most requested on your website.

Top Paths Table

Shows the most requested URLs with:

• Request count and percentage
• Average response time
• Human vs bot split
• Error rate

Path Detail View

Click any path to see detailed analytics including traffic over time, geographic distribution, and which bots are accessing it.

Filtering Paths

Use the search box to filter paths. This is useful for finding:

• Specific pages (e.g., /blog/)
• API endpoints (e.g., /api/)
• Static assets (e.g., .js, .css)

Referrers

See where your traffic is coming from.

Referrer Types

• Direct — No referrer (typed URL, bookmarks)
• Search — Google, Bing, DuckDuckGo, etc.
• Social — Facebook, Twitter, Reddit, etc.
• Other websites — Links from other sites

Referrer Detail View

Click any referrer to see which pages they're sending traffic to and how that traffic performs (bounce rate approximation based on single-request sessions).

Geography

Visualize where your visitors are located around the world.

Interactive world map showing traffic distribution by country

World Map

The interactive map shows traffic density by country. Darker colors indicate more traffic. Hover over any country to see exact request counts.

Country Table

A sortable table shows all countries with traffic, including:

• Request count and percentage
• Human vs bot ratio
• Top paths from that country

Devices

Understand what devices and browsers your visitors use.

Device Types

• Desktop — Windows, macOS, Linux
• Mobile — iOS, Android phones
• Tablet — iPads, Android tablets
• Bot — Automated crawlers

Browsers

See the distribution of browsers including Chrome, Safari, Firefox, Edge, and others.

Operating Systems

View traffic breakdown by OS: Windows, macOS, iOS, Android, Linux, etc.

Status Codes

Monitor HTTP response codes to identify errors and issues.

Status Code Categories

Error Investigation

Click on any status code category to see which paths are returning those codes. This helps identify:

• Broken links (404s)
• Permission issues (403s)
• Server problems (5xxs)

IP SearchNEW

Search for any IP address and instantly see all their requests. This is invaluable for investigating suspicious activity.

How to Search

1. Navigate to the IP Addresses page
2. Enter an IP address in the search box
3. Press Enter or click Search
4. View all requests from that IP in the selected time period

Search Results

Results include:

• Request history — Every request with timestamp, path, status, and user agent
• Bot classification — Whether the IP was identified as a bot
• Geographic data — Country of origin
• Response times — How long each request took

Use Cases

• Investigate suspicious IPs flagged elsewhere
• Verify bot activity from a specific IP
• Track what pages a particular visitor accessed
• Debug issues reported by a user at a specific IP

SEO & Crawlers OverviewNEW

The SEO & Crawlers section provides comprehensive analytics for search engine optimization, including crawler statistics and sitemap coverage analysis.

SEO dashboard showing crawler statistics, sitemap coverage, and crawl patterns

Key Metrics

Crawler Filter

Filter all SEO data by specific crawler using the dropdown:

• All Crawlers — Aggregate data from all search bots
• Googlebot — Google's main crawler
• Bingbot — Microsoft Bing's crawler
• Other crawlers — Yandex, Baidu, DuckDuckBot, etc.

Site Sections

View crawl activity broken down by site section (based on URL path structure). This helps identify which areas of your site receive the most crawler attention.

Sitemap CoverageNEW

Compare your sitemap URLs against actual crawler activity to identify coverage gaps and optimization opportunities.

Getting Started

1. Navigate to SEO & Crawlers
2. Click the "Sitemap Coverage" tab
3. Click "Refresh Sitemap" to fetch and analyze your sitemap
4. LogLens will automatically match sitemap URLs against crawl data

Coverage Statistics

• Total Active URLs — URLs currently in your sitemap
• Recently Crawled — URLs crawled within the last 30 days
• Stale — URLs not crawled in 30+ days
• Never Crawled — URLs in sitemap that have never been crawled
• Not in Sitemap — URLs crawled by bots but not in your sitemap

Coverage Tabs

URL Details

Each URL in the table shows:

• URL Path — The page path
• First Seen — When the URL was first added to sitemap
• Times Crawled — Total number of crawl requests
• Last Crawled — When it was last crawled
• Last Bot — Which crawler last visited
• Status — Crawled, Not Crawled, or Stale

Sorting

Click any column header to sort the table. This works across the entire dataset, not just the current page.

Crawl HistoryNEW

View detailed crawl history for any URL by clicking on a row in the Sitemap Coverage table.

History Modal

Click any URL to open a modal showing:

• Total crawls — How many times the URL has been crawled
• Bot summary — Breakdown by crawler (Googlebot, Bingbot, etc.)
• Request history — Individual crawl events with timestamps

Request Details

Each crawl event shows:

• Timestamp
• Bot name
• HTTP status code
• Response time
• Country (crawler location)

Pagination & Export

• Use the "Rows" dropdown to change how many events to show (25-500)
• Navigate through pages with Previous/Next buttons
• Click "Export CSV" to download the crawl history

Google IndexNEW

The Google Index tab correlates your server log data with Google Search Console data to show which of your pages are crawled, indexed, and performing in search results.

Four Buckets

Every URL is classified into one of four buckets based on crawl and index status:

Directory Breakdown

See per-directory bucket counts to understand which sections of your site are well-indexed and which need attention. Click on any directory to filter the URL list below.

URL Drill-Down

Click on any bucket to see the individual URLs in that category. The URL table shows:

• URL Path — The page path
• Crawls — Number of Googlebot crawls in the last 90 days
• Last Crawled — When Googlebot last visited
• Index Status — Indexed or not indexed (with reason)
• Impressions (28d) — Search impressions in the last 28 days
• Clicks (28d) — Search clicks in the last 28 days

Results are paginated for sites with large numbers of URLs.

Data Freshness

• Search analytics — 2-3 days behind real-time (Google's processing delay)
• URL inspection — Cached for 7 days, then re-inspected
• Crawl data — Based on the last 90 days of server logs

LLM CrawlersNEW

The LLM Crawlers page provides a dedicated view for monitoring AI and large language model bot activity on your website.

Bot Categories Tracked

LogLens identifies and tracks all major LLM crawlers, including:

Key Metrics

The LLM Crawlers page displays several key metrics at a glance:

• Total Requests — The total number of requests from LLM crawlers in the selected time period
• Unique Pages Accessed — How many distinct pages AI crawlers have visited
• Response Times — Average response time served to LLM crawlers
• Verification Status — How many requests come from verified vs unverified LLM bots

Bot Verification

LogLens checks each LLM crawler's IP address against official IP ranges published by the bot operator. This tells you whether a crawler claiming to be GPTBot or ClaudeBot is genuinely from OpenAI or Anthropic, or if it is an impersonator.

• ✓ Verified — IP matches the operator's published ranges
• ⚠ Unverified — Claims to be a known LLM crawler but IP does not match

Page Access Patterns

See which pages AI crawlers are reading most frequently. This helps you understand what content LLM providers are training on or using for retrieval, and whether they are respecting your robots.txt directives.

Time-Series Trends

View LLM crawler activity over time to spot trends, sudden increases in AI crawling, or changes in behaviour after updating your robots.txt.

Filtering by Crawler

Use the crawler dropdown to filter all data to a specific LLM bot. This lets you compare activity across different AI providers and understand each crawler's behaviour individually.

AlertsNEW

LogLens monitors your traffic and automatically alerts you when anomalies are detected.

Alerts dashboard showing alert history, run history, and configuration

How Alerting Works

1. Baseline Building — LogLens monitors your traffic for 24 hours to establish a normal baseline
2. Anomaly Detection — Incoming metrics are compared against the baseline using statistical analysis
3. Alert Triggering — When metrics deviate significantly from the baseline, an alert is triggered
4. Email Notification — You receive an email with details about the anomaly
5. Cooldown — To prevent alert fatigue, there's a cooldown period before the same alert can trigger again

Baseline Status

The Alerts page shows your baseline building progress. You need 24 hours of data before anomaly detection becomes active.

Alert Types

LogLens supports three types of alerts:

Traffic Alerts

Monitors total request volume and alerts when there are:

• Sudden spikes in traffic (potential attack or viral content)
• Sudden drops in traffic (potential outage or configuration issue)

Error Alerts

Monitors HTTP error rates and alerts when:

• 4xx error rate increases significantly (broken links, bad deployments)
• 5xx error rate increases significantly (server problems)

Bot Activity Alerts

Monitors bot traffic patterns and alerts when:

• Bot traffic suddenly increases (new crawler or scraper)
• Unverified bot traffic increases (potential impersonator bots)

Alert Settings

Configure each alert type independently in the Settings tab of the Alerts page.

Per-Alert Configuration

Each alert type can be configured with:

• Enabled/Disabled — Toggle the alert on or off
• Check Frequency — How often to check for anomalies (1 min to 24 hours, based on your plan)

Check Frequency Options

Alert History

The Alerts page has two history views:

Alerts Tab

Shows all triggered alerts with:

• Alert type (Traffic, Error, Bot)
• Severity level
• Description of the anomaly
• Timestamp
• Metrics (expected vs actual values)

Run History Tab

Shows every time the alert system ran, even when no alert was triggered. This helps you verify that monitoring is working correctly:

• Run timestamp
• Alert type checked
• Status (no anomaly detected, or alert triggered)
• Metrics at the time of check

CSV ExportNEW

Export data from any table in LogLens to CSV for further analysis in spreadsheets or other tools.

How to Export

1. Navigate to any page with data tables (Bots, Paths, IPs, etc.)
2. Click the "Export CSV" button above the table
3. If there's more data than displayed, choose between:
   • Export visible rows — Quick export of currently displayed data
   • Export all rows — Fetches all data from the server (may take longer)
4. The CSV file will download automatically

Export Locations

Export buttons are available on:

• Traffic page (hourly breakdown)
• Bots page (all bots list)
• Bot Detail page (paths and request history)
• Paths page
• Referrers page
• Geography page
• Devices page (browsers and OS)
• IP Addresses page (IPs, ranges, and request details)
• Status Codes page
• Alerts page (alert history and run history)

Public APINEW

Access your LogLens analytics data programmatically through our REST API.

Getting an API Key

1. Go to Organization Settings
2. Navigate to the "API Keys" section
3. Click "Create API Key"
4. Give your key a name and copy it (it's only shown once!)

Available Endpoints

Authentication

Pass your API key in the Authorization header:

Authorization: Bearer llapi_your_api_key_here

Rate Limits

Rate limits depend on your plan:

• Starter: 100 requests/hour
• Professional: 500 requests/hour
• Enterprise: 2,000 requests/hour

Full Documentation

For complete API reference with examples, see the API Documentation.

AWS CloudFront Integration

Send real-time logs from CloudFront to LogLens using Kinesis Data Firehose. This gives you full visibility into all traffic hitting your CloudFront distribution, including bot classification, country-level analytics, and content type breakdowns.

Step 1: Create a Kinesis Data Stream

CloudFront real-time logs are delivered via Kinesis Data Streams. Create one to act as the buffer between CloudFront and Firehose.

1. Open the Amazon Kinesis console → Data streams → Create data stream
2. Name: e.g. YourSiteCloudFrontLogs
3. Capacity mode: On-demand (recommended — scales automatically)
4. Click Create data stream

Step 2: Create a Firehose Delivery Stream

Firehose reads from the Kinesis stream and delivers log records to the LogLens ingest endpoint.

1. Open the Amazon Data Firehose console → Create Firehose stream
2. Source: Amazon Kinesis Data Streams → select the stream from Step 1
3. Destination: HTTP Endpoint
4. Endpoint URL: https://km52hdwg42qaoppe3n34tlaneu0wfkjy.lambda-url.eu-west-2.on.aws/ (your LogLens ingest endpoint — find this in your LogLens Settings page)
5. Content encoding: Disabled (do not enable GZIP)
6. Under Parameters, add a parameter:
   • Key: X-API-Key
   • Value: your LogLens API key (starts with ll_ — generate one in LogLens Settings → API Keys)
7. Buffer conditions: defaults are fine (1 MB / 60 seconds)
8. Backup settings: select an S3 bucket to store failed delivery records
9. Create or select an IAM role with permission to read from the Kinesis stream
10. Click Create Firehose stream

Step 3: Create a CloudFront Real-Time Log Configuration

This tells CloudFront which fields to log and where to send them.

1. Open the CloudFront console → Telemetry (left sidebar) → Real-time log configurations → Create configuration
2. Name: e.g. YourSiteRealtimeLogs
3. Sampling rate: 100 (100% — recommended; reduce for very high-traffic sites)
4. Fields: Select all 23 fields listed below
5. Endpoint: select the Kinesis data stream from Step 1
6. IAM role: create or select a role allowing CloudFront to publish to the Kinesis stream
7. Click Create configuration

Required CloudFront Log Fields

You must select all 23 fields when creating the real-time log configuration. Missing fields will result in incomplete data or failed parsing.

timestamp
c-ip
time-to-first-byte
sc-status
sc-bytes
cs-method
cs-protocol
cs-host
cs-uri-stem
cs-bytes
x-edge-location
x-edge-request-id
x-host-header
time-taken
cs-protocol-version
cs-user-agent
cs-referer
cs-cookie
x-edge-response-result-type
x-edge-result-type
sc-content-type
c-port
c-country

Step 4: Attach to Your CloudFront Distribution

1. Open your CloudFront distribution
2. Go to the Behaviors tab
3. Edit the default behavior (or whichever behavior you want to monitor)
4. Under Real-time log configuration, select the configuration from Step 3
5. Save changes

Data will start appearing in your LogLens dashboard within a few minutes.

Required IAM Permissions

You'll need two IAM roles:

• CloudFront → Kinesis: Allows CloudFront to write to your Kinesis Data Stream (kinesis:PutRecord, kinesis:PutRecords)
• Firehose → Kinesis + HTTP: Allows Firehose to read from Kinesis (kinesis:GetRecords, kinesis:GetShardIterator, kinesis:DescribeStream) and deliver to the HTTP endpoint

AWS will prompt you to create these roles during setup if they don't exist.

Troubleshooting

• No data appearing: Check the Firehose Monitoring tab in AWS Console — look for DeliveryToHttpEndpoint.Success metrics. If you see failures, check the error S3 bucket.
• Delivery failures: Verify your API key is correct and active in LogLens Settings → API Keys. Ensure content encoding is set to Disabled (not GZIP).
• Partial data: Make sure all 23 required fields are selected in the real-time log configuration. Missing fields cause records to be silently dropped.

Cloudflare Integration

Forward logs from Cloudflare using Workers.

Cloudflare Worker Setup

Create a Cloudflare Worker that:

1. Intercepts requests to your site
2. Extracts log data (path, method, status, etc.)
3. Forwards to the LogLens API

Sample Worker Code

addEventListener('fetch', event => {
  event.respondWith(handleRequest(event.request))
})

async function handleRequest(request) {
  const response = await fetch(request)
  
  // Send log to LogLens (non-blocking)
  event.waitUntil(sendToLogLens(request, response))
  
  return response
}

Vercel IntegrationNEW

Send logs from Vercel-hosted sites using Vercel Drains. This integration captures all traffic to your Vercel deployments with minimal setup.

Setup Overview

1. Create a Vercel-type website in LogLens
2. Configure a new Drain in your Vercel project settings
3. Enter the LogLens endpoint URL and signing secret
4. Logs start flowing within seconds

Step 1: Create a Vercel Website in LogLens

1. Log into LogLens
2. Click the website dropdown and select "Add Website"
3. Enter your website name and domain
4. Select Vercel as the source type
5. Click "Create Website"
6. Copy the Endpoint URL and Signing Secret shown in the setup instructions

Step 2: Configure Vercel Drain

1. Go to your Vercel Dashboard
2. Navigate to Settings → Observability → Drains
3. Click Create Drain
4. Select the data to drain:
   • Check Logs (required)
5. Configure drain settings:
   • Projects: Select "All Projects" or specific projects
   • Sources: Select all sources (Edge, Lambda, Static, Build, External)
   • Environments: Select environments to monitor (Production, Preview, Development)
6. Click Next to proceed to destination configuration

Step 3: Set Destination

1. Select HTTP as the delivery method
2. Enter the LogLens endpoint URL from Step 1
3. Enter the signing secret from Step 1
4. Leave other settings at their defaults
5. Click Create Drain to finish

Verification

After creating the drain:

1. Visit your Vercel-hosted site to generate some traffic
2. Return to LogLens within 1-2 minutes
3. You should see requests appearing in your dashboard

What Data is Captured

Vercel Drains send comprehensive request data including:

• Request path, method, and query string
• Response status code
• Client IP address and country
• User agent string
• Response size in bytes
• Cache status (HIT, MISS, STALE, etc.)
• Edge region where request was served

Vercel vs Other Integrations

Key differences when using Vercel:

• No API keys needed — Vercel uses HMAC signature verification instead
• Automatic setup — No infrastructure to configure (unlike CloudFront)
• All traffic captured — Including serverless functions and edge middleware

Google Search ConsoleNEW

Connect your Google Search Console account to correlate server log data with indexing status and search performance metrics.

Connecting

1. Go to Settings → Integrations
2. Click "Connect Google Search Console"
3. Authorize with Google (LogLens requests read-only access)
4. Select your GSC property (domain or URL-prefix)
5. Initial sync starts automatically

What Data is Synced

• Index status per URL — Indexed or not indexed, with reason
• Search impressions & clicks — Last 28 days of search performance
• Average search position — Per URL ranking data
• Top search queries — Queries driving traffic to high-impression URLs
• Canonical URL selection — Google's chosen canonical for each URL

Automatic Syncs

• Runs daily at 5 AM UTC
• Manual "Sync Now" button available in Settings → Integrations
• Search analytics data is 2-3 days behind real-time
• URL inspection results are cached for 7 days

URL Inspection Priority

• Highest-impression URLs are inspected first
• Up to 500 URLs per sync run
• URLs are re-inspected after 7 days

Disconnecting

Go to Settings → Integrations and click "Disconnect" next to Google Search Console. Cached data will expire automatically.

Import Logs

Upload historical log files to backfill your analytics. LogLens supports CloudFront standard and real-time log formats with automatic format detection. See Historical Log Import for full details on the import process, deduplication, and progress tracking.

Supported Formats

• CloudFront Standard Logs — Default CloudFront access log format (.gz)
• CloudFront Real-Time Logs — Real-time log format used with Kinesis Firehose

How to Import

1. Go to Import Logs in the Tools section of the sidebar
2. Drag and drop your log file or click to browse
3. The format is detected automatically
4. Processing begins and progress is tracked in real-time

Import Status

Track the status of your imports:

• Pending — Queued for processing
• Processing — Currently being analyzed
• Completed — Successfully imported
• Failed — Error during import

Deduplication

LogLens automatically deduplicates imported logs. Importing the same file twice will not create duplicate records. See Historical Log Import for details.

Website Settings

Configure settings for each website in your account.

General Settings

• Website Name — Friendly name shown in the UI
• Domain — Primary domain for this website

API Keys

Manage API keys for log ingestion:

• View existing API keys
• Generate new API keys
• Revoke compromised keys

Organization Settings

Manage your organization and billing.

Organization Details

• Organization Name — Your company or team name
• Plan — Current subscription tier
• Usage — Requests used this billing period

Billing

View and manage your subscription, update payment methods, and download invoices.

Team Management

Invite team members and manage permissions.

Roles

Inviting Team Members

1. Go to Organization Settings
2. Click "Invite Member"
3. Enter their email address
4. Select a role
5. They'll receive an email invitation to join

Privacy ModeNEW

Privacy Mode helps you share screenshots without revealing sensitive information.

What Gets Obscured

When Privacy Mode is enabled:

• Domain names — Website names are replaced with placeholders
• Path segments — Partial path data is obscured
• Organization details — Organization name and user info are hidden

How to Enable

1. Click on your profile/settings in the bottom-left corner
2. Toggle "Privacy Mode" on
3. The interface will immediately update to show obscured data
4. Take your screenshots
5. Toggle Privacy Mode off to return to normal view

AI InsightsNEW

AI Insights uses Claude to automatically analyse your analytics data and surface actionable findings about your traffic, bots, SEO performance, and more.

How to Access

Click the AI Insights panel available on any analytics page. The panel opens alongside your current view so you can see insights in context with your data.

What It Analyses

AI Insights can analyse a wide range of data depending on the page you are viewing:

• Traffic patterns — Unusual spikes, drops, or trends in request volume
• Bot behaviour — Crawler patterns, verification anomalies, and suspicious activity
• SEO performance — Crawl coverage, indexing gaps, and optimisation opportunities
• Status codes — Error rate trends, broken links, and server issues
• Geographic patterns — Traffic distribution anomalies across regions
• Path analysis — High-traffic pages, slow responses, and content performance

Filter-Scoped Insights

Insights automatically adapt to your current page and active filters. For example, if you are on the SEO page filtered to Googlebot, the AI will generate insights specifically about Googlebot's crawl behaviour. Switch to the Bots page filtered to a specific bot, and insights will focus on that bot's activity patterns.

Saved Insights

Every insight is saved and can be viewed later for the same page and filter combination. This lets you track how your analytics evolve over time without regenerating insights.

Tool Activity

While generating insights, the AI Insights panel shows which data the AI is querying in real-time. You can see exactly which analytics endpoints and data sources are being accessed, providing full transparency into the analysis process.

Dashboard Links

Insights include clickable links to relevant reports and pages within LogLens. This lets you quickly navigate to the underlying data to verify findings or investigate further.

Insight Format

Each insight is presented as a card with three sections:

• Key Takeaways — A concise summary of the most important findings
• Detailed Analysis — In-depth explanation of patterns, anomalies, and context
• Recommendations — Specific actions you can take based on the findings

Insights HistoryNEW

The Insights History page shows all AI-generated insights across every page and filter combination, in one place.

Viewing Past Insights

Navigate to the Insights History page from the Tools section in the sidebar. All previously generated insights are listed in reverse chronological order.

Filtering by Page

Use the page filter to narrow the list to insights generated on a specific section, such as Traffic, Bots, SEO, or any other analytics page.

Expandable Insight Cards

Each insight is shown as a collapsible card. Click to expand and view the full content including Key Takeaways, Detailed Analysis, and Recommendations.

Token Usage Tracking

Each insight card displays the number of tokens used during generation, so you can monitor your AI usage over time.

Deleting Insights

To remove an insight, click the delete button on any individual insight card. Deleted insights cannot be recovered.

Historical Log ImportNEW

Import historical log files to backfill your analytics with past data. Access this feature from Import Logs in the Tools section of the sidebar.

Supported Formats

LogLens supports the following CloudFront log formats:

• CloudFront Standard Logs — The default CloudFront access log format (tab-separated, usually .gz compressed)
• CloudFront Real-Time Logs — The real-time log format used with Kinesis Firehose

The format is detected automatically — you do not need to specify which format your files use.

Upload Process

1. Navigate to Import Logs in the Tools section
2. Drag and drop your log file or click to browse and select it
3. The file is uploaded and processing begins automatically
4. Monitor progress as the file is processed
5. Once complete, the imported data appears in your analytics

Deduplication

LogLens uses deterministic request IDs to prevent duplicate records. If you import the same log file twice, or if the imported data overlaps with logs already received via real-time ingestion, duplicate entries are automatically detected and skipped. This means you can safely re-import files without worrying about inflating your analytics.

Progress Tracking

Each import job displays detailed progress with the following counts:

• Processed — Total log entries parsed from the file
• New — Entries successfully added to your analytics
• Duplicates — Entries that already existed and were skipped
• Failed — Entries that could not be parsed or stored

After Import

Imported data appears in all analytics pages — Traffic, Bots, Paths, IPs, Geography, and more. It is treated identically to real-time data once imported.

DownloadsNEW

Export your analytics data as CSV files from any analytics page, and manage your export history from the Downloads page.

How to Export

Every analytics page with a data table includes a download button. Click it to export the current data as a CSV file.

Available Export Pages

CSV export is available on the following pages:

• Traffic — Time-series traffic data
• Bots — Bot list with request counts and verification status
• Paths — URL paths with request counts and metrics
• IPs — IP addresses and ranges with request counts
• Referrers — Referring domains with traffic counts
• Geography — Country-level traffic breakdown
• Devices — Device, browser, and OS breakdown
• Status Codes — HTTP status code distribution

Download Button Location

The download button is located in the header area of each page, typically next to the page title or above the data table. Look for the download icon or "Export CSV" button.

Downloads Page

The Downloads page in the Tools section of the sidebar shows your complete export history. From here you can:

• View all past exports with timestamps and file sizes
• Re-download previously generated CSV files
• See the status of exports currently being generated