Welcome to the Q&A Forum

Thanks David and Jarno, I thought the following may be useful to you. After extensive testing, we followed this process to remove the Sitelink: We added  <meta name="robots" content="index, nofollow">only to the page shown within the Sitelinks. Within our tests we found removing the page within GWT only elongated the removal process, therefore we refrained from doing this. Within GWT we did a Fetch and Render to inform Google of the change.</meta name="robots"> Within less than 24 hours the Sitelink was removed from the SERPs and organic sessions have not been effected whatsoever. Feel free to ask further questions if you'd like further information. Thanks, Phil

There isn't a tool that I'm aware of that does exactly this bit Followerwonk comes closest to it. You're able to analyse quite a lot about your tweets on there so would recommend checking it out. Also, Sprout Social is another good tool for Twotter analysis.

Hi Phil I don't know that I've seen this exact issue before, but I've seen similar situations recently as well. I almost wonder if this could have to do with what data center you happen to be hitting, or if perhaps just in their database for some reason they push back to a prior index. Or you could be seeing part of test in one of those instances. You could try asking others to check the cache from different places geographically. Have you also tried different browsers? I know some of that could be a stretch, but testing all variables can't hurt. End of the day, I don't think this is a huge issue if Googlebot crawls the site at a healthy rate. So I'd run through webmaster tools etc and make sure crawl depth is where it should be. -Dan