Primary related guide or tool
Continue the workflow with this related LLMs.txt Kit resource.
/proof.htmlServer logs vs analytics: which proof to use
How to separate crawler proof, human sessions, referrals, and organic performance evidence.
Fast answer
If your goal is to avoid mixing different evidence types, start with this framing: crawler hits, self-tests, bot traffic, and real visitors often get combined into one misleading number. The useful deliverable is a proof taxonomy for traffic measurement.
This page is intentionally conservative. It treats crawler files, URL inspection, feeds, and server logs as discovery and measurement aids, not as guaranteed ranking levers.
When to use this playbook
Use it when operators building a traffic proof system need a concrete next step and a page that can be linked from a hub, a community answer, a README, or a launch checklist. The page should help someone make a decision even if they never buy anything or contact the site owner.
The strongest pages in this topic cluster have three traits: they answer one narrow question, they include a copyable artifact, and they link to the relevant tool or proof page so the reader can act immediately.
Recommended workflow
- Use logs for crawler access.
- Use analytics for human sessions.
- Use UTM evidence for distribution placements.
- Use Search Console for organic queries and indexing.
Pre-publish checklist
- crawler proof separated.
- self-tests excluded.
- UTM placements recorded.
- organic proof imported.
Copyable working note
Use this as a starting point in a ticket, README, client note, or launch log. Edit it to match the real site before publishing.
Evidence type
Source
What it proves
What it does not proveWhat not to count as proof
Do not count this setup as traffic by itself. A submitted sitemap, an IndexNow receipt, a crawler log hit, or an indexing request can show discovery work, but none of them proves rankings, impressions, clicks, conversions, or AI citations. Organic proof should come from Search Console, analytics, qualified referral evidence, or server logs interpreted for the right purpose.
The main pitfall for this topic is: Calling every request traffic.
Related resources
Next supporting resource
Continue the workflow with this related LLMs.txt Kit resource.
/.well-known/traffic-measurement-plan.jsonAll free tools
Continue the workflow with this related LLMs.txt Kit resource.
/tools/Proof dashboard
Continue the workflow with this related LLMs.txt Kit resource.
/proof.html