Before we get to the good stuff, it’s important to touch on some of the issues which negatively impact your SEO and resulting traffic. The following are issues I encounter almost all of the time (and mostly because the blog owner does not realize the following issues).

Negative SEO Issues:

• Make sure you retain the services of a professional web hosting provider. If the server hosting your account is often unavailable, that means Googlebot also cannot access it. The more often this occurs, the less traffic will be referred to you (because your blog will not be as prominent in search results, as it could be).

• Don’t participate in “keyword stuffing” when writing your content. Keyword stuffing is the action of adding keywords to your content, beyond what  in context, renders as reasonable. Excessive repetition of any particular word or phrasing via  content description, title tags, (any other) meta tags and the post content tends to raise a red flag with the search engines. Read what Google has to say about keyword stuffing and if you have suffered a negative as a result, you can resubmit your blog (after fixing the issues first) for consideration.

• Do not link to or exchange links with lower quality spam or splog sites. To be quite blunt, doing this associates (and places) your blog in a bad neighbourhood. Here is a direct quote from Google:

…Don’t participate in link schemes designed to increase your site’s ranking or PageRank. In particular, avoid links to web spammers or “bad neighborhoods” on the web, as your own ranking may be affected adversely by those links…

• Don’t duplicate your content or the content of another blog or web site. Distinctive and original, in demand content will serve you best. Copying content from another source, even with permission, is nothing more than a copy. The original site with the original copy will garner search engine traffic – Not the copied content.

Blogs Links and SEO:

In my opinion, an important aspect of improving your blog’s value (to Google as well as readers) is ensuring valuable (high ranking) inbound links point to your blog – and that you in turn link (outbound) to valuable, relevant content. Below are some of the aspects I’d commonly advise and blog (or site) owner.

• Allow your links to develop some age. The older a link is, generally, the more circulated it becomes. Old, well established links are ideal for your blog.

• The popularity of the inbound link also has a positive effect on your ranking. For example, a blog with a PR (Page Rank) of 6 provides more benefit that one that has a PR of 3. But don’t rule out the value of lower PR inbound links. I’d enjoy the value of one or two hundred inbound links from a PR3 blog anytime. So what I’m I suggesting? Consider the value of the inbound links by also examining their PR. One tool I use to accomplish this is a Firefox plugin called SEOQuake. It’s a simple tool that allows you to see the page rank of any site you wish. You get get the plugin directly from Mozilla’s SeoQuake SEO extension page.

• One thing (you may have less control over) is the anchor text of the inbound link. Anchor text is the text used for the link itself and… the text immediately surrounding it. That text should be relevant to the content it is linking too. Anchor text of “Baking” pointing to a page about painting is just not going to work well.

• Again, remember that outbound links are important. According to Google’s official blog “Linking out: Often it’s just applying common sense“.

Your Blog and Your Domain:

Many are not aware that your domain name registration now appears to have an effect on your SEO.  To backtrack, in 2005, Google’s patent application specifically addressed this issue by saying:

“…Domains can be renewed up to a period of 10 years. Valuable (legitimate) domains are often paid for several years in advance, while doorway (illegitimate) domains rarely are used for more than a year. Therefore, the date when a domain expires in the future can be used as a factor in predicting the legitimacy of a domain and, thus, the documents associated therewith…”

• So it is probably a good idea to register your domain name for a longer period (than just 1 or 2 years). Incidentally, you can read United States Patent Application #20050071741. The gist of the pertinent sections of that patent application allude to the following additional issues for domain SEO:

“…the age, or other information, regarding a name server associated with a domain may be used to predict the legitimacy of the domain. A “good” name server may have a mix of different domains from different registrars and have a history of hosting those domains, while a “bad” name server might host mainly pornography or doorway domains, domains with commercial words (a common indicator of spam), or primarily bulk domains from a single registrar, or might be brand new. The newness of a name server might not automatically be a negative factor in determining the legitimacy of the associated domain, but in combination with other factors, such as ones described herein, it could be…”

• This essentially suggests that Name Servers (DNS) hosting your domain record is better contaning  a mix of different domains from different registrars. It appears Google considers this “Good”.

Finally, further advice is to ensure that you keep your domain on focus. For example, if your domain name contains keywords such as trees, weddings, real estate, law, or some other topic; ensure that your content is specific to the subject matter that your domain name suggests. If for example, you plan on launching content that is not directly related to the subject of the domain, then it may be advisable to launch it under a domain name that is more suited to the subject matter.

Keywords:

One aspect I think most of us are aware of is the issue of keywords. Specifically that we should place appropriate keywords in our document Meta Tags. (What is a keyword meta tag? – You can find out by reading Phil Bradley’s  “Meta tags – what, where, when, why?“). However did you know that the Meta tags for keyword, description and so forth do not have the effect they once did? Quite frankly, in my opinion they are a waste of time, and only useful for smaller search engines or directories, etc. that still use them – Which is why I still use meta tags.

In my opinion the only valuable use of keywords is to place the within your content! The post from Search Engine Watch, “How To Use HTML Meta Tags” says it best with their quote “Meta tags are not a magic solution”.

If you produce valuable content, Google and other search engines will be able to gather all they keyword information without any coded directions (such as meta tags).

SEO Tools for Your Blog:

In order to facilitate better SEO, there are some blog tools (WordPress plugins) that I use (and which you may want to put to good use as well). Two of the best free ones (in my opinion are:

• All in One SEO Pack provides automated (SEO) out of the box. Specifically, it takes care of titles, descriptions, keywords and duplicate content.
• Google XML Sitemaps generates a XML-Sitemap compliant sitemap for your blog. This helps googlebot better crawl your blog. It reduces the crawl time and improves speed.

In conclusion, I’d like to remind everyone who is new to SEO (and blogging). The focus should be to provide quality and in demand content. Having said this, don’t misunderstand me. Quality content is critical (that what readers are looking for) – But quality content isn’t the “key” to blog success. However, this is another topic for another day; which I have touched on in an earlier post Quality Content is Not “The” Key to a Blog Success.

Before I forget, there is one tool I really should mention, it’s the Canonical URL’s plugin. What this does is help resolve the issue of someone visiting your blog using a different URL. This is also common fro individuals who have registered more that one domain, but have them all pointing to one hosting account. Because they are different domains, this could suggest “Duplicate Content” – Not good. To learn a bit more, check out the Google video below:

What issues have you encountered with regards to Blog SEO? What do you do that I didn’t include here? Have a thought? A comment? Let us know below! – Cheers!

“Is wordpress better? and if it is can you explain why? Trying to feel my way around the blogging world!”

To answer, I think the best approach is to look at the pros and cons of self hosted (stand alone) versus site hosted (community) blogs. Personally I am biased towards a self hosted WordPress platform as it allows for greater control and customization. Again, having said this, the real issue is how you are going to drive your content, do you require full control or are you going to hand off your blog’s control to a third party?

As most blogging platforms offer more or less similar tools; for those interested in the nitty gritty (comparing platforms) WeblogMatrix has a nice tool to help you compare actual platforms. Another nice link that Google returned was “Blog software comparison chart“.

In my (humble) opinion self hosted blogs are the best (and most professional) way to go. However, without further delay, here’s my take on the pros and cons…

Self Hosted Blogs

The good:

• Using open source software (such as WordPress) results in an affordable installation (it’s free). There’s no payment for the downloaded code or licensing. Also, templates are free as well, unless you’re looking for a higher end professional branded look (requiring the time for a designer and/or developer to code). If you are able to design your own template, all the more cost effective for you.
• Better ability to offer or include specific interactive features. Most blogs are well supported by developers, who also provide valuable plugins, which you can install as needed. For example every feature of this blog is provided for free by other developers. Additionally, if you have the budget, a self hosted blog can be more adaptable as you can hire a developer to code a custom plugin and have it installed on your blog. WordPress (as an example) has a huge repository of plugins that handle everything from Adsense to ZenCart (ZenCart is an ecommerce platform).
• Complete (full) control, is the best benefit (in my opinion). Nothing speaks louder and looks more professional than the ability to stand out from the crowd. Additionally the professionalism is also further enhanced by facilitating the use of your own registered domain name. In my opinion (and I’ll probably annoy some people by saying this) using a URL that contains yourname.blogger.com or yourname.wordpress.com is akin to using a hotmail or yahoo email address on your business card – It looks tacky and unprofessional.
• You can always backup the blog content automatically by having the hosting company configure the server to do this for you.

The bad:

• To properly host your own blog, you’ll need to obtain the services of a reliable web hosting company (that can provide support when you need it!). In my case I run my own business that hosts my blogs and those of my clients. Hosting will cost extra money. Also, the registration of your own branded domain name will cost a little bit extra.
• Sometimes the installation of the blog software can be complicated, but if you have a good rapport with your hosting company, they might set up the database for you and install the code – Then all you’ll need to do is configure the blog the way you’d like it.
• Updating blog packages can also be tricky. Most of them update their code regularly, if you are technically savvy, you’ll be okay. If not, you’ll need to retain the services of a developer to do this. The same can be said for plugin updates (however WordPress is super cool and easy to update plugins in).
• Security can be an issue if you are not familiar with Internet systems and technology, however a reliable hosting company should minimize issues for you. Side note: ALWAYS have a backup of your blog current files and current database in your possession.
• These types of blogs depend on templates and it is easy for popular templates to appear on more than one blog. Remember, you need to stand out and be seen!

Site Hosted Blogs

The good:

• Usually the cost is free. All you need to do is sign up and provide the required details to start blogging.
• Software is updated regularly (as are any plugins), you don’t have to know how to do this.
• These blogs are easy to operate, there is a low learning curve.

The bad:

• Because the URL is not your domain, you’ll lack the professional (and easy-to-remember) URL. In my opinion, to some degree, your promoting the site that is hosting your blog with your content.
• Lack of control is an issue, remember, this type of blog is under another domain’s banner and your blog would be subject to it’s rules (not yours).
• Limited options are also an issue in that you cannot install plugins or other software solutions that are not already included in the package offering. As such, you have a reduced ability to adapt and customize features, etc.
• Speaking of customization, these types of blogs also are dependent on the default templates that come with them. Inevitably is can be difficult to distinguish your blog from the others (as I’ve often observed how similar they appear). In any event there will always be the branding of the “promoting site” on your blog.

While I’m sure that we could spend excessive hours (and pages) extolling the virtues for and against various platforms and the associated pros or cons, I think one pertinent point remains as a call to action:

If you are seriously considering a professional blog then you should (seriously) pursue the self hosted avenue (using WordPress).

If you want to experience installed blog versions without installing them yourself, then you can visit the “blog” section of OpenSource CMS. I have been using this site for several years to see working versions of packages before I download and install them. Also, I quick Google search also returned the post “Choosing a Blog Platform” which should help further clarify not only my opinions but also reinforce some of the issues raised in my post above.

What are your thoughts? Any pros or cons I should have included? What’s your take on this? Comment below and let us know.

Before we review some of the things we can do, let’s define what a “bounce rate” actually is, and see which tools can help us determine  our bounce rates.

“Bounce rate” has two definitions. According to Google (analytics) it refers to the act of a visitor entering your blog (or web site) and leaving within the first five seconds. More commonly, we understand it to mean the percentage (or number) of visits to your blog, where the visitor enters and exits the same page without visiting any other pages on your blog. Evidently we want visitors to remain on our blogs.

The top two tools I use to compare and find bounce rates are:

1. AWStats. AWStats is robust and is a standard statistics gathering system on most web servers.
2. Google Analytics. Is an online analytics service operated by Google.

Both of the above tools will help you determine your bounce rates. Personally I favour Google Analytics for ease. Additionally, I’d recommend reading Jacob Neilsen’s post “Reduce Bounce Rates: Fight for the Second Click“. In that post he discusses the trend where “…ever-more users are arriving deep within websites rather than entering them through the homepage…” and that your home page should really be your “orienteering point” (from which visitors can access to explore your blog further). He goes on to explain that we should focus on reducing bounce rates for Loyal users. Again, it’s a good read (and short).

What steps can we take to improve (reduce) our bounce rates?

• Provide links with which they can subscribe to your RSS feed (appearing on every page).
• For those who prefer notifications of new posts (and comments replies), provide the link or feature that enables them to subscribe. Two plugins that can assist you providing such features are: Subscribe To Comments and Subscribe2.
• Provide a feature that will inform them of similar content that they may be interested in (further reading). One plugin that can help with this is Yet Another Related Posts Plugin.
• Remember that visitors do not always arrive at the home page, so it will also help to ensure you have a search feature (to enable them to narrow down their search on your blog).
• Ensure you retain reliable web hosting services. If a site takes too long to access, visitors will move on.
• Highlight your feature or your most popular posts in the sidebar of your blog, (some of them may capture further interest).
• Ensure your blog is catering to your targeted niche. If your blog is about food and it visually looks more appealing to car enthusiasts, your bounce rate will increase.

The above reduced the bounce rates on my first blog by about 5% on average. Upon review I noticed that the bounce rate was also effected by the types of visitors I was receiving. For example, Stumbleupon campaign traffic incurred a lower bounce rate than traffic from Digg (which for me, had a super high bounce rate – 85%). Why? In my opinion, Stumbleupon visitors were visiting because they were more targeted, whereas my perceptions of Digg traffic was of a less “targeted” nature. As such, the issue that raises up again is the niche focus of the blog.  A blog that has posts with little relation to each other is going to have a higher bounce rate than a blog where the posts are naturally related to each other.

What are your thoughts on this? What are your experiences? Feel free to comment and add your input!

In my opinion, one issue is to maintain your own server. Do not host your blog on a shared server hosting account. Shared hosting accounts mean just that – other people (whom you don’t know) also have accounts on the same server, it can increase the likelihood of an incident. To give you one simple example, I was using a shared server for a quick small web site development project about six years ago. The hosting company had some issues with the server and left it in an unprotected state (they were working on it at the time). I remember logging in (via FTP) that afternoon and had full access to the files of every single account! I terminated my service the same afternoon. Using a dedicated server (or at the very least a VPS server) avoids such issues as you are in control of your own server.

All too often it seems we are so involved in how to grow, promote, enhance, etc. our blogs, yet seldom do we give serious thought to safeguarding our valuable investment.

Having said this, the question remains, for most of us (who are not network administrators), what can we do to help avoid (being proactive is more effective than reactive) security related issues? The following six tips should help you. Some may require a little more knowledge, but they are pretty easy steps to take. So, without further ado, here are the helpful tips:

1) Make sure you ALWAYS have an off-site backup.

I use a plugin called WP-DBManager, which emails me a scheduled backup of my database and also store several versions on my server. I should note that these database backups in turn are backed up by the server based software. The critical point here is that you have a CURRENT copy of your database (and blog files) offline in YOUR possession. Never ever assume that the server software (backup) is working as expected.

2) Keep your blog software updated – Always.

Updates often include bug and security fixes that plug potential exploits. One good feature of WordPress for example is that the administrative area will tell you when an update is available. It’s a simple matter to backup all your data and files, perform the update and continue blogging. If needed, you can find the update (upgrade) steps directly from WordPress’ post “Upgrading WordPress“.

3) Change your password – Do so often.

When you forget your WordPress password (or have just installed WordPress), it sends you a password. That password is short and fairly easy to crack – Change it to something more difficult. Also, there is a plugin you can use to help you lock out visitors who are trying to guess your password (to break into the administrative area), it’s called Login LockDown. Login LockDown will lock out the IP addresses of incorrect password submissions for whatever time period you choose.

4) Disable indexing of your files.

Search engines do not need to index all your WordPress files. Use a robots.txt file to disable such indexing. SImply add the statement:

Disallow: /wp-*

to your robots.txt file. The above statement tells the search engines that any directory beginning with “wp-” should not be indexed.

5) Disable viewing of your folders.

Anyone attempting to access your system may be able to see your files (such as plugins). In your web browser, try to visit your wordpress plugins by going to:

http://www. Your-Domain-Name.com/wp-content/plugins

If you can see a list of files and/or directories, that’s not good. You can create an index page that redirects visitors trying to see those directories, back your blog. Here is the code I use:


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="refresh" content="0;URL=http://bloggersavvy.com/" />
<title>Nothing Here</title>
</head>
<body>
</body>
</html>


Name the file “index.html” and place a copy of it (with the above code) in your plugins folder. Now if you try to view the contents of the plugin folder, you will be redirected to your blog’s home page. Note: Obviously, you will want to substitute the URL of my blog for your own. This tip is important because it prevents authorized visitors from inspecting your plugins and finding an exploit.

6) Deny access to your administrator login.

I use an .htaccess (among other things) to accomplish this. An .htaccess file allows me to customize how a folder is “treated”. In this case I want to deny access to all IP addresses except my own. If you find one day that you are locked out, simply edit the .htaccess file and re-upload it the the “wp-admin” folder of WordPress.

Here is an example of the code I use:

AuthUserFile /dev/null
AuthGroupFile /dev/null
AuthName "Access Control"
AuthType Basic
<LIMIT GET>
order deny,allow
deny from all
allow from 206.138.140.97
</LIMIT>

Again, change the IP address to your own. Don’t know your IP address? I’ve included a handy tool below. It does not store any data, it just shows you your current IP address (which means everyone else will only see their own IP address below). You can use this post whenever you quickly want to see your current (new) IP address:

This is your connection:
(For the technically adept, these addresses are not logged by the script that displays the IP address above, it simply finds the variable “REMOTE_ADDR” and displays it to you).

While there are several more advanced things network administrators can do to help protect your blog, the above are six simple tips that you may implement as soon as possible. Have any input, ideas, questions? Feel free to include them in your comments below.

• Top 100 of the Best (Useful) OpenSource Applications.
• Why I Quit Windows and Switched to Linux.
• Why is Linux Faster than Windows?

I enjoyed the traffic those posts provided (and still provide to this day) as they helped my blog grow. I think they were popular because they provided a valuable resource as well as elicited fair bit of discussion, as some of the posts and resulting comments were very outspoken and opinionated. One of the above posts (Why I Quit Windows and Switched to Linux) was a very personal story describing some of my career experiences and how they effected my professional life and thoughts.

Imagine my surprise when I found another blog with the identical content on it. So much so, that the author who scraped my content claimed it as his own! At that time I had more than enough technical knowledge to initiate actions that would catch-out scrapers, but I’d not yet fully experienced some of the nitty-gritty administrative aspects such as contacting the hosting providers, filing DMCA notices et al.

For that matter, why would this be an important issue? Why should bloggers (or any web site owner for that matter) take actions to mitigate such issues? Well a few good reasons immediately come to mind:

1. It’s annoying. A blogger puts a fair bit of work into his or her post, only to find it copied elsewhere and used to earn revenue (usually via advertising) for the content thief.



2. It can impact your web hosting cost if you have a busy site. Remember, most hosting accounts have a monthly bandwidth allowance. Exceed the monthly bandwidth and the blog owner incurs extra cost. But wait!… How did scrapers cause my cost to increase? Simply put, they copied the text content onto their blogs and linked the images (in that content) from my blog. This resulted in the text being duplicated on their site and the images being stored on my hosting account. When a web browser viewed the content on their page, it was pulling the images (for that content) from my hosting account, for which I had to pay the bandwidth.



3. It can reduce your Google (SEO) ranking. How does that happen? When Google finds content, it tries to determine if the content is original (not copied from another site) and proceeds to provide it with page ranking data. It is conceivable that content can be copied and receive a page rank (and inclusion in Google search results), without the original blog article being yet found by Google. If it get’s found by Google later, how can you ensure that your original becomes noted as the original post? Don’t misunderstand me, search engines like Google do try to remove duplicate content, but it becomes difficult when your original content becomes listed as the duplicate.

One important issue I realized is that you cannot be overly emotional about such actions. When trying to fix such issues, you need to work with various parties such as Google DMCA, Hosting Providers, etc. Sending them flippant or angry letters is not going to get you the help you need. Remember, large organizations and businesses deal with such issues daily and they are not impressed with theatrics. You need to have these people on your side. Remaining calm, assertive and professional goes a long way to getting support (as does courtesy).

Let’s define a couple things before we move on…

• A scraper is someone who copies your content and places it on another site, without your permission. In essence this is theft of your intellectual property.
• A hotlinker is someone who displays your images on another site, and uses the coding on their page is such a way so as to pull the image that is stored on your server (hosting account), for display on another page. As I mentioned earlier, this is tantamount to bandwidth theft.

I’m often asked how I discover that my content has been scraped or hotlinked. There are several tools that when used on a regular basis, can help you reduce the amount of content thieves.

Review your web statistics.

All good hosting accounts have built in web statistics. In my opinion AWStats ranks highly. AWStats has a feature that displays “Links from an external page (other web sites except search engines)”

The display will show you the URL of the page linking to you as well as the number of hits to your page. It will also tell you how many page loads (of your pages) that URL initiates. For example if another site URL causes 10 hits on my site, then there should also be 10 page loads. If not something’s up. Take a look at the image below (clicking on the image will show you the large version).

AWStats hotlinker example

What you’re seeing in the edited image above, is that another site has displayed something (from my site) 1645 times but never actually sent a visitor to my site. In other words my content (an image in this case) was shown on another site, but no page visits (referals) were ever recorded coming from that site. I visited the URL in question, and sure enough, the site was hotlinking to one of my images.

Use online services.

One service I’ve experimented with is Copyscape. They are a site that provides a service which scans other web sites, providing you with the URL of copied content. In my case I found scraped content (stolen from my other blog) during the writing of this very post. That is… one of my original blog posts, was found via Copyscape to be duplicated verbatum on another web site in another country. They were using it to sell their advertising space and also had hot linked to all my images. While they did include a link to my original post and did list my URL as the “Original link”, they did so without permission and were using my complete work for their own profit.

A Google search will provide you with a plethora of other sites that provide such services, I’m only mentioning Copyscape as one good example. To further take advantage of such tools, its most advantageous to include a very unique sentence in any given post and search for it in Google (that’s often a very quick method to catch sites that copy your valuable content).

Once you’ve been able to isolate a specific URL that has hotlinked and/or scraped content, what can you do about it?

Here’s how the process should work:

1. Find and isolate a specific URL that is using your content.
2. Evaluate the need to take action. Are they still sending you traffic or referrals in some fashion? The bottom line question you could ask yourself is “Does their copied content really do my blog enough harm that I have no option but to follow through?” If you’ve answered yes, action is the next step.
3. Take action.

But wait! What actions are there? Can I really protect myself from a scraper or hotlinker in another country?

Before moving into they types of actions (tools) you can use to protect your content, it’s important to keep one salient point in mind:

If you have some content that is so important, private or valuable, etc. and you do not want other people to copy it, then DO NOT POST IT ON THE INTERNET. If you post something of excessive value on the Internet, no measure of copyright protection is going to prevent an individual from accessing it and copying it. But (there’s always a “but”), there are ways you can impede the profitability and earning power of copied content and in some cases injecting your own revenue generating systems into content copied from your site.

So what kinds of actions can we take?

Make sure you provide appropriate copyright notifications within every page of your blog. If you intend to permit your content to be shared, Creative Commons provides a great copyright tool wherein you can specify how your content is shared. You’ll find that tool at Creative Commons. You can select your jurisdiction in a drop down menu on the upper right side of the home page.

Is the copied content being served by Google Adsense? If so, you can issue an infringement notice at Digital Millennium Copyright Act – Google AdSense. I’ve found the best method is to fax the notice to the number they provide. In practice, I’ve found that it takes a few days for this to work through their system. However, they have always acted professionally, responsible and have indeed taken action.

As a side note: If you are looking for notification templates you can use, take a look at Copyright Law and SEO Part 3 (Sample DMCA Notifications, in HTML and MS Word Format), found on the McAnerin International web site.

Personally, I’ve experienced an excessive number of blogs copying content to Blogger.com based blogs. If you review their Blogger Content Policy, you’ll also find that notifications are to be sent to Google at Digital Millennium Copyright Act – Blogger. Again, I’ve found the response to be incredibly fast and Blogger.com is very quick (in my experience) to remove the violating content.

Many scrapers capture and repost your content by tapping into the RSS feed of your blog.

Side note: If you’re not very familiar with RSS feeds, Commoncraft has a great video, RSS in Plain English.

The fact that they are simply capturing and re-posting your RSS feeds may be indicative of an automated system (with little human intervention), where the scraper may not necessarily read your copied content. If that’s the case, you could try embedding a link back to your blog. There’s a great WordPress plugin that will automatically do just that: RSS Footer. (One helpful thing is the RSS Link Tagger for Google Analytics, which helps with the tracking of non-adwords advertising campaigns. If you log into Google Analytics and go to your created campaign and view the traffic sources information you’ll garner more information).

Try earning a bit of revenue from your stolen feed content. If you’re a Google Adsense publisher, try the “AdSense for Feeds” option within your “Adsense Setup”. Additionally, the RSS Footer plugin above, I think can also be used to embed advertising content from any other affiliates or advertisers you subscribe to.

For those who are a little stronger at coding issues, you may want to try out a great little WordPress plugin called “From RSS?“, where, as their site says: “…do something extra for your RSS subscribers, you might want to give them a little bit of extra content, or simply leave out some annoying footer about subscribing to the RSS feed. This plugin facilitates that…”

You can of course Report a Spam Result to Google which they use to help “…maintain the quality of Google search results.”

Finally another tactic that’s available is to report the site to the hosting company. There must be a ton of resources to help isolate who is the ultimate network provider (for the server that hosts the offending web site), of which I primarily use two:

• Whois lookup and Domain name search and
• Netcraft’s Search Web by Domain.

Using the domaintools.com site, I can see which DNS servers are managing the domain (ostensibly indicating who’s hosting it). And with Netcraft’s tools, I can determine who owns the IP address block that the website and server is one, thereby opening another venue of recourse.

In conclusion, I’d like to remind everyone of on salient issue. There may always be hotlinkers and scrapers of our content. I don’t think anyone can stop all of them, as doing so would in all likelihood prevent legitimate visitors from viewing your content, instead the primary objective of this post was simply to impart the concept of DETERENCE, so as to reduce such activities.

• easy to remember
• be related to the content
• reinforce your branding
• not easy to confuse
• easy to spell

All too often someone has spent the time to thoroughly research their domain name and had someone register the name on their behalf. Another scenario is that the developers have researched and registered the domain. But what happens if the relationship breaks down or the developer’s business closes?

I’ve often encountered domain name issues , as well as mediated such disputes between clients and their former site or blog developers. Invariably the scenario involves a breakdown in communication in which the rightful owner realizes that they don’t have control over their domains. In other cases the domain name is held for ransom and in others the original developer is no longer in business, among many other scenarios.

Recently I was contacted by a client who needed more cost effective and responsive hosting. The primary issue at hand was that the original developer had passed away and there was nobody to update their site or tend to hosting related issues. Upon examination, I found that the domain was not registered directly to them and as such (from a technical perspective) they did not appear to be the rightful owners. This resulted in the inability to move to a different hosting provider. They had no usernames or passwords to access and edit the domain name records, they had no current payment receipts proving their ownership, nor did they even know who the real hosting provider or domain registrar was. The hosting service was a resold account from a third party provider. The domain name was also resold from a third party. I was able to return control of the domain back to them, but it took three weeks of phone calling and faxing to the registrar to accomplish this, additionally it did help to garner the support of the hosting company.

How did this happen? What are some of the caveats?

When you have a domain name registered on your behalf by a third party, make sure that the email address used for the “Administrative Contact” is YOUR email address. This ensures that any transfer of the domain (to someone else) needs to be approved by you (because you get the email request). Additionally, this also enables you to change other information pertaining to your domain name registration record.

In the above case, the client did not have their email registered as the Administrative Contact (or as the Registrant). In fact the developer used his name, email address and other personal credentials within the registration record. In my opinion this is a big no-no! What happens if the developer is unable to provide services? Can a blog or site owner really wait for an extended time period to gain access to their domain name so they can move to a new hosting provider?

I’m not suggesting that the world of web developers or designers is frought with unscrupulous characters intent on seizing control of your valuable domain names. Rather I’m suggesting that you ensure you’re involved in the registration process, that you ensure you protect your interests. For those not familiar with hosting systems, there will always be a learning curve. Avoiding that learning curve could in some cases be very costly!

When registering a domain name, or having someone register it on your behalf, make sure you are aware of the following:

The Registrant is the legal owner of the domain. The Registrant should always be you, your business, etc. NOT your web developer, web designer, hosting company or anyone else. Period!

The Administrative Contact has the credentials and access to change the domain record information. This should be you, your business, etc. NOT your web developer, web designer, hosting company or anyone else.

As I alluded above, the web developer had listed himself as the owner and administrator of the domain, which resulted in the client having to wait an excessive time to garner access to the domain. And I may add it was only through shear “consideration” on the part of the registrar that they obtained access to their domain prior to it’s expiry and (hopeful) re-registration.

The Technical Contact should be the individual with the technical knowledge to resolve issues with the domain (commonly the hosting provider).

Are you currently listed as the Registrant and Administrative Contact of your domain name? If not, your name could be at risk. Here is one of the tools I use to help clients view their registration records: whois.domaintools.com