Honestly, I feel like this is Google's fault. It shouldn't be prioritising new content as much as it does. The best articles are often "classics" from several years ago that haven't changed because they haven't needed to.
Blogwashing
61–70 of 117 posts
Re: Blogwashing
#62If I wrote an article in 2015 and freshen it up with more relevant links, better writing, or some other thing, is it still published in 2015? Should I re-date it? Am I "gaming" the system by doing that? Or am I notifying my readers (all 3 of them!) that there is fresh content? This is actually a real question from me, and I'd love feedback. I look back on my stuff from a few years ago and the blog posts need fixing u…
Often dates are extremely relevant, for example a 10 year old hardware review won't be as relevant as a new one. On the other hand, blogs don:t have to be static, some programing technique might still be relevant, but need to be updated for a new version of the language. Solution: put a "first published" and a "last updated" date, or use a wiki that makes the revisions available online and a way to link to the differ…
Re: Blogwashing
#63Re: Blogwashing
#64Honestly, I feel like this is Google's fault. It shouldn't be prioritising new content as much as it does. The best articles are often "classics" from several years ago that haven't changed because they haven't needed to.
There was a HN post a few weeks ago showing how Duck Duck Go was better at showing old content. I totally agree. We like what's fresh and new, but next time you go to a blog and read some tech article; look through their archive and see what else they've written. If you run your own blog, keep an easily indexd archive page. Mine goes back to 2007: https://battlepenguin.com/archives/
Re: Blogwashing
#65Re: Blogwashing
#66Honestly, I feel like this is Google's fault. It shouldn't be prioritising new content as much as it does. The best articles are often "classics" from several years ago that haven't changed because they haven't needed to.
Google's algorithm tends to classify queries as "evergreen" and otherwise. With the former, recency doesn't seem to matter that much. I've had content stick a page 1 ranking for 3+ years without any updates.
For non-evergreen keywords, recency matters a lot. A fresh article on an established domain can often outrank better, but older content.
The query classification system works well enough for most keywords, but there is a grey area where Google doesn't really know what to focus on. Like with a query that focuses on "best practices". It isn't clear whether Google should prioritize classic, evergreen best practices, or focus on more recently developed best practices.
I would definitely appreciate a filter that only shows me old school content for my target queries. Some of the best content I've read online sits on websites that haven't been updated since 2002 and still use tables based design.
Re: Blogwashing
#67Search is just getting worse and worse, its a problem that probably nobody can solve with the current paradigm. I think in a few years there will be a significant opening in the search market for an algorithm that manages to structure information differently
My local historical society decided to produce lots of content and exclusively post to Facebook. It’s incredibly dumb, but people seek the easiest path.
Re: Blogwashing
#68If I wrote an article in 2015 and freshen it up with more relevant links, better writing, or some other thing, is it still published in 2015? Should I re-date it? Am I "gaming" the system by doing that? Or am I notifying my readers (all 3 of them!) that there is fresh content? This is actually a real question from me, and I'd love feedback. I look back on my stuff from a few years ago and the blog posts need fixing u…
Even looking from usability standpoint I think that it is totally okay and even necessary to add 'updated' or 'modified' date. Personally, as a reader I'm relying on article created/updated heavily, if I cannot quickly and easily figure out if article is still relevant and up-to-date I'm usually leaving webpage immediately without even bothering to read.
Re: Blogwashing
#69And with version numbers, you are not limited to dates in the past, you can even write articles about the future!
Here's a brilliant example: https://gorails.com/setup/ubuntu/20.04
How to set up Rails on Ubuntu 20.04, which will be released in April next year. You can already read the guide today! Some of the links might not work yet, because obviously you can't download Ubuntu 20.04 yet, but once it's released, those guys are bound to be the first ones who had a guide out!
Re: Blogwashing
#70Honestly, I feel like this is Google's fault. It shouldn't be prioritising new content as much as it does. The best articles are often "classics" from several years ago that haven't changed because they haven't needed to.
I work in content marketing so SEO is a big part of my work focus. Google's algorithm tends to classify queries as "evergreen" and otherwise. With the former, recency doesn't seem to matter that much. I've had content stick a page 1 ranking for 3+ years without any updates. For non-evergreen keywords, recency matters a lot. A fresh article on an established domain can often outrank better, but older content. The quer…