One obvious approach is to ignore requests from your blog readers. That’s a 100% solution to saving time and improving productivity. However, in my opinion it’s not an effective approach for several reasons. Notwithstanding this approach will almost certainly damage the reputation of you and your blog. It would also reduce traffic as there’d be no valuable communication with your community. And to be blunt, that’s just plain stupid. If you’re not going to listen and communicate with your community, why even have a blog?

For blogs that are more established (having greater readership) one good way to respond to requests is to turn the request into a blog post. Blog about it! Doing so encourages your community to communicate and explore the ideas of the post. In turn this benefits the reader (who initiated the request) with valuable answers garnered from a multitude of perspectives and experience levels. This also benefits your blog in that the community in essence develops good content through discussion.

From an administrative aspect, another approach is to develop an FAQ page or adding content on your “Contact” page that explains what type of requests you field and which you don’t. This provides two immediate benefits. It reduces your time in responding to requests with a diplomatic “no” answer and it helps readers save time by only posting requests you do handle.

I’ve maintained better productivity using a “Request Response Template” for higher traffic blogs. This means I don’t have to craft a response from scratch. Almost all responses have more or less the same content with regards to salutations, introductions, conclusions, basic information, contact information, etc.  Depending on the blog, you can include links within that template which directs readers to appropriate information. Include your current status - Are you available to consult or not? Make sure you simply explain that you cannot always answer every request for personal assistance.

Keep in mind that canned responses are VERY OBVIOUS, as such it’s a good idea (a must!) to include relevant comments that are helpful. In many cases a link or two to your blog posts (that are relevant to the request) will be helpful and appreciated. Don’t misunderstand me, I strongly feel that all communication should address individuals on a personal level, that makes it a fine line between working with requests you do handle and those you do not.

Above all, be honest and up front, if the request for personal assistance is something you do not handle - Say so. This avoids reader frustration.

One method that I have found particularly helpful (and has turned readers into clients) is to invite those local to you for a face to face meeting. For example, I provide public seminars to local business people (about web site, marketing, promotion, hosting, etc.), if their request is related in some fashion to an upcoming seminar, I personally invite them to the seminar. If it’s not, I still invite them as it will afford me a few minutes to talk to them after the seminar.

One issue I think crucial (at least it is for my client), as a matter of fact it’s the crux of his phone call to me is that he did not want to provide paid consulting services for free. In this case, my response would not be built on top of my Request Response Template, rather it would be a personally crafted, targeted response. The following points should be covered for these types of issues:

• The reader’s request cannot be handle in a simple expedient manner.
• You need to spend significant time to deal with the personal assistance request as some research, planning or solution development, etc. is required.
• This is the type of consulting service that existing clients pay you for, and list some of the examples of your paid services.
• MAKE SURE you spend a bit of time clearly outlining the solid benefits your reader garners by paying for your services.
• Provide options if the reader is not in a position to render your full services.

While the volume of potential consulting jobs obtained from such requests is directly related to the traffic volume for your blog, I’d advise low volume blogs to be prepared for them, you never know when such opportunities might come your way.

In conclusion, if you get an excessive amount of requests that you simply cannot respond to, my perspective is that it’s a clear signal from the community, indicating what content they are interested it. Clearly note on your blog that you cannot possibly field personal assistance requests. and… Blog specifically about the requests with valuable information!

• 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