sitemap redirect to wp-sitemap

Hi @bpkbku,

Yoast SEO is expected to automatically turn off the default XML sitemap wp-sitemap.xml in WordPress and redirect to the Yoast Sitemap sitemap_index.xml. When you say sitemap.xml redirect to wp-sitemap.xml, we assume it’s being added by the different plugin, probably JetPack. If so, can you confirm if there’s any other plugin that adds the sitemap?

thanks for reply, i am not have another plugin, installed plugin it’s
Yoast
Litespeed cache
CF7
i’ve purge all cache and turn off all plugin but i got sitemap.xml still redirect to wp-sitemap.xml for no error like i said in first post.

googling done, and i got this, maybe the problem it’s in wp core?
https://github.com/GoogleChromeLabs/wp-sitemaps/pull/149

Hi,

WordPress creates its own sitemap at wp-sitemap.xml. If you have enabled the Yoast sitemap we would expect them to redirect both sitemap.xml and wp-sitemap.xml to the Yoast sitemap: sitemap_index.xml.

We are not sure why sitemap.xml is redirecting to wp-sitemap.xml. We would expect both to be redirected to Yoast’s sitemap.

If you were to briefly deactivate Yoast does sitemap.xml still redirect to wp-sitemap.xml?

Thank’s for reply,

i expect what you expect that if i enabled yoast, default wordpress sitemap it’s going redirect to sitemap_index.xml but for now after i updated to 5.5 it’s going wrong.

if i deactive yoast sitemap still redirect to wp-sitemap.xml with a normal sitemap page, but if i actived yoast, sitemap.xml still redirect to wp-sitemap.xml with 403 page

i don’t know what it’s wrong, i’ve rewrite 301 htaccess sitemap.xml>sitemap_index.xml but it’s not working.

Hi @bpkbku,

Thank you for your reply.

This sounds odd, is that is indeed not the default behavior. There should be no need to manually create a rewrite in your htaccess file.

If you disable Yoast SEO and visit /sitemap.xml, you get redirected to wp-sitemap.xml, as you said, right? If so, it would be nice to know what the Redirect-by header is from that redirect. You can find this information with a browser extension like Redirect Path or any other that shows all redirects for a pager. Please do test those out in a private window so you are sure you are not redirect by your browser cache.

thank’s for reply,

i’ve try to access with different browser but still redirect to wp-sitemap.xml

firefox 79
chrome 86
Microsoft edge

Respone Header:
HTTP/2 302 Found
x-powered-by: PHP/7.4.9
content-type: text/html; charset=UTF-8
x-redirect-by: WordPress
location: https://site.com/wp-sitemap.xml
x-litespeed-cache-control: no-cache
content-length: 0
date: Tue, 18 Aug 2020 13:45:43 GMT
server: LiteSpeed

@bpkbku Would you please be able to provide the exact URL of the sitemap so that we can check into this further? If you don’t want to provide the URL in a text/link format in your reply you can also take a screenshot of the URL, upload the image to an image sharing site such as Imgbb, Imgur, or something similar, and then post a link to the uploaded image in your reply.

i am going to access sitemap.xml then here the respon:

With yoast actived i got redirect to wp-sitemap.xml with 404 respone:
https://ibb.co/vxFygqF

with yoast unactive i got redirect to wp-sitemap.xml with normal respone that contain my blog list:
https://ibb.co/7jxLS2r

@bpkbku Thanks for proving the screenshots, however, we were requesting the actual URL of the sitemap. We were asking for this so that we can check the headers of the URLs and redirects to try to ascertain where the redirects are originating from (WordPress itself, Yoast SEO, or another plugin/theme).

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.

@devnihil I’m running into this exact same issue today. I’ve even gone ahead and changed the robots.txt file to point directly to the Yoast SEO generated XML sitemap.

Is there a way I can share a link to you in private? Given the customer and visiblity it would be ideal if we can share this information in private.

I have all the details of what we are running into.

I’ve same issue