Ceon URI Mapping (SEO)

[hockey2112]

Hi,



I don't know what you are talking about. There is no such problem, so you can't have the "same" problem!



The standard rewrite rule already lets index.html through, it is not mapped by Ceon URI Mapping:

# Don't rewrite any files ending with .[xxxxx]
RewriteCond %{REQUEST_URI} !\.[a-zA-Z]{2,5}$

However, in your code you've gone and made Ceon URI Mapping responsible for .html files:



You've done the opposite of what you wanted! (Simply misread the documentation I see).

Remove the modifications you made and just use the normal rewrite rule and things will work as you desire.

You should also upgrade to 3.8.0, it won't make a difference in this case but always best to use the latest version.

I'll upload a version of 3.8.0 to the downloads area shortly, for the minute you can get it from the Ceon website.

All the best..

Conor
ceon

Actually, I have the same thing happen to me. I usually put up an index.html "coming soon" page while the ZC website is still in progress, and that page is passed over in favor of index.php after I install CEON with its pre-packaged settings, thus "activating" the website whether i want it live or not.

[conor]

Hi,

Actually, I have the same thing happen to me. I usually put up an index.html "coming soon" page while the ZC website is still in progress, and that page is passed over in favor of index.php after I install CEON with its pre-packaged settings, thus "activating" the website whether i want it live or not.

Actually, that's not true. What is happening is that after you install Ceon URI Mapping, it becomes responsible for

/

/index.php

/index.php?main_page=

etc.

It is never responsible for /index.html

However, most people will see the root of a site as / so unless they come directly to /index.html Ceon URI Mapping will indeed take over.

Obviously to avoid that you need to add the following exclusion to your rewrite rule:

RewriteCond %{REQUEST_URI} !^/$

However, this means that you can't simply remove index.html to "switch the site live" as "/" would give a 404. You'd have to both remove the index.html file and remove the above exclusion.

Hope that clears things up!

All the best..

Conor
ceon

[hockey2112]

Hi,



Actually, that's not true. What is happening is that after you install Ceon URI Mapping, it becomes responsible for

/

/index.php

/index.php?main_page=

etc.

It is never responsible for /index.html

However, most people will see the root of a site as / so unless they come directly to /index.html Ceon URI Mapping will indeed take over.

Obviously to avoid that you need to add the following exclusion to your rewrite rule:

RewriteCond %{REQUEST_URI} !^/$

However, this means that you can't simply remove index.html to "switch the site live" as "/" would give a 404. You'd have to both remove the index.html file and remove the above exclusion.

Hope that clears things up!

All the best..

Conor
ceon

Thanks for the insight, Conor. This will help immensely!

[Pink]

Google Adwords doesn't like my Ceon URI Link!

I tried to put this link in a campagne:
http://www.feingut.ch/dufte_spa/atherische_ole

Google refused it saying that the URL doesn't work? I do not have any problems to call this page. So, what could be the problem?

I too can see, that google indexed the old pages with URLs like this: http://www.feingut.ch/index.php?main...dex&cPath=35_3. But the new Ceon URLs are not indexed.

Any hints?

[Ethan Kolasinski]

Hello. I had been using Ceon URI mapping very happily on Zen Cart version 1.3.8 for quite some time, and have recently upgraded to Zen Cart Version 1.3.9f. Ceon URI Mapping was not working properly after the upgrade, and I realized at that point my version of URI mapping was not current, so I upgraded to version 3.8.0. I backed up my database and affected files prior to upgrading. Everything seemed to be working fine (rewriting was successful), with the exception of the fact that none of the usernames nor passwords worked any longer on login attempts. I have reversed the process of installing Ceon URI mapping (replacing affected files with old back-up files and also deleting all ceon prefixed files, as well as restoring different databases that were saved prior to upgrading Ceon URI mapping. The login problem still persists. My customers and I are not able to log into our accounts anymore! It's as thought the info is gone.

Is there a place in this sea of discussion pages here that addresses this issue? If so, please direct me there.

Please help! Thanks!

[conor]

Hi Ethan,

The login problem still persists. My customers and I are not able to log into our accounts anymore! It's as thought the info is gone.

Is there a place in this sea of discussion pages here that addresses this issue? If so, please direct me there.

I've replied to you private e-mail to me. Just to reiterate here, this is nothing to do with Ceon URI Mapping, it does not interact with any login functionality of Zen Cart. This must unfortunately be a mistake you made when upgrading from 1.3.8 to 1.3.9f. Hopefully you can find the right answers/support or another thread.

All the best...

Conor
ceon

[Pink]

Google Adwords doesn't like my Ceon URI Link!

I tried to put this link in a campagne:
http://www.feingut.ch/dufte_spa/atherische_ole

Google refused it saying that the URL doesn't work? I do not have any problems to call this page. So, what could be the problem?

I too can see, that google indexed the old pages with URLs like this: http://www.feingut.ch/index.php?main...dex&cPath=35_3. But the new Ceon URLs are not indexed.

Any hints?

Ah, there is a 404 in the access_log:

66.249.66.3 - - [27/Sep/2010:20:33:23 +0200] "GET /dufte_spa/atherische_ole/citronella_kba_5ml HTTP/1.1" 404 41969 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"

But strange, the Link itself works: http://feingut.ch/dufte_spa/atherisc...onella_kba_5ml

Hints?

[conor]

Hi,

Google Adwords doesn't like my Ceon URI Link!

I'm not surprised: Although the link you posted has a page with content, your site is sending a 404 header for this page:

HTTP/1.1 404 Not Found

So Google is treating it as if it doesn't exist.

You need to fix the headers on your site! Make sure you have a proper, working rewrite rule. If that's not it, install the Ceon URI Mapping 3.8.0 module again from scratch (you don't need to delete the database tables, just reinstall the files). If that's not it, then look to see why your server is sending out a 404 header yet Zen Cart is actually loading the expected page!

All the best...

Conor
ceon

[conor]

Hi,

HTTP/1.1 404 Not Found

Just thought it worth pointing out that the only time I saw this before was when someone had a .shtml file responsible for handling 404s.

As they hadn't set up their rewrite rule(s) properly, the URI mapping (say /dufte_spa/atherische_ole) was causing a 404.

The 404 was loading 404.shtml but their Ceon URI Mapping rewrite rule didn't exclude .shtml files as it used the old example condition of

RewriteCond %{REQUEST_URI} !\.[a-z]{2,4}$ [NC]

instead of

RewriteCond %{REQUEST_URI} !\.[a-z]{2,5}$ [NC]

This meant that all 404 pages were being passed onto index.php.

Ceon URI Mapping was then able to run, look at the "/dufte_spa/atherische_ole" URI and map it to the appropriate Zen Cart page.

However, the error was still resulting in the page having a 404 header, even though the content of the page was what was expected.

To fix this you MUST make sure you are using the LATEST example rewrite rule, and that it is working. On your server it is not working as you are redirecting people to a 404, handled by Zen Cart.

All the best...

Conor
ceon

[Ethan Kolasinski]

Hi Ethan,



I've replied to you private e-mail to me. Just to reiterate here, this is nothing to do with Ceon URI Mapping, it does not interact with any login functionality of Zen Cart. This must unfortunately be a mistake you made when upgrading from 1.3.8 to 1.3.9f. Hopefully you can find the right answers/support or another thread.

All the best...

Conor
ceon

Conor, you are right, I am wrong. I bet you've heard that a lot. Anyway, thank you Sir. An explanation of my idiocy will be PM'ed to you, in addition to your well deserved "cups o' coffee".

Thanks!