Module 1
Reader Progress
How far readers actually got through a piece of content, counted, not estimated.
What Is Reader Progress?
Reader Progress is Semantic Journey's content engagement analytics module for measuring how far readers actually get through a piece of content. It counts four fixed milestones per page view, Started Reading, Reached the Middle, Read Most, and Reached the End, using the reader's position relative to the content rather than a scroll percentage.
It is one of two modules, alongside Decision Point, that make up Semantic Journey's approach to content engagement analytics.
Four milestones, no percentages
Reader Progress watches for four moments in a reader's path through an article. Each one fires at most once per page view, and each is reported as a plain count.
Started Reading
The reader moved past the headline and into the piece.
Reached the Middle
The reader kept going past the point where most readers stop.
Read Most
The reader made it through the large majority of the content.
Reached the End
The reader stayed for the conclusion.
Why Reader Progress matters for editorial decisions
Four counts, read together, describe a shape rather than a single number. A steep drop between Started Reading and Reached the Middle points to a problem early in the piece, often an opening that doesn't hold attention or a dense section readers hit too soon. A drop closer to Reached the End suggests something different: the piece holds readers most of the way, then loses them right before the conclusion.
This is what makes Reader Progress a content engagement analytics tool rather than a vanity metric. It doesn't just confirm that people visited an article. It shows where, specifically, within that article, readers stopped, which is the information an editor actually needs to revise a piece, restructure a format, or recognize when something is working and should be repeated.
How Reader Progress detects position, not scrolling
Reader Progress uses the browser's own visibility detection to watch where the reader's viewport sits relative to your main content. It is not measuring scroll speed, scroll percentage, or session duration. It is answering one question at four fixed points: did the reader's position reach this part of the piece.
If a page cannot be measured reliably, for example if a reader has JavaScript turned off, Semantic Journey records nothing for that view rather than guess. An honest gap in the data is worth more than a number that is not true.
Specification
| Specification | Value | Unit | Standard |
|---|---|---|---|
| Detection method | Reader position relative to content | ||
| Milestones per page view | 4 | fixed points | |
| Maximum fires per milestone | 1 | per page view | |
| Data stored | Aggregate daily count | per content item | |
| Personal data collected | None |
What Reader Progress doesn't measure
Reader Progress reports position reached, not comprehension, and not intent. Reaching the end of a piece is not proof it was understood or agreed with, only that the reader's position got there. It also isn't a traffic tool: it says nothing about where a reader came from, what device they used, or how many total visitors a page had. For that, use it alongside a general analytics tool, not instead of one.
Reader Progress also doesn't tell you whether a reader acted on what they read. That is a separate question, measured by Decision Point.
Common questions
How does Reader Progress detect these milestones?
Can a milestone be counted more than once per visit?
What happens if a page can't be measured reliably?
Does this replace time on page or bounce rate?
Pair it with Decision Point
Reader Progress tells you how far people got. Decision Point tells you what they did next. Both modules are free, on WordPress or as a self-hosted Static build.
See Decision Point →