Were you excited about the iPhone 5? I was. The phone as a piece of hardware is sleek and snappy. However, you may have noticed that the Push Notifications no longer work on a regular basis. As someone who sort of relies on email for work, it’s more than a little frustrating. Plus, I look like a douche pulling out … Continue reading →

This might be a tad off-topic but I was having some battery issues with my iPhone 4 recently. With a little research I was able to resolve my issues…for now. Here’s how I fixed it. Adjust Time Zone Auto-Set The first thing we need to do is tell the iPhone to stop trying to determine what time zone we’re in … Continue reading →

I’ve done most of the work getting the website looking all fresh and new. I’ll be adding more functionality on a regular basis to hopefully tighten a few things down. I know stuff looks a little janky right now…but I’m working on it.

I’m gonna try to take event notes here and then expand later. Enjoy 8:24 – just finished stale bagel 8:29 – ok. So I’m in the Master Group Training, SEO Track. This is a big reason why I came. First slides I see in the booklet? Title and meta tags…uh oh. 8:40 – I am overdressed 8:54 – intro to … Continue reading →

So I’m currently running an experiment on a student job site called JobDoggy.com. Initially the site had only been a place where we had a few articles and then a search box that led off to another job board site. We implemented a job board API, kept the articles, redesigned the site and relaunched.

At first I saw some positive traffic growth. Nothing spectacular but it was moving in the right direction. Then, a couple of days ago, traffic fell off a cliff. I’m still trying to figure out what’s going on here. My guess is it’s something Panda-related since much of the content is likely available elsewhere on the web. Here’s a screen cap of the Queries report for GWT:

I’ll try to update this post as I uncover more potential causes. If you’ve got some opinions, please share ‘em.

I’ve been thinking a lot about pagination and how to navigate the rel=”next/prev” and canonical tags. I wrote a fairly detailed article about how I think rel=next, rel=prev and canonical tags should be implemented over on the Ironworks blog.

I wanted to re-iterate some of the basic points that article attempts to address here in my own blog.

Do not use the canonical tag to point back to Page 1

I get that the idea is that you might think page=2 is considered duplicate content as the page 1 landing page you want to rank. It’s a valid concern and you might be right to some degree. However, using the canonical tag here just doesn’t do what you think it ought to. Remember that the canonical tag is acting like a redirect a “soft 301″ if you will. Imagine what would happen to a crawler if you used a regular 301 back to the first page every time a crawler hit page 2. See where I’m going with this?

Rel=next/prev are doing the heavy lifting

The Next/Prev tags are actually now performing the function we may have thought the canonical tag was doing for us when it comes to pagination. They’re consolidating all the indexing information into one aggregate. That’s kinda like what we though the canonical tag would do, right? It removes any sense of competition or duplication by creating a sort of “view all” version of the result set for the search engine.

So that’s the short answer. Read the Ironworks article for more details…

So I’ve been using Google+ for a couple days now and Hangouts are quickly becoming my favorite feature. However, there are a couple of ways Google could improve on it and I’ll be more than happy to share them with you… Read More