Developer forum

Forum » Development » SEO url on eCom item?

SEO url on eCom item?


Reply
With the newest release (19.2.0.2) the new feature regarding SEO urls on productlink dosent work if you've to lowercase url (backend option) :(

Did someone at DW (or DW SEO)  ever check out "best practice" on urls???

http://www.seomoz.org/blog/11-best-practices-for-urls

I think not!?

/Morten

Replies

 
Reply
Hi Morten,

Are you talking about using URL providers (Management Center -> Web and HTTP -> Customized URLs, "Add-ins" under the "Internal links" section).

Or you just use the META URL field of the product (Edit product -> Meta information -> URL)  ?

Could you please elaborate? It would be great if you could provide a set of steps that might help us to reproduce the problem.

-- Pavel
 
Reply
I'm talking about using URL providers (Management Center -> Web and HTTP -> Customized URLs, "Add-ins" under the "Internal links" section).

Have a look at the attached screendump...

If you choose to check "Case insensitive URLs" the new so called seo friendly product url dosent work any longer.
If you uncheck - it works.

What im really confused about is how DW allows uppercase urls? I dont get it!? You can also have url containing special chars - why dosent someon at DW ready this article :

http://www.seomoz.org/blog/11-best-practices-for-urls

Everything i lowercase + get rid of special chars in urls :)

If my custom choose to have a product called:
"Super @£$€{[]}|~€ÆØÅæøåæø"
the url DW makes is called:
Super-@£$€{[]}-~€ÆØÅæøåæø.aspx
#wtf  - this is far away from a seo-friendly url...


/Morten
Untitled-1.png
 
Nicolai Høeg Pedersen
Reply
Hi Morten

Thanks for your feedback.

I will have a look at the uppercase issue.

Why no special characters in the URL? They are allowed (http://labs.apache.org/webarch/uri/rfc/rfc3986.html) and if the name of the product is a lot of weird characters it makes perfect sense to use it as name, titel and url...
 
Reply
@Nicolai: Yes it makes sense but Im sure that robots understand "å" written as "aa" as well!?

We are having a lot of issues with specials chars in news (from
DW) shared (and then encoded) on facebook, twitter and so on.

Thats why i would avoid em. Maybe I could be an option.

Have a look on the attached screenshot from my iphone. Good or no good?
foto.png
 
Nicolai Høeg Pedersen
Reply
We could make it an option - but it is not without issues. Will look into it.

You can just write the URL with the ø - the browser will convert it to utf-8 in the transport level. That will work - even on the iPhone.
 
Reply
Sweet...

Actually the URL are written with an "ø" but if you're sharing the URL with other browsers that IE the URL are replaced/encode by the mozilla webkit :

IE:
http://www.dynamicweb.dk/Hjælp-og-Support-28883.aspx

FF, Chrome, Safari:
http://www.dynamicweb.dk/Hj%C3%A6lp-og-Support-28883.aspx


 
Nicolai Høeg Pedersen
Reply
Well - because you have old browsers... Or weird settings.
:)
See dump with Safari, Chrome and Firefox.
SafariChromeFirefox.PNG
 
Reply
Try to copy the urls to notepad!?
 
Nicolai Høeg Pedersen
Reply
Yes...

But - you can just replace the crap with characters. Or use the fields in Dynamicweb to overwrite the auto URL.

In terms of SEO - using the real characters is definitely a benefit. But - I'll look into the option of "replace evrything not in a-z and 0-9"
NotepadCopy.PNG
 
Reply
 
Replacing something like å with aa would be simple, but there are many other characters to consider and many of them will be more difficult to handle.
 
Here are some ideas about how it COULD be done...
 
DW could load (and cache) a configuration file that contains rules for character replacements, as is done in Wordpress... http://www.michael-ostergaard.dk/fjern-problemet-med-aeoeaa-i-dine-urler-i-wordpress
 
DW could have yet another checkbox for making the URL field mandatory and prefilled with all special characters replaced. The user should then be warned (and not able to save the page/item) if there is a URL conflict with another page/item. I don't know if that is possible at all.
 
However, no matter what approach is taken, replacing characters could cause more problems than it solves.
 
Before making any "nice to have" features in the URL handling, here are some issues that i think should be solved first :) ...
 
The "Replace spaces with..." does not work on all URL formats
- Page name and ID = No replace
- Page name and ID parameter = No replace
- Location and page name = OK
 
A page named something like "Pros / Cons" (slash with surrounding spaces) results in a .NET exception when you click on the link (URL format: Page name and ID). Replacing the spaces with dashes in the URL makes it work.
 
(19.2.0.4)
 
 
BR.
Morten
 
Nicolai Høeg Pedersen
Reply
Hi Morten

I'll have your issues checked out by QA and file a bug.
 
Reply
Bugs registered:

5922: Product catalog group list navigation broken when using ecom URL addins in combination with case insensitive URLs.

5893: In customized URLS of the types "Page name and ID" and "Page name and ID parameter" spaces are not replaced with an "-".
 
Reply
Hi,

I've run into a couple of other problems with SEO URLs on eCommerce products and groups.

First of all, I have five languages, default language for my web site is LANG1, however, group names from LANG2 are used for links, so my Danish links have Swedish "folder" names.

Another thing, Dynamicweb doesn't seem to be able to parse ProductID's containing spaces. Thus, the link to my product ID = KSI 160 95-02 is simply parsed as Produkter/Kylskåp.aspx?ProductID=KSI 160 95-02 (note the Swedish caption) rather than Produkter/Køleskabe/KSI 160 95-02.aspx.

Using a PRODXX product id works fine, however, this solution is integrated with AX, and we BOM lists from CSV based on the AX ID, so converting to Dynamicweb eCommerce IDs is not an option.

Could you fix this as well?

BR.
Lars
 
Nicolai Høeg Pedersen
Reply
Yes - that can be fixed.

Will look into it.
 
Reply
Excellent, let me know, if you need me to do some testing, or if you need files/database for the solution on which I'm experiencing problems. I'd be happy to chip in.

BR.
Lars
 
Reply
 Today, i recieved a notice from a paying customer, who wants to use the Facebook like button on products in their web-shops.

I encode the url of the each product before sending it to Facebook API.

But because DW does not follow international standards on replacing special characters, the Like link postes in to the users Facebook page doesn't work from ANY version of Internet Explorer browser.

Webkit posts this:
http://www.danbomoebler.dk/produkter/b%C3%B8rn-og-ungdom.aspx?ProductID=PROD1788&show=B%C3%B8rn%20og%20ungdom&p=Aeroplane%20rundt%20bord&by=Danbo

IE7+8+9 posts this to Facebook:
http://www.danbomoebler.dk/produkter/børn-og-ungdom.aspx?ProductID=PROD1788&show=B%C3%B8rn og ungdom&p=Aeroplane rundt bord&by=Danbo

Facebook doesn't understand ø and therefore the link on Facebook refers to:
http://www.danbomoebler.dk/produkter/b�rn-og-ungdom.aspx?ProductID=PROD1788&show=B%C3%B8rn+og+ungdom&p=Aeroplane+rundt+bord&by=Danbo

70% of visitors use IE.

Suggestion: Why don't you just make oe=ø, aa=å, ae=æ in your url interpreter?
 

 

You must be logged in to post in the forum