I've been working on my first Umbraco website which has to replace an old website that ranks quite well.
I have made my way through the various duplicate content issues Umbraco has, .aspx & clean urls, non www/www and what not using URL rewrite in IIS. Ok, so nothing surprising there but my latest discovery has really confused me.
Looking at the source there isn't any extra code injected into these preview pages to block bots, so has Umbraco got it's preview pages available to the public without any bot blocking code?
Is there any way to inject <meta name="robots" content="noindex"> for pages being accessed via their node id?
This content you see is from the published version of the document, not the content you will see in preview mode. Preview mode content is only visible when logged in as an Umbraco user.Test it by modifying something in the back-end, hit save without publish then logout and open the page based on its document id you will see the published version.
Don't know if you can block based on url but there is always a canonical you can specify.
SEO & Umbraco Preview Pages
I've been working on my first Umbraco website which has to replace an old website that ranks quite well.
I have made my way through the various duplicate content issues Umbraco has, .aspx & clean urls, non www/www and what not using URL rewrite in IIS. Ok, so nothing surprising there but my latest discovery has really confused me.
http://mywebsite/somepage can also be accessed using http://mywebsite/nodeid.aspx
Looking at the source there isn't any extra code injected into these preview pages to block bots, so has Umbraco got it's preview pages available to the public without any bot blocking code?
Is there any way to inject <meta name="robots" content="noindex"> for pages being accessed via their node id?
Hi alan,
This content you see is from the published version of the document, not the content you will see in preview mode. Preview mode content is only visible when logged in as an Umbraco user.Test it by modifying something in the back-end, hit save without publish then logout and open the page based on its document id you will see the published version.
Don't know if you can block based on url but there is always a canonical you can specify.
Cheers,
Richard
Hi Richard,
Using the canonical URL is the perfect solution, also thanks for clarifying the difference between the published & preview content.
- Alan
is working on a reply...