pwired Posted March 19, 2015 Share Posted March 19, 2015 Hi, I have build a website for a customer where I offered the client two options: 1. During the build up I send you screenshots/pdf's and the client can give feedback on that what needs to be changed. 2. I build the website online on a testserver and the client can see live how the build up is going and give me feedback on that. The client chose for option 2 because a live website is much more convenient than screenshots and pdf's. Now the website is finished and I have moved everything to the online server and connected the domainname with the website. Problem: Google search still shows results from the time when the website was on the test server. Never had any problems with this but now for the first time a client complains about this. Question: How can I build a website online without Google seeing anything so that Google search results will not show up from the time the website was build on a test server ? Link to comment Share on other sites More sharing options...
LostKobrakai Posted March 19, 2015 Share Posted March 19, 2015 I'm on mobile, but robots.txt is the keyword. For your current case I would suggest doing a permanent redirect from the testserver to the production one, so google will at least slowly move over to the real urls. 2 Link to comment Share on other sites More sharing options...
marcus Posted March 19, 2015 Share Posted March 19, 2015 During developement, use... <meta name='robots' content='noindex,follow' /> ...in the future and remove this tag before the Going Live. 3 Link to comment Share on other sites More sharing options...
tpr Posted March 19, 2015 Share Posted March 19, 2015 I would probably add a simple password protection (hpasswd for example). 6 Link to comment Share on other sites More sharing options...
pwired Posted March 19, 2015 Author Share Posted March 19, 2015 I would probably add a simple password protection (hpasswd for example). Is it sufficient to put this in the root of the website and then Google won't see anything anymore ? Link to comment Share on other sites More sharing options...
diogo Posted March 19, 2015 Share Posted March 19, 2015 Unless you give the password to google 5 Link to comment Share on other sites More sharing options...
adrian Posted March 19, 2015 Share Posted March 19, 2015 Or use: http://modules.processwire.com/modules/protected-mode/ If you are giving them a user account for the admin anyway, you may as well make use of it for accessing the front-end during development also. Much cleaner for them rather than having to login via the htpasswd entry, and then again for the PW admin panel. If you don't want them to have admin access you can still use this module and give them a guest role only! 6 Link to comment Share on other sites More sharing options...
pwired Posted March 19, 2015 Author Share Posted March 19, 2015 You guys are great, got it working. Just had to figure out that it is a combination of .htaccess and .htpasswd Inside .htaccess AuthUserFile /path/to/password-file/.htpasswdAuthType BasicAuthName "Identify"Require valid-user Inside .htpasswd username:password. ============================== Thanks everybody for all the solutions. Unless you give the password to google Maybe there is a protection against this also Link to comment Share on other sites More sharing options...
pwired Posted March 19, 2015 Author Share Posted March 19, 2015 If you are giving them a user account for the admin anyway, you may as well make use of it for accessing the front-end during development also. Much cleaner for them rather than having to login via the htpasswd entry, and then again for the PW admin panel. If you don't want them to have admin access you can still use this module and give them a guest role only! Yup, you're right. Just installed that module. 1 Link to comment Share on other sites More sharing options...
adrian Posted March 19, 2015 Share Posted March 19, 2015 And if you want more control, like protecting new areas that are being developed on sites that are already live, you can use: http://modules.processwire.com/modules/page-protector/ 3 Link to comment Share on other sites More sharing options...
Raymond Geerts Posted March 19, 2015 Share Posted March 19, 2015 Many valid solutions above. Here is another method: Make the site only accessable when logged in to the manager if (!$user->isLoggedin()) die(); Put it somewhere in /site/templates/_init.php or /site/config.php 3 Link to comment Share on other sites More sharing options...
adrian Posted March 19, 2015 Share Posted March 19, 2015 Many valid solutions above. Here is another method: Make the site only accessable when logged in to the manager if (!$user->isLoggedin()) die(); Put it somewhere in /site/templates/_init.php or /site/config.php That certainly works, but is not very friendly as you can't send them a link directly to a subpage. You could redirect them to the admin automatically, but then they still have to get back to the page they were looking for, so you'd need to redirect from login success back to that page. Hence the reason I created Protected Mode 3 Link to comment Share on other sites More sharing options...
Marty Walker Posted March 19, 2015 Share Posted March 19, 2015 +1 for ProtectedMode! 2 Link to comment Share on other sites More sharing options...
Recommended Posts