We have detected that the root domain is not a live URL.
-
I'm trying to add a URL that is having some obvious issues so I can further investigate. When trying to add this site to a campaign in SEOmoz i get the following:
Roger has detected a problem:
We have detected that the root domain theurbandater.com is not a live URL. Using this domain, we will be unable to crawl your site or present accurate SERP information.
==
What does that error mean? Where should I be looking to begin troubleshooting?
The initial issue was that back on 9/1 according to Google Webmaster Tools this site began getting a high number of 500 erros and that number continued to rise up to 3200 of the same type of error. So something screwy is going on and I'm not sure where to start looking.
-
REALLY pleased to hear this functionality is in the works, Keri. It's something I have felt was sorely missing here on SEOMoz.
I just tried this process manually with a number of questions I had contributed answers to that still remained unmarked and unclosed. Didn't have much luck, probably for just the reason you mention-no longer members.
Paul
-
Hi Paul,
Thanks for following up! The OP is no longer a PRO member, so there won't be a response from them. We're working on some upgrades that will automatically send a reminder note like this to the OP after a week or two, encouraging them to mark a good answer or write more about their question.
-
Did you get this issue resolved, Alex?
If so and you found my answer helpful, could you mark it as a "Good Answer" and mark the overall question as answered? This will help other users who may come across the question in the future.
And if you haven't' been able to resolve the issue, just post a followup here with whatever further info you have and we'll try to help!
Thanks!
Paul
-
If you've been getting that many 500 errors, it's possible that when Roger tried to access the URL to start the campaign, he got a 500 error as well.
500 errors are server errors, which means something is wrong with the server or software configuration of your website. You're going to need someone with technical expertise to analyse and assess your site's server and software error logs to get to the bottom of why your site's pages are failing to load. Usually this would be your hosting provider.
You need to get this solved ASAP, as not only will search rankings be hurt, but your users are unable to reach your website's pages an awful lot of the time. There's no point in putting effort into SEO until the site is reliable.
You can set up Pingdom's monitoring tool to get a clear idea of exactly how often your site is erroring out. Their free account would at least allow you to monitor your home page for outages. (Make sure you set it up to monitor for a particular word or phrase on the page, that way you'll get the best info on when your page is not fully responding properly.)
Paul
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
-
Redirecting one domain to another using utm tags
I have two live websites, which have both been live for over 10 years, so we have plenty of backlinks to both...domain1.com & domain2.com. Domain 1 and all urls is being merged into domain2.com. So 301 redirects will be setup for every page of the site....domain1.com/abc-1234/ to > domain2.com/abc-1234/ In Google analytics for domain2.com we want to be able to see which visits we have received as a result of a redirect from domain1.com. It is possible to see these visits that come in via organic, referrals and social etc, as those will come to us with the referral as domain1.com. However, with direct traffic, i.e. if someone types domain1.com into their search bar, these visits will be assigned as direct and we are not able to tell in GA if those users have typed in domain2.com, or domain1.com to get to our webpage. There are some suggestions in forums of adding utm_source tracking to all redirects (and add canonicals to those urls pointing to the non utm_source version), but my concern is that Google is going to have to go through one extra step to reach the page on the redirected domain. So without the utm source code Google will follow this route
Reporting & Analytics | | Sayers
domain1.com/123/ to domain2.com/123/ With the utm source code Google will follow this route
domain.com/123/ to domain2.com/123/?utm_source... then see's canonical, so moves to domain2.com/123/ So essentially I am giving Google one extra step to follow before it gets to the equivalent page on the new site. Is this an issue, and/or are there any other ways to track this redirection without adding extra parameters to the url?0 -
Question on structuring URLs in a Drupal CMS - Adverse SEO or Analytics impacts?
Hello Moz Community, We're building out a health system (think a bunch of hospitals and clinics etc.) website on Drupal for the first time. Nebraskamed.com is our domain. Because we're using nodes instead of pages, our URL structure can pretty much be whatever we think makes sense. Our proposal is to drop /blog/ and related terms from the URL structure, because it doesn't really mean anything to the user. Instead, we'd use the service line "cancer" for example, followed by the name of the blog post or document. Example: nebraskamed.com/cancer/10-bone-cancer-myths Do you see any red flags (perhaps with SEO or Analytics for example) to what I'm proposing? domain name/service line/blog-post-name If so, do you have a URL structure you advise?
Reporting & Analytics | | Patrick_at_Nebraska_Medicine1 -
Weird URL Structure in GA
Hey everyone, Thanks in advance for any insight on this. I've been researching it quite a bit on Google and haven't found anything yet. In Analytics, under our pages report, we're getting a lot of pages that look like this: www.execucar.com/https://www.execucar.com or www.execucar.com/https://www.execucar.com/locations/orlando-car-service Any thoughts on how to fix this? These pages don't exist...I'm at such a loss.
Reporting & Analytics | | SuperShuttle0 -
How to get multiple pages to appear under main url in search - photo attached
How do you get a site to have an organized site map under the main url when it is searched as in the example photo? SIte-map.png
Reporting & Analytics | | marketingmediamanagement0 -
Large event site - how should I structure my URLs?
Hi guys, I'm working on a new website which is consolidating a number of existing event sites into one. The existing sites use a variety of URL structures: www.eventsite1.com/events/event-name www.eventsite2.com/festival-program/event-name www.eventsite3.com/event-name This inconsistency has led to issues with tracking category usage properly in analytics - for instance, with eventsite3.com, events fall within categories (www.eventsite3.com/category-name) but as soon as you drill into an event detail page (www.eventsite3.com/event-name) from the category page, the category is lost to analytics. This is compounded when one event lives within multiple categories, as I can't figure out which category is the most effective for a particular event. I've seen other event sites establish a canonical URL for a primary category, display it in the URL (i.e. www.eventsite4.com/primary-category/event-name) yet still let that event get hit via the secondary categories (www.eventsite4.com/secondary-category/event-name). This way, the categories get passed to analytics without any duplicate content issues (i.e. via the setting of canonicals) Basically, I want to make sure that whatever instruction I give to the devs for the new site re: URL structure is correct from an SEO perspective and analytics perspective. Do I even need to worry about having the category in the URL? Can someone please help me with this? Hope this makes sense Cheers
Reporting & Analytics | | cos20300 -
Analytics not tracking traffic from Old Domain Redirect
We've recently 301 redirected one of our client's domains to their new website and the strange thing is, we aren't seeing an increase in traffic in analytics. You would expect the traffic to increase roughly by the traffic volume from the old domain. There were a few hundred redirects and we tested a large sample and the redirects have been implemented properly. Is there something that we did incorrectly in our implementation of the domain redirect? Or is there something else that we need to do in Analytics to properly track those redirects?
Reporting & Analytics | | ATMOSMarketing560 -
Yikes..what is this? "We have detected that the root domain xxxxxx.com does not repsond to web requests"!!!
Can anyone tell me what this means? "We have detected that the root domain xxxxxx.com does not repsond to web requests. Using this domain, we will be unable to crawl your site or present accurate SERP information"
Reporting & Analytics | | MannixSEO0 -
Ecommerce tracking problem with multiple domains on 1 web property
We recently launched 13 product marketing sites based on a Wordpress Multisite setup. To track all 13 sites we decided to use one web property, so we can use the same tracking code for all domains. To track the sites seperately, we set up a profile for each product site with a hostname filter. This works well for most stats, but eCommerce tracking is where the problem starts. Per profile we obviously want to track the products purchases on that website only. What happens now is that all purchases from all product sites are tracked on all profiles. How can we change this? Should I alter the eCommerce tracking code or can I fix this with an additional filter per profile? Thanks for your help Mozzers! Regards, Pieter van Diggele
Reporting & Analytics | | RBO
Online Marketing Executive
Elsevier Opleidingen0