Optimize Your Web » Wordpress

Google Analytics Limitations

admin — Tue, 30 Sep 2008 19:51:30 +0000

For those that are constantly reviewing site visitors with Google Analytics (or any web site analyzer), there are a few things you should realize about their measurements.

Avg. Time on Site.
-This is calculated when they first request a page, and then when they request another. This is not a true indication of the time. Say if a person wants to read one of your posts (say a really lengthy and informative post, and it fulfills their needs) it doesn’t say actually how long they sat there and read it. So it counts it as 0 time on your site if they do not click something else on your site.

Bounce Rate:
Many people don’t go to a website to find specific information and while they’re using that information for their intended purpose, do they continue to search your site unless either A) they’re returning to find out what else you wrote or B) complete finished whatever task they needed to accomplish at your site, and was curious about more.

So in conclusion, these are not great indicators of how your site helps people unless you have 20 articles written about similar subjects. Because there is not a way for them to see (unless the person clicks something after reading the article, which many don’t). If anyone has a good alternative or way to determine these and other measurements better, please feel free to share with all of us.

Why you should require authorization for every comment

admin — Thu, 04 Sep 2008 20:38:42 +0000

One main reason that you should require authorization for every comment and trackback/pingback for your blog is this: If you don’t, spam will get through and that will negatively rank your blog/website. It even has the possibility to show up your search results on search engines. I have seen this first hand, and it makes your site look very unprofessional and very spammish. I would take the extra 2 minutes and look through your comments and approve or mark as spam. This is minimal effort with great benefits and should be undertaken by any serious blogger or website administrator. Setup your options so it notifies you of any comment awaiting authorization and keep your blog looking great and appearing professional.

XML-RPC List of Sites

admin — Thu, 04 Sep 2008 02:55:08 +0000

Trying to get the most out of your blog? Want to inform a lot of XML-RPC site update services of your latest posts? Well you need to enable a few things in your WordPress wp-admin and then use a long list of sites that have been compiled for your convenience. But first, you need to have the following updated in your Settings. Go into Settings -> Writing and look for the following:

To post to WordPress from a desktop blogging client or remote website that uses the Atom Publishing Protocol or one of the XML-RPC publishing interfaces you must enable them below.

Remote Publishing

To post to WordPress from a desktop blogging client or remote website that uses the Atom Publishing Protocol or one of the XML-RPC publishing interfaces you must enable them below.

Atom Publishing Protocol	Atom Publishing Protocol Enable the Atom Publishing Protocol.
XML-RPC	XML-RPC Enable the WordPress, Movable Type, MetaWeblog and Blogger XML-RPC publishing protocols.

Then you need to add the list of update sites for XML-RPC to this part further below in the same section.

Update Services

When you publish a new post, WordPress automatically notifies the following site update services. For more about this, see Update Services on the Codex. Separate multiple service URLs with line breaks.

Here is the list:

http://api.moreover.com/RPC2

http://api.my.yahoo.co.jp/RPC2

http://api.my.yahoo.com/RPC2

http://audiorpc.wehttp://blogs.com/RPC2

http://blog.goo.ne.jp/XMLRPC

http://blogpeople.net/ping

http://blogsearch.google.ae/ping/RPC2

http://blogsearch.google.at/ping/RPC2

http://blogsearch.google.be/ping/RPC2

http://blogsearch.google.bg/ping/RPC2

http://blogsearch.google.ca/ping/RPC2

http://blogsearch.google.ch/ping/RPC2

http://blogsearch.google.cl/ping/RPC2

http://blogsearch.google.co.cr/ping/RPC2

http://blogsearch.google.co.hu/ping/RPC2

http://blogsearch.google.co.id/ping/RPC2

http://blogsearch.google.co.il/ping/RPC2

http://blogsearch.google.co.in/ping/RPC2

http://blogsearch.google.co.it/ping/RPC2

http://blogsearch.google.co.jp/ping/RPC2

http://blogsearch.google.co.ma/ping/RPC2

http://blogsearch.google.co.nz/ping/RPC2

http://blogsearch.google.co.th/ping/RPC2

http://blogsearch.google.co.uk/ping/RPC2

http://blogsearch.google.co.ve/ping/RPC2

http://blogsearch.google.co.za/ping/RPC2

http://blogsearch.google.com.ar/ping/RPC2

http://blogsearch.google.com.au/ping/RPC2

http://blogsearch.google.com.br/ping/RPC2

http://blogsearch.google.com.co/ping/RPC2

http://blogsearch.google.com.do/ping/RPC2

http://blogsearch.google.com.mx/ping/RPC2

http://blogsearch.google.com.my/ping/RPC2

http://blogsearch.google.com.pe/ping/RPC2

http://blogsearch.google.com.sa/ping/RPC2

http://blogsearch.google.com.sg/ping/RPC2

http://blogsearch.google.com.tr/ping/RPC2

http://blogsearch.google.com.tw/ping/RPC2

http://blogsearch.google.com.ua/ping/RPC2

http://blogsearch.google.com.uy/ping/RPC2

http://blogsearch.google.com.vn/ping/RPC2

http://blogsearch.google.com/ping/RPC2

http://blogsearch.google.de/ping/RPC2

http://blogsearch.google.es/ping/RPC2

http://blogsearch.google.fi/ping/RPC2

http://blogsearch.google.fr/ping/RPC2

http://blogsearch.google.gr/ping/RPC2

http://blogsearch.google.hr/ping/RPC2

http://blogsearch.google.ie/ping/RPC2

http://blogsearch.google.in/ping/RPC2

http://blogsearch.google.it/ping/RPC2

http://blogsearch.google.jp/ping/RPC2

http://blogsearch.google.lt/ping/RPC2

http://blogsearch.google.nl/ping/RPC2

http://blogsearch.google.pl/ping/RPC2

http://blogsearch.google.pt/ping/RPC2

http://blogsearch.google.ro/ping/RPC2

http://blogsearch.google.ru/ping/RPC2

http://blogsearch.google.se/ping/RPC2

http://blogsearch.google.sk/ping/RPC2

http://blogsearch.google.tw/ping/RPC2

http://blogsearch.google.us/ping/RPC2

http://feedsky.com/api/RPC2

http://hamo-search.com/ping.php

http://holycowdude.com/rpc/ping/

http://newsblog.jungleboots.org/ping.php

http://ping.blogoon.net/

http://ping.blogs.yandex.ru/RPC2

http://ping.fc2.com/

http://ping.feedburner.com/

http://ping.kutsulog.net/

http://ping.myblog.jp/

http://ping.namaan.net/rpc

http://ping.snap.com/ping/RPC2

http://ping.syndic8.com/xmlrpc.php

http://ping.weblogalot.com/rpc.php

http://ping.wordblog.de/

http://r.hatena.ne.jp/rpc

http://rpc.bloggerei.de/ping/

http://rpc.blogrolling.com/pinger/

http://rpc.icerocket.com:10080/

http://rpc.pingomatic.com

http://rpc.reader.livedoor.com/ping

http://rpc.technorati.com/rpc/ping

http://rpc.technorati.jp/rpc/ping

http://rpc.twingly.com/

http://rpc.weblogs.com/RPC2

http://wasalive.com/ping/

http://www.blogpeople.net/servlet/weblogUpdates

http://xmlrpc.blogg.de

http://xping.pubsub.com/ping/

http://zhuaxia.com/rpc/server.php

If you have any more, please let me know, but it should be a good start for most of you.

Askimet Spam

admin — Wed, 03 Sep 2008 06:08:22 +0000

I always check my Askimet Spam on my blog just in case something accidentally get’s marked as spam. I was checking it a few days ago and ran across a comment that seemed to be pretty decent, the only thing was that the website it was promoting was a spam site full of text-link-ads that obviously is just there for spammers. This wasn’t what actually made me think twice about it actually being spam. In the actual text of the coment, there was no links to give it away, but the fact that in the word “I’m” there was a backslash which was probably a mistype in their html code for the spamming of comments. Anyhow, I learned my lesson and will believe Askimet when I do not know who the commentor is that their filter is probably correct. Just wanted to give you a little first hand experience with the great work that Askimet does as a spam filter.