Our pricing page lists four goals, tracked daily. We built each one to count a single thing against a target fixed for the quarter. For ranking, we count how many of the target searches put the blog on page one, on Google and in AI answers. The pace goal counts posts published against the number the plan called for. For readership, we count time read. The Strategist proposes the full set at the start of the quarter, and the hour we spend with a new customer is where the targets get agreed. After that, Propaganda scores them every day. We'd rather you looked once a week, for reasons that come up further down.
Four numbers is a short list for a blog. It replaces the usual monthly ritual, where an agency sends a PDF with forty charts and a paragraph about "momentum". You finish the PDF unable to say whether the blog worked, and the agency would prefer it stayed that way.
The targets are set before the first post
Our own blog went through this first. On the day the blog started, the Strategist handed us a plan. We answered its questions over three rounds and approved the fourth version. That plan tracks ten searches, with data from DataForSEO, and watches four sites. It set the ranking target at two searches on page one this quarter.
We argued with it in places. The plan read "ai cms" as a search that brings people shopping for a free blog, and we kept it as a target anyway. It is on the strategy page with the plan's objection next to it, which is about as honest as a disagreement gets in marketing.
We care about the order more than the numbers. When the target comes before the posts, nobody can look at a quiet month and decide afterwards that the goal was "brand awareness" all along. That move has rescued more content budgets than any post ever did.
Pace is a goal because a blog that stops proves nothing
We learn nothing from a blog with three posts and a long silence. It didn't fail and it didn't work. It stopped. So pace gets counted like everything else, and our own pace goal reads 1 of 4 to 6 posts this quarter. That is behind, and we show it on the strategy page where anyone can see it.
We made pace a goal because slowing down is the easiest thing a busy company can do and the hardest thing to diagnose later. The Acorn Digital founder who built a niche blog on a fresh domain dropped to one post a month over the summer, and then his impressions crashed. He suspected a Google update more than his own slowdown, and his clicks came back. Without a pace count he had no way to separate the two, and neither would we.
Readership is counted as time read
We could count visits, which show only that someone arrived. We could count clicks, which show only that a headline worked. Neither one tells you whether anyone read the post. Time read is closer. Google Analytics documents engagement time as the time a page spends in focus, and it stops counting when the reader switches away from the tab or leaves. For web traffic, Google describes that number as active interaction with the page.
We left out the engagement score, which does something else. It adds clicks, scrolls, shares and likes into one figure and calls the total interest, which means a reader who scrolled to the bottom in four seconds can land in the same column as one who spent six minutes on the argument. Because we think that blend flatters the content and hides the reading, the readership goal counts minutes. Minutes can't prove that a post brings in customers. Even so, they prove it got read, and for a blog that is the first thing worth knowing.
A new domain ranks slowly, so October looks flat
Ranking is the goal that tests a founder's nerve. Our plan gives the searches it rates as low difficulty less time to reach page one. It gives the other eight longer. So if our ranking score sat flat through October, the plan was working as written.
The Acorn experiment had the same shape. In its first month on a fresh domain there were few impressions and few clicks. About a month in the clicks started climbing, and by summer the site had picked up steam. We expect a flat line in week three on a blog with no history. You should worry about a flat line once the weeks in the plan have passed.
A falling score changes the next batch of pitches
This is where the weekly look comes in. A falling score shows only that a goal is behind, and checking it every morning adds no reason why. On a new domain, a ranking goal checked daily produces eleven weeks of mild panic and one good day. Checked weekly, the same goal shows a trend you can do something about.
What changes is the work. When a goal falls behind, the Strategist weighs the next batch of pitches against it. If pace slips, the Strategist favours posts that are quick to finish. If a target search isn't moving, the next pitch goes after it. A topic that moves no goal gets no post, however clever it sounded on a call. We apply the cap here too, keeping proposed volume roughly in line with what was published the quarter before. Being behind gets a sharper pitch. It never gets a pile of filler.
Four is a limit we chose on purpose
We picked four because four get read. A fifth number gets checked less than the other four, and a dashboard of fifty gets opened twice, once when it was set up and once when someone asked whether it was still running. We think a founder with no content person can hold four numbers in their head between meetings and no more than that. We pay a price for the limit. Some things that matter, like which post a buyer mentioned on a sales call, never become a number. Those show up in the pitches instead, where they belong.
Where the four goals live
The goals section of our strategy page shows them on a sample company called Fullhouse. We used a sample because our own blog is only a few weeks old and its numbers would make a thin chart. On your own blog the four come with the paid plans, which are open through the waitlist. Propaganda Light, the free plan, already shows readership numbers for every post, so the minutes get counted from the first one you publish.