Ability to exclude individual entries/elements from sitemap about craft-seomatic

[khalwat]

So for me this ties into the Field discussion:

#14

...because if I implement an SEOmatic Field, then you could set any of the settings on a per-entry basis (including the Sitemap settings).

[bwlng]

I could get behind the field for this purpose, but it would also be nice to be able to “pull” from a field or override it in templates the way you can the content fields. In the event a page should be “private” it’d be a bummer if the client toggled the lightswitch to mark it private but Google was notified of its existence via the sitemap because they forget to change the sitemap setting and/or robots setting via the field.

With an override/mapping I could handle the intent for them to make it foolproof.

[khalwat]

Well, just not being in the sitemap doesn't mean anything really; the sitemap is just a way to make sure that Google finds the links you want it to find. It actually does a pretty good job indexing content just by spidering your site.

So what you really want is a way to ensure that the Robots header and tag (which Google does respect) are set properly for the entry you want excluded.

[bwlng]

I also wouldn’t want to aid a human who might be digging through the sitemap for some reason. It might not be super sensitive content, but the type of content that only targets certain visitors (landing pages with special offers, for example, that are still part of the Pages structure within the CMS)

[khalwat]

In fact... I'm gonna even go so far as to say that if you'll be toggling on/off the external access to some URIs, then you could make a case that you want it to be in the Sitemap. Why?

Consider... you have a URL that gets indexed by Google. Client now doesn't want it indexed, or made a mistake and it never should have been indexed.

If you remove it from the sitemap & adjust the Robots tag, Google isn't going to re-crawl it for some time.

If you keep it in the sitemap & adjust the Robots tag, now the sitemap says "hey Google, you need to index me, I changed!" and it comes in, sees that it shouldn't be in the index, and removes it.

:)

I get your scenario too, and understand what you mean. I'll do what I can!

[bwlng]

Thanks! It's probably an edge case, but I'll take what I can get ;)

[khalwat]

This is implemented as part of the Field #14