Our clients website recently had the paid version of the extension installed and configured by the developer. While the URLs are now SEF, we are seeing some strange redirects occurring and need them fixed ASAP.

JoomSEF 3.7.6

The problem:
The new SEF URLs are initially posting an HTTP Status Code of "303 See Other", while referencing the original non-SEF URL for the given page. When that non-SEF URL is accessed, the HTTP Status Code is a "301 Permanent Redirect" that then goes to the SEF version of the page (the correct page).

Here is an example page:
www.divasbrastraps.com/clear-collection/...tte-straps-sku-dc086

Plug that URL into Rex Swain's HTTP tool: www.rexswain.com/httpview.html

I have checked the FAQ and some other forum posts and it looks like this 303 redirect was supposed to have been fixed last year. For whatever reason, its still occurring here on this website.

These 303 redirects are hurting the website right now in the search engines so it's important that we're able to get these corrected quickly.

Where is the 303 being commanded? How do we get this to use the 301 redirect?

Please help.

Thanks,
Cory

Still trying to find out how to fix the 303 redirect status...

Admin? Moderators? Anyone?

Since I upgraded early on this year, I have been getting the same error.

HTTP Error: 303

URLs not followed
When we tested a sample of URLs from your Sitemap, we found that some URLs redirect to other locations. We recommend that your Sitemap contain URLs that point to the final destination (the redirect target) instead of redirecting to another URL.

Any ideas or help please.

Thank you
Glenn

I've got the same problem whith the paid version of JoomSEF. Google says there is HTTP Error: 303 in my sitemap.
Has somebody found the solution?

Thank you

Hello,

I am not sure if this redirect has anything in common with JoomSEF. I have checked its code and there is no 303 redirect initiated by JoomSEF. It only uses 301 redirects.

Are there possibly any other components, plugins or external tools that might be responsible for the 303 installed?

I've also got this error with Google Sitemaps, Do we have a fix?