Publishing consistently for three months and having no idea whether it worked is normal. It is also avoidable, and the fix is one table.
The table
Copy this. One row per published asset.
| Asset | Published | Impressions | Clicks | Avg position | Key event | Events | Next action |
|---|---|---|---|---|---|---|---|
| Pickleball coach site article | 2026-08-15 | Booking start | |||||
| Deposit policy article | 2026-07-11 | Booking start | |||||
| TeamUp comparison | 2026-07-23 | Launch enquiry | |||||
| Package worksheet | 2026-08-15 | Resource read |
Impressions, clicks, and average position come from Google Search Console. Events come from your analytics. Fill it in once a month.
The four columns that matter
The asset. A stable name you can ask a question about later. “Did the deposit article do anything” is only answerable if the deposit article is a row rather than one of thirty posts that happened.
Search visibility. Impressions tell you whether you are shown at all. Clicks tell you whether the title earns the visit. Average position tells you whether you are near the results people click. Check monthly. Search moves in weeks, and daily checking produces anxiety rather than information.
The key event. The action that counts as the content having worked. Not a pageview. Something a person did because they were persuaded: a booking flow started, an enquiry sent, a package page reached.
Choose it before publishing. Picking the metric afterward is how everything ends up looking like a success.
The next action. Exactly one decision per row. This is the output. Without it you have a report, and reports do not change anything.
Diagnosing from the row
Read the columns as a sequence. Where the row breaks tells you what to fix.
| What the row shows | The problem is | Next action |
|---|---|---|
| Almost no impressions | Discovery | Check indexing, internal links, and whether the page targets a real query |
| Impressions, few clicks | The promise | Rewrite the title and description |
| Clicks, no key events | The page | Add a clear booking path and cut the distance to it |
| Key events, no bookings | What happens after the click | Look at the booking flow, price clarity, and availability |
Four different problems. A follower count cannot tell them apart, which is why the scoreboard has four columns instead of one.
Setting it up once
- Verify the site in Google Search Console and submit the sitemap.
- Install analytics on every page, including the pages the booking flow runs through.
- Define your key events explicitly rather than inferring them later.
- Then leave it alone and let a month accumulate.
Before you act on a surprising number, re-check the plumbing. Most dramatic month-one results are tracking problems.
Reviewing it
Monthly, in about twenty minutes:
- Fill in the numbers.
- Read each row and find the failing column.
- Write one next action per row.
- Do those actions before publishing anything new.
That last step is the discipline. The scoreboard only pays for itself if the next-action column drives what you work on, rather than sitting next to a growing pile of new posts.
The actions worth counting have to be real. When booking, payments, and client records run as one system, a started booking is a genuine signal rather than a click on a link that leads to a text message.
Background reading: Growth needs a scoreboard, not vibes