8 de October de 2008 — Link Building
Not only the English speaking part of the world has been busy trying to find out which factors make a link valuable. Inspired by Wiep´s article, Spanish SEO Señor Muñez asked 15 Spanish experts to share their thoughts.
“Half the money I spend on links is wasted, the trouble is I don’t know which half”, wrote Patrick Altoft a few days ago. To find out which links are the valuable ones, Dutch link builder Wiep published an extensive survey with the opinion of 17 well-known SEO and link specialists.
The list with Top Value Factors was interesting, the graphics were great, but the real gems in the Link value Factors document were the comments of the participants. In the Spanish version of Link Value Factors, no remarks are published. This makes the article much more of a multiple choice test than a in-depth survey.
Still, I thought it would be interesting to compare the results of the two articles:
Top 10 Most Important Factors
| Link Value Factors |
Valor De Los Enlaces |
|
|
| 1. Robots.txt excluded page |
1. Anchor Text |
|
|
| 2. Anchor text |
2. Page authority (in inbound links) |
|
|
| 3. Link is on penalized page |
3. Domain authority (in quality of backlinks) |
|
|
| 4. Page authority (in inbound links) |
4. Page relevance (contextual relevance) |
|
|
| 5. Domain authority (in quality of backlinks) |
5. Link type (text, image, flash) |
|
|
| 6. Amount of outbound links on page |
6. Age of Domain |
|
|
| 7. Total amount of links on page |
7. Domain authority (in number of backlinks) |
|
|
| 8. Age of domain |
8. Domain authority (in rankings on relevant keywords) |
|
|
| 9. Relevant authority (in rankings on relevant keywords) |
9. Number of links |
|
|
| 10. Javascript link |
10. Page authority (in PageRank™) |
|
|
Top 5 Most Agreed Factors
| Link Value Factors |
Valor De Los Enlaces |
|
|
| 1. Alexa ranking |
1. Anchor text |
|
|
| 2. Robots.txt excluded page |
2. Alexa ranking |
|
|
| 3. Domain authority (in quality of backlinks) |
3. Relevance based on TLD (.com, .edu, etc.) |
|
|
| 4. Page relevance (words only) |
4. Page authority (in inbound links) |
|
|
| 5. Number of links |
5. Link location on page (boiler plate) |
|
|
Top 5 Most Controversial Factors
| Link Value Factors |
Valor De Los Enlaces |
|
|
| 1. TLD (.com, .edu, etc.) |
1. Target page |
|
|
| 2. Type of link (image, text) |
2. Surrounding text |
|
|
| 3. Domain authority (in PageRank) |
3. Quality of outbound links |
|
|
| 4. Domain authority (in rankings on irrelevant keywords) |
4. Page authority (in internal links) |
|
|
| 5. Target page |
5. Last date of page edit |
|
|
Looking at the Top 10 Most Important Factors, it´s interesting to see how the English specialists put much more wight on the dampening factors of a link. Actually 3 out of the Top 10 factors are dampening factors. (In a broader sense of the word, the amount of outbound links on page could also be considered a dampening factor, which would limit the number positive factors to 6).
The Spanish participants however, haven´t listed any DF in their Top 10. According to them, a Robots.txt excluded page - listed as most important in Wiep´s results - has only a “moderate influence on the link value”.
If we take the dampening factors out of the results, the Top 3 is the same for the English and Spanish survey.
27 de August de 2008 — SEO
If there´s one site that benefits from Google Suggest, it must be Hotels.com. Their site shows up first in Google´s search query suggestions for a highly competitive keyword.
While playing around with Google Suggest, I did a search for “hotels”. After typing four letters - “h-o-t-e” - Google already assumed I was looking for hotels.com. Not the generic term “hotels“, but the Expedia-owned booking site hotels.com:

Free traffic
It´s not the first time that I saw Google suggesting a website instead of a keyword, but only when searching for a brand term (e.g. “youtube” or “facebook”). Hotels.com has the advantage that their brand is a keyword, so they may catch a lot of long-tail traffic of people who were originally looking for:
- “hotel reviews”
- “hotel rooms”
- “hotel accomodation”
- “hotel in “
- etc
The amount of traffic that hotels.com will receive, depends on the percentage of searchers that will click on the first query suggestion. Keeping in mind that the first result in the SERP´s receives about 50% of all clicks, ranking first in Google Suggest will possibly also dramatically improve their traffic.
Google´s Golden Guess
Of all the possible search queries starting with “hotel”, why would Google suggest the site “hotels.com“? After all, the search volume of the query “hotels” is much higher:

19 de August de 2008 — Wordpress
Recently I´ve been translating a theme and while the translation process wasn´t complicated at all, it took me quite some time to figure out how to get started. Somehow none of the ´how-to´s available seemed to work for me. I´ll try to make this guide a practical one by covering only the need-to-know and leaving aside the technical details.
Localizing Wordpress - a brief overview
If you ever had to translate a Wordpress theme or plugin directly in the source code, you´ll know that it´s a time-consuming process. A time-waisting process as well, since which each update you´d have to translate the files all over again.
Fortunately, a growing number of Wordpress developers have made their work available for internationalization, by adding a PHP-function to all the text messages that will be displayed:
__($message)
_e($message)
For translators it´s not necessary to know exactly how these functions work.
This method allows you to make a list of all the text strings available for translation. This list is called a POT-file and consists of two columns: the left column contains all the words and phrases of the theme or plugin that are available for translation. The right column is still blank: this is where you can add your translations.
When the translation is completed, you´ll save the file as a PO-file. Now you have an external translation file that you can edit or update whenever you want! Converting this PO-file to a MO-file is the last step in the localization: this MO-file is basically a optimized PO-file for your server in order to retreive the translations faster.
Recapitulating:
| Internationalization/localization |
Making Wordpress available in languages other than English |
| POT (Portable Object Template) |
List of messages available for translation |
| PO (Portable Object) |
List of messages available for translation with translation next to it |
| MO (Machine Object) |
Optimized machine-readable binary file in order to speed up the process on the server-side |
Using Poedit to translate your theme or plugin
Poedit is a free open-source translation tool that allows even the most code illiterate blogger to translate his favourite theme or plugin in his own language. While simple to use, the interface is not the most intuitive. This step by step guide will lead you through the process.
- Download and install Poedit
project - download
- Run Poedit.
When asked for a prefered language just choose the language you want to use in Poedit. Fill in your name and email address. These will be included in your translations.
- Start a new translation
Choose File > New Catalog
(if provided, you can edit an existing POT-file by choosing File > New catalog from POT file)
- Fill in the settings
- Tab: Project Info -
- Poject name and version - Add the name and version of the theme or plugin
- Team - Add your name
- Team´s email address - Add your email address
- Language - Choose the language you´re going to translate to from a list. The order is not 100% alphabetical, so fill in the first letters and use your keyboard arrows to find the language.
- Country - Add your target country. To find it, use the same trick as mentioned above.
- Charset/Source code charset - Add them if you know what they are. Wordpress uses UTF-8 by default.
- Plural Forms - Add a function to describe how to process plural forms. For most languages you can just copy-paste the formula from this list.

- Tab: Paths -
* Click the little dotted square to add a new item *
- Base path - Add the path to the folder of the theme or plugin you want to translate. You can copy this path from your windows explorer browser window or by viewing the properties of the folder (right mouse click).
- Path - Add the path within the folder to your theme or plugin
Example:
This is what I´d fill in if I´d want to translate a theme called “TranslationTheme” located in this location:
C:\Documents and Settings\User\My Documents\Folder\TranslationTheme

- Tab: Keywords -
* Click the little dotted square to add a new item *
- Fill in the two functions the developers have used to make massages available for translation:
__ ( underscore underscore) and _e (underscore e)

- Save your POT-file.
When you´re done, just hit enter and Poedit will compile a POT-file of words and phrases ready to be translated. Save this list.
- Start translating.
Now that you´ve got a complete list of all the words and phrases, you can start adding your translations. Poedit also offers the possibility to add comments. To use this function, go to View > Show comment window. Remember to save the file while you´re working, so you won´t loose your data when you´re computer crashes.
- Save your PO- and MO-file
When done, go to File > Preferences > Editor and make sure the box ´Automatically compile .mo file on save´ is ticked. Save your file as a PO-file, using a combination of language and country codes. E.g. a Brazilian translation would be saved as pt_BR.po and Spanish would be es_ES.po.
- Upload your translations
On saving Poedit automatically prepared a MO-file for you. Just upload the PO and MO files to the appropriate folder of your theme or plugin and you should be able to view your translation in the theme/plugin interface. If you have defined the appropriate WPLANG in your wp-config.php file, that is.