Welcome to WebmasterWorld Guest from 188.8.131.52
Forum Moderators: open
<snip> see profile
[edited by: engine at 4:21 pm (utc) on Oct. 28, 2002]
[edit reason] Please use the profile [/edit]
Welcome to WebmasterWorld. [webmasterworld.com]
I was smart and I optimized my site to enhance the end user experience and Google cut me out.
We have a few jsp driven sites
Yesterday, we had a big storm in Berlin and that didnīt affect my Google ranking, so I do not think Google has a problem with storms in Germany.
<added>gsx beat me to it.</added>
Considering I had a #1 ranking, you know that my sites were worthwhile. I did not employ any tricks (never have and never will) to get those rankings. Although I am an adult webmaster, I am 100% honest (we tend to have bad reputations for understandable reasons).
What you're serving up to the GoogleBot is not the same as what you serving up to your regular visitors. This could easily be viewed as a way of cloaking. Were you banned from Goole?
Further more, if you use PERL you'll end up worried about CPU usage rather than bandwidth usage.
If I were you, HQ, I'd revert back to the content that gave you your #1 in Google. Get it in there before the next major spidering, which is probably imminent. One of the cardinal rules of SEO is if a page is working well, don't mess with it!
Jump over to Search Engine World and use their SE Spider Tool to see if your pages are follow-able.
The real reason I used JS was to make my page smaller and faster to load. Plus it made my gallery modifications much much easier. With 85 categories I can now just go in and add one more categories and new tables are created automatically. My JS code is more advanced than your average newbie! :)
I do not know if I was banned from Google. How can I tell? What I was serving to Google is 100% THE SAME as what I server to my visitors. Google is just not intelligent enough (yet) to realize it.
Do not worry about Perl and CPU usage. I would not create the same page via Perl code for every visitor. I would only run the Perl code whenever I updated the page.
Because the opposite is true: Non-server side in not interprated as regular HTML and is IGNORED.
To quote you:
"The site looked the same to the end user" - but completely different to a spider
HQ, if you're so advanced... ah, forget it.
You might consider on-the-fly content generation using PERL and an Apache Server. That combination works rather well. The concept is simple. The first time an HTML page is hit/requested, the PERL CGI script is executed and the HTML page is written. From that point on the Apache server serves up the written HTML page. But, I'm sure you already know this.
Dont settle for for 2nd best..they have the talent, and the money to beable to fix that problem..and is is their problem not yours..
Google is the problem, not my intelligence. I knew that my JS would harm my Google rating. If you are trying to say that I did not know this (?), then you are wrong.
My point is that it sucks that Google does not parse JS and I want to draw attention to it.
"Because the opposite is true: Non-server side in not interprated as regular HTML and is IGNORED."
I already know this. Nothing you have said is news to me. I think I confused you or you did not understand what I was saying. (I was not trying to start a flame war in my first thread.) This thread has nothing to do with my lack of knowledge in this area. I 100% fully understand server side and client side issues. I was just asking a question because I did not understand where you were coming from and wanted you to clariy it. If you thought that I did not understand all of what you have said, then I apologize.
[edited by: HQ_Webmaster at 1:23 am (utc) on Oct. 29, 2002]
[edited by: Marcia at 6:01 pm (utc) on Oct. 30, 2002]
[edit reason] Please stay with issues without getting personal [/edit]
"You might consider on-the-fly content generation using PERL and an Apache Server."
Yes I do already know this. I wrote in this thread somewhere before that I could do this. The problem with this? I have to use my server and my server's resources plus more bandwidth and thus a slower site. It is not fun. I am in a no-win situation.