Why the extension stayed quiet
How ATSReady decides whether a page looks like a job posting and why the save control stays hidden on low-confidence pages.
On this page
The ATSReady extension shows its save control only when the current page looks like a job posting.
Detection order
The content script checks in this order, and stops at the first layer that answers:
- known job-board URL patterns,
- structured job data on the page,
- DOM heuristics over the page text.
Layers 1 and 2 both produce high confidence. If neither matched and the heuristics stay below the threshold, ATSReady removes the in-page control instead of guessing. When that happens, Add a job is the way to get the posting into ATSReady anyway.
Special case: embedded ATS pages
If the top page embeds a known applicant tracking system inside an iframe, the outer page stays quiet so the script inside the iframe can handle detection there.
This check runs only after the first two layers have both declined. A page that matches a known job-board URL, or that publishes structured job data, is detected on the outer page regardless of what it embeds.
What medium confidence looks like
Only the third layer can produce medium confidence, and a medium-confidence page still shows the save action. The in-page button keeps its usual label, Save to ATSReady, and adds a second line beneath it reading We are not sure this page is a job posting. There is no separate marker or icon for the uncertainty; that sentence is the whole signal.
Saving from a medium-confidence page works exactly as it does from a high-confidence one — see Save a job with the extension.