Moz not recognising url to setup a new account
-
I am attempting to setup a new account for my client but Moz is having a problem and not registering the url http://www.esc.uk.net/. I get the "oops" message & read the info on the FAQ page it refers to.
Why do I keep getting an "Oops" message when I type and submit my campaign URL?
To create a campaign, we need to receive a valid HTTP response from the web server hosting your site. While the site may be accessible from a standard web browser, other user-agents and search engine bots may receive a different response. If you receive this error, we recommend running a test by sending an HTTP response using any online HTTP tool.
Using an online HTTP tool I believe I received an HTTP response. What else can I do?
Regards
Terry
-
Hey Terry,
I know we talked in a private email about this temporary bug, but I just wanted to reply here so the post in the Q&A forum doesn't remain unanswered. I know you were able to get the campaign set up already, but please do let me know if you need help with anything else.
-
I am having the same problem, and it has persisted for several weeks. I am trying to set up a campaign and am getting the "Oops" message.
I have used Hurl.it to test a GET and a HEAD request; in both cases the site returns a 301 Moved Permanently response (which is correct, the url redirects to a subdomain).
Any suggestions on what else I can try? The url in question is http://texas-cash-out.com.
-
Hey Kimberly, thanks for writing in.
When I use the Hurl.it tool, I'm actually seeing a 500 internal server error from the site: http://www.screencast.com/t/q8ztS92saho, but that doesn't seem to be the main issue that is causing the error for our tools.
When I curl the site as Rogerbot, I get a 403 Forbidden error for our crawler: http://www.screencast.com/t/x6hfVJj85I. Unfortunately, this means that your server is specifically blocking Rogerbot from accessing the site, so you would need to work with your webmaster to white-list our crawler in order to create a campaign for your site.
Once we are allowed access to the site, the 500 internal server error would also become an issue, so I would have the webmaster for the site look into that, as well.
I hope this helps!