Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Does Hiding the article´s date in a blog affect SEO?
-
We are running a blog and would like to hide date, as users find the article less interesting if they are dated more than 2 years ago.
Will hiding the article´s date in a blog affecto SEO?
Thanks in advance
-
I can answer that question as I just did an experiment on this which you can review here: http://www.rlmseo.com/blog/seo-impact-blog-post-dates/
The summary is this:
Assuming no displayed date as a baseline, recent dates (not sure exactly how recent - looks like up to 3-12 months but probably depends on industry, etc) will boost traffic significantly.
Compared to the baseline, distant past publish dates will reduce traffic a good bit.
I would recommend this:
- Display update date instead of publish date.
- If a post is still relevant, update it, maybe even add a disclaimer for your users that the post was first published on x date but has been updated and is current.
We've seen dramatic traffic increases with this strategy and it ensures people know how relevant your post is, which is actually more important than the publish date.
-
Hi,
I'm with Philip on doing this selectively. Many users find content hard to digest in the manner it was intended when they have no idea if it was written in 2006 or 2014. If your industry is one where time really doesn't matter or change anything, this may be different. From an SEO point of view, Google still knows when it first crawled a piece of content, so not including a date won't fool Google into believing the content is fresh when it's not.
I agree that creating evergreen content where appropriate is also a good move - articles, case studies, etc. that can be updated where appropriate (and blogged about + linked to to spur re-indexing).
If you see a marked drop off in traffic to or engagement in a post from 2+ years ago that used to be successful for the site, I'd consider re-writing the post with a current slant, linking to the old one from the post and being upfront about the fact that you're refreshing an old article. You can move engagement to the new post. If there really isn't anything new to say about the subject, you can still cover it again "for new readers" and redirect the old post to the new one, canonicalise it or leave it as is if there are no duplicate content issues.
-
I wouldn't recommend hiding the date because you don't want users to know that the content is old. What about when you publish something fresh and someone lands on the page but they can't find a date? They won't know how up to date that information is. I think a lot of people look for dates on blog posts, and rightfully so. They want to see that they're getting good information. You're right, if something is 2+ years old they might look for something more up to date. But you can update old blog posts and re-date them. Add something new to it, make some changes, and update the date.
Imagine an SEO strategy blog that didn't date the posts. You would be doing your visitors a complete disservice by hiding the date. You might have a post all about article directory submissions and they won't see that it's from 2008. That's not enhancing user experience, and people won't be happy with you.
Old content won't always be a bad thing. Read #4, "Burstiness," on this blog post: http://www.seobythesea.com/2014/03/incomplete-google-ranking-signals-1/
It's really interesting and a great read about how older content will sometimes receive the boost in rankings over fresh content.
EDIT: I'd like to add that it's completely okay to hide the date in some circumstances. You might have some sort of evergreen content that truly will stand the test of time and info may not ever, or rarely, change on the topic. For instance, if you were writing a blog post about how to improve your basketball shot. Who cares if the post is from 2006? In that case, hiding the date isn't going to reduce the overall user experience.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Filter By Category bad for seo?
Hello Everyone! I know that a single product should not have filter by color option since it will create duplicate content, and you have to use canonical tags to solve it. BUT how about sorting through products via category/brands?
On-Page Optimization | | Safxmed
Filter by category changes the URL of the General shop page (ex: hello.com/Shop/Category1022039 ). This page only displays the products within, no content/ descriptions etc unlike the original category page (ORIGINAL CATEGORY PAGE) Each of these category/brand already have their own individual pages (ex: hello.com/Shop/A). This is the page that will be optimized for content, FAQ, and ranking etc. Unlike in the url created when filtering through the categories. So technically I would have 2 URL for each Brand/Category. Would they compete with each other? What would you guys suggest. Please advise me on this. Thank You0 -
Is it SEO-wise to edit an already published article?
One of the pages on the website is #7 on the first page for a highly competetive keyword. Since I would like to improve rankings and the page is not optimized (e.g. keyword density is 0), is it SEO-wise to edit an article and create a good on-page optimization? Of course, the ultimate goal is to be in TOP 3 for a specific keyword.
On-Page Optimization | | zorsto1 -
Add content as blog post or to product pages?
Hi, We have around 40 products which we can produce plenty of in-depth and detailed "how to"-type pieces of content for. Our current plan is to produce a "How to make" style post for each as a long blog post, then link that to the product page. There's probably half a dozen or more of these kind of blog posts that we could do for each product. The reason why we planned on doing it like this is that it would give us plenty of extra pages (blog posts) on their own URL which can be indexed and rank for long tail keywords, but also that we can mention these posts in our newsletter. It'd give people a new page full of specific content that they can read instead of us having to say "Hey! We've updated our product page for X!", which seems a little pointless. Most of the products we sell don't get very many searches themselves; Most get a couple dozen and the odd few get 100-300 each, while one gets more than 2,000 per month. The products don't get many searches as it's a relatively unknown niche when it comes to details, but searches for the "categories" these products are in are very well known (Some broad terms that cover the niche get more than 30,000+ searches a month in the UK and 100,000+ world wide) [Exact].
On-Page Optimization | | azu25
Regarding the one product with more than 2,000 searches; This keyword is both the name of the product and also a name for the category page. Many of our competitors have just one of these products, whereas we're one of the first to have more than 6 variations of this product, thus the category page is acting like our other product pages and the information you would usually find on our product pages, is on the category page for just this product. I'm still leaning towards creating each piece of content as it's own blog post which links to the product pages, while the product pages link to the relevant blog posts, but i'm starting to think that it may be be better to put all the content on the product pages themselves). The only problem with this is that it cuts out on more than 200 very indepth and long blog posts (which due to the amount of content, videos and potentially dozens of high resolution images may slow down the loading of the product pages). From what I can see, here are the pros and cons: Pro (For blog posts):
1. More than 200 blog posts (potentially 1000+ words each with dozens of photos and potentially a video)..
2. More pages to crawl, index and rank..
3. More pages to post on social media..
4. Able to comment about the posts in the newsletter - Sounds more unique than "We've just updated this product page"..
5. Commenting is available on blog posts, whereas it is not on product pages..
6. So much information could slow down the loading of product pages significantly..
7. Some products are very similar (ie, the same product but "better quality" - Difficult to explain without giving the niche away, which i'd prefer not to do ATM) and this would mean the same content isn't on multiple pages.
8. By my understanding, this would be better for Google Authorship/Publishership.. Con (Against blog posts. For extended product pages):
1. Customers have all information in one place and don't have to click on a "Related Blog posts" tab..
2. More content means better ability to rank for product related keywords (All but a few receive very few searches per month, but the niche is exploding at an amazing rate at the moment)..
3. Very little chance of a blog post out-ranking the related product page for keywords.. I've run out of ideas for the 'Con' side of things, but that's why I'd like opinions from someone here if possible. I'd really appreciate any and all input, Thanks! [EDIT]:
I should add that there will be a small "How to make" style section on product pages anyway, which covers the most common step by step instructions. In the content we planned for blog posts, we'd explore the regular method in greater detail and several other methods in good detail. Our products can be "made" in several different ways which each result in a unique end result (some people may prefer it one way than another, so we want to cover every possible method), effectively meaning that there's an almost unlimited amount of content we could write.
In fact, you could probably think of the blog posts as more of "an ultimate guide to X" instead of simply "How to X"...0 -
Recommended number of blog posts per page?
Good day! We want to have your suggestions here.
On-Page Optimization | | robinwade
What's your recommended (best) number of blog posts per page? Thanks!0 -
Do images on a CDN affect my Google Ranking?
I have recently switched my images to a CDN (MaxCDN) and all of the images within my post are now get loaded directly from the CDN. Will this affect my Google ranking? Do Google care if the image is hosted physicaly on the domain?
On-Page Optimization | | Amosnet0 -
SEO for Japan
Google and Yahoo are the two major search engines in Japan. You can search using Western characters, and you often see English language results with Japanese (Chinese) characters next to them. As I don't speak Japanese, how do I approach SEO for my Japanese-language site? would appreciate any experiences and educational sources on the topic.
On-Page Optimization | | KnutDSvendsen0 -
HAVING A POPUP WINDOW ON HOMEPAGE AFFECTS SEO?
Good evening, I currently have a blog that uses a popup window after 15 seconds that is used to add visitor to my newsletter. My question is : Does it have a negative effect in SEO? Thanks in advance Maria Jesus
On-Page Optimization | | goperformancelabs0 -
Should I use my blog posts in a sub folder
Ok I did a search and didn't see an answer to this exact question. Most of them were about if a blog should be in a sub folder and not the blog posts themselves... so here it goes. I have a blog on my website the blog itself is in /blog/ but the blog posts themselves are situated in the root folder so it looks something like mydomain.com/cool-seo-blog-post/ Is there any reason I should change this and make it read mydomain.com/blog/cool-seo-blog-post/
On-Page Optimization | | jaybrn10