It is now fairly common to see Google insert jump to anchor links for popular pages in their search results. For example, a search for “wordpress loop” returned 3 anchor links.
Inline Jump To Links
Then I did a search for “wordpress multiple loops” and noticed an additional jump to link within the description text.
Google has picked that section of the page as being more relevant to my search terms and has included a link to that anchor. Not only that but the description is taken from the page content immediately after that anchor point and heading. Clever.
Let’s look at the source code
In this example, looking at the page source code reveals an anchor tag followed by a heading tag followed by a paragraph of content.
<a name="Multiple_Loops_in_Action" id="Multiple_Loops_in_Action"></a>
<h4><span class="mw-headline">Multiple Loops in Action</span></h4>
<p>The best way to understand how to use multiple loops is to actually show an example of its use...
It’s unclear wether Google in picking the “Multiple Loops in Action” link text from the anchor name or the following heading text.
Interestingly the ‘mw-headline’ class applied to the heading seems to be a fairly standard class applied to headings in Wikis, so maybe this is what Google is picking up on.
I think I may have to try out some of this HTML markup and see what happens…
I was just about to update an old plugin I created to create an XML site map for products in WP e-Commerce…
…then I stumbled across the WP e-Commerce XML Sitemap plugin by Lee Willis.
The plugin worked well with WP e-Commerce 3.7.5 (the latest version) apart from a few minor issues. I got in touch with Lee and suggested a few tweaks/fixes – he has just released an updated version:
- Unpublished products are now not added to sitemap.
- Is now compatible with WordPress installations with custom table prefix.
You can download the latest version here…
One plugin I recommend that everyone should add to their WordPress installation is the Google XML Sitemaps plugin.
This plugin will automatically generate an XML sitemap of your posts and pages and ping supporting search engines to notify them that the sitemap has been updated.
But the best thing about this plugin for other plugin developers is it provides hooks so you can ‘borrow’ it’s functionality so that your plugin can add additional pages into the XML sitemap that is generated.
So if you’re a WordPress plugin developer, read on…
I recently stumbled across this post by Matt Cutts of Google which gives an in-depth view of how Google PageRank is affected by rel=”nofollow” links.
I have seen a lot of advice from SEO consultants recommending the use of “nofollow” on links to prevent Google leaking your PageRank out to other web sites and therefore concentrating the passing of PageRank to other pages on your site.
For example, if your page had 10 PageRank points and 10 links to other pages, 5 of which were set to “nofollow”, the other 5 pages would each carry a PageRank of 2 points (ie share the full 10 points between the 5 links).
It would seem from what Matt says that this isn’t exactly how Google works. Sculpting the links on your page to concentrate link traffic to other pages does not equate to a concentrated amount of PageRank being passed to those pages.
In the example above, adding “nofollow” does prevent PageRank being passed through those links but the other 5 links will still only receive 1 PageRank point per link.
In general, Matt suggests whenever you’re linking around within your own site don’t use “nofollow”. Only use “nofollow” on links when you do not want a page to be indexed by Google, or for external links of which you may not have been able to verify the content (for example, a link added by a commenter on your blog).
If that makes no sense, Matt explains it much more clearly…
I’ve just released version 2.1.2 of the WP Geo Wordpress Plugin.
It includes Geo capability for feeds using GeoRSS (Geographically Encoded Objects) – for more information see www.georss.org. This will make it easier for developers to create mash-ups of post geo data using your site’s feeds.
Find out more…