Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
It's not possible to exlucde individual users from the sitemap.
The setting reverts to the default when the user is saved.
It might be related to:
http://drupal.org/node/708078
Comments
Comment #1
Daniel Schaefer CreditAttribution: Daniel Schaefer commentedI can confirm the isssue. I can either completely enable or disable users in the module configuration panel. There is no control over single users. I can set the user on no-index and it shows under the configuration, however the user is still indexed in the sitemap.
This is a serious problem for me. I'm not sure if might it be kernel-related, though. However, a possible fix would be to provide another tab (other than "Include manually") where I can manually EXCLUDE URLs from the sitemap. There is no way for my site to do it the other way round. (Purpose is only to completely exclude the administrators)
Anyone has a solution/workaround? Help is much appreciated.
Comment #2
Daniel Schaefer CreditAttribution: Daniel Schaefer commentedI can confirm the issue. I can either completely enable or disable users in the module configuration panel. There is no control over single users. I can set the user on no-index and it shows under the configuration, however the user is still indexed in the sitemap.
This is a serious problem for me. I'm not sure if might it be kernel-related, though. However, a possible fix would be to provide another tab (other than "Include manually") where I can manually EXCLUDE URLs from the sitemap. There is no way for my site to do it the other way round. (Purpose is only to completely exclude the administrators)
Anyone has a solution/workaround? Help is much appreciated.
Comment #3
Daniel Schaefer CreditAttribution: Daniel Schaefer commentedAny update?
Comment #4
Anonymous (not verified) CreditAttribution: Anonymous commentedSorry, I have not looked at the _user.module, nor do I use it.
Comment #5
Daniel Schaefer CreditAttribution: Daniel Schaefer commentedThe exclusion of single URLs/user accounts still doesn't work... any workaround suggested?
Comment #6
Anonymous (not verified) CreditAttribution: Anonymous commentedI still haven't had time to look at the code. Maybe Dave Reid can chime in.
Comment #7
Daniel Schaefer CreditAttribution: Daniel Schaefer commentedplease.. This is bothering my client, he puts a lot of effort into SEO. help is appreciated.
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous commented@dsjena: Do you really need the xmlsitemap_user module enabled? I'll see if I can get some time this weekend but don't count on it.
Comment #9
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #10
Anonymous (not verified) CreditAttribution: Anonymous commentedSee also #708078: user submodule is borked.
Comment #11
Daniel Schaefer CreditAttribution: Daniel Schaefer commentedIt's a catalogue for consultants, where clients can register. I set up the consultant's pages using the User module so the user/... pages are the actual listings (consultant/...). Problem is that some accounts would have to be excluded from the sitemap (e.g. the admin accounts). I set up a 301 redirect for now, but the client doesn't like it because the accounts are still listed in the Sitemap and therefore cause warnings in the Google dashboard.. The client puts a lot of effort into SEO.
I checked the other thread but couldn't see any updates. Can you tell me if there is a solution already?
THANKS!
Comment #12
Anonymous (not verified) CreditAttribution: Anonymous commentedMaybe use Views module to create a custom access and stop using xmlsitemap_user module. Or supply a fix for this issue.
Dave, do you have a suggestion?
Comment #13
Daniel Schaefer CreditAttribution: Daniel Schaefer commentedThanks!
How could I include the user accounts (= business pages, very important for SEO) into the sitemap then without the sub-module, one by one adding custom paths?
If I can take some time off my schedule, I will try to look into the module myself. Maybe the issue sits "deeper", but for me it's really just this issue of not respecting the custom setting.