I am trying to figure out where people are landing when they find my sites through the search engines (MSN, Yahoo, google, whatever...). I have google analytics set up, but I can't seem to figure out where they are landing based on each keyword. I have found that by looking at the entrance points, I can see what keywords landed them there, but I can't go in reverse (i.e. keyword -> landing point). Am I missing something or is this just not possible? Thanks for your help.
try putting in yoursite.com "keyword+keyword" in google or wherever they came from, you should get an idea as to which page shows up the highest for that particular keyword/phrase
Well, that really stinks. I'd like to see where these people are landing based on the keywords they enter. I like being able to see (from statcounter) how individuals are interacting with my site. It's nice to know that someone bothered to see 8 pages, but if I don't know what they were looking for on those 8 pages, how can I expand on that topic?
You could add another counter service to your blog. Statcounter.com offers exactly what you are searching for in their "recend keyword activity" report. You will see which keywords from which engines ended up on which site.
While that's good advice, I'm trying to find a free way of doing that. Statcounter (free version) looks at the last 100 hits. While that's fine if I want to look several times a day, it's not really practical.
Sorry, can't resist: If you have much more data to worry about I would suggest investing the money you have saved by choosing blogspot into a good tracking service ;-) Anyway, you could of course setup your own counter on another server, perhaps by setting up a customized simple script yourself. Analyzing referrers with a regex and saving the results shouldn't take much more than 10-20 lines of code.
Why do you think I chose blogspot? ;-) Although to be honest, I have been thinking about moving off of it. I'm having trouble overcoming the inertia of my original choice, however. Back on topic: I was hoping to find the solution within analytics, though. It seems to have (almost) everything else I needed to keep track of.