| 8:29 pm on Sep 2, 2007 (gmt 0)|
Interesting bug - it's not there for me. Hope they fix yours soon, especially since you're probably not the only one.
| 10:14 pm on Sep 2, 2007 (gmt 0)|
I sometimes wonder why I bother with GWT - it's a nice idea but poorly implemented.
Many will say "it's better than nothing" and I understand what they mean, but the tools themselves are erratic and the reporting is often flawed or long out of date. "Data is not available at this time" is hardly worth logging in for, and I too currently suffer from the bug mentioned above (which makes a change from the recent logout errors and verification problems).
I have no objection to Google collecting my data in exchange for a free service, but I suspect there may be more in it for them than there is for me, and while it is reassuring to see my main site still reported in the top ten for its primary keyword, any member of the public who actually searches for it will find it has been languishing on page seven for the past week.
I almost feel sorry for Google - until I remember how much money they have.
| 10:43 pm on Sep 2, 2007 (gmt 0)|
I have the same bug :-(
| 4:03 am on Sep 3, 2007 (gmt 0)|
Have the same problem. I also notice how slow the external links are to update in GWT. I spot links much faster by searching for www.example.com.
| 6:38 am on Sep 3, 2007 (gmt 0)|
Google is getting too big for its trousers. They are trying to be too much too fast and getting a lot screwed up. Their code sucks bad.
Example: I had a project to ceate a search feature on a site using thier search API. The client wanted some advanced features not compatable with the base API, so I rewrote the thing. Benchmark shows a 68% increase in speed, all output generated at the DOM level, and compliant with more browsers than their original code.
I see more css and Dom level errors on Google pages than almost any other.
I think they hire too many graduates with no practical experience, just like so many other corps.
| 2:22 pm on Sep 4, 2007 (gmt 0)|
I see the same bugs with the listing of the link since 3 or 4 weeks; further the status shown by the URL removal section is wrong: the URLs are removed but the tool is showing them as pending since 2 months, further a duplicate entry is shown.
The errors above are not very frustrating because they can easily be recognized! But what about all the others very hard to detect? The ext/int links, the results of the site-command, etc,?
| 11:49 am on Sep 9, 2007 (gmt 0)|
I see the exact same bug in my GWT account.
| 4:32 pm on Sep 11, 2007 (gmt 0)|
|The Next link in GWT > Links takes you back to the list of pages with links rather than showing you the next page of links |
Yes. Same for me.
But it only affects viewing links to my home page. Presumably it thinks you haven't selected any page to examine.
You can hack the url to get what you want....
Go to your first page of backlinks and instead of clicking the erroneous next button just tag this onto the end of the URL in your address bar:
where x is the BL number you want to start from
| 7:51 pm on Sep 11, 2007 (gmt 0)|
Yes i have noticed this bug for at least three weeks now..very annoying. All you can do is download the entire table and look at it in excel
| 9:46 pm on Sep 11, 2007 (gmt 0)|
I noticed this about 2 weeks ago.
I have several sites and those with thousands of links, I have the same issue.
But those with less than 100 links, it seems to work OK.
I posted the issue on Googles Webamster Help Forum a week ago, of which I presumed those from Google read.
But no one has replied to it.
I have to convert to excel to read.
| 11:57 pm on Sep 11, 2007 (gmt 0)|
I have the same bug.
Here is a cute one:
I was searching via google netherlands the other day and now my sitemaps pages are in whatever language the netherlands is set to.
I'm in the USA.
| 7:19 pm on Sep 12, 2007 (gmt 0)|
I have this problem also... had to export to csv to check my links.
| 11:10 am on Sep 13, 2007 (gmt 0)|
@sailorjwd: If you want to get back to the english language version, just add the following to the end of the URL: &hl=en (if it already has a "hl" parameter, just change the value to "en")
You can do that with almost all Google services. I believe your preference is stored in a cookie somewhere, by adding that you're just overriding the setting.
| 1:28 am on Sep 14, 2007 (gmt 0)|
Google has apparently fixed this problem, as well as updating the look and feel of the Webmaster Tools. When I checked earlier tonight, the whole thing has been revamped.
Would bite, wouldn't it, if the whole PR update has been put on hold while they were re-designing GWT? :)