Salience

Server log monitoring integrations

Connect the CDN, host or server your site already runs on.

Salience reads the request logs your platform already produces and shows every crawler, bot and error behind them. Enter your domain to see which integration fits.

  • About 10 minutes to connect
  • No code changes on most platforms
  • Free plan, no card

Explore sample data

Example of the Website setup strip in the Salience dashboard: logs receiving through a Cloudflare Worker, Google Search Console and Google Analytics connected, sitemap and robots.txt checked, and the first site crawl optional. Five of six steps completed.

Website setup

www.example · 5 of 6 completed

Example
  • LogsCloudflare Worker · latest record todayReceiving
  • Google Search ConsoleProperty selected · last sync 05:00Connected
  • Google AnalyticsGA4 property selected · last sync yesterdayConnected
  • SitemapChecked automatically when the site was addedChecked
  • Robots.txtChecked automatically when the site was addedChecked
  • First site crawlStarts only when you ask for oneOptional

Pick the platform your site runs on

Each integration reads the request logs that platform already produces. Logs come first; Search Console, Google Analytics and a site crawl can be added once requests are arriving.

How each integration delivers data

Every integration takes about 10 minutes to connect. They differ in how requests arrive, how quickly they show, and whether older logs can be imported.

Cloudflare

Method
Cloudflare Worker
Freshness
Within seconds
Historical import
Via origin-log file import
Good to know
Covers proxied records; requests Cloudflare blocks before the Worker runs are not recorded

Vercel

Method
Vercel Drain
Freshness
Within seconds
Historical import
No, starts at connection
Good to know
Needs a Vercel Pro or Enterprise team; history starts at connection

CloudFront

Method
Kinesis + Firehose real-time logs
Freshness
Seconds to minutes
Historical import
Yes, standard log files
Good to know
Below 100% sampling, a sample of requests; paths without query strings

Kinsta

Method
Kinsta API log pull
Freshness
Every 15 minutes
Historical import
Up to ~4 days (Kinsta's retention)
Good to know
New requests every 15 minutes; access log only

Shopify

Method
Cloudflare O2O Worker
Freshness
Within seconds
Historical import
No, Shopify exposes none
Good to know
Every path except /checkout, where Cloudflare does not run Workers

Apache

Method
Vector agent
Freshness
Within seconds
Historical import
Yes, rotated/archived files
Good to know
Access logs only; timing needs a %D-style field

Nginx

Method
Vector agent
Freshness
Within seconds
Historical import
Yes, rotated/archived files
Good to know
Access logs only; real client IP needs care behind proxies

Add Google's view of the same pages

Search Console and Google Analytics are data connections. They add Google's index status, search performance and session figures to the URLs in your request logs, once a log source is connected.

Every source ends up in the same reports

Requests from any integration go into one request model, so a site on Cloudflare and a site on Apache read the same way in the dashboard, the alerts and the API.

  • Verified crawler identities

    200+ crawler identities, checked against the address ranges their operators publish.

  • The same 21 alert types

    Crawler errors, unverified bots, traffic changes and edge policy changes, each with a recommended next step.

  • One URL page per path

    Requests, status codes, crawlers and AI fetches for each URL, with Search Console and GA4 figures when connected.

  • API, MCP server and CLI

    Read the same data from scripts, AI agents and the terminal, on every plan.

How connecting a site works

The check above reads your domain's public DNS and response headers and names the platform behind it. Nothing is installed and nothing on the site changes until you run the setup.

  1. 1

    Check your domain

    Enter the domain shoppers or readers use. The check names the platform and the integration that connects it.

  2. 2

    Follow the guided setup

    Create your account and the app walks through that platform's setup, in about 10 minutes. You can send a delegated setup link to whoever manages the platform.

  3. 3

    Confirm requests are arriving

    The connection check sends test requests and confirms they reach Salience. Then add Search Console, Google Analytics or a first site crawl if you want them.

Read the setup instructions for every platform Put Cloudflare in front of any other host

Trust & data protection

Your data stays yours.

You stay in control

Salience processes your data only to provide the service. You remain the controller.

Stored in the UK

Core data is hosted in AWS London and encrypted at rest.

No browser tracking

Collection happens server‑side. There’s no client‑side pixel or tracking script.

Never sold or pooled

Your logs are not sold, used for advertising, or shared between customers.

Privacy and data protection

Integration questions

Can I connect more than one platform to the same account?

Yes. Each site connects its own source and appears separately in one organisation, with the same dashboards, alerts and API. A site on Cloudflare and a site on Apache report the same way.

How long does setup take?

About 10 minutes on every platform. Search Console and Google Analytics connect with a Google sign-in once a log source is in place.

Do I need a developer?

You need access to the platform: a Cloudflare account, a Vercel team, an AWS account, a MyKinsta API key, or sudo on the server. If someone else has that access, send them a delegated setup link from the app. They complete the steps without access to your Salience account.

What if my platform is not listed?

Cloudflare's free plan in front of the site works for most hosts, and the Cloudflare integration then applies. The setup guide walks through it in about 10 minutes.

Put Cloudflare in front of your site

Can I import log files I already have?

Yes. Apache, Nginx and CloudFront access logs upload with deduplication against anything already streaming. Historical imports do not count against your monthly request allowance.

How is this different from Google Analytics?

GA4 measures what its tag records in a browser and filters known bots out. Salience reads the request logs, so it records crawlers, AI bots and scrapers that never run a tag, and the status code each request received. The Google Analytics connection puts both side by side.

Where is the data stored?

In AWS eu-west-2 (London), with encrypted S3, DynamoDB and Aurora storage. A GDPR Article 28 DPA applies to every account, and request data is never sold, used for advertising or shared between customers.

Salience security and data protection

Can I disconnect later?

Yes, from your side on every integration: remove the Worker route, delete the Drain, stop the agent or revoke the key. Collection stops straight away.

Check which integration fits your site.

The Free plan needs no card. Setup takes about 10 minutes on every platform.

Explore sample data