Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Search Console Errors 400 and 405
-
Hi,
Does anyone know if search console errors showing as follows are damaging to serps:
/xmlrpc.php is returning 405 error
/wp-admin/admin-ajax.php is returning 400 error
These errors seem to of coincided almost to the day that there was a ranking drop for the primary keyword from mid page 1 to bottom of page 2.
No matter what I do I cannot seem to correct these errors.
Any advice would be greatly appreciated.
Thanks
-
Both issues are on ALL WordPress sites.
xmlrpc.php return 405 because it's work under HTTP POST but bot crawl under HTTP GET.
And error 405 mean switch from GET to POST. But bot can't do that.admin-ajax.php return 400 because it's not designed for direct use. You must make call with some parameter and it will return some information.
But as name says - it's responsible for AJAX calls and it's not for direct use that's why it return 400 when it's called w/o parameters.So - that issues are not related to your issue.
For example mine WP sites also return same error codes to the bot.Peter
-
To answer your question: "Does anyone know if search console errors showing as follows are damaging to SERPS." - No, this would almost be impossible. The errors that you're mentioning are just two core pages of WordPress that cause some errors where the 400 error is actually supposed to happen as it's not a URL that is just accessible like this. It's a file that is being used to make AJAX requests.
The fact that this potentially coincides with a uplift/drop in rankings is probably caused by something else.
-
Hello there,
Both of this error can be caused by either a corrupted file, which you can download a new one from WordPress and see if this fix the problem.
If not I would suggest you start by turning off all your plugin one by one and see if there's some plugin that caused the conflict.
Hope this helps.
Joseph Yap
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Explore more categories
-
Chat with the community about the Moz tools.
-
Discuss the SEO process with fellow marketers
-
Discuss industry events, jobs, and news!
-
Chat about tactics outside of SEO
-
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
-