Funny you mentioned Greasemonkey, because I started working on my own
script more or less right after I posted here. The Yoast script does
do just what I was looking for, although the presentation of the info
isn't all that attractive. One thing that my Greasemonkey script does
that the yoast script doesn't do is allow you to remove nofollow/no
link found rows from the output table. My script doesn't have
anything for PageRank, but that shouldn't be too hard if I can find a
good site with an API for getting PageRank or an easy site to scrape
it from.
On Oct 17, 3:32 pm, JLH wrote:
> Here's a greasemonkey script that does just that, and adds PR and
> anchor text.
> http://yoast.com/seo-tools/link-analysis/
> On Oct 17, 10:27 am, GeekLad wrote:
> > As I understand it, GoogleBot does index nofollow links but they are
> > not used for the purposes of calculating PageRank. Currently Google
> > Webmaster Tools has all external links displayed together, regardless
> > of whether or not they are nofollow links. If a webmaster wants to
> > find out whether or not they are nofollow links, each linking page has
> > to be individually visited and inspected to make that determination.
> > This is very tedious and inconvenient.
> > It would be very helpful to webmasters to provide nofollow information
> > about external links within Google Webmaster Tools. Perhaps splitting
> > the external links column into two separate columns, one for links
> > that are nofollow and links that are "dofollow" (for lack of a better
> > term for links that are not nofollow). Finding the sources of what
> > incoming links are contributing to PageRank would be an invaluable
> > tool, as it would allow webmasters to learn more about they are doing
> > right to promote their sites.
> > I've seen a lot of discussion in the webmaster help about external
> > links and nofollow. I tried searching to see if there are any
> > existing feature requests regarding the identification of nofollow
> > external links, but I could not find any such existing request. My
> > apologies if this feature has already been requested.
