Finseo

Webflow Server Log Access

How to access server logs from Webflow sites for AI bot analytics and visibility tracking.

About Webflow

Webflow is a visual web development platform that combines design, CMS, and hosting. With the introduction of Webflow Cloud, developers can now build full-stack applications with server-side functionality and access runtime logs, though traditional Webflow hosting has limited log access.

Visual Builder
Webflow Cloud (New)
Limited Traditional Logs

Overview

Webflow offers different hosting options with varying levels of log access:

Webflow Cloud (New)

Full-stack apps with runtime logs showing server-side activity and bot visits

Traditional Hosting

Static site hosting with no direct log access - requires workarounds

Method 1: Webflow Cloud Runtime Logs

Webflow Cloud is Webflow's new platform for building full-stack applications. It provides runtime logs that capture server-side activity, including AI bot visits.

1

Set Up Webflow Cloud Project

Create or migrate your project to Webflow Cloud:

  1. Navigate to Webflow Cloud dashboard
  2. Connect your GitHub repository
  3. Deploy your Next.js or Astro application
  4. Configure environment settings
2

Access Runtime Logs

View your application's runtime logs:

  1. Click your project name to open Environments Dashboard
  2. Click the environment name to open Deployment Dashboard
  3. Select the "Runtime Logs" tab
  4. View real-time server activity including bot visits
3

Export Logs for Analysis

Runtime logs capture server-side activity including:

  • Server-side function execution
  • API endpoint requests (showing bot User-Agents)
  • Application errors and exceptions
  • Console logs with request details
4

Implement Custom Logging

For better log management, implement custom logging in your app:

// Example: Log bot visits to external service
export default function handler(req, res) {
  const userAgent = req.headers['user-agent'];
  
  // Detect AI bots
  if (userAgent?.includes('GPTBot') || 
      userAgent?.includes('ChatGPT-User') ||
      userAgent?.includes('PerplexityBot')) {
    
    // Log to external service
    logToExternalService({
      timestamp: new Date(),
      userAgent,
      ip: req.headers['x-forwarded-for'],
      path: req.url
    });
  }
  
  // Your regular handler code...
}

Method 2: Traditional Webflow Hosting

Traditional Webflow hosting serves static sites and doesn't provide server log access. However, there are workarounds to track bot visits:

Option 1: CDN/Reverse Proxy

Use a CDN in front of your custom domain:

  1. Point your custom domain to Cloudflare or Fastly
  2. Configure the CDN to proxy to your Webflow site
  3. Access logs through the CDN provider
See Cloudflare guide →See Fastly guide →

Option 2: Analytics Integration

Use server-side analytics to track bots:

  • Implement server-side tracking (e.g., Plausible, Fathom)
  • Configure to log User-Agent strings
  • Export data for bot analysis

Option 3: Custom API Endpoint

Create a logging endpoint using Webflow Logic (Beta) or external service:

  • Set up an API endpoint to receive page view data
  • Use JavaScript to send visitor data (limited to JS-enabled bots)
  • Store and analyze the collected data

Method 3: Exported Sites

If you export your Webflow site and host it elsewhere, you gain full control over server logs:

1

Export Your Webflow Site

In Webflow Designer, go to Settings → Hosting → Download and export your site code.

2

Host on Traditional Server

Deploy to any hosting provider that offers log access (cPanel, Plesk, VPS, etc.)

3

Access Server Logs

Follow the guide for your chosen hosting provider to download and analyze logs.

Limitations & Considerations

Webflow Cloud Requirements

Webflow Cloud only supports Next.js and Astro frameworks. Traditional Webflow sites built with the Designer cannot use Webflow Cloud runtime logs.

CMS and Dynamic Content

Bot visits to CMS-powered pages on traditional hosting are still served statically and won't generate server-side logs without a CDN or proxy.

Webflow Subdomain Limitation

Sites using Webflow subdomains (*.webflow.io) cannot use CDN proxies. You need a custom domain for CDN-based logging solutions.

Export Limitations

Exported sites lose CMS functionality and automatic updates. This method is best for static sites that don't change frequently.

Best Practices

Webflow Cloud First: If building a new project, consider using Webflow Cloud with Next.js/Astro for native log access.

Custom Domain Required: For traditional sites, always use a custom domain to enable CDN proxy solutions.

Implement Logging Early: Add custom logging logic during development rather than trying to retrofit it later.

Monitor Bot Patterns: AI bots often visit specific types of content. Use this insight to optimize your most visited pages.

Next Steps

After implementing your chosen logging method:

  • Monitor which pages receive the most AI bot traffic
  • Optimize content structure for AI comprehension
  • Track the impact of Webflow's built-in SEO features on bot visibility
  • Use insights to improve your content strategy
Back to Bot Analytics OverviewWebflow Cloud Docs