Results tagged “movable” from Just Another Hacker

The reason behind the change is a simple one. They do not (currently) fudge NXDOMAIN records like openDNS do. This has a tendency to break RBL queries, openDNS "solves" this problem by making exceptions for known RBLs. As you can see from this OLD discussion on the openDNS forums this has been their policy for a long time.

The default RBL services used by the movable type spamlookup plugin are bsb.spamlookup.net and sc.surbl.org. I also use additional lookups like stopforumspam, spamhaus and others. As a result I was constantly experiencing false positives for comments and trackbacks. Changing to google solved all these problems. If you are using niche RBLs and openDNS I would recommend that you test these.

[OpenDNS]
$ host nopes.grrrr.bsb.spamlookup.net 208.67.222.222
nopes.grrrr.bsb.spamlookup.net	A	208.69.32.132
 !!! nopes.grrrr.bsb.spamlookup.net A record has zero ttl
$ host nopes.grrrr.bsb.empty.us 208.67.222.222 nopes.grrrr.bsb.empty.us A 208.69.32.132 !!! nopes.grrrr.bsb.empty.us A record has zero ttl
FAIL!

[Google]
$ host nopes.grrrr.bsb.spamlookup.net 8.8.8.8
nopes.grrrr.bsb.spamlookup.net does not exist at google-public-dns-a.google.com, try again
$ host nopes.grrrr.bsb.empty.us 8.8.8.8 nopes.grrrr.bsb.empty.us does not exist at google-public-dns-a.google.com, try again
WINNAR!

I have taken the liberty of reporting these two to openDNS as they are common for MT users, however there are several other RBLs that I use which aren't covered by openDNS. By changing to google public DNS I don't have to put up with false positives. It also saves me the hassle of having to verify and "fix" RBLs every time I make changes.

If you want to make the change you can find the details at: http://code.google.com/speed/public-dns/


Ok, so this post might be a sell out, but since none of the movable type seo advice tutorials I've seen so far do it right I thought it was time for someone (me) to do better. I assume you have done some research so I won't go through the purpose of the meta tags. In this example I will be adding author, keywords and description meta tags.

In your entry template find the line <mtsetvarblock name="html_head"> and add the following lines.
<meta name="author" content="<$MTEntryAuthor$>" />
<meta name="keywords" content="<$MTEntryKeywords encode_html="1"$>" />
<meta name="description" content="<$MTEntryExcerpt encode_html="1"$>" />
Do the same for the page template, but use the variables MTPageAuthorDisplayName, MTPageKeywords and MTPageExcerpt.

The final result should look like;

[Entry template]
<mtsetvarblock name="html_head">
<meta name="author" content="<$MTEntryAuthor$>" />
<meta name="keywords" content="<$MTEntryKeywords encode_html="1"$>" />
<meta name="description" content="<$MTEntryExcerpt encode_html="1"$>" />

[Page template]
<MTSetVarBlock name="html_head">
<meta name="author" content="<$MTPageAuthorDisplayName$>" />
<meta name="keywords" content="<$MTPageKeywords encode_html="1"$ >" />
<meta name="description" content="<$MTPageExcerpt encode_html="1"$>" />

The big difference between my method and most others is that I supply the encode_html directive. This means that if your entry contains html tokens, such as the double quote (") it will be encoded as &qout; inside the meta tags, rather than breaking your html which the " by itself would do.

For the index lists, such as the index page, archives, author entry list and so forth I would recommend using static content for seo. The reason for this is that the MT tags we have just used are context sensitive. So if you used the entry tags in the author list it would only display the content of the last entry for this author due to the context.

Good luck!
No Clean Feed - Stop Internet Censorship in Australia
Creative Commons License
This weblog is licensed under a Creative Commons License.