{"id":1361,"date":"2014-08-11T10:20:51","date_gmt":"2014-08-11T09:20:51","guid":{"rendered":"https:\/\/www.bronco.co.uk\/our-ideas\/?p=1361"},"modified":"2020-07-06T15:24:16","modified_gmt":"2020-07-06T14:24:16","slug":"updating-our-calendar","status":"publish","type":"post","link":"https:\/\/www.bronco.co.uk\/our-ideas\/updating-our-calendar\/","title":{"rendered":"Updating our Calendar"},"content":{"rendered":"

A couple of weeks ago we launched our Google Update Calendar<\/a>. We built it to become a resource for ourselves, our clients and anyone else that happens to find it so that they can keep up with any updates Google makes to its search algorithm.<\/p>\n

It also helps users go back through time and match a specific update to a time where they began to lose traffic and rankings. This provides SEO\u2019s or clients alike a starting point in discovering what issues their site might have and how to rectify them.<\/p>\n

So we launched our Google Update Calendar and saw that it was good. But after resting on that 7th day (yup, some good old bible references for you) we started working on a few enhancements\u2026<\/p>\n

Hat Tips<\/h2>\n

At Bronco we like to think we\u2019ve got our ear to the ground and discover quickly any confirmed or rumoured updates. But on occasion it can be other helpful souls in the community that point us in the direction of a new update.<\/p>\n

We wanted to be able to recognise these people as well as open our calendar up to allow others to come to us and fill in any blanks. Essentially we\u2019re crowd sourcing this, not so we don\u2019t have to do any of the work, but so we can ensure the calendar is as accurate as possible. We know if we\u2019ve got any glaring omissions in our calendar that the value and trust placed in it goes down.<\/p>\n

To recognise those that help keep the calendar up to date we\u2019ve added just a small hat tip with a link back to their personal website or twitter profile.<\/p>\n

Direct links<\/h2>\n

When the new HTTPS update<\/a> was announced last week Dave, our glorious leader, used the calendar page as a way to tweet about this news. But many people clicking the link would visit the page, possibly see the default calendar view and not be sure exactly what Dave is trying to communicate.<\/p>\n

The issue is that the update Dave wanted to show people isn\u2019t obvious on the calendar view and is only a little more obvious on the timeline view as it\u2019s the latest update.<\/p>\n

We needed a way to allow not only ourselves but others to share specific updates and for those links to navigate a new user directly to that update in the timeline view. And that\u2019s exactly what we did.<\/p>\n

So if an update happens to have a description or links to more reading then we also provide links to share on Twitter, Facebook and Google+. Once these links are clicked the user will be taken directly to the update with the content already in view.<\/p>\n

Anything else?<\/h2>\n

Over time we might find ourselves looking to enhance this resource further, but at the moment we\u2019ve not got anything specific planned.<\/p>\n

But if you have an idea for a feature that would make using our update calendar easier then leave a comment below. We can\u2019t promise to implement every new idea we get but your suggestion might just be too awesome to ignore.<\/p>\n","protected":false},"excerpt":{"rendered":"

A couple of weeks ago we launched our Google Update Calendar. We built it to become a resource for ourselves, our clients and anyone else that happens to find it so that they can keep up with any updates Google makes to its search algorithm. It also helps users go back through time and match […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[4],"class_list":["post-1361","post","type-post","status-publish","format-standard","hentry","category-search-engine-optimisation"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/posts\/1361","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/comments?post=1361"}],"version-history":[{"count":0,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/posts\/1361\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/media?parent=1361"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/categories?post=1361"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}