measuremy.site

How to use analytics to decide what to write next

Business meeting featuring laptops, notes, and teamwork around a white table.
Photo by Artem Podrez on Pexels

The most useful content decision is rarely “what do I feel like writing?” It is usually “what do the people who already visit my site need next?” Analytics can answer that without turning writing into a formula. The goal is to spot demand you are already attracting, then serve it more directly.

Start with the pages people already visit

Pull your most visited pages for the last 30, 60, and 90 days. Compare the lists. Pages that appear in all three are stable demand. Pages that only appear recently are emerging interest. Note the topic behind each page, not just the URL. Ignore vanity pages such as your homepage unless it is a landing page.

For a small site, five to ten pages are usually enough to see a pattern. You do not need a large report. You need a short list of topics that already earn attention.

Separate traffic from usefulness

Traffic alone can mislead. A page can get visits because it ranks for a broad term but still attract the wrong reader. Check what readers do after arriving.

Look at sources before you brainstorm

Where a page’s visitors come from changes what you should write next. A page that gets steady visitors from a community or forum has an audience already discussing that problem. Write the follow-up question they are likely to ask next.

Track the step after reading

Content decisions improve when you connect pages to actions. Define the useful next step for each article: sign up, start a trial, read a related guide, click a download, or use a tool.

Use click tracking on the main call to action. Then group pages by their next step. Some pages may drive signups, others may only drive more reading. Both are useful, but they suggest different follow-ups.

Build a shortlist from patterns

A simple shortlist beats a long content calendar. For each candidate topic, ask:

Then pick one or two. Do not turn every observation into a new article. If a page is already working, sometimes the best decision is to update it, add a clearer call to action, or link it to a newer page.

Ask your coding agent for the numbers

If you use measuremy.site, its MCP server lets Claude Code, Cursor, or Codex read the same dashboard data, so you can ask questions in plain English instead of clicking through reports manually. That can save time when you want to compare pages, sources, and signup events across date ranges.

Useful questions to ask include:

The point is not to hand over the writing. The point is to get the evidence into a form that makes the next step obvious.

Turn one finding into one next piece

A practical workflow looks like this:

This keeps analytics from becoming a reason to publish more noise. The point is not to fill a quota. It is to extend what is already working.

Analytics will not tell you exactly what to write, but it will tell you which topics already earn attention and which ones move readers toward action. Use that evidence to make a small, specific choice: expand one page, answer one follow-up question, or create one clearer path. Over time, that beats guessing.

See it on your own site

measuremy.site is cookieless analytics your coding agent can read. 30-day free trial, no card. Plans from $9/month.

Start free trial See the live demo

Add measuremy.site analytics to this project: connect the measuremy.site MCP server at https://a.measuremy.site/mcp for all my projects (claude mcp add --scope user; it signs in with OAuth, no key, and one sign-in covers every site), then tell me how to sign in. Details: measuremy.site/llms.txt

Free tools

All free tools

More from the blog