If I was to implement a visitor queuing system for my website, where if visitor count is higher than n, place them in a queue. Would this have an effect on google's ability to crawl the site?


  • 1
    How would this system be implemented? Would it rely on login? On cookies? On IP addresses? Commented Jun 22, 2017 at 20:20
  • @StephenOstermiller it would be implemented by placing a javascript tag inside the header. There is no login. not sure about the last two Commented Jun 22, 2017 at 20:35
  • @StephenOstermiller it would be ip based in that we can add an exclude ip list for the queue Commented Jun 22, 2017 at 20:52
  • 2
    …where if visitor count is higher than n, place them in a queue... Why would you do this? This is counter to good user experience(UX). If fact, any webserver should handle a huge number of users these days without issue. Why would you not pursue performance enhancements instead of performance degradation? This does not make sense.
    – closetnoc
    Commented Jun 23, 2017 at 4:04
  • What higher level problem are you trying to solve? This sounds like an XY Problem
    – charlietfl
    Commented Jun 25, 2017 at 22:14

2 Answers 2


Yes, agree with comments above. You need to think in a way to solve the problem so that users do not need to wait. As no one likes waiting.

Having said that if the core design is to let user wait after x number due to tech, resources or other issues then you may have an issue from SEO side.

Google expect either you let the Google bot to crawl or clearly notify not to crawl. If Google will not be successful to crawl every time then possibly you will have a ranking issue and you will get warnings in Google Webmaster Tools.

So, the recommendation would be to think hard about your implementation strategy have a clear approach, Yes or No for Google.


It depends on how you implement it. For Google to crawl the website, it must get a successful status and get a crawlable response, which usually means returning a 200 OK status plus some HTML back.

Now suppose you send back a 503 Service Not Available instead, it will attempt to crawl back later. If it gets them often though, the crawling rate will drop and possibly eventually stop.

Any actual error returned such as 4xx status codes will really impair Google bot from crawling the site and they will appear as errors in Google Webmaster Tools.

If you are limited in resources, you should probably let googlebot through and serve it content from a cache. Of course if the limit is bandwidth, then there is not much you can do about it.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.