Editorial · July 2026
The Article Everyone Read and No One Finished
A short story about an editor, a dashboard that told her less than she needed, and the gap between finishing an article and acting on it.
Priya edited features for a regional news site called The Northfield Review. Every Monday she pulled up the analytics dashboard, and every Monday it told her less than she needed.
Bounce rate. Session duration. Pages per session. Numbers that moved up and down for reasons nobody on the editorial team could name. Last month, a 4,000-word investigative piece on the town’s water board had done well by every metric on the screen. High time on page. Low bounce rate. The chart looked great in the Monday meeting.
But Priya couldn’t shake a feeling. Time on page doesn’t tell you if someone read the piece or left the tab open while they made coffee. Session duration doesn’t tell you whether a reader made it past the second paragraph. She had a dashboard full of numbers and no honest answer to the only question she actually cared about: did people read this, and how far did they get?
That was the week she installed Semantic Journey.
What she was actually asking for
Semantic Journey is built around one idea: an editor should be able to ask “how did readers experience this piece?” and get an answer in plain English, not a chart that needs a training session to interpret.
Its first module, Reader Progress, watches four moments in a reader’s path through an article:
- Started Reading. They moved past the headline and into the piece.
- Reached the Middle. They kept going past the point most people quit.
- Read Most. They made it through the large majority of it.
- Reached the End. They stayed for the conclusion.
That’s it. No scroll percentages, no session identifiers, no cookies, nothing about who the reader was or where they came from. Just: how far did they get, counted and added up, day by day.
Two weeks later
By the second Monday, the water board article had a story to tell that the old dashboard never could.
Readers were starting it. A lot of them. The Started Reading count was strong, better than average for the site. But the Reached the Middle count dropped hard, and Read Most barely registered at all.
Priya didn’t need a data analyst to read that. People were clicking in, hitting the second section (a dense procedural paragraph about municipal budget line items), and leaving. The piece read well in the newsroom, but out in the world, it lost most of its audience exactly where the writing got dry.
She pulled up the Reports screen, exported the numbers to a spreadsheet, and brought it to the next editorial meeting. Not a theory. Not a hunch. A plain count of where readers actually stopped.
The next investigative piece moved the procedural detail to a sidebar and kept the narrative moving in the main body. Reached the Middle nearly doubled.
A different kind of gap
A month later, the fix was clearly working. Across the site, Reached the End counts were up. People were finishing pieces they used to abandon. Priya felt good about that, and by every measure Semantic Journey gave her, she was right to.
Then she looked at a feature the team was proud of: a long piece on a local family shelter running out of funding, ending with a Donate Now button and a phone number for anyone who wanted to volunteer instead. Reader Progress told her the story everyone wanted to hear. Reached the End was one of the strongest numbers on the site that month. People were reading the whole thing.
But almost nobody was clicking Donate Now. And the volunteer phone number, sitting right next to it, had barely been touched at all.
That gap was invisible to Reader Progress by design. Finishing an article and acting on it are two different things, and Semantic Journey doesn’t pretend a completed read means anything beyond itself. To see the second half of the picture, Priya needed the plugin’s other module: Decision Point.
Decision Point watches for clicks on whatever a site owner decides matters: a donate button, a phone number, a sign-up link, anything. The Northfield Review’s developer had marked the Donate Now button directly in the template months earlier, and the volunteer phone number needed no marking at all, since Semantic Journey recognizes a phone link automatically. Both were already being counted. Priya just hadn’t had a reason to look until Reader Progress told her the reading side of the story was fine.
Sitting side by side on the same Reports screen: a strong Reached the End number, and a Donate Now count near zero. Not a theory about why people weren’t giving. Just the plain fact that they were reading all the way through and then not acting, which was enough to start a real conversation about whether the ask came too late in the piece, or whether the button itself was easy to miss.
The next version of that story moved the donate button higher and repeated it at the end. The phone number stayed exactly where it was, since at least people were seeing it, even if they weren’t calling it yet either.
What you actually get
If you install Semantic Journey, here is exactly what happens, no more and no less.
Reader Progress, on your site, a small script watches for a reader’s position relative to the main content of a page, using the browser’s own visibility detection. It does not track scrolling as a behavior. It fires each of the four milestones at most once per page view.
Decision Point watches for clicks on whatever you decide matters, in three ways: a marker you (or your developer) add directly to a button or link, automatic recognition of any phone number link with no setup required, or a simple rule you set up yourself in Settings, matching links by their address, no template editing needed. Unlike Reader Progress, a Decision Point can be counted more than once per visit, since each click is a real, separate signal, not a milestone you either pass or don’t.
In your database, nothing personal is ever stored, for either module. No IP addresses. No cookies. No session identifiers. No individual reader can be picked out of the data at any point. What is stored is a daily count: per piece of content, how many times each Reader Progress milestone was reached, and how many times each Decision Point was clicked.
In your WordPress admin, under Semantic Journey, you get:
- Reports, a searchable, sortable table showing every piece of content, its four Reader Progress counts, and a column for every Decision Point you have set up, over the last 7, 30, or 90 days, with a one-click CSV export.
- Settings, where you control retention for each module, set up Decision Point rules, and switch either module on or off.
- A small box on the post editor itself, and a column on your Posts list, showing the same counts without leaving the page you’re working on.
That is the whole free plugin. There is no hidden second tier inside it, no feature waiting behind a license key.
What this is not
This document is meant to set expectations honestly, so here is the other half of the story.
Semantic Journey is not a replacement for full analytics. It will not tell you where your traffic came from, what device someone used, or how many total visitors your site had this month. It answers two narrow questions well: how far did readers get through a piece of content, and did they reach the actions you’ve marked as mattering. If you need broader traffic data, you will want a separate tool alongside it.
A Decision Point count is not a conversion, a sale, or an attribution claim. A click on Donate Now tells you someone clicked it, not that they completed a donation, and a click on a phone number tells you someone tapped it, not that the call was answered. Semantic Journey stops exactly at the click. What happened after is a fact it does not have and will not guess at.
It is not a promise of more traffic, more donations, or better rankings. It is a measurement tool, not a growth tool. What you do with what it shows you, as Priya did, is up to your editorial judgment.
It does not track individuals, build reader profiles, or support any kind of targeting or personalization. That is a deliberate limit, not a missing feature. If your goals require knowing who is reading or who is clicking, Semantic Journey is the wrong tool by design.
And it will not give you a number every time. If a piece gets very little traffic, if a reader has JavaScript turned off, or if a page’s structure cannot be reliably read, the plugin stays quiet rather than guess. An honest gap in the data is worth more than a number that is not true.
The Monday after
Priya still opens a dashboard every Monday. It is smaller than the old one. It does not try to tell her everything. But when she asks it “how far did people get” and “did they act,” it answers both in words she would use herself, and she has stopped needing to guess at either one.
That is what Semantic Journey is for.