Search Results for: seo analysis

SEO Advice: linkbait and linkbaiting

(just a quick post.)

On a meta-level, I think of “linkbait” as something interesting enough to catch people’s attention, and that doesn’t have to be a bad thing. There are a lot of ways to do that, including putting in sweat-of-the-brow work to generate data or insights, or it can be as simple as being creative. You can also say something controversial to generate discussion (this last one gets tired if you overuse it, though). Sometimes even a little bit of work can generate a reason for people to link to you.

Example 1: Danny Sullivan actually sat down and checked the spam filtering accuracy of SpamCop, Yahoo Mail, and Gmail. And not once or twice, but three different times. Personally, counting false positives in your Spam folder would annoy me to death, but putting in that work generates insights on the differences between the competing services. Admittedly, the results will vary by individual, but as the great Fred Brooks would remark, often some data is better than no data at all. Now Danny doesn’t need any more links than he already has, but it’s producing info-laden content that makes a site or blog well-known over time.

Example 2: You can be creative. I’m happy to link to Marc Hil Macalua for a creative app that he wrote in which you can vote on head-to-head battles between SEOs. The Ning service attempts to make it easy for people to write social web apps, so this is a really easy app to create: just drop in your own photos and you’re good to go. Now did Marc do a ton of work? Well, a little bit, but not a ton. But he had that creative insight of something that would grab people’s attention and generate discussion. By the way, it looks like someone is click-spamming on DaveN’s behalf. 😉

Example 3: Saying something controversial. You can be cheeky, like Threadwatch, or you can be incredibly earnest. I give the creator of Google Watch credit for staking out the “anti-Google” territory way before anyone else. Later, Andrew Orlowski probably realized that taking potshots at Google or blogs was a way to generate lots of discussion. By the time it trickles down to sites like FuckedGoogle or whatever, it gets to be “done”–that niche is starting to be tapped out. So how do you take a new approach?

Example 4: Back to something creative: the Google: Evil or Not? site. The site takes RSS feeds that mention Google, lets people vote between Real Good or Real Evil, and adds a graph. It took a little bit of work, but probably not a ton. How much work would it be to extend that to another subject, like graphing the mojo levels at the Yahooplex as it waxes or wanes?

Linkbaiting sounds like a bad thing, but especially if it’s interesting information or fun, it doesn’t have to have negative connotations. I hereby claim that content can be both white-hat and yet still be wonderful “bait” for links (e.g. Danny’s spam email analysis). And generating information or ideas that people talk about is a surefire way to generate links. Personally, I’d lean toward producing interesting data or having a creative idea rather than spouting really controversial ideas 100% of the time. If everything you ever say is controversial, it can be entertaining, but it’s harder to maintain credibility over the long haul.

SEO advice: url canonicalization

(I got my power back!)

Before I start collecting feedback on the Bigdaddy data center, I want to talk a little bit about canonicalization, www vs. non-www, redirects, duplicate urls, 302 “hijacking,” etc. so that we’re all on the same page.

Q: What is a canonical url? Do you have to use such a weird word, anyway?
A: Sorry that it’s a strange word; that’s what we call it around Google. Canonicalization is the process of picking the best url when there are several choices, and it usually refers to home pages. For example, most people would consider these the same urls:

  • www.example.com
  • example.com/
  • www.example.com/index.html
  • example.com/home.asp

But technically all of these urls are different. A web server could return completely different content for all the urls above. When Google “canonicalizes” a url, we try to pick the url that seems like the best representative from that set.

Q: So how do I make sure that Google picks the url that I want?
A: One thing that helps is to pick the url that you want and use that url consistently across your entire site. For example, don’t make half of your links go to http://example.com/ and the other half go to http://www.example.com/ . Instead, pick the url you prefer and always use that format for your internal links.

Q: Is there anything else I can do?
A: Yes. Suppose you want your default url to be http://www.example.com/ . You can make your webserver so that if someone requests http://example.com/, it does a 301 (permanent) redirect to http://www.example.com/ . That helps Google know which url you prefer to be canonical. Adding a 301 redirect can be an especially good idea if your site changes often (e.g. dynamic content, a blog, etc.).

Q: If I want to get rid of domain.com but keep www.domain.com, should I use the url removal tool to remove domain.com?
A: No, definitely don’t do this. If you remove one of the www vs. non-www hostnames, it can end up removing your whole domain for six months. Definitely don’t do this. If you did use the url removal tool to remove your entire domain when you actually only wanted to remove the www or non-www version of your domain, do a reinclusion request and mention that you removed your entire domain by accident using the url removal tool and that you’d like it reincluded.

Q: I noticed that you don’t do a 301 redirect on your site from the non-www to the www version, Matt. Why not? Are you stupid in the head?
A: Actually, it’s on purpose. I noticed that several months ago but decided not to change it on my end or ask anyone at Google to fix it. I may add a 301 eventually, but for now it’s a helpful test case.

Q: So when you say www vs. non-www, you’re talking about a type of canonicalization. Are there other ways that urls get canonicalized?
A: Yes, there can be a lot, but most people never notice (or need to notice) them. Search engines can do things like keeping or removing trailing slashes, trying to convert urls with upper case to lower case, or removing session IDs from bulletin board or other software (many bulletin board software packages will work fine if you omit the session ID).

Q: Let’s talk about the inurl: operator. Why does everyone think that if inurl:mydomain.com shows results that aren’t from mydomain.com, it must be hijacked?
A: Many months ago, if you saw someresult.com/search2.php?url=mydomain.com, that would sometimes have content from mydomain. That could happen when the someresult.com url was a 302 redirect to mydomain.com and we decided to show a result from someresult.com. Since then, we’ve changed our heuristics to make showing the source url for 302 redirects much more rare. We are moving to a framework for handling redirects in which we will almost always show the destination url. Yahoo handles 302 redirects by usually showing the destination url, and we are in the middle of transitioning to a similar set of heuristics. Note that Yahoo reserves the right to have exceptions on redirect handling, and Google does too. Based on our analysis, we will show the source url for a 302 redirect less than half a percent of the time (basically, when we have strong reason to think the source url is correct).

Q: Okay, how about supplemental results. Do supplemental results cause a penalty in Google?
A: Nope.

Q: I have some pages in the supplemental results that are old now. What should I do?
A: I wouldn’t spend much effort on them. If the pages have moved, I would make sure that there’s a 301 redirect to the new location of pages. If the pages are truly gone, I’d make sure that you serve a 404 on those pages. After that, I wouldn’t put any more effort in. When Google eventually recrawls those pages, it will pick up the changes, but because it can take longer for us to crawl supplemental results, you might not see that update for a while.

That’s about all I can think of for now. I’ll try to talk about some examples of 302’s and inurl: soon, to help make some of this more concrete.

css.php