Shortening root parts in URLs?

[Tomas12345]

Hi,

and one more question :) is it ok to shorten root parts in URLs?

example:
domain.org/en/t/345/health-care/Italy
domain.org/it/t/345/assistenza-sanitaria/Italia

instead of:
domain.org/en/topic/345/health-care/Italy
domain.org/it/tema/345/assistenza-sanitaria/Italia
or alternatively with "topic"
domain.org/it/topic/345/assistenza-sanitaria/Italia

we see no point in showing English root parts in other languages & suppose it's important to focus only on local-laguage slugs to describe perfectly the page content.. is such thinking OK?
Thank you very much...

[keyplyr]

Hi Tomas12345, sorry no one has replied to your question.

Makes sense to me, but I'm no expert. Do you plan on using a 301 Moved Permanently redirect?

Hopefully someone more knowledgeable will comment.

[lucy24]

Do you plan on using a 301 Moved Permanently redirect?

I thought this was a new site where URLs are getting created for the first time. If the URLs already exist, in significant numbers, I would say don't mess with them. It's just not worth the trouble.

This is assuming there will be many different (pseudo-)directories, so /tema/ or /topic/ or /t/ is just one option, alongside /s/ and /v/ and the rest of the alphabet. If it's all /t/ then why have two separate elements (/t/ and /345/) at all?

Most humans don't really look at the URL. Or so they keep telling us. But for the ones that do, /topic/ seems more intuitive, even if nobody will be directly typing it in.

[keyplyr]

I thought this was a new site where URLs are getting created for the first time

I don't see that in the OP unless the question is still concerning the site mentioned here [webmasterworld.com]

[Tomas12345]

@keyplyr @lucy24
Thank you very much. It's a totally new site as keyplyr mentioned, no URLs indexed.
Yes, we'd love to avoid any future 301s.

Yes, there will be approximately 5-10 various directories.
The number (for example 345) is the unique ID of an item in one of the directorie.
Thus, technically, the slug "health care" is there only to describe the subpage content.

The goals are
1/
Make it easy to compare data for every content item in various languages in Google Analytics
"it/t/" filters all topics in Italian
"/t/345/ filters the 'health care' topic in all languages

2/ And Avoid English root parts showing in other languages
domain.org/it/country/55/Italia
(55 is Italy's ID, this URL shows all topics for a country including "health care ")

OR avoid translating root parts
domain.org/it/paese/55/Italia
This looks better, but I am afraid some root part translations might change in some languages + might be more difficult to compare "italy topics" in various languages in Analytics? What do you think?

....Thus the proposed URL would be just
domain.org/it/c/55/Italia
domain.org/en/c/55/Italy

Would you still stick to:
domain.org/en/country/55/Italia
and
domain.org/it/country/55/Italia
OR
domain.org/it/paese/55/Italia
?

[Tomas12345]

another example from the domain to better explain... a QUESTION included in the "heath care" topic:

EN
domain.org/en/q/4343/is-the-new-law-on-heath-insurance-companies-better-than-the-old-one
domain.org/en/question/4343/is-the-new-law-on-heath-insurance-companies-better-than-the-old-one

IT
domain.org/it/q/4343/la-nuova-legge-sulle-compagnie-di-assicurazione-sanitaria-e-meglio-di-quella-vecchia
domain.org/it/question/4343/la-nuova-legge-sulle-compagnie-di-assicurazione-sanitaria-e-meglio-di-quella-vecchia
domain.org/it/domanda/4343/la-nuova-legge-sulle-compagnie-di-assicurazione-sanitaria-e-meglio-di-quella-vecchia