In case anyone else runs into this problem there is a way to force google-bot to re-download the robots.txt file. Go to Health -> Fetch as Google [1] and have it fetch /robots.txt That will re-download the file and google will also re-parse the file. [1] in the previous Google UI it was 'Diagnostics -> Fetch as GoogleBot'.


If you know that the verification file should be named googled1085b59adc211cb.html (and you are told after you add a site within Webmaster Tools), then you can place the following into the appropriate server context of your nginx.conf: location = /googled1085b59adc211cb.html { rewrite ^/(.*) $1; return 200 "google-site-...


I know this is very old, but... If you uploaded the wrong robots.txt (disallowing all pages), you can try the following: first correct your robots.txt to allow the correct pages, then upload a sitemap.xml with your pages as google tries to read the xml sitemap, it will check it agains robots.txt, forcing google to re-read your robots.txt.


The way you have created your new sitemap is correct. Each URL is listed only once inside <loc> tags but next to those are all the alternative URLs for the same page in other languages so it might seem that you are listing everything three times. A sitemap index is used when you outgrow a single sitemap file. Sitemap files have a limit of 50,000 ...


Did you tried to send a site map to Google. Ask Google to recrawl your URLs If you’ve recently added or made changes to a page on your site, you can ask Google to (re)index it using the Fetch as Google tool. The "Request indexing" feature on Fetch as Google is a convenience method for easily requesting indexing for a few URLs; if you have a ...


You can try adding 301 redirects for those pages so that they point to your front page. This might make it faster for Google to expire the hacked pages.


The problem is that Google is not a "live" search, at least not for the vast majority of sites that get indexed every few weeks or so. Just wait until the Googlebot visit your site again or read this.


Looks like your question is a two parter. First, the best way to ensure that your website load times are fast is to make sure you are not maxing out your bandwidth (looks like you occasionally hit your cap, so that shouldn't be a problem). Employee web surfing (download) should not impact your website serving (upload) until you are maxing out the connection ...

Only top voted, non community-wiki answers of a minimum length are eligible