Welcome to the Q&A Forum

I'm very fond of Striker (Responsive in my case). Affordable, highly customizable and great support by the developing company.

It's been quite a few months since the last updates regarding HTTPS crawling of OpenSiteExplorer.

https://seomoz.zendesk.com/entries/20770156-open-site-explorer-to-crawl-https

http://moz.com/community/q/in-opensiteexplorer-why-is-https-not-an-option

But, as the last update dates October 2013, is there any news in regards to the progress on this subjects? More and more sites are switching to full HTTPS and support for this has been asked and responded upon for over two years.

Thanks for any updates.

When we moved our site over to full HTTPS we noticed that GWMT needed to re-authenticate for the HTTPS domain, and actually shows different information from the HTTPS profile compared to the HTTP profile.

The Analytics proporty won't change, but your sitemap will need an update for provide the HTTPS links compared to the HTTP ones. Google will quickly pick-up the protocol change and as long as you set-up correct redirects from HTTP to HTTPS you won't be dropping traffic that much. In the long run you'll see your site returning to it's old self again, depending on how good the rest of your optimization is.

Do keep in mind that if you're mixing content (retrieving external content from HTTP sources) some browsers start throwing warnings to users; if you're embedding HTTP content in an HTTPS site, browsers like Chrome don't load the HTTP at all unless the user clicks the option for mixed content at the end of the address bar.

Hope this helps!

The keywords can be set-up and changed in the Campaign Settings menu. In the top menu, go to "Campaigns", then choose the link "Campaign Settings" under the "View this Campaign" button. Then navigate to the tab "Manage Keywords".

It seems Moz completed the required engineering work and the index will build up in the upcoming months. 
https://seomoz.zendesk.com/entries/20770156-open-site-explorer-to-crawl-https

[quote]
Hi RKG-Dev -
When we release this you will be able to retrieve https URLs and associated metrics from the API in the same way you currently retrieve http metrics. We will be crawling https URLs at the same time we crawl http URLs so they will be available on the same dates.
April 26, 2013 01:50 pm
[/quote]

[quote]
As I understand it, the HTTPS crawl data will work it's way into the indexes iteratively over time, and this should start in one of the next few indexes. This means that we should have better and better secure site representation over the next few months.  I'll try and keep this thread posted as we see uptake with this.
With regard to the SERP analysis reports, if you are asking about metrics for https pages, this will come along for the ride, as will access via the API, campaigns, and OSE.
May 02, 2013 07:40 am
[/quote]

For the review submission page, I'd include some extra meta tag elements like:

This to tell Google not to index this page, not follow links on this page and to force using your meta description in the search engine result instead of a Open Directory Network description.

Thank you again for your response.

The following link forwards to one of the affected pages: http://bit.ly/1b3IVYB

I'm downloading Screeming Frog right now and give it a try, thank you for the advice.

Thank you for your response.

Our CMS generates the following meta-tags on the affected pages:

Pragma is for cache control, content-type and google verification are clear. P: is Pinterest Social media, the rest is standard again. I searched the source of the page for "robots" as well, but no results.

The CSV export for Crawl Diagnostics contains a column named "blocked_google". It states a blocking date/time but doesn't occur on all our webpages, not even on all pages of the same type / structure.

There are no other flags on these records that would explain a blocking of Google; all other agents are not flagged, and our robots.txt doesn't contain any blocks either. The only flag the records have in common is "Page Title > 70 characters". Of course, I could just assume this is the reason for the "blocking_google", but is it?

What evaluation makes the crawler fill in this property, and how to handle/solve it's occurrence?

The keywords can be set-up and changed in the Campaign Settings menu. In the top menu, go to "Campaigns", then choose the link "Campaign Settings" under the "View this Campaign" button. Then navigate to the tab "Manage Keywords".

For the review submission page, I'd include some extra meta tag elements like:

This to tell Google not to index this page, not follow links on this page and to force using your meta description in the search engine result instead of a Open Directory Network description.