I want to remove the date stamps on each post on my Drupal site. That way, visitors won't be put off when I am not able to update and post new articles and posts. Is it possible? I know that on pages there is no date but on blog posts it is automatically added??
Removing date stamps on the posts can be done in several different ways, depending on the system you use to post (is it a content management system or straight up HTML?), or your comfort level with CSS.
With many popular Content Management Systems (CMS) you have the ability to turn off post attribution. For example, this website runs on Drupal. With Drupal content, you can turn off post attribution in the content type itself. Without getting super heavy into details (it could be boring), a Drupal site is setup by content types (think page, article / blog, videos, etc), all of which you have the ability to turn on or off the post attribution.
For anyone else not quite following along on what we are talking about, the post attribution is typically at the beginning or end of an article Check out this image with an arrow pointing to exactly what we are talking about:
These are fields we do not want to show up any more in our Article Content. In the case of Drupal, you would login as an administrator and navigate to /admin/structure/types - where you will then see all your content types like the image shown here:
On the content type you want to have the field display or hide on, click edit. In our case, we want Articles since that's our blog posts. When you edit the content type, be sure to look below the main options at the top to the sidebar options on the left bottom. In particular, you want the tab that says "Display settings". You want to make sure it's unchecked, like the image below shows:
Since this is now unchecked, the author and date information will no longer show up with Articles. While at first this may seem like a good thing, you are sorta shooting yourself in the foot - especially with blog / article content where the relevant post data is typically in the author and date information. So the next best option is to leave the content so search engines can find it and know who wrote the article, and when. If we do this though, won't that be a bit ugly? Well, no. Hiding with CSS does not make it go away for search engines, only a human being visiting the site. SO, leave this option turned on (if you're using Drupal) and then hide the content with CSS.
Going back to our test post, we can use Google Inspect (or the equivalent Firefox option) to find out exactly what CSS class to target, or we will have no idea what to hide. Since we are using Google Inspect, we want to right click on the actual piece of content we are looking to hide: In our case the posted by line with date and time. You should see something similar to below:
Once we have the element targeted (In our case, div.submitted) we can add a rule in Google Inspect to see a live view of what our changes would look like had we actually implimented them. This allows us to essentially edit a website live, and then make the changes in the code after and only if we decide we like the new output. In our case, we noticed that div.submitted is displaying all of the submitted data. If we add a simple display:none; to our div.submitted class, the entire div will disappear from view, but still be visible to search engines. The end result is similar to the following image:
Notice how the submitted by data below our "test" text went away? It's still there, and still contains our metadata so search engines know who posted the article and when, but it's not hidden from the regular user of the website. If your article / blog / website content displays a picture (as mine does above) you can use the same technique to target the picture and hide it.
Once you've decided the changes you've made look good, go ahead and add the changes to your actual stylesheet that is being used. Typically, this is named something like style.css or in custom builds you may even have a custom.css file. You should look more into your setup to make sure you understand what files are rendering the content, or you could likely be making changes to content that would break your site elsewhere.
I hope this helps clear things up a bit.