Skip to content
This repository has been archived by the owner on Jan 15, 2020. It is now read-only.

robots.txt #74

Closed
tobyhunt opened this issue Apr 17, 2013 · 4 comments
Closed

robots.txt #74

tobyhunt opened this issue Apr 17, 2013 · 4 comments

Comments

@tobyhunt
Copy link
Member

Add one.

@taktran
Copy link
Contributor

taktran commented Apr 25, 2013

What do you want in it?

@tobyhunt tobyhunt mentioned this issue Apr 26, 2013
12 tasks
@taktran
Copy link
Contributor

taktran commented Apr 29, 2013

I can think of a use for the robots.txt - to exclude all files on pebblecode-staging.herokuapp.com and pebblecode-sandbox.herokuapp.com, so search engines don't duplicate their content

Robots.txt is also used to avoid what is known as “canonicalization” problems or having multiple “canonical” URLs. This problem is sometimes referred to incorrectly as a “duplicate content” problem.

http://seoroi.com/seo-faq/robotstxt-what-it-is-why-its-used-and-how-to-write-it/

Although there are passwords on these sites, sometimes we need to take off the password during development, so they might get spidered.

@shapeshed
Copy link
Member

We should have the following robots.txt for production if we don't have one.

User-agent: *
Disallow: 

Google Webmasters moans if you don't have one and it is good practice.

taktran added a commit that referenced this issue May 1, 2013
@taktran
Copy link
Contributor

taktran commented May 1, 2013

I read that you can just leave it out if you want to allow everything, and submitting the sitemap to google webmasters seemed to be ok, but no harm adding it in. Have added it in http://pebblecode.com/robots.txt

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants