8 Comments


  1. D’oh! I’ve done this more than I care to admit. I hate how something that’s such a simple oversight can have such a devastating impact on a website’s success. I will definitely be kicking the tires on this new plugin, and if it works for me I’ll be including it on all future builds.

    Reply

    1. I’ve never worked in the consultant/client environment but I’d have to hit my head on a desk if I forgot to enable search engines for a site I designed that went live.

      Reply

  2. I’ve done it, and I felt awful. My clients called me many weeks after the website had gone live to say they couldn’t find it on Google. I have a check-list that includes “make sure discourage search engines is not ticked”, and somehow I missed it. I’m considering this plugin as a backup just in case I forget to remove the tick again.

    Reply

  3. Yep. I’ve done it plenty of times too, so we have checking reading settings on our site go live checklist.

    Yoast’s WordPress SEO plugin also includes a warning to check the settings.

    Reply

  4. Even worse, is when people do an IP block. I’ve seen sites get launched with a block on all traffic outside of a small set of IP addresses. Then it’s taken a week for anyone to realise there was a problem.

    Reply

  5. Been there and done it.

    I used to develop sites locally before I went live.
    Now I develop live but check the discourage search engines box until the site is complete or almost complete.
    Because that’s the way I develop I have a reminder on my “to do” list to uncheck the box.

    Reply

  6. Thanks for the coverage Jeff.

    To those who say “Yoast Plugin does it as well”, well, yes it does :). Where we differ is that Yoast’s plugin (to the best of my knowledge) can be dismissed easily. This is a lot harder to remove. :)

    Reply

Leave a Reply