Slug /post/ in blog posts
P
Peter Hiebl
You should either be able to completely remove /post/ from blog posts or, in the best case, have the opt-in to remove it or replace it with your own keyword. From an SEO perspective, /post/ is very annoying, unprofessional and meaningless. Because it only extends the URL without adding value. Everyone who had any kind of SEO background should actually know that, especially in the agency sector.
Log In
C
Cornelia Fischer
All blog category pages currently use the /category/ slug by default — in the form of mydomain.com/blog/category/ki, for example.
From an SEO perspective, this is a significant disadvantage because:
The URL is extended unnecessarily, there is no semantic relevance in the word “category”, there is no possibility of adaptation or individualization, it contradicts best practice in SEO (short, keyword-relevant URLs).
Request/suggestion for improvement:
Similar to /post/-slug for blog articles, please also enable category pages:
The ability to completely remove the /category/slug. Or replace it with your own keyword (e.g. /topic/, /area/, /knowledge/, etc.),
Or — unless otherwise feasible — to be able to adapt it linguistically (e.g. for non-English pages).
Especially for agencies, SEO-savvy users and anyone who wants to set up reputable blogs, the current structure is a hindrance and looks unprofessional.
The wish is therefore analogous to the frequently mentioned /post/ topic — and should be considered together.