correct handling of /jobs/ vs /job/ folders
-
hi
I was wondering why this plugin uses two separate folders, one for job listings (/jobs/) and a separate one (/job/job-name) for individual job pages
maybe this issue was already raised by someone
now, the major issue with such an approach bleeds from two sides, one from an SEO perspective and last but not least from information architectural point of view
prior listing an ideal form of organising folders and pages, my question relates to the opportunity of changing the built in /job/ folder/slug under which job pages are being listed currently
and now here is a potential scenario of a correctly used information architecture:
main job listing page: /jobs/
single detailed job page: /jobs/job-name-whatever.html
job category: /jobs/category01categories are only listing pages just like the main /jobs/ listing page, all individual job pages would be accessible under the root /jobs/ folder
so the basic idea would be to use one single /jobs/ folder under which would be added all other job pages
my message got a little bit longer than expected, so sorry for this
I still hope someone could assist me in overcoming this issue and offer a solutionthanks in advance
P.S. : I’m not planning to use the singular form /job/ page as the listing page, the question is if we can alter the built in /job/ slug to whatever we want to (ex. /jobs/, /vacancies/, /career/ or whatever we want to)
- The topic ‘correct handling of /jobs/ vs /job/ folders’ is closed to new replies.