There is a known issue that is affecting sitemaps for some accounts. The sitemaps should be available for accounts with 10 or more Hubs and questions, but in some cases the URL for the sitemap is returning a 404 code.
Our engineering team is aware of this issue and we are working on a resolution. We thank you for your patience.
I'm pleased I spotted this forum today. Last night on WMT I was thinking i'd have to create a new one because my sitemap couldn't be found. Had decided to leave it until today ... but now I'll just leave it.
Matt, If Google WMT can't see our sitemap, then how can Google be using it? I'm concerned about this. I just ran a sitemap test in my WMT and it reports "404 not found" detected on Oct 26, 2014 (today).
We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit.
Matt, Thanks for your reply, but if you read my last post you'll see that I already knew what you said. I know that search engines find the URL of the sitemap in the robots.txt file and they use that sitemap. But there are additional reasons why we all put the URL of the sitemap in our Webmaster Tools. The problem now is that neither Bing nor Google accept a sitemap that is not in our own directory. So we lose that feature of our webmaster tools. It's not a big loss, but some error reporting is now lost.
As you know, Hubpages supports allowing us to specify our webmaster tools for both Bing and Google. So I'm surprised that a decision was made to move the sitemaps into another domain, breaking the feature of Webmaster Tools support of it.
This is great news Matt. I'm glad you put our sitemaps back under our subdomains so we can specify them again in WMT. I just added mine back and it tested okay. Of course our hubs that are "Editor's Choice" are not in our personal sitemaps, but that has always been the case and I realize there is no solution to that since they are in the top domain. It was worth the wait.
Please note, however, that tonight there are a number of bugs appearing across HubPages. Since you say you deployed a fix, I wonder if that fix contained changes that brought on the following new bugs...
• The group maintenance page fails • Can't select sub tabs on stats in hubs • Some people are reporting failure to leave comments in hubs.
My WT is full of connectivity errors, such as site blocking google, 404 and 410 errors, and robots txt file errors. The dates are from August to September. Do you need screenshots, as I don't have much success? I will try if you need them.
Mine is still showing a 404 error. We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit.
I honestly don't know. I know that Google can crawl our sites without a sitemap if our hubs are indexed, which mine are, except one which isn't featured. I wonder why there have been so many glitches lately, it would be nice to have some kind of update regarding the site in general. I have my own opinions as to why traffic has slowed down, but until we know for sure, it's all speculation. Panda is a site wide penalty. Subdomains that are holding their own can be less affected, but I think with this last Panda we're seeing effects of a large volume of transferred content from a site that was heavy with affiliate based content. It may take a few months to see significant change. My opinion only, from someone who doesn't write online for a profession, but I read a lot to stay in touch with what's happening.
RebekahELLE Webmaster Tools cannot access the sitemap on mine, and two hubs cannot be found. I have 26 errors but, some may be questions that HubPages deleted for lack of traffic. I too read a lot, rebekahELLE and pay attention to hubbers with authority and the sites they mention. There are so many things in play here: moving the server, migration of new hubs and Panda. I know we are supposed to look at WT for penalties, and I have no penalties. Maybe we will hear more tomorrow. Good luck
Matt, please confirm: Are you saying we no longer have individual site maps in our subdomains? If so, please answer brakel2's question. For now, our Google Webmaster Tools will continue to report a problem.
The sitemaps were relocated to another domain during the server transfer, it would seem. Because Webmaster Tools requires the user submitted sitemap to be on the same domain, it can't be submitted to WT. Google can still locate it through the robots.txt file though. You still have a working sitemap, you just can't look at in your Webmaster Tools account.
That is the link Matthew Myer gave earlier that leads you to your robots.txt file. This tells search engines what they can and cannot index, and it can also be used to show search engines where your sitemap is located.
The previous sitemap address you have set up in Webmaster Tools shows a 404 error because it's on a different domain now. You can't set up the new sitemap in Webmaster Tools when it's not on the same domain as your account. Google can still use your sitemap; you just can't view it in Webmaster Tools at the moment.
I see where mine is also. It's on another domain now. No longer in our subdomain. So I had to delete the sitemap in my Google Webmaster Tools and Bing Webmaster Tools.
Both Google and Bing were reporting not found (404) errors. I know they will follow the link from robots.txt anyway. But we no longer can verify that the map is set up right. There was a time a year or two ago when HP messed it up and some of us discovered it only because we were using Webmaster Tools. So that ability to gone now. Anyway, Thanks, Maffew, for your input on this.
Yes, I've used that URL and all it brings up is a page of HP sites with this forum thread URL at the top of the page. What am I doing wrong? I seem to not have one. I've used various URL's trying to find it including WMT.
You're looking at your robots.txt file. That has disallows in it to avoid sections you don't want indexed. You'll see your two sitemap links at the top of the file. You have one for your hubs and one of your questions/answers.
But remember that you can't specify your sitemap this in your Webmaster Tools anymore. Both Google and Bing require it to be in our own subdomain. I just tried it with Bing tonight and they also will not accept it under hubimg.com, which is where the site maps are now since HubPages moved to a new server.
Don't worry about it though. All search engines find it via the robots.txt file.
That's an example of a possible use. You have more hubs than what Google has indexed, meaning some of them aren't indexed for some reason. Go to the 'fetch as Google' section, fetch your homepage, then submit for recrawl.
After a week, if there are still missing hubs, type in site:yoursubdomainaddress as a Google search, then you can see which are indexed, and thus work out what is still not indexed.
Now there are 74 indexed and 13 blocked by robots. My first site search showed a couple of my hubs and then a ton of outside sites that apparently have my site link on them. One was a collection of sports games (gambling?) that blocks my entry. Can anyone get into these and tell me what they are and what my hub is doing there? Because that hub is hardly ever read:
Still getting this... "We encountered an error while trying to access your Sitemap. Please ensure your Sitemap follows our guidelines and can be accessed at the location you provided and then resubmit." So I guess it is still not working
I submitted http://hubimg.com/sitemaps/hub/current/ … meguru.xml as my sitemap on bing, it wasn’t accepted. Then I tried http://incomeguru.hubpages.com/robots.txt and it was accepted. However, after waiting for some hours I got this message “We weren't able to extract URLs from the sitemap or feed you submitted. Please verify that the sitemap is in a supported format, check it for errors, and resubmit the sitemap”. Is there suggestion on how to correct this error?
robots.txt is not a sitemap. That's why you received that error. But your sitemap URL is in your robots.txt file. However, you can't specify it in your webmaster tools (Bing or Google) because it's no longer under your own domain. See prior discussion above for a full understanding.
Ads are delivered based on your own search history, indicating your interests. No one else sees the same ads.
Nevertheless, ads that startup automatically are not acceptable and HubPages is known to ban those advertises. You need to report it to staff. Be specific about the advertiser in your report so they know where it's coming from.
The URL you stated above is correct, but Google won't accept it since it's not under your subdomain. So Matthew made a duplicate under our respective subdomains to get around this problem. You have to use this URL in Google WMT…
Yes, I am a new "hubber." I am also a new writer. It has only been a few months since discovering I really enjoy writing on HubPages. My problem is, since I started writing on HubPages I have been a bit, let's...
Ever since the 18th of May there has been an increasing jump in 403 errors because of some xml-stats-realatedhubevents.php.... which can't be good for rankings. I know the 403 error means that you're denying...
This is just one example of many errors showing up in Google webmaster tools that appear to have category information added into the url of my hub creating a link to a non-existent hub. In the link below,...
I don't suppose I'm the only person wondering what happens if the machinations - automated or otherwise - lead to HubPages having a much REDUCED income stream from Amazon.Make no mistake - as Google Adsense income dives...
Looks like another content sniper is at work, stealing our shizz from HubPages. This so called "music news" site has sniped at least four of my Hubs and it looks like there are many other pieces pinched from...
I have been hub hopping lately and I am disgusted with the incoherent garbage that I am coming across - nothing but poorly translated articles of about 400 words, usually without even any formatting. I would say that...