Separate reader traffic
Cloudflare paths indicate substantial non-reader activity; headline optimization alone cannot fix this.
Design the entry copy around reader actions: check eligibility, define constraints, and choose next step.
Requests are not readers
The useful question is not whether traffic looks busy; it is which activity represents readers, monitoring, crawlers, retries, or system errors.
Check the logs first
- Add one explicit action row for each entry point in index/archive/toolkit
- Keep the test narrow: one priority page with clear topic, source links, internal links, and a conversion action
What still needs proof
Treating raw request counts as growth will bias content toward the wrong user intent. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.