Ww.domain.com coming up with error
-
our domain is showing in moz with the following error in crawl reports
Crawl Error
We were unable to access your homepage, which prevented us from crawling the rest of your site. It is likely that other browsers as well as search engines may encounter this problem and abort their sessions. This could be a temporary outage, but we recommend making sure your network and server are working correctly.
note that the url being displayed is ww.domain.com and not www.domain.com . we do not have a 301 in place, we have switched off wildcard forwarding from the server..
its acting as the url is a subdomain that is not working.. should i just ignore it?
-
hi sorry for late reply,
yes its working elsewhere whcih is strange.. its also working here but gives this extra message about this subdomain we dont have and is not active
thanks again
-
Hi there
Can you provide a URL? One thing I would do is check your Robots.txt & meta robots and make sure everything there is fine. I would also go through your account in Moz and make sure that you properly set up the campaign and that you don't have a typo somewhere or clicked something that would cause your URL to be crawled the way it is by Moz. I would also take a look at your internal links and see if something could be wrong there.
Have you tried crawling it with ScreamingFrog or any other crawler services? Have you seen any other errors elsewhere?
Let me know, good luck!
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Domain Analysis Limit
Hello, even though we are a Moz Pro user we have a 'part-timer' who keeps the client metrics scoreboard up to date. Rather than have him running wild in Moz Pro we bookmarked the 'Domain Analysis' page and he knows that only 3 can be reported on per day. If it was an immediate need then we would use Moz-Pro. The issue was reported to me that he is receiving 'Search Limit reached' and do a moz-pro trial. So, has the 3 per day limit been changed? Thanks, Dave
Moz Bar | | 7thPowerInc0 -
I have too many tittle tag issue for my site on moz site crawl error
I have too many tittle tag issue in site crawl error but when I checked manually for the error there is no title in source code. Please Help me to understand
Moz Bar | | Nileshaggarwal0 -
Why My Website DA decreased as the no of domain catches in google webmaster?
My Website is www.naturesouq.com and its domain authority not increased till the last 5 months and SEO possessed on it in regular interval and all the things going well . More than 150 domain pointing to the website but the website DA is being Decreased from 9.6 to 6. Why this is happend? What i have to do to improve my site performance and dercrease the spam score. Please help me. .
Moz Bar | | seohomemarket210 -
Rogerbot will not crawl my site! Site URL is https but keep getting and error that homepage (http) can not be accessed. I set up a second campaign to alter the target url to the newer https version but still getting the same error! What can I do?
Site URL is https but keep getting and error that homepage (http://www.flogas.co.uk/) can not be accessed. I set up a second campaign to alter the target url to the newer https://www.flogas.co.uk/ version but still getting the same error! What can I do? I want to use Moz for everything rather than continuing to use a separate auditing tool!
Moz Bar | | digitalascend0 -
804 : HTTPS (SSL) Error in Crawl Test
So I am getting this 804 Error but I have checked our Security Certificate and it looks to be just fine. In fact we have another 156 days before renewal on it. We did have some issues with this a couple months ago but it has been fixed. Now, there is a 301 from http to https and I did not start the crawl on https so I am curious if that is the issue? Just wanted to know if anybody else has seen this and if you were able to remedy it? Thanks,
Moz Bar | | DRSearchEngOpt
Chris Birkholm0 -
SEO MOZ ERROR
Hello moz comunity, I tried to use the moz keyword difficulty service in the last 2 days and I get this error over and over again... see photo: http://www.evernote.com/shard/s238/sh/5775a179-1be7-4e76-8563-cf087c37cf2b/576bda1a72f446a8806a0f1914193829 Oops Gosh! It looks like something has gone a bit wrong. Don't worry though, we know and are fixing it. How Can I solve this? I need to check a lot of keywords for my websites. Any alternatives? Thank you !!!
Moz Bar | | Sebastyan220 -
Moz is reporting a broken link error but GWT is not
My latest Moz report is showing a 404 for: http://www.fateyes.com/how-will-googles-hummingbird-affect-your-search-ranking/”ht
Moz Bar | | gfiedel
(and showing the link this way with the characters after the last / which are not part of the page URL) Google Webmaster Tools says we have no errors. I'm wondering why there is this descrepancy and I'm wondering how I can track down where this link is originating from on our site. I've tried downloading screamingfrog and deeptrawl to no avail (java issues). I've also tried a couple of services online and installed Broken Link Checker plugin with no luck finding it. Any suggestions? Thanks in advance!0 -
Link Metrics API: sort by domain authority not working?
I’m trying to make calls to the Link Metrics API (via the Linkscape gem); queries that set sorting to :page_authority work, but queries that set it to :domain_authority return Unrecognized API method: 'links/page_to_domain.domain_authority' Unrecognized API method: 'links/page_to_page.domain_authority' Meanwhile, Open Site Explorer happily sorts by domain authority. How should I query the Link Metrics API to get results sorted by domain authority?
Moz Bar | | ginzametrics1