LinkedIn Job Search URL Builder — Control Every Filter From the URL
LinkedIn's job search is driven by URL parameters — geoId, f_TPR, f_E, f_WT and more. Set them deliberately — a Boolean keyword string, a geoId location, a posted-in-the-last-hour window — instead of fighting the filter UI, or paste an existing search URL to see exactly what it does.
Add a title, pick filters, or paste an existing LinkedIn search URL to decode it. The URL updates live as you build.
How the URL builder works.
Every filter on LinkedIn's jobs page maps to a query parameter in the URL. The keyword box supports Boolean search: "exact phrase" for titles, AND to require terms, OR for alternatives, NOT to exclude, and parentheses to group. The builder assembles that syntax for you — job titles become an OR-group, required terms are AND-ed, and excluded words become a NOT-group.
The date-posted filter (f_TPR) is a rolling window in seconds, not a calendar date — r86400 is 24 hours, r3600 is one hour, and any custom value works. Sorting by sortBy=DD shows the newest postings first, which pairs well with a short time window when you want to be among the first applicants.
How to find geo IDs, company IDs, and more.
Locations, companies, and industries are stored as numeric IDs — not names. The fastest way to find one: run the search on LinkedIn, apply the filter in the normal UI, then read the number out of the URL — after geoId=, f_C=, or f_I=. Paste that whole URL into the box above and this tool will decode it back into editable filters.
Common geo IDs are built in (United States 103644278, United Kingdom 101165590, India 102713980, Worldwide 92000000, plus major metro areas). Company pages reveal their ID too — visiting linkedin.com/company/1441 redirects to the company it belongs to, which is a quick way to verify an ID before using it.
Every LinkedIn job search parameter, decoded.
The full vocabulary the builder writes into the URL — handy when you are reading a shared search link or checking what a pasted URL actually does.
| Parameter | What it controls | Values |
|---|---|---|
keywords | Boolean search string | "exact phrase" · AND / OR / NOT in capitals · parentheses to group |
location | Location label shown in the UI | Free text — display only; geoId does the actual filtering |
geoId | Location filter | Numeric geo ID — 103644278 = United States, 92000000 = Worldwide |
distance | Search radius | Miles: 5, 10, 25, 35, 50, 75, 100 |
f_PP | Extra locations searched at once | Comma-separated numeric place IDs |
f_TPR | Date posted | r + seconds — r3600 = last hour, r86400 = last 24h, r604800 = last week |
f_E | Experience level | 1 internship · 2 entry · 3 associate · 4 mid-senior · 5 director · 6 executive |
f_JT | Job type | F full-time · P part-time · C contract · T temporary · V volunteer · I internship · O other |
f_WT | Workplace type | 1 on-site · 2 remote · 3 hybrid |
f_SB2 | Minimum salary (US postings) | 1 = $40k+ through 9 = $200k+ |
f_C | Company filter | Comma-separated numeric company IDs — include only; it cannot exclude |
f_I | Industry filter | Comma-separated industry codes — all 147 are built into the tool |
f_F | Job function | Codes like eng, it, sale, prdm — undocumented, may be ignored |
f_AL | Easy Apply only | true |
f_EA | Under 10 applicants | true |
f_JIYN | In your network | true — needs a signed-in account |
f_VJ | Verified postings only | true |
f_FCE | Fair chance employers | true |
sortBy | Sort order | R relevance (default) · DD newest first |
spellCorrectionEnabled | Spell correction | false disables "did you mean" rewrites |
origin, trk, refId, position… | Tracking & navigation | No effect on results — the builder drops them on decode |
What these parameters cannot promise.
LinkedIn's newer AI-powered job search (rolling out since mid-2025) honors only a subset of URL filters — keywords, location, date posted, company, Easy Apply, and under-10-applicants are the most reliable. Classic facet parameters like experience level (f_E), job type (f_JT), and salary (f_SB2) still work in the classic filter UI but may be ignored in AI mode. If a filter seems ignored, put the intent in the keywords instead.
Some filters are account-dependent: “in your network” only does anything when you are signed in, and the salary filter is available mainly for US postings. For the broader context, see what changed in LinkedIn's 2026 AI job search.
Common questions.
Does LinkedIn Boolean search need capital letters? Yes. AND, OR and NOT must be uppercase — lowercase "and" or "not" are treated as literal search terms, not operators. Quotation marks mark an exact phrase ("product manager"), and parentheses group clauses: ("software engineer" OR "backend engineer") AND python NOT intern.
Does NOT exclude a company from results? Almost — but not literally. NOT matches words anywhere in the posting text, so NOT Acme hides postings that mention Acme in the description. It is not a company-name field: a posting that never repeats the employer name in the text can still appear. And f_C only includes companies — LinkedIn has no exclude-company parameter.
Is there a limit on LinkedIn job alerts? Roughly 20 saved-search alerts per account. Alerts are also batched rather than real-time, so they may not honor a sub-24-hour f_TPR window. The same URL opened directly — or kept as a bookmark — applies every parameter every time, which is why a built URL beats an alert for "posted in the last hour" searches.
Nothing you enter leaves your browser.
The builder runs entirely on your device: it never fetches LinkedIn, never uploads your filters, and saved searches live only in this browser's local storage. Analytics may record that the tool was used, subject to consent, but never the URL you pasted or the filters you chose.
Search sharper. Apply faster.
Join early access. We will write once, when Jobsistant is ready for you to try.