Serendipity Forums

Hi there,

(1) When CATEGORIES is selected to be in the sitemap those links look like
.../categories/5-cars
.../categories/6-bikes

Now when ARCHIVES is added to the selection. Those category links disappear and are substituted with category links per month.
E.g.
http://blog.fcon21.biz/archives/2007/12/C3.html "Marketing | Entries from December 2007"
http://blog.fcon21.biz/archives/2013/05/C3.html "Marketing | Entries from December 2013" (0 entries)

Since all categories are iterated for each month this are a lot of pages to index but most of them do not return actual posts. Most return 0 entries.
This makes it not a good idea to have it in the sitemap.

But I think the more useful entries, e.g. .../categories/5-cars, should not disappear when CATEGORIES and ARCHIVES are selected.

(I therefore have deselected archives to avoid the issue)


(2) The default sites to ping with the sitemap are Goolge and ask.com. As per my research aks.com doesn't accept those pings anymore. If so for fact, it's probably a good idea to remove this default item.

Update: I also found how to submit to bing.

http://www.google.com/webmasters/sitema ... itemap.xml
http://www.bing.com/webmaster/ping.aspx ... itemap.xml


Cheers.

_________________
I am running Serendipity 1.6.2 on PHP 5.3.14
Sitemap Generator (for Crawlers) aka serendipity_event_google_sitemap version: 0.58

It also seems that the plugin pings the configured search engines every time when a post is saved as draft.

Shouldn't it ping only when there is a change in the public content?
(I also have the mobile output plugin installed.)

Hi!

Yes, the reason behind this is it could be that an entry previously was saved as a published version and is only now saved as a draft. In that case, the entry needs to be removed from the sitemap, and thus it's recreated. It would be harder to implement code to distinguish this behaviour rather than simply re-executing the sitemap on either case...

Regards,
Garvin

garvinhicking wrote:... It would be harder to implement code to distinguish this behaviour rather than simply re-executing the sitemap on either case...

Understood.
Thanks for the reply.