The Career Search Engine

Your future is here!


Employers

How to get the most from your career postings.

Here are some guidelines to help our job search engine (and Career Seekers) get the most out of your job listings.

Include the location of the job in each posting

Example: Location: My City, My Province, My Country

Explanation: The number one search criteria of career seekers is location. The minimum we need to index a location is "City, Province". If your posting does not contain the work location, we do not index it.

Exceptions: If you have only one work location, you may list it on your "About Us" or "Contact" page. Make it the first address on one of these pages or mark as "Headquarters:" or a similar designation. Another alternative is to use a "job table" with location as one of the headings. Information from the table will be associated with the posting.

Provide headings for each section (including the Job Title).

Example 1: Explicit Headings
        Position: Software Developer
      Location: Ottawa, ON, Canada
    Reference: SD001-7
           Term: Full-time, permanent
   Description: Describes the roles and responsibilities.
Requirements: Describes the education, experience and knowledge.
       Apply to: Postal and/or Email address.

Example 2: Tool Tip (Title) Headings

Software Developer

Ottawa, ON, Canada

SD001-7

Describes the roles and responsibilities.

This position requires a knowledge of ...

Explanation: The more headings you have, the easier it is for candidates to find the information they are looking for, and for our search engine to index the information correctly. If you prefer postings without headings, put the heading in the html element title attribute. (<p title="Job Title">Software Developer</p>)

Exceptions: You do not need all the above headings to have your posting indexed, but clear headings make reading easier for candidates and our search engine. You choose your own headings. Keep headings short and to the point. Break requirements into Mandatory Requirements, Additional Requirements, Education and Experience, if it meets your needs.

Use consistent headings in your site.

Use standard headings for each section. Pick headings that best suit your company and stick to them. Companies with many departments or organizations that are aggregating career postings should make sure the people issuing the posting use standard headings.

Exceptions: If you have a single career posting per page, this is less important. However the greater the heading variability the more postings that can be missed.

Use single purpose headings.

Example:
Position: Software Developer

Explanation: Use a heading for its intended purpose. Do not fill it up with other information. Some companies put multiple "fields" into one (and often it does not have a heading). Make postings easier for candidates and our search engine to read.
DO NOT overload headings example: Contract Position, Software Developer (2007-123) reporting to the Director of Software Development, Ottawa ON

Exceptions: None. While we will properly index some cases of an "overloaded" heading, results are never guaranteed.

Delimit your headings:

Use HTML heading constructs to highlight you headings. Include a title and a delimiter (:) in the heading.

Example 1: <h3>Job Title: Software Developer</h3>

Explanation: Follow the heading title with a colon (:) or some HTML break such as a new line, new table cell, new paragraph etc.

Exceptions:

Job Title

This is the single most important field in the posting. Job titles are about people, not activities. You are looking for a Manager not Management, Developers not Development.

Explanation: It is beyond the scope of our job search engine to look at activities that might be career positions.

Exceptions: More of a special case than an exception, you can post for a Manager of Development.

Use proper HTML

Match opening delimiters with closing delimiters.
Use HTML "<a href=...></a>" or "<area href=>" links.

Example: <a href="http://www.myco.com/careers/softwaredeveloper1.html">Software Developer</a>

Explanation: There are many ways to link to another page that will confuse our search engine (and others). Keep it simple for best results.

Exceptions: We do process onClick events that take a URL address.

Use directory names

Example: www.myco.com/careers/listing1.html

Explanation: The search engine uses path and filename information to find and index career postings. The directory can be a second or third level directory (www.myco.com/english/company/careers/listing1.html).

Exceptions: Sites that use non-informational paths and filenames (e.g. /02/03/index?id=27) will still be indexed - but that indexing depends on the quality of the link captions.
Link captions like "Click Here" are dead ends; use "Click Here For Job Opportunities" as the link caption.

How to Promote a Career Opportunity

Career search results are listed by the date they were found, in a reverse chronological order (most recent first).

Paid placement listings will be available in the future.

The frequency a site is searched depends on

  1. The career posting activity on the site.
  2. Sites that link to Career Seer. (See How to link to Career Seer)
  3. Sites that have been submitted.
  4. Sites that have been found by our search engine.

More Common Sense

In response to some examples we have found.

  • Job Reference codes are intended to be unique. We only index one posting per reference code on a site (not six different jobs with the same code).
  • Do NOT use unusual HTML such as putting a javascript "onClick" event in the "valign" attribute of a "td" element. Put the javascript onClick in an "<a" element.
  • Do NOT make the job title an Email link. Use a separate "To Apply, click here".

Career Seer reserves the right to not list pages that contain offensive language

Career Seer does not guarantee listing of career submissions.

Have a suggestion? We would like to hear it!
  Employers      Advertisers      Community      News      About Us    Help    Add a Site
Career Seer: The Career Search Engine - Your Future is Here!