You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a user updates a post, the post updated time changes. TSF reads this and puts it in various places: structured data, Open Graph metadata, and the sitemap.
Google takes this data and can show it in the search engine result pages. This may be an unwanted side effect.
We could allow users to freeze the updated time to prevent that from changing (or, sometimes, even showing up). Subsequently, when that is requested, we shouldn't ping search engines about changes on the site.
When a user updates a post, the post updated time changes. TSF reads this and puts it in various places: structured data, Open Graph metadata, and the sitemap.
Google takes this data and can show it in the search engine result pages. This may be an unwanted side effect.
We could allow users to freeze the updated time to prevent that from changing (or, sometimes, even showing up). Subsequently, when that is requested, we shouldn't ping search engines about changes on the site.
Still, search engines can use other indicators to determine the date shown. But freezing the time helps a lot.
https://developers.google.com/search/blog/2019/03/help-google-search-know-best-date-for
The text was updated successfully, but these errors were encountered: