Title: Idexability problems: Maybe a Bug?
Last modified: June 17, 2020

---

# Idexability problems: Maybe a Bug?

 *  Resolved [andreasilicati](https://wordpress.org/support/users/andreasilicati/)
 * (@andreasilicati)
 * [5 years, 12 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/)
 * Hi there,
    in my site, the section “Site Health” gives me a the problem “Your
   site can’t be found by search engines”. After reading tons of articles between
   Yoast and Ryte, I’ve been searching for my site with the “site:mysite.it” on 
   goole but I found various pages of my site. So … the issue in my “Site Health”
   section is a bug or somewhere there is a problem?
 * The robot.txt says:
    User-agent: * Disallow: /wp-admin/ Allow: /wp-admin/admin-
   ajax.php
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fidexability-problems-maybe-a-bug%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

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

 *  [Rumejan](https://wordpress.org/support/users/onlyincebu/)
 * (@onlyincebu)
 * [5 years, 12 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13001472)
 * Hello! It looks like the Ryte warning is just wrong. Can you please deactivate
   and reactivate the Ryte feature directly from SEO > General > Features (tab),
   and fetch the index status again to see if this resolves the issue? If it’s still
   the same, we suggest three actions.
    1. Ignore the issue. Your site is appearing
   in Google. 2. Deactivate the Ryte feature. 3. Contact Ryte here: [https://support.ryte.com/hc/en-us](https://support.ryte.com/hc/en-us)
 *  Thread Starter [andreasilicati](https://wordpress.org/support/users/andreasilicati/)
 * (@andreasilicati)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13003502)
 * Hi,
    thank you for your answer. I’ve tried to deactivate/reactivate the Ryte 
   feature but it continues with the issue, so i deactivated it.
 * Really thank you for the support, I was going mad with it!
 *  [Jeroen Rotty](https://wordpress.org/support/users/jeroenrotty/)
 * (@jeroenrotty)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13003551)
 * Hi [@andreasilicati](https://wordpress.org/support/users/andreasilicati/),
 * Thank you for your reply.
 * Your homepage is indexed, but when we check your homepage now, we see that the
   HTTP header of your homepage is a 503, which technically means Service unavailable.
   This is probably because you are using any maintenance mode plugin at this time?
   Is this temporary?
 * By default, most maintenance plugins output that header information. Because 
   the maintenance page is not a fixed/permanent page. If the current page is what
   you really want to have and you’ll continue with this, we encourage you to check
   the plugin if you can change that behavior.
    -  This reply was modified 5 years, 11 months ago by [Jeroen Rotty](https://wordpress.org/support/users/jeroenrotty/).
      Reason: typo
 *  Thread Starter [andreasilicati](https://wordpress.org/support/users/andreasilicati/)
 * (@andreasilicati)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13004124)
 * Yes, at the moment I’m using a Maintenance Mode because the site is under construction.
   And yes it’s temporary, I hope in a few weeks to take down the Maintenance Mode
   and go on with the “fresh-and-new” site.
 * Oh ok, seem like all my problems are because I’m in a Maintenance mode. :O So,
   when the site will be totally online the indexability problems will be gone automatically?
 *  [Jeroen Rotty](https://wordpress.org/support/users/jeroenrotty/)
 * (@jeroenrotty)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13004195)
 * Yes, when you disable the maintenance plugin, we expect that all the content 
   that is configured to be public and indexable, to be indexable;
 *  [devnihil](https://wordpress.org/support/users/devnihil/)
 * (@devnihil)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13004230)
 * [@andreasilicati](https://wordpress.org/support/users/andreasilicati/) Yes, the
   indexability warnings seem to stem from you using maintenance mode. A 503 response
   is essentially telling a bot that is crawling your site that is isn’t currently
   available, and should try back later.
 * If you do continue to experience any problems with indexing after taking the 
   site out of maintenance mode though, please let us know.
 *  [devnihil](https://wordpress.org/support/users/devnihil/)
 * (@devnihil)
 * [5 years, 11 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13036612)
 * We are going ahead and marking this issue as resolved due to inactivity. If you
   require any further assistance please create a new issue.

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

The topic ‘Idexability problems: Maybe a Bug?’ 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

 * [robot.txt](https://wordpress.org/support/topic-tag/robot-txt/)

 * 7 replies
 * 4 participants
 * Last reply from: [devnihil](https://wordpress.org/support/users/devnihil/)
 * Last activity: [5 years, 11 months ago](https://wordpress.org/support/topic/idexability-problems-maybe-a-bug/#post-13036612)
 * Status: resolved