Christian Ross

Proofreading is hard.

But it’s necessary.

In my Monday morning ‘down a rabbit hole,’ I was looking into a local restaurant for dinner with some friends for this evening. I hit their menu to see if there’s anything that I’d be interested in (there is) and then I got distracted by the rest of their website (as I often do). I ended up on the Blog page wondering just what a local Mexican restaurant might be blogging about these days. Riveting stuff for most of you, I’m sure.

While I applaud the efforts of any business to actually take heed of the recommendations we often give in the web world of, “provide your customers fresh and relevant content on your website,” it was easy to see that this blog has just been farmed out to a content factory to generically produce Mexican restaurant/food related content. I’m not dogging the practice or the effort but it doesn’t take an expert to see this content for what it is — in this case, blog posts written more for the SEO (search engine optimization) purpose of getting Google to send them traffic rather than focusing on content written for humans first.

The reason for me to come to my own blog and point all of this out? Just to note that if they’re going to continue utilizing a content creation company (which I fully applaud the utilization of a good one for a lot of businesses), I’d at least encourage them to proofread or a least loosely scan the content before (or just after) it gets posted on their website.

Case in point:

In their second most recent blog post titled, “How to Tell if You’re Eating at An Authentic Mexican Restaurant in Grapevine Texas,” I find it interesting that they conclude their entire blog post with the following lines, “If you are ready to experience some real authentic Mexican food Grapevine TX, contact us to make a reservation today. It will be our pleasure to serve you our most delicious dishes.”

I only call attention to the fact that they’re pretty clear in the few paragraphs prior, outlining what restaurants a diner should avoid due to the establishment’s inability to be “authentic.” The two that jumped out at me quickly were their points that Mexican restaurants selling ‘queso’ and ‘frozen margaritas’ were obviously inauthentic — and while I’m not here to dispute the authenticity of these statements — I would like to call the attention to their Dinner Menu page where they clearly are not afraid to sell me both queso (multiple types) and frozen margaritas.

Mesa Grapevine - Mexican food gaffe

But hey, something’s better than nothing, right?

If you need me this evening, you can find me dinning at the possibly-authentic Mesa Grapevine while sampling some of their finest queso and frozen margaritas.

P.S. Mesa, happy to give you a recommendation or two for content creation (or at least proofing help) companies if you’d like!

The things we notice

Filed under the category of: Not of any importance but caught my attention none-the-less

While getting a map set up for a client’s contact/location page, I noticed that the Google map about to be used has the same street spelled two different ways on the same city block. Nolen vs. Nolan

I don’t know whether its my weird obsession with typos or just my typical bad habit of pointing out others’ mistakes that prompted me enough to write about it. (more…)

I’ve arrived

In my ever increasing attempt to look as vain as possible to my readers, I wanted to point out that for the first time ever, I have arrived at the number one spot in a Google search for my name.

Myself and some dot-comrades were Jellying today and got on the subjects of online presences and so we all did what any nerd does, we proved our manliness through Google rankings.

I want to thank the academy for this award, Jesus and the Christian-emo rocker from Frisco for all of their help. No thanks to my .com squatter and Myspace, for with their assistance this could have all been obtained at an earlier date.

I’m pathetic.

I Google'd myself. Again.

Open-source code rescues again

It took all of about 24 hours for there to be fixes for the unwarranted iGoogle update. Thank goodness. If you’re using FireFox – and you should be – you would just need to install the Greasemonkey plugin and the newly minted Rockmaster’s iGoogle Sidebar Collapse Greasemonkey script.

If you’re still using Internet Explorer (shame on you), you’re stuck with what you’ve got due to the nature of non open-source code.

Let me know if you give it a shot and have no luck, I can probably walk you through it pretty easily.

A misstep for Google.

Google, you know I have mad love for you. But why in the world would you take up more screen real estate on your latest update to iGoogle? Terrible idea. Terrible. I didn’t even use your tab system before, and now I am forced to. Not a good UI practice from a team with a very good UI reputation.

Here’s to waiting for a Greasemonkey script to set it back to its old self.