A quick and easy way is to inject a <meta name="robots" content="noindex"> tag into the <head> tag of your page. For extra points you can make this optional in your doctype with a checkbox or similar.
You can use the <meta name="robots" content="noindex, nofollow"> tag to achieve this. You can for instance make a "Hide from search engines" checkbox on your "SEO" tab and if it's checked then render this line on the page - You can read more this meta tag here http://www.robotstxt.org/meta.html
But if you're thinking about making a password protected area on your website then it will not be indexed anyway (The login screen can be) since the pages are not reachable for the search engines since they do not have a login.
In regards to password protection you can read more about it here http://siempresolutions.co.uk/blog/UmbracoMembersProtectedAreaof_Website - In short you can right click a node and setup "public access", which can be either "Single user protection" or "Role based protection". Single user protection allows you to quickly allow access for a certain member/user on the fly providing email and password for one person directly on the node - The most common approach is to set role based protection, which is based on the member groups created in the "Members" section.
That way you can have a password restricted area on your website, which will require members to logon to gain access to the content. The public access settings will be inherited from parent to children all the way down to the last level of children.
In your code you'll then need to check if a certain member has access to the nodes - This is also illustrated in the article I referenced.
Blocking pages from search engine
Hello,
Anyone know how to block certain pages from showing up in search engines? robot.txt will only work for directories..
Also looking for a way to password protect certain pages if anyone can help?
Thanks
Hi Ciaran,
you can use Members in umbraco to protect certain pages.
Here you can find some informations about members:
https://our.umbraco.org/Documentation/Using-Umbraco/Backoffice-Overview/Members/index
Tutorial for creating protected member area:
http://siempresolutions.co.uk/blog/Umbraco_Members_Protected_Area_of_Website ;
Topic about member management:
http://24days.in/umbraco/2014/managing-members/
Maybe you can also block your packges from search engines with this great commercial package, instead using members:
http://soetemansoftware.nl/seo-checker/features ;
Hope this helps?
Best,
Sören
A quick and easy way is to inject a <meta name="robots" content="noindex"> tag into the <head> tag of your page. For extra points you can make this optional in your doctype with a checkbox or similar.
More info on the tag: https://support.google.com/webmasters/answer/93710?hl=en
Basic template editing stuff should allow you to get this working.
For password protection see Sören for more links.
Cheers
Pete
Hi Peter,
of course this is the easiest and fastest way! Great :)
Sören
Hi Ciaran
You can use the
<meta name="robots" content="noindex, nofollow">
tag to achieve this. You can for instance make a "Hide from search engines" checkbox on your "SEO" tab and if it's checked then render this line on the page - You can read more this meta tag here http://www.robotstxt.org/meta.htmlBut if you're thinking about making a password protected area on your website then it will not be indexed anyway (The login screen can be) since the pages are not reachable for the search engines since they do not have a login.
In regards to password protection you can read more about it here http://siempresolutions.co.uk/blog/UmbracoMembersProtectedAreaof_Website - In short you can right click a node and setup "public access", which can be either "Single user protection" or "Role based protection". Single user protection allows you to quickly allow access for a certain member/user on the fly providing email and password for one person directly on the node - The most common approach is to set role based protection, which is based on the member groups created in the "Members" section.
That way you can have a password restricted area on your website, which will require members to logon to gain access to the content. The public access settings will be inherited from parent to children all the way down to the last level of children.
In your code you'll then need to check if a certain member has access to the nodes - This is also illustrated in the article I referenced.
Hope this helps.
/Jan
Damn I'm slow...just hit "post" and then Pete and Sören have already made nice answers for you :D
/Jan
@Jan you covered the best of both answers though :)
@Jan you have completed both very well :)
This is great, thanks for the help guys :)
Ciaran
is working on a reply...