LinkedIn Hide Viewed Jobs

Hides viewed job cards on LinkedIn Jobs pages, adds a compact draggable badge, and lets you reveal hidden items anytime.

You will need to install an extension such as Tampermonkey, Greasemonkey or Violentmonkey to install this script.

You will need to install an extension such as Tampermonkey to install this script.

You will need to install an extension such as Tampermonkey or Violentmonkey to install this script.

You will need to install an extension such as Tampermonkey or Userscripts to install this script.

You will need to install an extension such as Tampermonkey to install this script.

You will need to install a user script manager extension to install this script.

(I already have a user script manager, let me install it!)

You will need to install an extension such as Stylus to install this style.

You will need to install an extension such as Stylus to install this style.

You will need to install an extension such as Stylus to install this style.

You will need to install a user style manager extension to install this style.

You will need to install a user style manager extension to install this style.

You will need to install a user style manager extension to install this style.

(I already have a user style manager, let me install it!)

Author
sametcn99
Daily installs
1
Total installs
30
Ratings
1 0 0
Version
1.1.8
Created
2026-02-28
Updated
2026-06-07
Size
67 KB
Compatibility
Compatible with Firefox Compatible with Chrome Compatible with Edge
License
MIT
Applies to

LinkedIn Hide Viewed Jobs

Hide or highlight viewed job postings on LinkedIn Jobs with a privacy-first userscript built for Tampermonkey and Violentmonkey — or install as a standalone browser extension for Chrome and Firefox.

This project focuses on three things: stable LinkedIn SPA behavior, high-confidence multilingual viewed/applied detection, and safer scrolling with guard and cooldown protections.

Quick Links

Screenshot

Screenshot of the userscript badge Screenshot of the extension popup

Project Links

Features

  • Dynamic Control:
    • ON/OFF status toggle.
    • Guard (ON/OFF): Scroll protection to prevent LinkedIn rate-limits. This is especially important when hiding jobs, as rapid scrolling through hundreds of hidden items can trigger bot-detection filters.
  • Two-Layer Detection:
    • Hide Mode: Automatically vanishes viewed jobs.
    • Highlight Mode: Keeps jobs visible but adds separate low-opacity full-card color filters for viewed and applied cards.
  • Active Card Accent: On jobs and jobs/search views, the currently open job card gets its own configurable highlight filter color so the selected row stays easy to spot.
  • Draggable Handle: Reposition the badge anywhere on the screen.
  • Custom Keyword Highlights: Add your own keywords to highlight or hide job cards based on company names, job titles, or any text appearing on the card — useful for filtering listings from specific companies or matching role titles you are targeting. Custom keywords are matched across every job card on the page (including recommended/discovery cards), independently of whether a card was previously viewed or applied to. Keyword matches take priority: keyword > active > viewed/applied. Keywords are managed via chip input in the settings panel with duplicate detection.
  • Dynamic Settings Panel: Expandable menu to switch between Hide and Highlight modes, tune viewed, applied, active, and keyword card colors, adjust filter opacity, and open the GitHub repository.
  • Navigation Reload Toggle: Choose whether SPA path changes should trigger a full page reload or stay on soft refresh.
  • Live Counter: Track the total number of detected cards (N hidden/N marked) — which includes both viewed/applied detections and custom-keyword matches, counted once per card — with a +N keyword breakdown showing how many of those are keyword matches, all updated in real-time.
  • Persistence: Remembers your preferences for ON/OFF, Scroll Guard, Detection Mode, Navigation Reload, Viewed/Applied/Active/Keyword Colors, Filter Opacity, Custom Keywords, and Badge Position.
  • Robust Navigation: Full support for LinkedIn's SPA routing; automatically restarts scanning when you switch pages or collections.
  • Multilingual: Intelligent keyword detection across 15+ languages.

Supported Pages

Browser Compatibility

Userscript

  • Chrome + Violentmonkey/Tampermonkey
  • Edge + Violentmonkey/Tampermonkey
  • Firefox + Violentmonkey/Tampermonkey

Browser Extension

  • Chrome 88+ (Manifest V3)
  • Firefox 109+ (Manifest V3)

Installation

Installation of Userscript

  1. Install a userscript extension in your browser:
  2. Chrome/Edge: Tampermonkey or Violentmonkey
  3. Firefox: Tampermonkey or Violentmonkey
  4. Import linkedin-hide-viewed-jobs.user.js into the extension.
  5. Save and enable the script.
  6. Refresh a LinkedIn Jobs page.

Alternative:

Installation of Browser Extension

The browser extension provides the same functionality as the userscript in a standalone package — no Tampermonkey/Violentmonkey needed.

Chrome:

  1. Download linkedin-hide-viewed-jobs-chrome.zip from the latest release.
  2. Unzip the file to a permanent folder on your computer.
  3. Open chrome://extensions in Chrome.
  4. Enable Developer mode (toggle in the top-right corner).
  5. Click Load unpacked and select the unzipped folder.
  6. Navigate to any LinkedIn Jobs page.

Firefox:

  1. Download linkedin-hide-viewed-jobs-firefox.zip from the latest release.
  2. Unzip the file to a permanent folder on your computer.
  3. Open about:debugging in Firefox.
  4. Click This FirefoxLoad Temporary Add-on.
  5. Select the manifest.json file from the unzipped folder.
  6. Navigate to any LinkedIn Jobs page.

Note: Firefox temporary add-ons are removed when the browser closes. For persistent installation, the extension needs to be signed by Mozilla.

GitHub Pages

This repository includes a GitHub Pages setup that renders this README through Jekyll with a polished dark editorial layout, a branded hero section, and responsive documentation styling.

Included site assets:

  • manifest via icons/site.webmanifest
  • robots.txt
  • sitemap.xml
  • favicon and Apple touch icon links from icons/
  • Open Graph, Twitter, canonical, and JSON-LD metadata

Publish flow:

  1. Open repository settings on GitHub.
  2. Go to Pages.
  3. Set Build and deployment to Deploy from a branch.
  4. Select the master branch and /(root) folder.
  5. Save.

Published site URL:

Supported Languages

The script supports detection for the following languages:

  • English (Viewed, Seen, Applied)
  • Turkish (Görüntülenen, Görüntülendi, Başvurulan, Başvurulanlar, Başvuruldu)
  • Spanish (Visto, Vistos, Aplicado, Postulado)
  • Portuguese (Visualizado, Visualizados, Candidatado, Candidatura)
  • French (Vu, Vue, Postulé, Postulée, Candidature)
  • German (Angesehen, Gesehen, Beworben)
  • Italian (Visualizzato, Visto, Candidata, Candidati, Candidatura)
  • Dutch (Bekeken, Solliciteerd)
  • Russian (Просмотрено, Откликнулся)
  • Polish (Wyświetlono, Aplikowano)
  • Swedish (Visad, Sedd, Sökt)
  • Chinese (已查看, 已申请, 已檢視, 已申請)
  • Japanese (閲覧済み, 応募済み)
  • Korean (조회됨, 지원함, 지원 완료)
  • Arabic (تمت المشاهدة, تم التقديم)
  • Hindi (देखा गया, आवेदन किया गया)

Usage

  1. Open a LinkedIn Jobs listing page.
  2. The script scans for viewed cards.
  3. When OFF, viewed jobs are not hidden; they are only counted.
  4. When ON, viewed jobs are hidden.
  5. In settings, Reload OFF is the default. SPA navigation stays on soft refresh unless you explicitly enable Reload ON.
  6. In Highlight mode, Viewed and Applied cards use different colors so you can distinguish them at a glance.
  7. On jobs and jobs/search pages, the currently selected card also gets its own full highlight filter color.
  8. In settings, use the native color pickers to adjust Viewed, Applied, Active, and Keyword card colors, and use the opacity slider to make the highlight filter lighter or stronger.
  9. In settings, type a keyword in the chip input and press Enter to add it. Matching job cards are highlighted or hidden depending on the detection mode. Click the × on any chip to remove a keyword.
  10. The settings panel includes a direct GitHub Repo shortcut for the project source and issue tracker.
  11. If rapid downward scrolling is detected while most cards are viewed/hidden, the guard can enter a random cooldown (5-15s) and slow scroll steps to reduce LinkedIn rate-limit risk.
  12. If guard is triggered again while a cooldown is already active, the new cooldown is added on top of the remaining time (stacked), instead of restarting as separate back-to-back cooldowns.
  13. During cooldown, pagination controls inside div.jobs-search-pagination are temporarily disabled (including collections/search pagination buttons).
  14. Drag the badge using the handle on the left to reposition it.

Detection Logic

The script performs detection in multiple layers:

  • Card selectors: li[data-occludable-job-id] and related LinkedIn list item selectors
  • Footer/marker-focused detection (VIEWED_MARKER_SELECTORS)
  • Text, aria-label, and title checks inside each card
  • Card-level fallback scan for missed cases

Text matching uses normalize('NFD') plus diacritic removal for more stable multilingual matching.

Customization

Source-of-truth customization lives under src/** and the userscript bundle is generated from that source.

Common knobs:

  • VIEWED_KEYWORDS: Add more viewed-language phrases
  • APPLIED_KEYWORDS: Add more applied-language phrases
  • JOB_CARD_SELECTORS: Card selection scope
  • VIEWED_MARKER_SELECTORS: Marker selection scope
  • STORAGE_KEY: Preference storage key
  • UI_POSITION_KEY: Badge position storage key
  • HIDDEN_CLASS: CSS class used for hiding
  • KEYWORD_HIGHLIGHT_COLOR: Highlight/overlay color for keyword-matched cards

Architecture

Userscript Mode

main.ts → LocalStorageService → App → Badge / DetectionService / RouterService / StyleManager
  • Entry: src/main.ts
  • Storage: window.localStorage via LocalStorageService
  • UI: In-page draggable badge

Extension Mode

content.ts → ChromeStorageService → App → Badge / DetectionService / RouterService / StyleManager
popup.ts ← chrome.storage.local → background.ts → chrome.storage.onChanged → content.ts
  • Entry (content): src/extension/content.ts — injected into LinkedIn pages
  • Entry (background): src/extension/background.ts — service worker relaying storage changes
  • Popup: src/popup/popup.html + popup.ts + popup.css — settings UI in browser toolbar
  • Storage: chrome.storage.local via ChromeStorageService
  • Sync: Popup changes → chrome.storage.local → background relays → content script calls app.refreshSettings()

Shared Code

Both modes share the same core business logic:

  • src/core/App.ts — orchestrator (accepts IStorageService via dependency injection)
  • src/services/DetectionService.ts — viewed/applied/keyword detection
  • src/services/KeywordMatcher.ts — multilingual keyword matching and custom keyword matching
  • src/services/RouterService.ts — SPA route change detection
  • src/ui/Badge.ts — in-page badge UI
  • src/ui/StyleManager.ts — CSS injection

The storage adapter pattern (IStorageService) means App works identically whether backed by localStorage or chrome.storage.local.

Build Commands

bun run build              # Build userscript only (.user.js)
bun run build:extension    # Build browser extension (dist/extension-chrome/ and dist/extension-firefox/)
bun run build:all          # Build both
bun run package:chrome     # Create Chrome zip
bun run package:firefox    # Create Firefox zip
bun run package:all        # Create both zips
bun run lint               # Check code quality
bun run check              # Lint + format
bun run release             # Create GitHub release (local)

Limitations

  • If LinkedIn changes its DOM structure, selectors may need updates.
  • New phrasing variants in some languages may require additions to VIEWED_KEYWORDS.

Privacy

  • The script runs fully on the client side.
  • It makes no external API calls.
  • It does not send data anywhere.

Contributing

Contributions are welcome.

  1. Fork the repository.
  2. Create a feature branch (feature/your-change) or fix branch (fix/your-change).
  3. Make source changes under src/** and update README.md if behavior changes.
  4. Run bun run check to verify lint and formatting.
  5. Run bun run build:all to verify both userscript and extension build.
  6. Test on LinkedIn Jobs pages to verify detection, badge UI, toggle behavior, and extension popup.
  7. Open a pull request with a clear summary, before/after notes, and screenshots when UI is affected.

Guidelines:

  • Keep changes focused and minimal.
  • Avoid unrelated refactors in the same pull request.
  • Preserve compatibility with Tampermonkey/Violentmonkey on Chrome, Edge, and Firefox.
  • Preserve compatibility with the standalone browser extension (Manifest V3).
  • If you add new language keywords, include only high-confidence terms to reduce false positives.
  • If you change storage keys or settings, ensure both LocalStorageService and ChromeStorageService are updated.

Releasing

Releases are created manually via GitHub Actions:

  1. Update version in package.json.
  2. Commit all changes.
  3. Go to Actions → Release → Run workflow.
  4. The workflow builds both the userscript and extension, packages ZIP files, generates release notes from conventional commits, and creates a GitHub Release with all artifacts attached.

For local testing:

bun run build:all
bun run package:all
# Then sideload from dist/extension-chrome/ or dist/extension-firefox/