Tracking regional job vacancies without counting duplicates

Count job vacancies across regional sources without double counting translated adverts, syndicated postings and multi-country remote roles.

A public noticeboard displays six hiring notices on a town sidewalk.

One company can advertise the same opening on its careers site, a regional portal and a jobs board. Counting every URL as a vacancy overstates demand and often makes the largest employers look as though they are growing fastest.

Define a vacancy identity

Use an authorized feed where available. Keep the employer, source job ID, role, location, employment type and first-seen date. A remote role eligible in three countries may still represent one job. Preserve the eligibility countries separately so the data remains useful for geographic reporting. Google Search job posting documentation.

Investigate regional display gaps

When an employer permits comparison of its localized careers pages, XtremeProxy can help verify which listings a visitor sees in each market. Test the same language and query before attributing a difference to geography. Publish your duplicate and expiration rules alongside the figures. Then another analyst can tell the difference between ten new roles and ten additional places where existing roles were advertised.

As a control, select one vacancy the employer lists in two languages. The two URLs should map to one role if their requisition ID is identical. Preserve both language versions for navigation QA, but keep only one observation in the employer-level count of positions.

One vacancy appears on three regional pages

A company publishes vacancy R17 in English, French and German with the same requisition identifier and a choice of work locations. Three URLs can describe one open position. Retain all three observations under the requisition and list the stated locations separately. If a fourth URL introduces a new requisition identifier for the same job title, check the employer's record before merging it. Distinct openings and distinct translations need different counts in a labor-market report.

Separate job ads from positions to fill

One listing can advertise multiple vacancies and one opening can appear in several languages. Track the number of distinct postings and the employer's stated number of positions as different fields. If a posting leaves head count unstated, an unknown value is more defensible than an inferred single hire.

Check whether an expired closing date actually removes the vacancy from the active feed. A translated landing page can remain online months after a requisition closes. Keep the observed web-page status and the employer’s stated application status as separate fields. An accessible archive belongs in historical coverage.

Handle one role that accepts several locations

A requisition permits candidates to work in Toronto or Montreal. Store the two permitted work locations while counting one open requisition nationally. Regional reports can each include the role, but summing those regional counts would count it twice. Give users the level of aggregation and a deduplicated national total where that is the intended measure.

Vacancy duration needs a rule for gaps in observation. Imagine a requisition visible on Monday, missed during a Tuesday feed failure and visible again on Wednesday under the same employer ID. Treat Tuesday as unknown until the employer's revision history confirms a closure or continuation. Counting a new opening on Wednesday would turn a collection gap into a hiring event. Preserve the first and last observed dates separately from the employer's declared opening and closing dates when publishing a weekly series.

Separately identify evergreen recruitment adverts. An employer might keep a single listing open year-round for future applicants, even when there is no dated vacancy for a specific position. Look for the employer's own wording or a dedicated feed field and preserve its stated interpretation. A weekly report can count such adverts in its published opportunities population while excluding them from a series of newly opened roles. Label the two measures clearly so a long-running talent pool is not counted as a new job each week.

If a requisition is split into two independently approved roles partway through a month, record the split date. Historical counts before the split still describe one opening. After it, the two successor records can be counted independently.

A monthly report can display distinct openings and the number of local pages advertising them as separate measures. Preserve uncertain duplicate matches for the employer or data steward. Duplicate vacancy listings demonstrates vacancy matching. Comparing advertised salaries across countries and job types applies the same insistence on original source terms to cross-market salary comparisons. Compare XtremeProxy network types.

Frequently asked questions

Should a repost restart the vacancy's age?

Track first seen, latest revision and reopening as separate events. A changed URL or refreshed listing date is insufficient by itself. Use an employer-provided requisition history where available and qualify uncertain matches.

Related articles