Grav/robots.txt

User-agent: *
Disallow: /backup/
Disallow: /bin/
Disallow: /cache/
Disallow: /grav/
Disallow: /logs/
Disallow: /system/
Disallow: /vendor/
Disallow: /user/
Allow: /user/pages/
Allow: /user/themes/
Allow: /user/images/
Allow: /
Added a default all-access robots.txt 2014-12-22 10:51:10 -07:00			`User-agent: *`
Prevent crawling of unnecessary directories Prevent search engines from crawling and indexing unnecessary files and directories. The "/user/plugins/" directory may need to be added to the Allow list if plugins use frontend accessible assets. This is tested at a basic level using Google Fetch and Render. 2015-11-20 19:33:24 -07:00			`Disallow: /backup/`
			`Disallow: /bin/`
			`Disallow: /cache/`
			`Disallow: /grav/`
			`Disallow: /logs/`
			`Disallow: /system/`
			`Disallow: /vendor/`
			`Disallow: /user/`
			`Allow: /user/pages/`
			`Allow: /user/themes/`
Update robots.txt (#2043) When using "Fetch and Render as Google" in Google Search console it will report "partial" rendering due to the blocked images in /user/images directory which is blocked because of the Disallow /user/ rule. Proposing this small change as it improves google rendering of the page. 2018-05-30 19:47:21 +02:00			`Allow: /user/images/`
Update robots.txt (#2632) I have found that Bing/Yahoo/DuckDuckGo, Yandex and Google report crawl errors when using the default robots.txt. Specifically their bots will not crawl the the path '/' or any sub-paths. I agree that the current robots.txt should work and properly implements the specification. However it still does not work. In my experience explicitly permitting the path '/' by adding the directive Allow: / resolves the issue. More details can be found in a blog post about the issue here: https://www.dfoley.ie/blog/starting-with-the-indieweb 2019-08-19 03:22:33 +10:00			`Allow: /`