Search Engine Optimization

[Vince Clark]

There aren't very many postings about this on the ML. Here is what I have found:

http://www.nabble.com/Apache-server%2C-Tomcat-%2C-SEO-and-302-issue-tf4124891.html#a11739112 
http://www.nabble.com/Users---Search-Engine-Optimization-and-session-IDs-tf1101601.html#a2877375 

Basic questions from a not so "SEO savvy" developer:
1) If we frontend with Apache but hand off all requests to Tomcat (OfBiz) does that really cause a problem with search engine indexing? One of the posts claims there is a problem with the 302 redirect that occurs using the mod_jk connector.
2) If in fact mod_jk uses a 302 redirect and that causes a problem with site indexing, that would lead me to believe that we need to use Tomcat as the web server and use default ports 80 and 443. This creates an annoying but solvable problem if you operate in a Linux environment. Most flavors do not allow binding to 80 and 443 with any user other than root. But I digress.... The question is, by running Tomcat as the webserver os OfBiz "search engine friendly." Will the site be indexed? I must believe that given OfBiz emphasis on eCommerce it is compatible with search engines.
3) The second post I referenced discusses the problem of jsessionid in the URL. Is this really a problem?

Frontending with Apache is really the most desirable solution. We need to power multiple sites from the same backend and we were planning on using Apache name based virtual hosting.



Vince Clark
Global Era
The Freedom of Open Source
[hidden email]
[phone]

[Tim Ruppert]

We have a number of customers who are very search engine savvy and haven't had any issues using OFBiz with an apache web server.

Cheers,

Tim

--

Tim Ruppert

HotWax Media

http://www.hotwaxmedia.com

o:801.649.6594

f:801.649.6595

On Oct 25, 2007, at 4:06 PM, Vince M. Clark wrote:

There aren't very many postings about this on the ML. Here is what I have found: 

http://www.nabble.com/Apache-server%2C-Tomcat-%2C-SEO-and-302-issue-tf4124891.html#a11739112 

http://www.nabble.com/Users---Search-Engine-Optimization-and-session-IDs-tf1101601.html#a2877375 

Basic questions from a not so "SEO savvy" developer: 

1) If we frontend with Apache but hand off all requests to Tomcat (OfBiz) does that really cause a problem with search engine indexing? One of the posts claims there is a problem with the 302 redirect that occurs using the mod_jk connector. 

2) If in fact mod_jk uses a 302 redirect and that causes a problem with site indexing, that would lead me to believe that we need to use Tomcat as the web server and use default ports 80 and 443. This creates an annoying but solvable problem if you operate in a Linux environment. Most flavors do not allow binding to 80 and 443 with any user other than root. But I digress.... The question is, by running Tomcat as the webserver os OfBiz "search engine friendly." Will the site be indexed? I must believe that given OfBiz emphasis on eCommerce it is compatible with search engines. 

3) The second post I referenced discusses the problem of jsessionid in the URL. Is this really a problem? 

Frontending with Apache is really the most desirable solution. We need to power multiple sites from the same backend and we were planning on using Apache name based virtual hosting. 

Vince Clark 

Global Era 

The Freedom of Open Source 

[hidden email] 

[phone] 

[Jacques Le Roux]

De : "Vince M. Clark" <[hidden email]>

> There aren't very many postings about this on the ML. Here is what I have found:
>
> http://www.nabble.com/Apache-server%2C-Tomcat-%2C-SEO-and-302-issue-tf4124891.html#a11739112
> http://www.nabble.com/Users---Search-Engine-Optimization-and-session-IDs-tf1101601.html#a2877375
>
> Basic questions from a not so "SEO savvy" developer:
> 1) If we frontend with Apache but hand off all requests to Tomcat (OfBiz) does that really cause a problem with search engine
indexing?
One of the posts claims there is a problem with the 302 redirect that occurs using the mod_jk connector.

Not really, it's a matter of taste for the 302 vs 301 issue. I still not have a sure opinion about that (choicing one or another)
...

> 2) If in fact mod_jk uses a 302 redirect and that causes a problem with site indexing, that would lead me to believe that we need
to use Tomcat as the web server and use default ports 80 and 443. This creates an annoying but solvable problem if you operate in a
Linux environment. Most flavors do not allow binding to 80 and 443 with any user other than root. But I digress.... The question is,
by running Tomcat as the webserver os OfBiz "search engine friendly." Will the site be indexed?

Yes it will index your products, no worries. But Search Engines are strange beasts (at least Google...)

I must believe that given OfBiz emphasis on eCommerce it is compatible with search engines.
> 3) The second post I referenced discusses the problem of jsessionid in the URL. Is this really a problem?

This has been fixed recently (can't find the version)

Jacques

> Frontending with Apache is really the most desirable solution. We need to power multiple sites from the same backend and we were
planning on using Apache name based virtual hosting.
>
>
>
> Vince Clark
> Global Era
> The Freedom of Open Source
> [hidden email]
> [phone]
>

[BJ Freeman]

Search engine optimization is different the indexing or getting you
links on a search engine.
it has to do with content.
you get so much rating if you had good descriptions.
you get better rating if you have feed back
you get even better ratings if you add some content about products on a
regular basis.


Vince M. Clark sent the following on 10/25/2007 3:06 PM:

> There aren't very many postings about this on the ML. Here is what I have found:
>
> http://www.nabble.com/Apache-server%2C-Tomcat-%2C-SEO-and-302-issue-tf4124891.html#a11739112 
> http://www.nabble.com/Users---Search-Engine-Optimization-and-session-IDs-tf1101601.html#a2877375 
>
> Basic questions from a not so "SEO savvy" developer:
> 1) If we frontend with Apache but hand off all requests to Tomcat (OfBiz) does that really cause a problem with search engine indexing? One of the posts claims there is a problem with the 302 redirect that occurs using the mod_jk connector.
> 2) If in fact mod_jk uses a 302 redirect and that causes a problem with site indexing, that would lead me to believe that we need to use Tomcat as the web server and use default ports 80 and 443. This creates an annoying but solvable problem if you operate in a Linux environment. Most flavors do not allow binding to 80 and 443 with any user other than root. But I digress.... The question is, by running Tomcat as the webserver os OfBiz "search engine friendly." Will the site be indexed? I must believe that given OfBiz emphasis on eCommerce it is compatible with search engines.
> 3) The second post I referenced discusses the problem of jsessionid in the URL. Is this really a problem?
>
> Frontending with Apache is really the most desirable solution. We need to power multiple sites from the same backend and we were planning on using Apache name based virtual hosting.
>
>
>
> Vince Clark
> Global Era
> The Freedom of Open Source
> [hidden email]
> [phone]
>

[SkipDever]

I had an interesting afternoon hooking up an old Windows 3.1 machine to a Novell server for an emergency situation.  I was surprised to see that it all still worked and with 256k of ram.

Holy cow.

[rajsaini]

> Basic questions from a not so "SEO savvy" developer:
> 1) If we frontend with Apache but hand off all requests to Tomcat (OfBiz) does that really cause a problem with search engine indexing? One of the posts claims there is a problem with the 302 redirect that occurs using the mod_jk connector.
> 2) If in fact mod_jk uses a 302 redirect and that causes a problem with site indexing, that would lead me to believe that we need to use Tomcat as the web server and use default ports 80 and 443. This creates an annoying but solvable problem if you operate in a Linux environment. Most flavors do not allow binding to 80 and 443 with any user other than root. But I
You can run tomcat as daemon using Apache JSVC
(http://commons.apache.org/daemon/jsvc.html).Stock Tomcat distribution
has this in the bin directory. In fact you can launch any Java
application as Daemon and chrooting to a normal user.

Thanks,

Raj