How to use analytics to decide what to write next
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 signup clicks or custom events on each top page.
- Calculate a simple action rate: signup clicks divided by visitors for that page.
- Compare pages with similar traffic. A page with half the traffic but twice the action rate may be a better topic to expand.
- If you have time-on-page or scroll data, use it only as a secondary signal. Explicit clicks and events are stronger evidence of intent.
- If a page has high traffic and low action, the topic may need a different angle or a clearer next step.
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.
- A page that gets traffic from a campaign link may reflect campaign interest, not long-term demand. Wait for repeat visits before building a content series around it.
- A page that gets direct or search traffic with no recent promotion is a candidate for a companion piece.
- If a source sends readers to one page but they never click further, your next piece should answer the next question before that source moves on.
- A page that gets traffic from a specific community may deserve a version written for that community’s skill level or constraints.
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.
- If an article drives signups, write the piece that removes the last objection before signing up.
- If an article drives clicks to another page, write the missing page in between.
- If an article gets visits but no clicks, the next piece may be a clearer explanation of the same problem, not a new topic.
Build a shortlist from patterns
A simple shortlist beats a long content calendar. For each candidate topic, ask:
- Has a related page received steady visitors for two or three months?
- Did that page generate a signup click, event, or download?
- Did a specific source keep sending readers to it?
- Is there a repeated question in the funnel after that page?
- Can I write the next page in under two focused sessions?
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:
- Which pages had the most signup clicks per visitor in the last 30 days?
- Which sources sent visitors to pages that reached the signup page?
- Which of my top pages has the lowest action rate?
- Which page had the biggest traffic spike this week?
- Which page gets repeat visitors but no signup clicks?
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:
- Pick one page that has stable traffic and some signup clicks.
- Read the page as if you were the visitor. Ask what is still missing.
- Check the source that sends the most visitors. Write for that audience’s next question.
- Add one click-tracked event to the current page so the next decision has better data.
- Write one follow-up piece that connects the current page to the next action.
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 demoAdd 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
- Analytics tag checker: Which analytics and pixels a site runs, plus duplicate and broken tags.
- Free UTM link builder: Add utm_source, medium and campaign to any link.
- Website traffic checker: A site's popularity rank and estimated monthly visits.
More from the blog
- How to calculate your website conversion rate, and what to compare it to
- Is my A/B test result significant? A plain-English guide with a worked example
- What is bounce rate, how is it calculated, and is yours a problem?
- How to add a visitor counter to your website or GitHub README
- How much traffic does a website get? How to estimate any site's visits
- How to track QR code scans: count them, and see which poster worked
- How to see how many people clicked your link (without a paid shortener)
- How to check if your Google Analytics 4 tag is installed (and only counting once)
- Why GA4 shows your campaign traffic as Unassigned (and how to fix the links)
- Does your redirect keep your UTM tags? How to check before a campaign goes out
- How I built a self-hosted analytics MCP server on Cloudflare Workers and D1
- UTM tracking explained: what the parameters mean and how to use them
- Conversion funnel analysis for small sites: a practical guide
- Sudden drop in website traffic? A checklist for finding the cause
- What is an MCP server? A plain-English guide for people who run websites
- How the Model Context Protocol Works
- Track File Downloads Without Guesswork
- Adding analytics to a Next.js app without slowing it down
- Core Web Vitals and Traffic: Is There a Link?
- Analytics After Cookies: What Actually Changes
- GDPR and website analytics: a practical guide for small sites
- How to Compare Website Analytics Tools by Privacy
- GA4 Events Explained for Beginners
- How to measure a newsletter send with UTM links
- How to track Hacker News traffic
- Adding Analytics to a Framer Site
- How to ask your coding agent about your analytics
- What Is Bounce Rate and How Is It Calculated?
- A practical website analytics retention policy
- Map your site's funnel from first visit to signup
- What Is a Good Bounce Rate?
- How to automate a weekly traffic report
- A Practical Privacy-Friendly Analytics Checklist
- Adding an MCP server to Claude Code
- How long should you keep analytics data?
- How to Build a Small MCP Server That Actually Helps
- How to Find the Biggest Drop Off in a Funnel
- What Is the Urchin Tracking Module?
- What Microsoft MCP servers actually do
- UTM parameters for email newsletters
- Track Button Clicks Without Google Tag Manager
- How to track the results of a social media post without cookies
- How to track traffic from a GitHub README
- How to measure a product launch without guessing