ilia
f5179304c1
Some checks failed
CI / Linting (Biome) (push) Failing after 41s
CI / Tests (push) Successful in 5m27s
CI / Type Check (adzuna-extractor) (push) Successful in 1m9s
CI / Type Check (gradcracker-extractor) (push) Successful in 1m13s
CI / Type Check (hiringcafe-extractor) (push) Successful in 1m9s
CI / Type Check (orchestrator) (push) Successful in 1m24s
CI / Type Check (startupjobs-extractor) (push) Successful in 1m8s
CI / Type Check (ukvisajobs-extractor) (push) Successful in 1m9s
CI / Documentation (push) Successful in 1m59s
Add blockedCountries in Settings so pipeline discovery drops jobs whose location mentions listed countries (existing discovered rows are kept). Document the feature, fix smoke tsconfig inheritance for nested extractors, and run smoke via an absolute-tsconfig wrapper. Co-authored-by: Cursor <cursoragent@cursor.com>
55 lines
2.2 KiB
Markdown
55 lines
2.2 KiB
Markdown
---
|
|
id: company-skip-list
|
|
title: Company skip list
|
|
description: Block unwanted employers during discovery using blocked company keywords in Settings.
|
|
sidebar_position: 6
|
|
---
|
|
|
|
## What it is
|
|
|
|
The **company skip list** is the **Blocked company keywords** field in **Settings → Scoring Settings**. Any job whose **employer / company name** contains one of your tokens (case-insensitive substring match) is **dropped during discovery** and is never imported.
|
|
|
|
## Why it exists
|
|
|
|
You may want to avoid certain agencies, staffing brands, or employers without having to filter them out of every search manually.
|
|
|
|
## How to use it
|
|
|
|
1. Open **Settings** and expand **Scoring Settings**.
|
|
2. Find **Company skip list (blocked keywords)**.
|
|
3. Add tokens one at a time, or paste a comma- or newline-separated list.
|
|
4. Click **Save Changes**.
|
|
5. Run the pipeline again — blocked companies apply to **new discovery only**; they do not remove jobs already in the database.
|
|
|
|
### Tips
|
|
|
|
- Use substrings that reliably identify the employer on listings, for example `recruit`, `staffing`, or a distinctive part of a brand name.
|
|
- Avoid overly short tokens that could match unrelated companies (for example a three-letter acronym shared by many firms).
|
|
- The list is capped in Settings validation (max 200 entries, each up to 200 characters).
|
|
- To block more precisely, prefer the exact spelling that appears on job posts you see in JobOps.
|
|
|
|
### Maintenance
|
|
|
|
- **Add** entries when you notice employers you never want to see again.
|
|
- **Remove** entries if you blocked too much — save, then run discovery again.
|
|
- **Review periodically** — staffing brand names change, and your targets may shift.
|
|
- **Existing jobs** are unchanged; use the Jobs UI or **Danger Zone** in Settings if you need to clear old rows.
|
|
|
|
## Common problems
|
|
|
|
### Blocked companies still appear
|
|
|
|
- Confirm you clicked **Save Changes** after editing the list.
|
|
- Remember: only **new** runs apply the filter. Old jobs stay until you delete or clear them.
|
|
|
|
### Too many jobs disappeared
|
|
|
|
- A token may be too broad. Remove or narrow it in Settings.
|
|
|
|
## Related pages
|
|
|
|
- [Blocked countries](./blocked-countries)
|
|
- [Settings](/docs/features/settings)
|
|
- [Pipeline Run](/docs/features/pipeline-run)
|
|
- [Orchestrator](/docs/features/orchestrator)
|