I'm looking into the need for an Apache mod_rewrite hack. The most recent information I can find goes back to 2004, and I need something more current.
I own and have been working to build
http://www.panama-guide.com since August 2004 and now have more than 3,700 articles in the database. The site is very popular and regular fans keep returning. I've got more information in one place about Panama in English than any other site on the Internet.
But, Google is not indexing my site well. And, my page-rank goes up and down usually between a 4 and 5.
So, the obvious question is - If I have such a content rich site, how come I'm not getting rewarded in the Google, Yahoo, MSN, (etc) search engine game? I’ve got hundreds of times more and better content than most of the other sites out there (in English about the Republic of Panama) but many other nickel and dime sites are beating me every day in the rankings.
The reason, I'm learning, is because as far as Google and most of the other search engines are concerned, most of the articles on my site simply don’t exist (or, better said) the search engines are not indexing them well.
For example, I've got more than 80 articles in the "Law and Lawyers" topic category. But unless Google happens to index my site while those articles are on the front page they basically don't exist as far as Google is concerned. When I examine the site with spider and crawler simulators they can only “see†the links and articles that are on the homepage. Most of the site is ignored and very poorly indexed.
I know this has been an issue or a problem for years. I feel this should be a critically important issue for the future of Geeklog. Or better said, it’s a critically important issue to me and my continued use of Geeklog. I’m doing everything I can think of to work around this issue - robot.txt files, site maps, site tweaks with IBP and Alrelis, meta tag analysis, etc. Nothing I do works and it can’t work because the problem is apparently built into the Geeklog CMS.
In short, I either have to get it fixed or (unfortunately) migrate to another CMS that has addressed this problem. As much as I like Geeklog, and as much as I don’t want to migrate, I will have to unless I can figure out a work around or fix. I have invested literally thousands of hours in building
http://www.panama-guide.com and I’ve been on Geeklog since day-one. The thought of possibly risking my database by having to go through a migration scares the heck out of me. I would much rather have a Geeklog fix.
Can anyone help? I need an update to the old plug-in/hack from 2004 that I ran into on a demo site somewhere in the past couple of days. It was really little more than a packaged mod_rewrite hack, and it came out at about the 1.3.9 timeframe. I looked at the files but was afraid to stick it into 1.4.1.
And, I don’t know enough to hack the mod_rewrite myself - I've spend days confirming my ignorance. And, I really need to get this fixed.
Can anyone tell me what I need to do? Help! :pray: