I've been working with my friend Scott Sheehan on his website 1031investmentservices.com. It's a Joomla website which is new for me but luckily I'm not a programmer on this project (php? yeeks!) but I'm always interested in opportunities to try something new. So what is the purpose of this blog entry, on a blog I rarely write to any more? I think the biggest part of this project is going to be developing the inbound links. One down, hundreds more (hopefully) to go.
Monday, September 23, 2013
Wednesday, February 4, 2009
Google, why do you hate SEO so much?
See the post on GetClicky blog re:Google's new Ajax-powered search results breaks search keyword tracking for everyone.
In a nutshell, the referrers you get from Google SERPs may no longer have the keyword phrase on the query string. So good luck trying to figure out how your customers are finding you!
Posted by
Steve Bywater
at
6:13 AM
0
comments




Labels: rant, SEO, web analytics, web site development
Tuesday, February 5, 2008
Google hearts Cupid
In the past I've blogged about Cupid.com running afoul of Google's mystical algorithm. That's a thing of the past, now it's the first search result for the term "cupid."
Our business model of advertising on local radio means we don't have to play the PPC game or get crazy worried about our Google search results, as long as we do well for branded search. For example, if you search for "online dating", the competition to get on that page is fierce/expensive, and we just haven't engaged in that pursuit.
Today I noticed, however, if you search for "online dating" or even "dating," Google's new "Searches related to" section includes "cupid.com" or "cupid." Very cool. Nice to be finally getting our props, just in time for Valentine's day.
Google, Cupid.com hearts you too.
Posted by
Steve Bywater
at
8:00 AM
0
comments




Labels: Cupid.com, rave, search engines, SEM, SEO, web analytics
Friday, January 11, 2008
VoilaBot, behave!
My websites are in the local advertising space: employment, online dating, business listings. My audience is in the USA, Canada, and Mexico. Because of that, I have no chance of making revenue from traffic from Europe, China, or Nigeria.
So when I see a spider called voilabot, for Voila.fr, pounding my server farm, that's a spider I'd like to disallow. No problem, just add them to robots.txt. Only thing needed is how the bot identifies itself when scanning that file.
Typically, a spider will identify it's useragent and, parenthetically, give a link to info regarding the bot. Voilabot does not, it just points to their homepage:
2008-01-09 05:00:12 GET /robots.txt - - 193.252.149.16 Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+fr;+rv:1.8.1)+
VoilaBot+BETA+1.2+(http://www.voila.com/) - - 200 1100 358 546
which redirects to http://www.voila.fr/, which sucks for me since I don't know French. I am able to find a page on their site about robots.txt, and how to block *all* spiders from visiting my site -- no thanks! I heart Google -- but nothing that mentions what user-agent top specify to block Voilabot.
The Google index, interestingly, includes the robots.txt files they scan. Examining these, some people specify Voila and just as many specify Voilabot. Other Google results include rant like mine -- apparently this bot has been in Beta since 2001.
So Voila.fr Webmaster: please tell us how to block your bot. Thanks!
Update: 1/15/08
No response from Voiala.fr so I'm now denying them at the firewall. If you don't want this bot, I encourage you to do the same.
We've seen it from
81.52.143.15
81.52.143.16
193.252.149.15
193.252.149.16
Posted by
Steve Bywater
at
6:25 AM
4
comments




Labels: rant, search engines, SEO, web site development
Wednesday, July 11, 2007
Duplicate content
We have over 300 local web sites, each advertised on the radio as a local domain. But they all redirect to regionalhelpwanted.com because of 1 thing: Google.
If you have separate domain names that all have significantly similar content, especially if they are all hosted at the same IP, Google's algorithm infers that you are trying to spam the search engine, and all your domains get banned from Google. The broad rule is "duplicate content."
It does not matter that for our business model, separate domain names are completely legitimate. Google has no mechanism to make exception, and no venue to argue the merits of our case.
We learned this the hard way with Cupid.com. Can you imagine: we had tonsvof radio play, but when someone went to Google and searched for Cupid, we were not listed. Not on page 1, or 1000, or anywhere in between. It took us awhile to figure out what they had a problem with, and of course they
don't tell you, but even after we changed our system, it took 9 months for Google to list Cupid.com again.
I guess that's the downside of Google owning the search space: they make the rules and everyone else follows or sits out.
Wednesday, April 18, 2007
How to tell if your website uses 301 redirects
I was at Search Engine Strategies in NYC last week so I'm in an SEO mood. It was a good conference... 90% reenforcement and 10% new stuff. Most of the people there were marketers, not technologists, which is good because they did most of the small talking for me.
One thing Search Engine Marketing people stress is using 301 redirects instead of META REFRESH or 302 "Moved temporarily" redirects. 301 and 302 are HTTP headers. Most web pages send a 200 for normal status. 404 is standard for missing page ("Help! I've lost my 404 page!"). Google and, presumably, other search engines prefer 301 redirects. Why? I guess it intuitively makes sense... they don't want to bother putting something in their index if they think it's not going to be around for awhile.
I know I've made sure both RegionalHelpWanted.com and Cupid.com use 301 redirects. We have a new product, PurplePages.com in beta, though, and I wasn't sure if we coded that correctly. So I needed to check. And I realized most SES attendees probably wouldn't know how to check if their sites use 301 redirects and would have to either learn or trust their coders, so therefore I decided to blog it. It's good for marketing people to not have to rely on coders. Good for all.
You can't just "view source" of a web page to see if it's doing a 301 versus a 302, because by the time you have a web page you've already been redirected. You need something that will interrupt the process. An intermediary browser. A proxy!
In the past I've used Achilles proxy server for this. But I grimace every time I install it or suggest someone install it because it really is crappy. Free software doesn't have to be crappy. Achilles would run for a couple minutes and hang. Awful interface. But it was enough to get the job done. Barely.
Searching for Achilles today to install it on my new laptop, I found that it still hasn't been update but someone else had made a new proxy. Odysseus is the successor to Achilles. I love it-- wish it had come out years ago.
Ummm... if you are using a Mac ( and lots of marketing people do, right?) this isn't going to help you. Feel free to read on anyways. Like I could stop you anyway.
Download it (it's free). Install it. Start it... in your Windows System Tray right click on it and choose IE Settings > Odysseus. Now all your Internet Explorer requests will go through Odysseus. Right click on Odysseus again and choose Configuration. Check Intercept Reply. You can deselect Intercept Request unless you really want to click on the Ok button a lot (although that is great to leave on when use are security testing your site). Right click on Achilles one more time and select Interceptor.
Now navigate to whatever page you want to test. If you left Intercept Request checked then you'll need to click "Ok" for every pages and cookies along the way. Notice that the window title bar will say "Interceptor - REQUEST" for every item you request, and "Interceptor - REPLY" for your response from the web server. To see the status number, click on the Raw tab of a reply. The first line with be something like "HTTP/1.1 200 OK" for a normal page.
For me, I went to HudsonValleyPurplePages.com and got the status "HTTP/1.1 302 Moved Temporarily" as it redirected to http://www.purplepages.com/?osn=1 D'oh! I immediately assigned it to a Web Developer to fix. Then as a sanity check I went to HudsonValleyHelpWanted.com and thankfully it was "HTTP/1.1 301 Moved Permanently" to http://regionalhelpwanted.com/home/1.htm?SN=1&. Whew!
When you are all done, just right click on Odysseus again and deselect Interceptor to turn it off to resume normal browsing.