Skip to content

Commit 16dd1c3

Browse files
committed
more updates
1 parent 7630f79 commit 16dd1c3

File tree

4 files changed

+39
-34
lines changed

4 files changed

+39
-34
lines changed

docs/how/index.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,12 @@
11
# How to publish Job Openings
22

3+
There are 5 easy steps to optimize job publishing.
4+
35
## 1. Website
46
You need **your own website**: e.g. www.example.com, on which you publish your job openings as usual. This can be a [Wordpress](https://wordpress.org/), another CMS, plain HTML or any other way.
57

6-
## 2. Create a ojobpub.json
7-
Create file `/.well-known/ojobpub.json` (all lower case!) in a **specific JSON format containing structured meta information** about your job openings and link to the full job description on your website.
8+
## 2. Create an ojobpub.json
9+
Create a file `/.well-known/ojobpub.json` (all lower case!) in a **specific JSON format containing structured meta information** about your job openings and link to the full job description on your website.
810

911
!!! tip "File or Application?"
1012
While we have used a static ojobpub.json file to demonstrate the simplest way to provide the data, this endpoint is not limited to a static file. It could just as easily be served by a dynamic application or script.
@@ -15,9 +17,9 @@ To validate the JSON data format, we provide a [oJobPub JSON schema](https://git
1517

1618
## 4. Let's index
1719

18-
Go to [search.ojobpub.org](https://search.ojobpub.org), enter your domain and **let us index your jobs**!
20+
Go to [index.ojobpub.org](https://index.ojobpub.org), enter your domain (fqdn) and **let us index your jobs**!
1921

20-
This helps us to see, how things are growing. Once this format is known and etablished, this step may become obsolete (hopefully!).
22+
This helps us to see, how things are growing. Once this format is known and etablished, this step may become obsolete (hopefully!). Job crawlers can get all the domains from us for free using an API.
2123

2224
## 5. Spread the Word
2325

docs/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# About oJobPub
22

3-
oJobPub is an initiative with the goal, to create a free, simple and efficient process to publish on your own website and collect distributed job positions and vacancies around the globe.
3+
oJobPub is an initiative with the goal, to create a free, simple and efficient process to publish your vacancies on your own website and make it easy, simple and efficient to collect the data for everyone.
44

55
![](static/nutshell.png)
66

docs/solution.md

Lines changed: 13 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,24 @@
11
# Our Solution
22

3-
## Use your own Website
3+
How we want to address the issues:
44

5-
So, we ask ourselves:
5+
- On Your Website
6+
- Structured Meta Data
7+
- Well-Known Location
68

7-
> Why do we even need to post job openings on commercial portals?!
9+
## On your Website
810

9-
Actually, we don't!
11+
Having a website is almost a given for a company, and the cost of a website has never been lower than it is today.
1012

11-
The **World Wide Web** is a vast, **distributed database** where websites are stored all over the globe, not on a single, centralized platform.
13+
We still believe that publishing job vacancies on your **own website is the best and most cost-effective solution**, as you have full control and the data belongs to you.
1214

13-
![](static/nutshell_1.png)
15+
However, we believe that something is missing. An element that makes this actually work and ensures that your job postings are found by applicants.
1416

15-
## Structured Data
17+
![](static/nutshell_1.png){ height="100" }
1618

17-
Because there's **no standard format** (yet) for published job data on websites, job information can vary widely — from a simple list of jobs to a searchable input field to query jobs to an individual pages for each opening.
19+
## Structured Meta Data
20+
21+
Because there's **no wide adopted standard format** for published job data on websites, job information can vary widely — from a simple list of jobs to a searchable input field to query jobs to an individual pages for each opening.
1822

1923
This lack of consistency and structure **makes it difficult for search engines** to accurately recognize the context as job openings.
2024

@@ -24,21 +28,16 @@ A simplistic, minimalistic, structured data file containing **meta information**
2428

2529
## Predefined Path
2630

27-
> How can this data be found?
28-
29-
By placing a metadata file at a **specific**, **predetermined path**, we can ensure that search engines looking for job openings **know exactly where to find the data**.
31+
Inspired by robots.txt or sitemap.xml, we place a metadata file at a **specific**, **predetermined path**, we can ensure that search engines looking for job openings **know exactly where to find the data**.
3032

3133
This means they are aware of the data's context, allowing them to optimize how often they revisit to update their index.
3234

3335
As a result, job openings can be indexed by **multiple search engines** without further efforts and without any additional cost.
3436

3537
![](static/nutshell_2.png){ height="100" }
3638

37-
3839
## Keep the Control
3940

40-
> Why use metadata instead of full job descriptions?
41-
4241
The metadata you provide will be stored as an index by search engines, we can't control how long they keep that data.
4342

4443
That is why **only as much information as necessary** is provided. This strategy ensures that there is just enough information to pique a candidate's interest and **send them to the employer's website**.

docs/why.md

Lines changed: 19 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,39 +1,43 @@
1-
# What is the Issue?
1+
# Why
22

3-
## Expensive
3+
Let's look at three topics regarding job postings:
44

5-
> How much will it cost to publish my job opening? Can my company afford that?
5+
- Costs
6+
- Convenience
7+
- Efficiency
8+
9+
## Costs
610

711
Publishing and finding jobs is a huge market. Nowadays there are **hundrets or thousands** of job portals, job boards and career platforms world wide.
812

913
An estimated **34.4 USD billion** is spent annually on online job advertisements. This figure for 2023 underscores the immense importance of online job boards and career platforms in modern human resources management. The market for online job ads is a central component of the global recruiting industry. These figures come from Staffing Industry Analysts (SIA), a leading analysis firm in the field of human resources management.
1014

1115
Needless to say, job portals typically **charge employers regardless** of whether they fill the position or not.
1216

13-
We believe that the search for the right employees should be **free of charge** and should not depend on spending money on job board advertisements.
17+
We believe that a publishing job offerings is rediculous expensive, it should be **free of charge**.
1418

1519
??? info "Small selection of well-known job portals"
1620
Just to name a few: [Indeed](https://www.indeed.com), [LinkedIn](https://www.linkedin.com), [Monster](https://www.monster.com), [Glassdoor](https://www.glassdoor.com), [CareerBuilder](https://www.careerbuilder.com), [ZipRecruiter](https://www.ziprecruiter.com), [Jobrapido](https://de.jobrapido.com), [Simply Hired](https://www.simplyhired.com), [Dice](https://www.dice.com), [Upwork](https://www.upwork.com), [Fiverr](https://www.fiverr.com), [Freelancer](https://www.freelancer.com), [FlexJobs](https://www.flexjobs.com), [Adzuna](https://www.adzuna.com), [StepStone](https://www.stepstone.de), [XING](https://www.xing.com), [Stellenanzeigen.de](https://www.stellenanzeigen.de), [Jobware](https://www.jobware.de), [Meinestadt.de](https://www.meinestadt.de), [Absolventa](https://www.absolventa.de), [Kimeta](https://www.kimeta.de), [JobNinja](https://www.jobninja.com), [Jobs.ch](https://www.jobs.ch), [JobScout24.ch](https://www.jobscout24.ch), [JobUp.ch](https://www.jobup.ch), [Karriere.at](https://www.karriere.at), a.s.o
1721

1822

19-
## Inefficient
20-
21-
### Employers
23+
## Convenience
2224

23-
> On which job portals should employers publish job openings?
25+
Employers must decide where and on which of the many, many job portals they want to publish their job vacancies. An account must be created on each platform and all data must be entered separately into each of these portals.
2426

25-
Employers must decide on which of the many, many job portals to publish our job openings.
27+
Publishing a job on **multiple portals** often means to *copy/paste* data and **more work to publish and manage**. This can take a lot of time you even pay for.
2628

2729
It is **not obvious to find the criteria** to decide on which portal they have the best chances to find a candidate.
2830

29-
Publishing a job on **multiple portals** often means to copy/paste data and **more work to publish and manage**.
31+
We think, this is rediculous unneccessary: As an employer we want to publish the job on **one location** and **spread** the info.
32+
33+
We think, our solution might be the missing piece to make it work.
3034

31-
As an employer, we want to publish the job on **one location** and **spread** the info.
35+
## Efficiency
3236

33-
### Job Seekers
37+
Finding job postings online in the web is unnecessarily difficult due to unstructured data.
3438

35-
> Where to look for a new job? On which job portals? Or should I search the web?
39+
While there has been some attempts to address this using a job posting schema for jobs, which even Google supports ([Why a new Format](faq.md#why-a-new-format)), it hasn't been widely adopted and **still forces search engines to crawl entire websites** just to find the relevant page. This is like searching an entire library for a single page of a book.
3640

37-
If an employer **can't afford** to pay for a job posting, they might only list the vacancy **somewhere on their own website**. Further, all Google/Bing indexed job openings are often **outdated** because they do or can not distingues normal website content from job openings.
41+
We propose a much simpler approach, **inspired by conventions** like robots.txt or sitemap.xml. Companies would place all their job listings in a structured file at a single, well-known URL.
3842

39-
We think, our solution might be the **missing piece to make it work**.
43+
Job search engines and aggregators would only need to check this one location to get all the data they need. This would make discovering and indexing job postings vastly more efficient for everyone.

0 commit comments

Comments
 (0)