<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>robotstxt on bascht.com</title><link>https://bascht.com/tags/robotstxt/</link><description>Recent content in robotstxt on bascht.com</description><generator>Hugo -- gohugo.io</generator><language>de-de</language><lastBuildDate>Thu, 20 Jun 2013 00:00:00 +0000</lastBuildDate><atom:link href="https://bascht.com/tags/robotstxt/index.xml" rel="self" type="application/rss+xml"/><item><title>Emulate a robots.txt file with a simple nginx directive</title><link>https://bascht.com/tech/2013/06/20/emulate-a-robots.txt-file-with-a-simple-nginx-directive/</link><pubDate>Thu, 20 Jun 2013 00:00:00 +0000</pubDate><guid>https://bascht.com/tech/2013/06/20/emulate-a-robots.txt-file-with-a-simple-nginx-directive/</guid><description>If you use nginx as a reverse proxy, you might want to emulate a simple robots.txt file just to be sure that Googlebot doesn&amp;rsquo;t traverse into each and every location.
So why bother serving those bytes from a file when you can answer requests directly from nginx:
location /robots.txt { return 200 &amp;#34;User-agent: *\nDisallow: /&amp;#34;; }</description></item></channel></rss>