Will .jobs Domain Yank The Business Model Out From Online Job Boards?
from the the-marketplace-is-changing dept
It already seems like the way ICANN is dribbling out new top level domains is somewhat pointless other than as a way to increase revenue for ICANN. We already were wondering what the possible reasoning was behind a .jobs TLD, as there was no indication anywhere that anyone was having any particular trouble finding where a company lists their job openings. Combined with some already questionable moves by ICANN in assigning who gets to control these new top level domain names, and the whole thing seems pretty sketchy. With today's official approval of both .jobs and .travel, though, some are wondering if .jobs will end up causing problems for online job boards. With a designated area to post jobs on an individual site, it will be that much easier for someone to create a meta-search engine of job listings (some of which already exist), and companies won't feel the need to post their jobs to the same sites as before. Of course, that's only if the job boards view their main purpose to be hosting job listings. It's not hard to see how they can (and should) offer much more beyond that in terms of helping people find the right job and manage their careers more effectively, while also helping companies target their open job leads more efficiently. As long as the job sites know how to do that, then the .jobs domain shouldn't have much of an effect -- other than making a bunch of companies feel they need to shell out for yet another domain that they probably don't need.
Thank you for reading this Techdirt post. With so many things competing for everyone’s attention these days, we really appreciate you giving us your time. We work hard every day to put quality content out there for our community.
Techdirt is one of the few remaining truly independent media outlets. We do not have a giant corporation behind us, and we rely heavily on our community to support us, in an age when advertisers are increasingly uninterested in sponsoring small, independent sites — especially a site like ours that is unwilling to pull punches in its reporting and analysis.
While other websites have resorted to paywalls, registration requirements, and increasingly annoying/intrusive advertising, we have always kept Techdirt open and available to anyone. But in order to continue doing so, we need your support. We offer a variety of ways for our readers to support us, from direct donations to special subscriptions and cool merchandise — and every little bit helps. Thank you.
–The Techdirt Team
Reader Comments
Subscribe: RSS
View by: Time | Thread
Indeed
A metasearch engine will still have to crawl non-.jobs sites to be successful anyway (or so I'd think). In any case, there's as much work in parsing and indexing the job descriptions etc than in finding them. The .jobs TLD as it is setup (only companies can get a domain and only with their name) seems pretty pointless.
- ask (maintainer of http://jobs.perl.org/ )
[ link to this | view in chronology ]
jobs tld
jobs.mycompany.com or www.mycompany.com/jobs is a much better use of DNS space than managing a whole new tld to support www.mycompany.jobs and doesn't have the issue of policing cybersquatting on the entire new tld.
what the hell are they thinking?
[ link to this | view in chronology ]
.jobs TLD
If i registered mybrand.jobs with some registrars, then later they found i am listing jobs of other companies, then will they refund my registration fees?
[ link to this | view in chronology ]