The new solution (WordPress) is fabulous, but now I have a couple hundred inbound links that are broken. Trying to get all of the links updated by the other sites was a losing proposition, so my next step was to put some 301 redirects into my friendly neighborhood .htaccess file and transfer all the link love to the new pages.

Easy (normal) 301 redirects via .htaccess
Normally, a 301 redirect in your .htaccess file would look like this:
Redirect 301 /old/url.shtml http://domain.com/new/filename
or if we’re being fancy…
RewriteEngine on
RewriteBase /
RewriteRule ^old/url.shtml$ new/filename [R=301,L]

Normally, the examples above are perfect for redirecting incoming links from old, defunct pages to the new, correct location of the file. The problem I ran into is that my pages were dynamically generated; i.e., they all shared the same URL, and which review was presented to the user was determined by an argument passed in the URL after the file extension.
http://www.domain.com/cgi-bin/script.cgi?review=bobs_shrimp_hut

To address this, I figured I would just include the argument in the pattern that the RewriteRule tries to match, and make sure that I remembered to escape the question mark after the file extension since question marks are special characters in regex.
RewriteEngine on
RewriteBase /
RewriteRule ^cgi-bin/script.cgi?review=bobs_shrimp_hut$ restaurants/bobs-shrimp-hut [R=301,L]

Looks right… but nothing happened. Like, nothing-nothing. It didn’t return a 500 Server Error, which would have let me know I screwed something up, and it also didn’t even attempt to rewrite the URL. When I tried the original (old) address, I got a 404. :(

Since my .htaccess file already had a number of other RewriteRules that were executing correctly, I ruled out the possibility that the .htaccess file wasn’t being read. To test my assumption, I tried removing the argument portion from the rule (the question mark and everything after it).
RewriteRule ^cgi-bin/script.cgi$ restaurants/bobs-shrimp-hut [R=301,L]

Okay, that worked. We’ve confirmed the .htaccess file is being read and things are working correctly. The only problem with this solution is that this rule will fire every time any of the reviews are accessed, regardless of the argument, and will always rewrite as “restaurants/bobs-shrimp-hut”. Great exposure for Bob’s Shrimp Hut, but not cool if you were expecting to find Chez Francois or Chuck’s Cheese Chalet.

Let’s RTFM!
After re-reading the Apache documentation on the Mod_Rewrite Module, I found this in the RewriteRule Directive section:

What is matched?

The Pattern will initially be matched against the part of the URL after the hostname and port, and before the query string. If you wish to match against the hostname, port, or query string, use a RewriteCond with the %{HTTP_HOST}, %{SERVER_PORT}, or %{QUERY_STRING} variables respectively.

Crap. The part of the URL after the hostname and before the query string is identical for all 200 restaurants. The query string is what I HAVE to match.

Alrighty, so the manual says I need a RewriteCond if I want to match anything against the QUERY_STRING (argument). So I tried the following:
RewriteEngine on
RewriteBase /
RewriteCond %{QUERY_STRING} ^(.*)bobs_shrimp_hut$
RewriteRule ^cgi-bin/script.cgi$ restaurants/bobs-shrimp-hut [R=301,L]

And it worked! Mostly. The rewritten URL looked like this:
http://www.domain.com/restaurants/bobs-shrimp-hut/?review=bobs_shrimp_hut

So we’re 98% of the way there at this point. Realistically, this is still a success as far as the user is concerned because the link does redirect to the new page successfully. It’s just ugly and will cause some canonical issues for the engines.

So I RTFMd some more, and a little further down the page, I found this:

Modifying the Query String

By default, the query string is passed through unchanged. You can, however, create URLs in the substitution string containing a query string part. Simply use a question mark inside the substitution string to indicate that the following text should be re-injected into the query string. When you want to erase an existing query string, end the substitution string with just a question mark. To combine new and old query strings, use the [QSA] flag.

Eureka! So now my .htaccess looks like this:
RewriteEngine on
RewriteBase /
RewriteCond %{QUERY_STRING} ^(.*)bobs_shrimp_hut$
RewriteRule ^cgi-bin/script.cgi$ restaurants/bobs-shrimp-hut? [R=301,L]
which gives us
http://www.domain.com/restaurants/bobs-shrimp-hut
YAY!

The only downside to this method of redirection is that there has to be a separate RewriteCond/RewriteRule pair for each argument I need to redirect. This is only because I failed to use a consistent naming scheme. If I had thought ahead when I set up the original script, I probably would have named the files differently and wouldn’t be having this problem now.

If the names were consistent between the old script and the new solution, I would have been able to do something like this:
RewriteEngine on
RewriteBase /
RewriteCond %{QUERY_STRING} ^review=(.*)$
RewriteRule ^cgi-bin/script.cgi$ restaurants/%1? [R=301,L]
%1 retrieves a captured value from the RewriteCond. $1 (more commonly seen) retrieves a captured value from the first part of a RewriteRule. This single Condition/Rule pair would have handled all of the dynamic URLs from the old script and redirected them to their new homes.

Okay, that’s it for the .htaccess tonight. My head feels like it’s going to explode.

Post from: Cshel Chicago SEO, Web Development

Mod_rewrite doesn’t look at arguments? D’oh!

No related posts.

Btw, I should probably mention that I did all of this development on a completely different domain.

So anyway, as I’m dangerously close to the point where I can flip the switch and turn the new site on, it occured to me that I’m not entirely sure what the best way is to go about doing it… so I’m asking for advice from those of you who know WordPress far better than me.

The Options

Option 1

1. Backup existing site
2. Rm -rf * the entire directory to make sure it’s good and clean
3. Install fresh copy of WordPress with fresh new database
4. Export the contents of the development site using WP’s export feature.
5. Copy the theme off the development site and upload onto the production server
6. Turn theme on
7. Import the file created by the export into the production WP.

I *think* that should work. I think.

The problem is that I have a couple of plugins (remnants from one of the two smaller WPs I had been using on the frankenstein site) that lose tables and data everytime I do the export/import thing because they have all sorts of extra tables associated with them. I won’t *die* if I have to start over with no historical data on those few plugins, but I’d like to avoid it.

Hence, option 2…

Option 2

1. Back up existing production site.
2. Rm -rf * the whole directory to make sure it’s good and clean for the new WP install.
3. Install WordPress fresh, but point the DB at the one currently in use by the development site.
4. Copy the theme files from the development site and put them on the production site and turn on.
5. Fix whatever is broken in the DB to make it work on the new domain.

I guess my hangup on going with option 2 is the “Fix whatever is broken in the DB to make it work” as I don’t know exactly what will break or how much of a migraine it will cause to try to fix it.

So is there anyone who’s done this before? Advice? Suggestions?

Thanks in advance for the help!

Post from: Cshel Chicago SEO, Web Development

Question for WordPress Gurus…

No related posts.

So why would you want to start a social network?
In addition to adding coolness and generating additional traffic for your site. Branded social networks help build your brand by creating a community for your users and fans. The users connect with other like-minded people and while bonding with each other… they emotionally bond with the brand… that turns users into fans and fans into brand evangelists.

Let’s not forget that a social network also creates additional ranking opportunities for your site. More content, more potential spots to occupy on the SERPs.

So why is Lovd so special?
Lovd is a) really cool looking and fully featured right out of the box, b) FREE, c) open source, and d) supposedly very easy to install and run — if you’re familiar with Ruby On Rails. I say supposedly only because I am absolutely NOT familiar with RoR, and will have to defer to Steve’s expert opinion on that topic.

If you’re interested in adding a unique facet to your site, and you (or a geek you love) are familiar with Ruby on Rails, go check out Lovd — check the system requirements, demo, features, etc — then download it and give it a spin. It’s open source and you can’t beat the price :)

Post from: Cshel Chicago SEO, Web Development

SEO 101: Starting Your Own Social Network

No related posts.

Now that I’m in the process of setting up my new laptop, I’m availing myself of the opportunity to examine what I have installed on my desktop and deciding if the plugins and various programs I have are useful enough (or just plain used enough) to bother installing on the laptop. (Note to self: Probably wouldn’t be a bad idea to go through the closet and do the same thing with clothes and shoes… seriously, when *was* the last time I even looked at that purple tweedy houndstooth suit?)

What Plugins Do I Have?
Here is what’s currently on the desktop. The desktop is the machine on which I am prone to installing all kinds of various crap, so the odds are I am stuff installed that I can’t even remember why I downloaded it. The plugins listed in bold not only made the cut and are being installed on the new baby, but would also make my list of “cannot live without”.

1. Colorzilla: I love this tool. When I’m working with picky designers who just MUST have a color exactly so, it completely takes the guess work out of finding the exact hex code.
2. DT Whois: Eh, I tend to use other tools or sites. This isn’t a bad plugin, I just don’t seem to ever use it.
3. Facebook Toolbar: I’m still on FB, just not as much lately — bitten by one too many werewolf-zombie-ninjas, you know?
4. Google Toolbar: There’s nothing this tells me that some of the other plugins don’t tell me.
5. Header Spy: Displays header info right at the bottom of the browser window as you’re meandering about the web. Very handy.
6. Live HTTP Headers: This is really helpful for seeing redirect codes.
7. Search Status: This one pops a little PageRank bar, an Alexa bar and a Compete bar onto the bottom of the browser window and automatically checks the domain/page you’re viewing. It’s cute. I like it.
8. SEO for Firefox: I feel lost and confused when I’m using machines that don’t have this installed. It highlights nofollowed links, collects all sorts of useful info about each SERP and displays it underneath the result right on the page. I could go on and on. Just go get it.
9. SEOpen: Similar to the SEO Book Plugin, so there is some redundancy, but I still like it and it’s going on the laptop.
10. Stumbleupon Toolbar: Makes my life easier. It stays. :)
11. Twitbin: I don’t even know why I installed this. I don’t think I ever used it.
12. Twitterfox: Keeps the busy-bodies at the office from noticing (and commenting about) how often I check Twitter :)
13. ViewRenderedSource: This is pretty neat if you like to view the source code. I don’t think words can do it justice, so go take a peek. It pretties up the code and just generally makes it easier to read.

If anyone has any other SEO or web development related plugins they can’t live without, please leave a comment and share!

Post from: Cshel Chicago SEO, Web Development

Firefox Plugins I Can’t Live Without (Updated)

No related posts.

It is a pretty site… too bad it’s all Flash.

I’m not even entirely sure what to say here. I mean, can you honestly say your business provides search engine optimization services when you sell websites that are built entirely in Flash and, literally, the ONLY two links on the WHOLE site that a spider can see go to YOUR site… not a site that has anything to do with the client?

It is a pretty site… too bad it’s all Flash, but it’s nice to look at none-the-less. Check out the site in Lynx though. There’s hardly anything there at all.

Check out the site in Lynx. There's hardly anything there at all.

Holy Mackerel! is a seafood restaurant… you wouldn’t know that from the Lynx screenshot though. Seafood is in the domain, so I guess that’s helpful; however, it might be more helpful to have the title tag say something like “Holy Mackerel! Seafood – Lombard, IL” or maybe even add in “Restaurant” after Seafood. Just “Holy Mackerel!” isn’t descriptive enough. The page is pretty crystal clear about the location, which is good, but you still don’t really know this is a seafood place if you can’t see the Flash.

Now look at the source…
Even operating under the assumption that the client is completely IN LOVE with the Flash site… which they’re entitled to be, it’s a very slick site… one would still think that a company who SEOs the crap out of the links to THEMSELVES might take some time to consider the needs of the client when putting the design together.

Things that make you go hmmmmm.

A few things that struck me as odd…
(A) One might think that the name of the hotel in which the restaurant is located might be a good opportunity for a link to — oh I don’t know — the hotel. Maybe that’s more of a “good neighbor” type of link. I know I’d find it useful *shrug*, but I guess we can let this one slide…

(B) Actually having some anchor text where the mailto: link is might make the link functional.

(C) It’s easier to rank for terms like “restaurant” when you spell “restaurant” correctly (and maybe have it on the page more than once).

(D) Clearly someone there knows something about SEO. Pity they didn’t use their mad skillz to SEO the client’s website.

So why am I picking on this site?
For one thing, this supports my previous post about double checking the work that your vendors do to make sure you’re not getting screwed. I realize there’s more to SEO than just on-page stuff, but it’s not THAT hard to make some minor changes to this page so that it looks like someone at least tried. Further, it wouldn’t have annoyed me so much if the links to the developer weren’t *SO* SEOd. So it’s not like they don’t know how, you know?

The other thing that bugged me is that I have a general dislike for using your client’s website to promote yourself. Just a personal thing. I know as a client, if I’m paying the vendor good coin for the work, I don’t want to have to give them free advertising, too. Maybe if they cut me a break on the cost we can discuss it, but for the most part, I want the site to be about my business, not theirs.

Post from: Cshel Chicago SEO, Web Development

Holy Mackerel! You call that SEO?

No related posts.

Here’s what happened. I vaguely recalled the name of the place being “Anthony Vince” something or other. So verily, I go to Google and search for “Anthony Vince Salon” and here’s what comes up…

Well. Okay. The name is right… but from the description it looks like it’s a multimedia development company that needs to go back to fifth grade and learn to spell “professional”… I have a sneaking suspicion I know what happened here, so I clicked on through to check out the site.

Oh look! It is indeed a salon/spa and not, in fact, a multimedia development company who can’t spell professional right. Next, just for giggles, I took a peek at their source code.

Aside from the glaring issue with the meta description being a self-serving plug for the illiterate multimedia developers — oh and the keywords too — there were the usual problems with making the site look pretty but completely ignoring/not caring about how the bots see the code. No H1 tags, no H-anything tags, no emphasis, no nothing. Yes, CSS is way kewl; however, the ability to convey emphasis and importance directly within the HTML is available for a reason. Digging further into the site, every page has the exact same title/description/keywords, a lot of the good content is flash so it’s useless anyway, and to top it off, the site hasn’t been updated in like 4 years.

So why pick on the poor saps?
I felt like this is a perfect example of why it’s important to know enough about what you’re doing in terms of your online marketing to be able to double check your developer’s work. No one expects you to know your business AND be a world class web developer. If your primary job function is NOT search engine marketing, no one expects you to be the world’s foremost authority on that either. That is still no excuse for not bothering to learn enough about what you’re paying people to do to know if they’re half-assing the project or just plain incompetent.

And the moral of the story is…
How do you *know* your consultants know what they’re doing? Ask the other people they’ve done projects for? Okay… sure… but ask them WHAT? How do you know which questions to ask if you don’t know what it is you want or need? If you do have a defined goal, but you really have zero idea how to reach said goal, what will you do then? Just let other people fret about the technical, voodoo magic details. Mmmmm… no. Bad idea.

Seriously… if you’re going to spend a ton of money on, let’s say, an engagement ring, you’re going to spend a few weeks learning about how to tell a bad diamond from a good diamond, a cheap setting from a high quality setting, etc. A cubic zirconium LOOKS pretty, but you’re spending money on a diamond and you want to know you’re not getting ripped off. Apply the same logic to your web projects.

Learn enough to know that you’re getting quality work out of your vendors and consultants.

Post from: Cshel Chicago SEO, Web Development

Double Check Your Web Developer’s/SEO’s Work

No related posts.

Post from: Cshel Chicago SEO, Web Development

Search Friendly Site Architecture on Beginning SEO Podcast

No related posts.

Thanks to Brian and Dave for having me on again!

Post from: Cshel Chicago SEO, Web Development

Using RSS to create dynamic content for SEO

No related posts.

So how did I fix it? Much like I write my greeting cards :) I found a functional theme and copied a line of code out of the working theme to replace the line of broken code in the broken theme… Voila! Old theme now functional.

Post from: Cshel Chicago SEO, Web Development

WordPress theme fixed. Yay.

No related posts.

Post from: Cshel Chicago SEO, Web Development

WordPress Upgrade == Icky

No related posts.