Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should priority “not indexed” set a noindex meta tag? #118

Open
kinglozzer opened this issue Feb 6, 2017 · 3 comments

Comments

@kinglozzer
Copy link
Contributor

@kinglozzer kinglozzer commented Feb 6, 2017

We’ve had a few clients set a page to “not indexed”, only to find their page has still been indexed (either because it was indexed before they set “not indexed”, or because there are links pointing to it from other pages that are indexed). It’s excluded from the sitemap, but may still be crawled if it’s discovered another way.

IMO it makes sense to set <meta name="robots" content="noindex"> on these pages too. It’s arguably outside of the remit of a “sitemap” module, but I think it’s the expected behaviour of that dropdown.

@dhensby

This comment has been minimized.

Copy link
Collaborator

@dhensby dhensby commented Feb 6, 2017

I'd have thought it was outside the scope of this module - you could write a plugin to do that?

Perhaps better to rephrase the option from "not indexed" to "unlisted"?

@kinglozzer

This comment has been minimized.

Copy link
Contributor Author

@kinglozzer kinglozzer commented Feb 6, 2017

I think both are equally misleading to CMS users, maybe “Not included in sitemap” instead?

@dhensby

This comment has been minimized.

Copy link
Collaborator

@dhensby dhensby commented Feb 6, 2017

Sure

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.