Title: OnPage and HTTPS
Last modified: August 30, 2016

---

# OnPage and HTTPS

 *  [M](https://wordpress.org/support/users/infolegal/)
 * (@infolegal)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/onpage-and-https/)
 * OnPage.org does not work with https websites so you might want to consider adding
   an option to mute OnPage verification for these websites. Quite annoying to see
   that warning all the time..
    Thanks!
 * [https://wordpress.org/plugins/wordpress-seo/](https://wordpress.org/plugins/wordpress-seo/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Thread Starter [M](https://wordpress.org/support/users/infolegal/)
 * (@infolegal)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/onpage-and-https/#post-6765243)
 * After the 3.0.3. update I’ve created the account on OnPage.org and looks like
   my homepage is indexable (with https).
 * However, Yoast still shows the “Your homepage cannot be indexed by search engines”
   message in my dashboard.
 * So, I would propose you either link the data between your plugin and the OnPage
   account (since creation of the account is offered in a joint landing page) or
   you just add the possibility, in the WP dashboard, to reset the indexability 
   check.
 * Thanks!
 *  [jhm](https://wordpress.org/support/users/jhm/)
 * (@jhm)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/onpage-and-https/#post-6765274)
 * Hey M,
 * to investigate in that case i need your domain. is it [http://www.mediasinfo.ro/](http://www.mediasinfo.ro/)?
 * Best, Merlin
 * PS: Sounds like your hoster blocks requests based on useragents, but i need to
   validate
 *  Thread Starter [M](https://wordpress.org/support/users/infolegal/)
 * (@infolegal)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/onpage-and-https/#post-6765276)
 * Hi Merlin,
 * it’s with https, but you got the domain right.
    Maybe it’s something in .htaccess
   that it’s blocking something? Could Wordfence be the culprit here too?
 * Thanks for looking into it!
 * M
 *  [jhm](https://wordpress.org/support/users/jhm/)
 * (@jhm)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/onpage-and-https/#post-6765277)
 * Hey M,
 * yap, Wordfence seems to be the cause. We already reached out to them to get this
   out of the way.
 * They seem to block all our crawlers and return a 403 error … thats why we report“
   not indexable” because it looks like your webserver generally tells bots to go
   away.
 * Looks like nothing you or we could do at this moment. We will try to convince
   the Wordfence guys to whitelist our crawlers, so these “false positive” Warnings
   do not confuse users of both plugins.
 * thanks for the feedeback and sorry again for the confusion!
 *  Thread Starter [M](https://wordpress.org/support/users/infolegal/)
 * (@infolegal)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/onpage-and-https/#post-6765279)
 * Hi Merlin,
 * that’s great to hear! Both plugins are “must have” on my site, so I’m sure it’ll
   work out.
 * M

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘OnPage and HTTPS’ is closed to new replies.

 * ![](https://ps.w.org/wordpress-seo/assets/icon-256x256.gif?rev=3419908)
 * [Yoast SEO - Advanced SEO with real-time guidance and built-in AI](https://wordpress.org/plugins/wordpress-seo/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-seo/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-seo/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-seo/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-seo/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-seo/reviews/)

## Tags

 * [HTTPS](https://wordpress.org/support/topic-tag/https/)
 * [onpage.org](https://wordpress.org/support/topic-tag/onpage-org/)

 * 5 replies
 * 2 participants
 * Last reply from: [M](https://wordpress.org/support/users/infolegal/)
 * Last activity: [10 years, 7 months ago](https://wordpress.org/support/topic/onpage-and-https/#post-6765279)
 * Status: not a support question