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.


Reader Comments (rss)

(Flattened / Threaded)

  1.  
    identicon
    Ask Bjørn Hansen, Apr 8th, 2005 @ 1:50pm

    Indeed

    I run a small specialized job site and we're getting more postings than ever. People post to reach an audience, not just to put the job online.
    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/ )

     

    reply to this | link to this | view in thread ]

  2.  
    icon
    brent ashley (profile), Apr 8th, 2005 @ 2:06pm

    jobs tld

    surely ICANN should know better than anyone that the heirarchy goes in the other frickin direction.

    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?

     

    reply to this | link to this | view in thread ]

  3.  
    identicon
    Elaiyaperumal, Sep 24th, 2008 @ 6:14am

    .jobs TLD

    If i am a placement consultant. If I need to get job seekers for some other companies, can i have .jobs domain name?

    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?

     

    reply to this | link to this | view in thread ]


Add Your Comment

Have a Techdirt Account? Sign in now. Want one? Register here
Get Techdirt’s Daily Email
Save me a cookie
  • Note: A CRLF will be replaced by a break tag (<br>), all other allowable HTML will remain intact
  • Allowed HTML Tags: <b> <i> <a> <em> <br> <strong> <blockquote> <hr> <tt>
Follow Techdirt
A word from our sponsors...
Essential Reading
Techdirt Reading List
Techdirt Insider Chat
A word from our sponsors...
Recent Stories
A word from our sponsors...

Close

Email This