Forum Moderators: martinibuster
Any Idea what this is really saying?
[edited by: martinibuster at 5:21 am (utc) on Nov. 24, 2009]
[edit reason] Examplified URL. Example.com, it's what's for examples. ;) [/edit]
I never really bothered, because there were so few occurrences, but then I read:
"Please also keep in mind that this report is not exhaustive"
Does that mean that the blocked URLs list is only a short summary... and that I may be missing more than the ~100 reported pageviews/week?
Does that mean that the blocked URLs list is only a short summary... and that I may be missing more than the ~100 reported pageviews/week?
Close your AdSense Control Panel. Open up your favorite log file analyzer, Google Analytics, or whatever you use to track visitors to your site. Check your traffic stats for how many visitors come from other countries. Also check your referrer stats because it will show you how many of your visitors came from Google Translate.
Is it significant? How many of those visitors are coming from countries/languages that are less developed and thus do not have a competitive CPC? It's possible you will find that only a fraction of a percent come from countries that might need translation, and of those countries many of them are less developed than North America and Western Europe and thus not profitable to worry about.
Those are the questions that will lead to the answers that will help answer your original questions. Those answers are found in whatever analytics you use. ;)
There are several pages showing links for translations. The reason given for the translate pages is "Robots.txt File," which has recently been removed.
Since it was removed, the reason given is "Not Found."
I note that most of the "Not found" urls are those used before the site was redesigned and launched. My web developer did loads of redirects.
Could it be that more redirects are needed?
YES, you geniuses at the Plex, I do admit that I do not have access to these properties and thus can not fix that robots.txt problem reported in the site diagnostics. I suggest that you query one of the popular WHOIS services to find out who might be able to fix the problem! (Hint: He or she may be sitting closer to you than you probably think.) ;-)
Seriously, Google should filter at least their property from those "site diagnostics" reports; all these fake alarms make the feature useless. And no, it can't be that difficult to implement.