will site submissions accept URLs with client folder as extension to server name? Done to keep hosting costs down ie www.example.co.uk is cloaked URL to www.otherhost.co.uk/example
redirects and cloaked URLs
- Thread starter dorritj37
- Start date
chaos127
Curlie Admin
- Joined
- Nov 13, 2003
- Messages
- 1,344
I'm afraid I'm confused by your question with the context of the answer you got above.
In case what nea wrote above wasn't clear, in your example above, we would be happy to consider listing www.otherhost.co.uk/example (the real URL) but would not list www.example.co.uk (the cloaking / forwarding URL).
In case what nea wrote above wasn't clear, in your example above, we would be happy to consider listing www.otherhost.co.uk/example (the real URL) but would not list www.example.co.uk (the cloaking / forwarding URL).
my company's website uses a content management software for development to enable 'non-technical' people to update content on our site without messing up functionality and design. Because of this our domain always adds /content to the end of the url when you go to the site. We always use www.companynamehere.com on marketing materials but as i said when you enter that site it adds /content into the address bar. Will this affect our inclusion in the ODP? i have been suggesting our site (without the '/content') for about 8 months or so with no response and i know it takes a while but if i am submitting incorrectly i would like to correct it to begin the process again as soon as possible so as to not lose any more time. Thanks!
Technically, what you describe ("www.example.com", the root domain, to "www.example.com/content", the actual website entry point) is a redirect. But there are big advantages to us to list the root domain anyway. So we do.
Suppose you change your content management system to some other system, that always adds "/index.htm" to the root domain. If we list only your root domain, then our listing still works.
Or suppose you have multiple, equally functional, entry points: example.com or example.com/content/ or example.com/content/index.htm or whatever. If we just list the root (whenever it works), then we won't accidentally list multiple URLs for the same content, just because Eddy editor uses Google search, which shows it as /content/index.htm, while Edie editor uses Yahoo search, which found the /content/default.htm entry point.
That keeps life simpler for us.
It's the cross-domain redirects that we do not list, because they cause us so much difficulties, and the offsetting advantages are so few and rare.
Suppose you change your content management system to some other system, that always adds "/index.htm" to the root domain. If we list only your root domain, then our listing still works.
Or suppose you have multiple, equally functional, entry points: example.com or example.com/content/ or example.com/content/index.htm or whatever. If we just list the root (whenever it works), then we won't accidentally list multiple URLs for the same content, just because Eddy editor uses Google search, which shows it as /content/index.htm, while Edie editor uses Yahoo search, which found the /content/default.htm entry point.
That keeps life simpler for us.
It's the cross-domain redirects that we do not list, because they cause us so much difficulties, and the offsetting advantages are so few and rare.