brozek/website
1
0
Fork 0
mirror of https://github.com/Brandon-Rozek/website.git synced 2024-11-24 17:16:30 -05:00
Code Issues Projects Releases Packages Wiki Activity

New post

Browse source
This commit is contained in:
Brandon Rozek 2023-05-17 23:45:44 -04:00
parent 9f93a9b6c3
commit 921e4c28dd
No known key found for this signature in database
GPG key ID: 26E457DA82C9F480
1 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

28
content/blog/website-analytics-usefulness.md Normal file
View file

@ -0,0 +1,28 @@
---
title: "The Usefulness of Website Analytics for Personal Websites"
date: 2023-05-17T22:22:10-04:00
draft: false
tags: []
math: false
medium_enabled: false
---
Should personal websites contain analytics? One argument is that analytics create a perverse incentive for the author. Let's say that someone spent a lot of time uploading their favorite [recipes](https://brandonrozek.com/menu/) which have gone mostly unnoticed. Meanwhile, their post on [wildcard domains in PiHole](https://brandonrozek.com/blog/wildcarddomainspihole/) has thousands of visits regularly. Upon seeing their analytics, they decide to abandon uploading recipes and instead only write about Raspberry Pis.
While this would likely get you more views, the idea is that the personal website then loses some *personal touch*. Some argue that personal websites should not be driven by any agenda other than yourself. No data, no click-bait titles, etc.
Of course this goes into why you created your website to begin with? For myself, this website's primary purpose is for *me*. I often forget how to perform many tasks and use this website as a reference guide.
Though one of my core principles is in sharing knowledge. An important secondary goal of mine is that others find my website useful in some way. The best way to achieve this is to carefully craft each and every one of my blog posts.
Personally, I find this difficult. Striving for perfection in a post often leads to its incompletion. In fact, it's not uncommon for me to sit on a topic for multiple months (sorry [OpenStreetMap](https://brandonrozek.com/blog/contributing-openstreetmap/)) only to then force myself to write something on the topic to remove it from my backlog.
Now I could revisit older posts and spruce them up, but over the years I've written more than 300 blog posts covering a variety of technical content. It would be a slog to comb over each individual one.
This is where [analytics come into play for me](https://brandonrozek.com/blog/goaccess/). This allows me to identify popular blog posts and spruce up those instead. It does mean that unpopular blog posts are unlikely to get corrected[^1]. However since time is limited, it's nice to know that I'm improving a post that many look at and potentially rely on.
[^1]: I also improve posts as I reference them personally. Some people email me with questions and provide suggestions which eventually make their way to the blog posts as well.
Also throughout the years, I've edited the engine that creates these posts. This means that there are some broken links in the Internet that gets surfaced every now and again in my error logs :)
I understand that to some looking at an analytics dashboard can cause *fixation*. That doesn't mean, however, that we should dismiss analytics entirely. It's a tool, and if there's some benefit and it's right for you, then we should make use of it.