Forums / Install & configuration / /content/browse/ view found by Google
Helle Andersen
Monday 17 August 2009 1:52:51 am
Google is able to find a content/browse view of our pages - how can we avoid this ? See e.g. http://www.cbs.dk/content/browse/68157(Google search for Lars Eskebæk)
Jean-Luc Nguyen
Monday 17 August 2009 2:08:15 am
Hello,
Maybe you can use robots.txt file to exclude content from being indexed by google?
http://www.acidre.com
Monday 17 August 2009 2:26:34 am
We thought about that too, but I believe that the problem should be solved within eZ...
André R.
Monday 17 August 2009 4:26:58 am
I could not find any occurrences of links to content/browse in any of our default templates except when your already in browse view. (You need to perform a post to get into content/browse by default as far as I can see, and crawlers don't post forms).So, do you have link to content/browse in your content or templates by any chance?
eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Monday 17 August 2009 5:49:53 am
Nope - just checked to be sure. We do not use content/browse anywhere in our templates...Could it be some default ini setting from old times - we have used eZ since 2003...
Heath
Monday 17 August 2009 9:30:41 am
@ Helle
It may be foolish to ignore the simplest solution in this case. The robots.txt file is the universally accepted way to prevent this concern in general. Ignoring the trivial robots.txt file configuration which would prevent this problem outright is worth completing.
Afterward you could change down other possible causes internally (ghosts/shadows) with free time as needed.
Updated: Useful related links, http://ezpedia.org/ez/robot_txt
Cheers,Heath
Brookins Consulting | http://brookinsconsulting.com/ Certified | http://auth.ez.no/certification/verify/380350 Solutions | http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project | http://ezpedia.org
Monday 17 August 2009 9:43:53 am
Only "solution" we can do in eZ Publish would be to add an additional permission rule for content/browse, so you can control access to it independently of content/read permissions.
If you don't do editing in front end siteaccess, then you can always disable the view in addition to the mentioned robots.txt suggestion.