7880 Posts in 2037 Topics by 1136 members
Jump to:If this is your first visit, you will need to register before you can post. However, you can browse all messages below.
| Page: 1 | go to end | Reply | |
| Author | Topic: Exclude pages from sitemap. | 39689 views |

6 May 2008 at 9:26pm
Hi,
how do I exclude certain pages or folders from the sitemap (generated as in tutorial #6). For example, I have a site recently built at http://gvac2.web.pin.se, which uses a folder named "banners" to display the 4 banners at the frontpage. I don't want those to be shown in the sitemap (http://gvac2.web.pin.se/site-map), but I don't know how to exclude them. Any ideas?
/jens
Last edited: 6 May 2008 at 9:26pm

7 May 2008 at 12:55am
I think you can in the Page Register Behavior clicking and remark "In the search ads?" and View in Menus then these files also disabled for sitemap?
I'm not shure, because i think so !!!
Stooni----------------

7 May 2008 at 1:09am
I have already deselected both "Show in menus" and "Show in search" on each file and the folder the files are placed in, but they still show up in the sitemap.

7 May 2008 at 4:46am
The newer versions of SS come with a sitemap feature built in, so you don't have to use the tutorial any more.
There is a bug with the feature to exclude certain pages from the sitemap. It isn't working correctly as even if you specifically select "not indexed" under the meta-data -> advanced options, it still shows up.
There is a ticket in the trac for milestone 2.2.3

7 May 2008 at 5:02am
The site is built on SS 2.2.1, is the "not indexed" functionality in 2.2.2? Anyway, since you say it's not working, and there's a ticket in the trac, I guess I'll just have to wait for the next release. Not a big issue. Thanks for the help!
Last edited: 7 May 2008 at 5:02am

7 May 2008 at 8:57am
I think there is even the built in sitemap with 2.2.1, so you could use that by default and clean up some extra code.
However, the not indexed function doesn't work. I was the one who opened the ticket cause I ran into the same problem as you. I was hoping it would be fixed by 2.2.2 final, but they moved it to 2.3. I made a mistake in my first post about thinking it was set to 2.2.3.
| 39689 views | |||
| go to top | Reply |