Hi, if i set “split by year” or “split by month” in plugin setting the sitemaps generated for specific year or month are not available because as response i receive a 301 – Moved Permanetly to the Home Page.
Otherwise main sitemap and page sitemap works well.
That is strange… Do you have some custom .htaccess rules that could be triggered by the use of year and month number in the URL of these sitemaps?
Can you share a link to your site with the ‘split by’ option set so I can verify the response headers for these redirects?
No, no special .htaccess, there are only directive from WP Super Cache and WordPress.
Here the link to my website with splitted sitemap:
Give me a feedback when you have visioned the problem, because i have to set a valid sitemap as soon as possible (the site is a local news magazine). . .
Do you need also .htaccess dump ???
OK, thanks you can reset the config to the unsplit post sitemap. There are three things that intrigue me:
1. You are using WP Super Cache but the usual WP Super Cache timestamps (and other remarks) at the end of the source are not there. They are visible in your normal pages sources but not the sitemaps. But then again, neither are they showing in your RSS feeds. What configuration of WP Super Cache are you using? It might be helpful when sitemaps (and other feeds) are treated by WP Super Cache…
2. Your server is equiped with Plesk and I notice it appends some response headers of it’s own. I wonder if any config in Plesk might be adding the redirect response header…
3. I see you are using a custom Permalink structure /%post_id%/%postname%/ and I suspect this might be the cause. I’m not going to ask you to change that even for a brief moment, so I’ll do some tests on my production server and will let you know if I can reproduce the redirect.
In any case, thanks for reporting the issue and your cooperation 🙂
Thank you for investigation.
1 – Yes i am using WP Super Cache but not with:
It’s better to cache sitemaps?
2 – No i dont think is Plesk, i have not done any particular
configuration on it
3 – Yes may be, thanks a lot!
Hmmm, I cannot reproduce this 🙁 With both WP Super Cache installed and Permalinks set to /%post_id%/%postname%/ the split by year and month sitemaps work fine on my test server…
About not caching archives and feeds, I suppose on a small site it’s no problem but on larger sites, you might benefit from allowing WP Super Cache to cache them too. Feeds (at least, but maybe archive pages and even searches too) get cleared upon each new publication so there is no danger 🙂
I have to resolve the problem since there are about 15/20 new post every day and the sitemap grow fast.
At the moment i have “hacked” the plugin because in the last release “split by year” is selected by default if there are more than 500 post (i’m over 700).
I will investigate furtheremore . . . any suggestion is apprecciated.
Thank’s a lot.
I see what you mean. Your sitemap will be growing fast and you’ll be running into trouble soon if you cannot split it… Can you mail me the .htaccess rules via http://status301.net/contact-en/ and tell me what other plugins are running on your site?
For what it’s worth, I don’t think it is related to my plugin because I cannot even pull a yearly archive on you regular site using the URL parameter ‘m’ like http://www.informaresicilia.it/?m=2013 gets redirected to the main site too…
What do you have as category and tag base in the Permalink settings?
Nothing. And “category” word erased by “SEO by Yoast” plugin configuration
…And “category” word erased by “SEO by Yoast” plugin configuration
Ah! That plugin is a likely source of the issue.
Now I don’t know Yoast’s SEO plugin but you can get rid of the category base by entering a dot (.) in that field on your Settings > Permalinks page. So there is no need for using that setting in the SEO plugin unless it is also doing something else meaningful.
But there probably is another configuration setting that is causing the redirects. Is there an option for disabling and/or redirecting date archives?
- The topic ‘301 redirect for splitted sitemaps’ is closed to new replies.