See how fast Google finds each story and which AI systems read it.

Server requests appear as they happen. Search Console's recent performance data is synced daily and runs two to three days behind Google, and it is then read against the first-party request timeline.

Yes, by each system's published purpose. Training crawlers such as GPTBot and CCBot, AI search and retrieval crawlers such as OAI-SearchBot and PerplexityBot, and user-triggered fetches such as ChatGPT-User are counted separately. Where a provider publishes no purpose, the system is listed under the name it declares.

Yes. A human visit is counted as AI-referred when the referrer is an AI assistant such as chatgpt.com, perplexity.ai, claude.ai, gemini.google.com or copilot.microsoft.com, or the URL carries a matching source tag. Salience lists the landing stories per assistant, what those readers open next, the share of human traffic they represent, and each AI company's fetches against the visitors it sent back. With Google Analytics 4 connected, the sessions and engagement for those readers appear alongside.

For every request from a declared crawler: the system, the URL, the time, the verification result, what your robots.txt said for that path and the status your infrastructure returned. That record shows which content was fetched, by whom and when. What a provider did with the content after the fetch happens outside your infrastructure, so the record is presented as access, with the provider's published purpose alongside it.

At your CDN, WAF or robots.txt. Salience records what each system fetched before a block and whether the requests stopped after it, so the evidence for a rule and the check on its effect come from the same record.

It is your own first-party access log, classified and exportable: system, URL, timestamp, response, verification result and the robots.txt rule that applied. Whether and how to use it is a question for your counsel.

They appear in the log like everything else. Salience fetches your live robots.txt, parses the rule groups and reports every request from a declared crawler to a path its rules disallow, with the system, the path and the time.

Google-Extended is a robots.txt token. Google fetches publisher content with Googlebot, and the token tells Google whether that content may be used for its AI products. Salience reports Googlebot's requests and audits the rules you publish for the token.

Salience recognises 200+ named crawler and agent identities and alerts you the first time a new system appears on your site, so the inventory grows with the ecosystem.

The AI Act's copyright obligations apply to general-purpose AI providers, and they refer to machine-readable rights reservations such as robots.txt. Salience gives publishers and their advisers the first-party technical record of which declared crawlers fetched what, and whether those fetches respected the reservation you published, to use in that assessment.

Yes. Segments are saved page groups defined by path prefix, pattern or query string, with exclusions and nesting, and a one-click library adds common groups such as articles, pagination, search results and parameter URLs. Segments apply to all history, and every report, alert and export can be read per segment.

Access-log fields: path, method, status, IP, user agent and timing. Data is held in AWS eu-west-2 (London), encrypted in transit and at rest, processed under a GDPR Art. 28 DPA and never shared between customers.

One website, 500,000 requests a month, 30 days of history, real-time analytics, bot and AI crawler detection, all 21 site checks and two email alerts. Solo at $19 a month adds the sitemap and Search Console joins, all 16 alerts by email and Slack, log import and six months of history; webhooks and shared dashboards start on Starter at $49. Every plan except Solo has unlimited users, and no card is needed to start.