Reusable resource
GA4 Direct traffic diagnostic checklist
Check reporting, campaign links, consent and website journeys to work out why Direct traffic has changed and what to investigate next.
How to use it
Check the evidence behind the change
Start with the report comparison, then work through the sections that apply to your website. Tick a point when you've checked the evidence and keep notes of anything that needs further investigation.
The 48 checks cover the main reporting and technical causes, rather than every possible website setup. Ticks record your progress through the checks, not proof of a diagnosis, and aren't saved when you leave the page.
Agree the decision and comparison
Start with the business question rather than a target Direct traffic percentage.
Check the report before explaining the change
Confirm that the figures describe the same thing before comparing them.
Review links you control
Follow representative campaign links and check which information reaches the website.
Test measurement on the affected journeys
Test the affected pages and journeys with the appropriate website and analytics access.
Review consent and privacy effects
Treat missing measurement and source labelling as separate questions.
Check journeys across domains
Include this section when bookings, payments or other website functions use a different domain.
Investigate suspicious activity without guessing
Unexpected locations or low engagement are reasons to investigate, not sufficient grounds to exclude visitors.
Return evidence and a proportionate decision
The deliverable is an explanation the business can act on, not a lower percentage by itself.
0 of 48 checks reviewed
Review outcome
Record what the evidence supports
Keep a short record beside the checklist with the comparison dates, report links, relevant test results, person responsible and next review date. Record unavailable evidence explicitly so a future review doesn't mistake a missing figure for zero.
A source-information repair may improve future reporting without reconstructing earlier visits. Review whether the evidence is strong enough for the business decision, rather than judging the work by how small the Direct traffic category becomes.
Google Analytics documentation
Guidance for the checks
Use these documents to check the platform rules behind a finding. Each explains a different part of measurement rather than diagnosing your website.
Each guide opens in a new tab.
| Guide | What it covers |
|---|---|
| Google guidance on Direct traffic | What the Direct traffic category can include and why source information may be missing. |
| Traffic-source scopes | How first-user, session and key-event reports answer different questions. |
| Campaign URL guidance | How campaign parameters identify the source, medium and campaign behind a visit. |
| Cross-domain measurement | How the linker carries measurement information between configured domains. |
| Unwanted referrals | How referral exclusions affect source attribution and returning visits. |
| Behavioural modelling and its limits | What consent-related estimates can show and when modelling is available. |
| Known bot exclusion | Which known automated traffic Google excludes and the limits of that filtering. |