Hello at all,
as I wrote: in google webmaster you can see at the bottom the url which is not correct. This url http://anti-babypille.eu/content/node/62 contains the base path, a part of the url-alias (content) and the path of node/nid.
I looked at the url-alias Table and the content seems fine. Looking for /content/node/62 in the db gave 2 results in watchdog as error. The correct url http://anti-babypille.eu/content/levina-stada-21 works seemlessly with or without settings of the url-alias (?q=). But in both cases the result of the url in google richsnippets is wrong.
So I believe that the interpretation of the URL is wrong in microdata. Assuming that I don't take a longer path instead I take the short cut http://anti-babypille.eu/levina-stada-20 the resulted Url in richsnippets is correct with the intern path http://anti-babypille.eu/node/62 which is not the goal in my mind!???
I use:
drupal 7.22,
pathauto 7.x-1.2,
token 7.x-1.5,
Entity API 7.x-1.1,
Chaos tool suite (ctools) 7.x-1.3,
microdata 7.x-1.0-beta2+15-dev (2012-Okt-12) with the microdata_1854698.patch to map the fields correctly.
Does anybody knows more than me???
Comments
Comment #1
maen commentedNobody? So isn't that feature important for search engines?
Comment #2
roderikLook at #1854352: Relative microdata schema urls point to nowhere
Comment #2.0
roderikWrong urls after changing