Today is a very big day for me, because today is the day when I get to start telling everyone about our latest creation: STAT – Search Tracking & Analytics Tools.

STAT is a comprehensive suite of search analytics tools geared towards the needs of search marketers. Make no mistake: STAT is not another SEO tool, it’s an analytics tool, and it is truly one-of-a-kind.

STAT is ideal for researching competition, tracking organic rankings in the major three search engines (Google, Yahoo, Bing), and monitoring incoming backlinks and indexed pages. Further, with the ability to monitor changes to SERPs in real-time, you can identify algorithm changes when and where they happen. STAT archives past SERPs and audits them in the background to determine key search metrics that affect your rankings. Best of all, STAT does all of this in a drag-and-drop window based interface; it is a web application that looks and behaves like any of your run-of-the-mill desktop applications. Because of the intuitive nature of the platform, using STAT is easy and you can hit the ground running.

After a year of being available only to larger search agencies, I’m proud to announce that STAT is now open to the general public on an invite-only basis. If you want to signup, visit STAT – Search Tracking & Analytics Tools and I’ll send you an invite ASAP.

I could talk ad infinitum about how amazing this platform is, but really, it’s best if you experience it for yourselves. To take it for a test drive, visit STAT and click on the link for a demo.

The code was poorly presented, and poorly formatted. It wasn’t at ALL my normal caliber of work, so I went ahead and rewrote the concept into a tighter little wrapper.

I am using the Gattica gem to interact with the Google Analytics API.

This little script provides a wrapper around the gem that easily allows you to extract your sites organic keywords and sort them based on the number of unique entrances to your site via each keyword.

Enjoy!

http://www.2shared.com/file/3839085/7448ec0a/laptops.html

Situation:
Shared Host
CPanel
No SSH Access

Solution 1: FTP Transfer Folder  to server, Mechanize/CURL Install
Process:

1) Collect variables: database, username, cpanel login, cpanel password, keywords

2) If necessary, create databases and users on CPanel host (using CURL, or Mechanize)

Here is a function I use to create CPanel DBs:
def self.create_db(base_url, cpanel_loc, cpanel_user, cpanel_pass, db, dbuser, dbpass)
agent = WWW::Mechanize.new
agent.user_agent_alias = $USER_AGENTS[rand($USER_AGENTS.length)]
agent.basic_auth(cpanel_user,cpanel_pass)
url = “http://#{base_url}#{cpanel_loc}/frontend/x/sql/”
agent.get(url)
agent.get(”#{url}adddb.html?db=#{db}”)
agent.get(”#{url}adduser.html?user=#{dbuser}&pass=#{dbpass}”)
agent.get(”#{url}addusertodb.html?user=#{cpanel_user}_#{dbuser}&db=#{cpanel_user}_#{db}&ALL=ALL”)
end

3) For each keyword in the keyword list, create a different blog

3a) Write local wordpress-config file with user entered data

3b) Pull a random theme from local theme library

3c) Pull required plugins from local plugin library

3d) Create local folder for blog, copy base wordpress install files, plus files from 3a,3b,3c

4) Begin FTP Transfer of files from master server to destination on install server (Thread this process to speed up)

5) Mechanize/CURL to appropriate Install URL, then Mechanize/CURL through management panel to activate theme selected in 3b and plugins selected in 3c

*Repeat step 3 for each keyword supplied to the function

NOTES: This method, when optimized and threaded, can install about one blog / 90 seconds. The major speed limiting factor is the FTP transferring. A base wordpress install already has a TON of files, and depending on how many plugins and how many themes you are including, the number of files really slows down the FTP transfer. I recommend creating a personal WP base install with ALL of the junk and cruft removed (ie: the management panel niceities like password strength checking etc..). Removing all non-essential files from a wordpress base install can really speed up FTP transfers. This is a good practice anyways, since we want to be as resource efficient as possible, since we’re going to cram this shared server with nothing but blogs.

Solution 2: FTP package file to server, extract through file manager, Mechanize/CURL Install
Process:

1) Collect variables: database, username, cpanel login, cpanel password, keywords

2) If necessary, create databases and users on CPanel host (using CURL, or Mechanize)

3) For each keyword in the keyword list, create a different blog

3a) Write local wordpress-config file with user entered data

3b) Pull a random theme from local theme library

3c) Pull required plugins from local plugin library

3d) Create local folder for blog, copy base wordpress install files, plus files from 3a,3b,3c

3e) Package folder

4) FTP Transfer Package from master server to destination on install server

5) Mechanize or CURL CPanel Filemanager to unzip file on server

6) Mechanize/CURL to appropriate Install URL, then Mechanize/CURL through management panel to activate theme selected in 3b and plugins selected in 3c

*Repeat step 3 for each keyword supplied to the function

NOTES: This method, when optimized and threaded, can install one in about 25 seconds. Once again, the major impediment to speed here is the FTP transfer. This is still a lot faster than Solution 1, and is perhaps the best solution for a situation where you can’t use SSH. I should note that you could also just create one central tarball and then mechanize/CURL the CPanel File Manager to copy and unzip it for each new install, but…I really hate to use that amount of screen automation. It just tends to break down so often.

Situation:
Shared / VPN Server
CPanel
SSH Access

Solution 1: Master Server Central Wordpress Install / Mechanize CURL Install
Process:
1) Upload base Wordpress install files, Theme Library, Plugin Library from master server to central location on install server
2) Create a deployment file that does the following:
2a) Copy base Wordpress install to destination folder using SSH
2b) Set up symbolic links between destination install themes & plugins, with the central libraries uploaded in step 1.
2c) If necessary, create databases and users
2d) Create Wordpress Config file based on information supplied by master server
3) Mechanize/CURL to appropriate Install URL, then Mechanize/CURL through management panel to activate desired theme & plugins.
* For each blog you wish to install, just upload a new deployment file

NOTES: Once you have installed the central libraries, this method is extremely fast.

CONCLUSIONS: At the end of the day, it is definitely faster and more space efficient if you have SSH access through which you can automate the install process. Unfortunately, many shared hosts don’t offer SSH access (some offer it only if you provide some form of government identification). Many people go for shared hosting situations because they are very cheap, low-risk and you can afford to buy many different hosting packages with different IP addresses. For people who are running more sophisticated networks and have greater resources, VPS situations (without CPanel) are preferable, since they are more stable with more available resources, and of course, SSH, which really makes automation a breeze.

Automating the deployment and install of Wordpress blogs can be a really frustrating process to wade through. That said, ..blah….blah…and…gratifying….blah…1000 blogs….blah blah…button click….bla
h…elite spammer…blah blah

I thought I’d take a second to post it here for you all to see.

Enjoy!

BTW: Alex does great video work. He’s one of the most talented and reasonably priced video producers I’ve worked with.

Enjoy!

PS: You may want to view it in full size, since the images don’t look great at this width.

Datapresser.com

Check it out for yourself! You’ll find it at the top of the list in the downloads section.

Have fun!

Visit datapresser.com/signup to register now!

Hurry, space is extremely limited!

**UPDATE: Well thats it! We sold out in just under 30 minutes! Thanks to everyone for their support, and Ill get to approving your accounts right away.

For those of you who are sad you missed the opportunity, go on over to the signup page and add your email to the waiting list. We will be increasing our user base in a few weeks.

THANKS AGAIN!

Anyways, here is a screen shot of what the xml-rpc posting method looks like.
http://img77.imageshack.us/img77/9942/dpressssmu7.png

This method posts content directly to your blog, all with the click of the create button.

The madlib script you see in that demo calls from 6 different databases…just like that!

The black menu you see is the cheat sheet…it has the wildcard names for every database in the system, so all you have to do it highlight and drag it to the text editor…no typing awkward characters.

This test will be ongoing until about the end of November before we shut down for a final overhaul and then go live to the public…..in the meantime, watch the official datapresser screencast: http://www.youtube.com/watch?v=tSdjJjWOoVQ

Datapresser.com is a one-of-a-kind utility that lets you create mad-lib websites out of all the databases available here on Seocracy.com.

Don’t know PHP? Don’t worry about it. With Datapresser, if you can type, you can create a HUGE madlib wordpress site of over 100,000 posts in less then 5 minutes.

If you aren’t sure what a madlib site is, read more about it on Blue Hat SEO

Datapresser.com is currently in private beta. I plan on accepting the second round of beta testers in early November and launching to the public by the end of November.

If you would like to be considered for the second round of beta testing, leave a comment in this post with your Seocracy.com username. I will contact you via your registered email address early in November.

Check out datapresser.com for more info!