Your own traffic out of every figure, visibly
Salience's own crawls and checks are excluded from every figure by default, organisations can add their own exclusion rules (IPs, networks, user agents, bots, paths, time ranges) that apply to history, every report says what it excluded, and a Raw switch shows the unexcluded figures.
An audit crawl from your own office, another agency's Screaming Frog run, Salience's own site checks: none of it is the traffic you are analysing, yet it sat in every total. On one site the exposure checker alone was at least 500 of 3,426 weekly 5xx.
What changed
- Salience's own traffic is excluded by default: SalienceBot's crawls and site checks, the exposure checker and its test paths, out of every log-derived figure on every page, in the API and in the MCP server.
- Organisation exclusion rules: under Organisation settings, add an IP, a network (an IPv6 /64 included), a user-agent fragment, a bot name, a path prefix or a time range. Rules apply to every website in the organisation and to history, not just from today.
- Never silent. Every report carries an exclusions line saying what was left out; every API response carries an
exclusionsblock and the receipt says whether exclusions applied. - Raw switch. The period picker gains a Raw toggle that shows the unexcluded figures everywhere; the API takes
raw=1.GET /public/v1/websites/{id}/exclusionslists what applies; MCPget_exclusions(1.29.0); CLIexclusions(2.9.0). - The daily rollups are rebuilt without Salience's own traffic, so fast and live views agree.
See exclusions in the help.