Page > advanced settings enhancements

[lsrtdavis]

1. allow for the choice of a 301 redirect. currently it redirects with a 302.
2. Check box to add meta robots "noindex"

[FinalAngel]

Has been enhanced in 3.2

[HenryMehta]

Is part 2 (meta robots noindex) of this issue delivered? And if so, how do I find it because I cannot see a it on the admin screens and I cannot find it in the documentation

[fsbraun]

@HenryMehta To add meta tags to sites please use djangocms-page-meta.

[HenryMehta]

@fsbraun I am trying to implement using djangocms-page-meta but I don't understand how I would set DjangoCMS pages to be noindex

[benzkji]

How can I achieve point 1? I dont see any 301 checkbox anywhere?

[fsbraun]

@benzkji No, a 301 redirect is not available out of the box for the django CMS UI.

I'd suggest using the django.contrib.redirect app (see docs here). It issues a permanent redirect (301) by default.

The idea is that you just keep a list of URLs to redirect and need not have stub pages cluttering the page tree.

[benzkji]

Thanks for clarifying. We've removed the parent, and will add a "manual url" to the previous child page. We already use a redirects app, but if the parent page is a status code 200, that doesnt help much. I know many cases where a page serves as parent, but doesnt have it's own content... no cluttering there, normally.

Why not change it to a 301? It is an intended redirect, so, worth a real 301, no? It's just the SEO guys lurking around the corner...

[fsbraun]

Well, 301 is irreversible. But I see your use case. It might be a nice PR for v4... What do you think?

[benzkji]

Well, some SEO specialist might be needed to tell if it really always could be a 301. But as far as I can see, Search Engines come back to check 301s from time to time...so...it would recognize the removed redirect. Or at least if the page has again links to that page, it would get crawled and indexed again.

Yes, a PR. :-)