New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Enhancement] Provide a setting to remove the datepublished date published schema #12707
Comments
Please inform the customer of conversation # 495523 when this conversation has been closed. |
From user: Schema.press and other schema plugins are providing this feature |
@mayada-ibrahim can you tell me why you're not just updating the publish date in your WP site? Doing this would mean the date gets shown differently in many spots... |
@jdevalk I am surprised you do not seem to grasp the point or maybe I missed something. If you publish a post say January 2017 which you update every 6 months with the latest information. Even if your schema is set up to reference the modified date Yoast SEO stubbornly shows the original publish date. Changing that is not straightforward or clear. The published date your plugin shows to the public in the SERPS is misleading and very detrimental from a CTR viewpoint. Who wants to click on an article 2 years old when you can see much newer ones in the SERPS. So your article which is possibly the latest and the best never gets clicked on. You can turn the date off in Yoast but that is only half an answer. For a paid plugin this is a glaring and obvious faux pas. |
@slipperx help me out here, since WordPress shows that date in multiple places, why not just change the actual publish date in WordPress itself? Trying to understand this reasoning. |
@jdevalk Indeed you can change the publish date of updated content but then you are effectively saying that piece of content was created on the date it was modified rather than the date it was actually published in its first form. I am not sure Google would be very happy at that slightly misleading info but I do not know for sure. The better solution seems to me to just publish the modified date and leave the published date unstated for the purpose of honesty. |
I created the following snippet to remove the datePublished and dateModified from Yoast's 'article' and 'webpage' Schema markup:
|
This new way of placing all in a JSON without any control is bad. EDIT: Forced to go back to pre-version 11.- |
Hi @Salamander3, you can use the information on our knowledgebase to create, or have someone create, some code to alter the schema pieces to your liking. This thread remains open as a feature request for a visual interface to these settings. |
Thanks for feature request. |
How to remove New Person capabilities in Yoast SEO Premium? |
Just want to bump this request up in the priority queue. I too want a simple way to opt out of displaying the datePublished schema. For now, I'll have to do it via a code snippet, but it would be much easier (and more helpful) to have it as a plugin option. I think @jdevalk approach of changing the published date is fundamentally misleading. If you tell Google the date it was last updated only, then this is both true, and not misleading. |
Is your feature request related to a problem? Please describe.
Google only shows published dates in its search result pages and does not show updated dates. This can lower the CTR and lead to reduced traffic.
Users can create a filter to remove this using this guide here https://developer.yoast.com/schema-documentation/api/ but not all users are technically skilled to do so.
Describe the solution you'd like
Provide a setting to remove the datepublished date published schema
why you think the feature request is something we should consider for the Yoast SEO plugins?
Improve Technical SEO and UX
NOTES
Google uses the datepublished schema Yoast outputs as one signal to determine if it should show the date. This guide explains more: https://webmasters.googleblog.com/2019/03/help-google-search-know-best-date-for.html.
The text was updated successfully, but these errors were encountered: