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
-
On-page SEO
This is a question for the organic SEO experts, once you added the main keyword that you want to rank for in the homepage title, meta title plus meta description, perhaps once or twice in the text on the homepage. How often do you then write it in the content marketing, say blog posts, we want to rank higher on Google for "SEO agencies Cardiff" however if you mention this in the blog posts too much say once a week, this could lead to over optimisation issues?
On-Page Optimization | | sarahwalsh1 -
Tags - Good or bad for SEO
We are getting Moz errors for duplicate content because tag pages share the same blog posts. Is there any way to fix this? Are these errors bad for SEO, or can I simply disregard these and ignore them? We are also getting Moz errors for missing descriptions on tag pages. I am unsure how to fix these errors, as we do not actually have pages for these on our WordPress site where we are able to put in a description. I have heard that having tags can be good for SEO? (We don't mind having several links that show up when searching for us on google...) As far as the SEO goes, I am not sure what to do. Does anyone know the best strategy?
On-Page Optimization | | Christinaa0 -
SEO audit on a beta site
HI there, Is there much point conducting an SEO site audit on a site that has not yet launched and is protected behind a login? Presumably none of the usual SEO tools (Moz, Screaming Frog etc) can crawl this site becuase it is all locked behind a login. Would it be better to launch it and then do a site audit? Thanks
On-Page Optimization | | CosiCrawley0 -
SEO can id and class be used in H1?
Can ID and class be used in my H1 tag. I realize best case would be to change it, but it's going to require a change order from the ecommerce company to fix their sloppy code. Will this hurt seo? Example:
On-Page Optimization | | K-WINTER0 -
ECommerce Filtering Affect on SEO
I'm building an eCommerce website which has an advanced filter on the left hand side of the category pages. It allows users to tick boxes for colours, sizes, materials, and so on. When they've made their choices they submit (this will likely be an AJAX thing in a future release, but isn't at time of writing). The new filtered page has a new URL, which is made up of the IDs of the filter's they've ticked - it's a bit like /department/2/17-7-4/10/ My concern is that the filtered pages are, on the most part, going to be the same as the parent. Which may lead to duplicate content. My other concern is that these two URLs would lead to the exact same page (although the system would never generate the 'wrong' URL) /department/2/17-7-4/10/ /department/2/**10/**17-7-4/ But I can't think of a way of canonicalising that automatically. Tricky. So the meat of the question is this: should I worry about this causing issues with the SEO - or can I have trust in Google to work it out?
On-Page Optimization | | AndieF0 -
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 -
How do Maximize WordPress with 2 SEO Plugins
I have 2 WordPress SEO Plugins, Yoast and All-in-One SEO. I have tried like heck to make them work together, but every time I crawl my site here, I get multiple error messages. My question is, how can I tweak the title settings to avoid having multiple meta desctiptions, titles etc.
On-Page Optimization | | TheSportsDaddy0 -
Best SEO structure for blog
What is the best SEO page/link structure for a blog with, say 100 posts that grows at a rate of 4 per month? Each post is 500+ words with charts/graphics; they're not simple one paragraph postings. Rather than use a CMS I have a hand crafted HTML/CSS blog (for tighter integration with the parent site, some dynamic data effects, and in general to have total control). I have a sidebar with headlines from all prior posts, and my blog home page is a 1 line summary of each article. I feel that after 100 articles the sidebar and home page have too many links on them. What is the optimal way to split them up? They are all covering the same niche topic that my site is about. I thought of making the side bar and home page only have the most recent 25 postings, and then create an archive directory for older posts. But categorizing by time doesn't really help someone looking for a specific topic. I could tag each entry with 2-3 keywords and then make the sidebar a sorted list of tags. Clicking on a tag would then show an intermediate index of all articles that have that tag, and then you could click on an article title to read the whole article. Or is there some other strategy that is optimal for SEO and the indexing robots? Is it bad to have a blog that is too heirarchical (where articles are 3 levels down from the root domain) or too flat (if there are 100s of entries)? Thanks for any thoughts or pointers.
On-Page Optimization | | scanlin0