Search results

Site analytics

Last updated: Jul 26, 2026

This page provides site analytics for my site. Each year in January, I gather up these analytics to analyze trends and plan content directions.

I’ll admit I skipped this exercise for two years running. Watching the numbers fall after 2023 was demoralizing enough that I didn’t want to look, let alone write it up. Having finally sat down with the 2024 and 2025 data, I think the story is more interesting — and honestly more encouraging — than the headline totals suggest. If you only read one part of this page, make it What I make of the decline at the bottom, where I try to work out what actually happened and which of these numbers still mean anything.

Overall page traffic

In 2025, idratherbewriting.com had 454,036 page views, or about 1,244 page views a day. More details are in the following table:

Metric 2025 2024
Pageviews 454,036 (-21%) 577,097
Average engagement time 1:14 minutes (-13%) 1:25 minutes
User sessions 339,557 (-20%) 426,021
Users 227,470 (-19%) 281,545
Sessions per user 1.49 (-1%) 1.51

A "page view" is when the page loads, regardless of whether it's the same visitor or a different visitor. A "session" refers to a unique visit to the site. If the same visitor views 10 pages, it only counts as a single session.

This section compares the same values across years, providing a sense of trends over time. Years run newest to oldest from left to right, and the percentage in parentheses is the change from the prior year (the column to its right).

Metric 2025 2024 2023 2022 2021 2020 2019
Page views 454,036 (-21%) 577,097 (-42%) 992,255 (-35%) 1,535,622 (-18%) 1,865,635 (+3%) 1,814,770 (-8%) 1,974,524
Average page views per day 1,244 (-21%) 1,577 (-42%) 2,719 (-35%) 4,207 (-18%) 5,111 (+3%) 4,971 (-8%) 5,409
Users 227,470 (-19%) 281,545 (-46%) 517,954 (-37%) 820,365 (-17%) 982,313 (+7%) 916,922 (+1%) 909,236
Sessions 339,557 (-20%) 426,021 (-46%) 782,783 (-27%) 1,068,404 (-15.7%) 1,266,999 (+6.0%) 1,195,729 (-1.0%) 1,207,264
Average engagement time* 1:14 (-13%) 1:25 (+9%) 1:18 (+3%) 1:16 (-34%) 1:19 (-7%) 1:25 (-16%) 1:41
Page views per session 1.34 (-0.7%) 1.35 (+6%) 1.27 (-12%) 1.44 (-2.0%) 1.47 (-3.3%) 1.52 (-7.3%) 1.64
* Previously, this value was "Average sessions per user." With the change in 2023, I think "Average engagement time" most closely maps to this previous value.

Two caveats before anyone reads too much into the cliff. First, Universal Analytics stopped processing data in mid-2023 and GA4 counts users differently — generally lower — so part of the 2023 drop is a change in how I'm measuring rather than a change in who's visiting. The 2023 through 2025 numbers are GA4 throughout, so those comparisons are honest ones: page views down 54%, users down 56%.

Second, and more importantly, these totals are the least useful numbers on this page. They lump together two completely different audiences that have moved in opposite directions. The traffic origins section below is where that comes apart.

Locations

Location 2025 2024 2023 2022 2021 2020 2019
US 43.3% (+14%) 37.9% (+22%) 31% (+11%) 28% (+12%) 25% (-14%) 29% (-9%) 32%
China 10.7% (+310%) 2.6%
India 7.0% (-38%) 11.3% (-25%) 15% (-12%) 17% (-15%) 20% (+5%) 19% (+12%) 17%
Canada 4.9% (+3%) 4.8%
UK 4.2% (-21%) 5.3% (+6%) 5% (+25%) 4% (0%) 4% (-20%) 5% (0.0%) 5%
The biggest shift here is China, which went from 2.6% of users in 2024 to 10.7% in 2025, moving it to second place. Meanwhile India, long my second-largest audience, fell from 11.3% to 7.0%. The US share has grown steadily for three years running.

Because these are percentages of a shrinking pie, the absolute numbers tell a sharper story. Between 2023 and 2025 my US audience fell about 39%, while my India audience fell about 80%. That's a big enough gap to mean something: the readers I lost skewed heavily toward search-driven, mobile, non-US visitors — which is exactly the profile of someone arriving for a quick answer rather than for me.

The China figure I'd treat with suspicion. Tripling in absolute terms during a year when every other segment halved doesn't look like a sudden surge of Chinese readers; it looks like crawlers or VPN traffic. I'd want to check bot filtering and the engagement time on that segment before believing it.

Browsers

Browser 2025 2024 2023 2022 2021 2020 2019
Chrome 74.8% (+7%) 70.2% (+5%) 67% (-8%) 73% (-5%) 77% (-1%) 78% (+3%) 76%
Safari 11.4% (-21%) 14.4% (+31%) 11% (-8%) 12% (+33%) 9% (+13%) 8% (0%) 8%
Edge 6.7% (-17%) 8.1% (+34%) 6% (0%) 6% (+20%) 5% (+67%) 3% (+50%) 2%
Firefox 5.0% (+10%) 4.5% (-10%) 5% (-17%) 6% (-14%) 7% (-13%) 8% (-11%) 9%

Device types

Device type 2025 2024 2023 2022 2021 2020 2019
Desktop 81.7% (+4%) 78.2% (-7%) 84% (+2%) 82% (-4.7%) 86% (-2.3%) 88% 88%
Mobile 17.7% (-17%) 21.2% (+33%) 16% (-11%) 18% (+28.6%) 14% (+16.7%) 12% (+9.1%) 11%
Tablet 0.38% (-17%) 0.46%

Traffic origins — organic and social referrals

Traffic Origin 2025 2024 2023 2022 2021 2020 2019
User sessions 339,557 426,021 782,783 1,068,404 1,266,999 1,195,729 1,207,264
Organic Search Traffic 39.3% (-33%) 58.4% (-19%) 72% (-11%) 81% (-9.1%) 90% (+1.1%) 89% (+4.7%) 85%
Sessions via Social Referral 11,939 (-20%) 14,839 (-74%) 56,327 (17%) 48,018 (+3,960%) 11,346 (+2%) 13,840 (+24%) 11,163

Organic search as a share of sessions is the single most important row on this page. It went from 90% at its peak to 39% in 2025. But percentages of a shrinking total are slippery, so here is the same thing in absolute sessions, split into search traffic and everything else:

Year Total sessions From organic search From everywhere else
2025339,557133,276206,281
2024426,021248,583177,438
2023782,783563,604219,179
20221,068,404865,407202,997
20211,266,9991,140,299126,700

This is the finding that made me feel better about the whole thing. Organic search is down 88% from its 2021 peak. Traffic from everywhere else — direct visits, newsletter, LinkedIn, other sites linking to me — is up 63% over the same period, and down only 6% since 2023.

In other words, essentially the entire decline is search. The audience that shows up because they know who I am hasn't gone anywhere; if anything it has grown. What collapsed is the drive-by traffic that arrived from a Google result, read one paragraph, and left. That traffic was always the bulk of the total, which is why losing it looks catastrophic in the charts.

One thing worth separating out: the social referral collapse is not an AI story. Social sessions went from 56,327 in 2023 to 11,939 in 2025, a 79% drop. That's Twitter falling apart and platforms suppressing outbound links. Different cause, different problem, and I shouldn't blame AI for it.

Top 30 pages

The API documentation course still dominates the top of the list, even though there are only about 100 course pages against roughly 3,000 blog pages. Nearly every page declined, but not evenly — and the pattern in *which* pages fell hardest turned out to be the most useful thing in this year's data. See [the page-type pattern](#what_it_means) below.
Page 2025 views Change vs. 2024
I'd Rather Be Writing blog 45K +2.3%
Documenting APIs: A guide for technical writers and engineers 29K -15.6%
The ideal number of slides for an hour-long presentation, and other thoughts on preparing slides 7.8K -60.9%
Access and print a specific JSON value 5.7K -67.0%
Step 3: Parameters (API reference tutorial) 5.6K -61.6%
Page Not Found 6.9K -18.8%
What is Diátaxis and should you be using it with your documentation? 4.7K -35.8%
Chapter 1: Introduction to REST APIs 4.2K -41.6%
Quick Reference Guide Templates 4.2K -36.4%
Chapter 3: Documenting API endpoints 4K -36.8%
Step 2: Endpoints and methods (API reference tutorial) 3.9K -55.1%
Introduction to REST API documentation 3.7K -36.7%
OpenAPI tutorial using Swagger Editor and Swagger UI: Overview 3.6K -30.0%
What is a REST API? 3.5K -11.0%
Tom Johnson 3.3K -2.6%
AI is accelerating my technical writing output, and other observations 3.1K -34.7%
Step 1: Resource description (API reference tutorial) 2.9K -42.8%
Swagger UI tutorial 2.8K -56.8%
Quick Reference Guides: The Poetry of Technical Writing 2.4K -45.1%
Movemate standing board review — fixing your back, legs from sedentary decline from a tech job 2.4K -37.6%
Redocly tutorial -- authoring and publishing API docs with Redocly's command-line tools 2.4K -35.2%
Documenting APIs: A guide for technical writers and engineers (PDF) 2.3K -45.4%
curl intro and installation 2.2K -59.9%
Working in YAML (OpenAPI tutorial) 2.2K -54.5%
Step 5: Response example and schema (API reference tutorial) 2.2K -53.1%
Make a curl call 1.9K -59.0%
Step 7: The tags object (OpenAPI tutorial) 1.8K -65.9%
Activity: Generate a Javadoc from a sample project 1.7K -65.2%
My experience trying to write original, full-length human-sounding articles using Claude AI 1.5K -68.7%
My 2024 technical writing trends and predictions 1.1K -87.4%

What I make of the decline

Here's my attempt to work out what actually happened between 2023 and 2025, and which of these numbers I should still be paying attention to.

The pages that lost most are the ones an AI can answer

I grouped my top 30 pages by what kind of page each one is. The classification is rough and my own judgment, but the gradient is hard to miss:

Type of page Average change, 2024 to 2025
Destination pages (blog home, author page, course landing)-5%
Conceptual explainers ("What is a REST API?")-32%
Essays and opinion pieces-47%
Step-by-step how-tos-54%
Pure lookups ("Access and print a specific JSON value")-64%

The more a page exists to answer a question someone could just ask a chatbot, the harder it fell. "How do I access a JSON value" and "what's the ideal number of slides for a presentation" are precisely the queries that no longer become clicks. Meanwhile my blog home page actually grew 2.3% in 2025 and my author page was flat, in a year when everything else halved. The pages people navigate to on purpose held up fine.

The audience that stayed behaves the same as it always did

If AI were degrading the quality of my remaining traffic, I'd expect people to be reading less per visit. The opposite happened: page views per session went from 1.27 in 2023 to 1.34 in 2025, and sessions per user held steady at about 1.5. Engagement time bounces around within noise.

So I didn't lose readers. I lost searchers. Those are different populations, and I'd been counting them in one bucket for fifteen years.

The reach I can't measure is probably the largest part now

My API documentation course is almost certainly part of what these AI assistants learned from, and it gets cited and summarized in conversations I'll never see. That's real reach, and Google Analytics has no way to represent it. The uncomfortable implication is that my influence and my page views have come apart, possibly permanently — and page views were only ever a proxy for the thing I actually cared about.

Which numbers I actually watch now

Given all that, here's how I've reweighted this page:

  • Traffic from everywhere except search. This is the number I'd keep if I could only keep one. It tracks the audience that chose to come here, and it has been climbing.
  • Destination pages. The blog home page, the course landing page, my author page. When those fall, I have an actual problem.
  • Newsletter subscribers. Not on this page, but the most honest measure of an audience that isn't mediated by a platform. Currently there are 7,200 subscribers.
  • Page views per session and sessions per user. Small numbers that tell me whether the people who arrive are engaging or bouncing.

And what I've stopped treating as meaningful: total page views, which now mostly measures Google's product decisions rather than my work; browser and device breakdowns, which have never once changed anything I did; and social referrals, which measure the health of platforms I don't control.

Podcast numbers deserve a mention, because I'd like to include them and can't. My host only exposes 60 days of download data, and the YouTube view counts don't correlate with audio listens much, so there's no honest annual figure to publish. That gap is itself part of the story: as an audience shifts from search to direct relationships — podcast, newsletter, book club — it gets harder to count, not easier.

What this means for what I write

The reference and tutorial material that built this site's traffic is now largely infrastructure that AI reads on my behalf. I don't regret writing it and I'll keep it current, but I've stopped expecting it to bring people here.

What still works is everything that can't be summarized out of existence: opinion, first-hand experience, argument, community. The book club, the podcast, and the agent skills course all fall into that category, which in hindsight looks less like coincidence and more like my instincts arriving ahead of my analytics.

Previous posts analyzing site analytics

For more details about analytics, see the following posts. These posts expand on audience interests and demographics.

About Tom Johnson

Tom Johnson

I'm an API technical writer based in the Seattle area. On this blog, I write about topics related to technical writing and communication — such as software documentation, API documentation, AI, information architecture, content strategy, writing processes, plain language, tech comm careers, and more. Check out my API documentation course if you're looking for more info about documenting APIs. Or see my posts on AI and AI course section for more on the latest in AI and tech comm.

If you're a technical writer and want to keep on top of the latest trends in the tech comm, be sure to subscribe to email updates below. You can also learn more about me or contact me. Finally, note that the opinions I express on my blog are my own points of view, not that of my employer.