Ah, is your embedded blog on a different domain and being iframed in? The analytics would be more detailed looking at the direct blog data. It sounds like something within the blog went mini-viral and is producing the spike.

Hi. Typically you should have some idea of the keywords a page is targeting, i.e. What is it called? What's the title tag say? What's the content of the page? And so on.  Also, in general, you can model your pages using a break down of Moz' http://moz.com/learn/seo/on-page-factors where applicable for your content.  If you have a list of keywords that you're trying to rank for, have you associated that list with different pages on your site?  That would at least give you a start.

Hi Ram. If Jon's fix above doesn't work, you might want to post the link(s) you're testing with Screaming Frog so that people here can see what's going on and give you specific recommendations. It sounds like there's a 302 in place on the http version of your site, but people will need details to see where exactly. Cheers!

Right. Moz Local uses the matching verifired Google + and Facebook listings to verify those locations. So what you have there is what gets applied to the myriad of others. See: https://moz.com/local/how and:

Moz Local takes the time and hassle out of managing your listings across multiple sites and directories. When you submit a listing on Moz Local, it must match an existing Google Places or Facebook listing across all of the following attributes: Business Name, Address, Phone Number, and Website. Because you've already gone through the phone or postcard verification process with Google and/or Facebook, your Moz Local listings will be validated if they exactly match Google or Facebook.

Some of our partners—such as Infogroup and Best of the Web—may call or email to confirm your listing information is accurate, but no postcard or PIN entry is required.