Searching jobs with Google site: queries

Why go around the job boards

When a company opens a role, the listing is created in its ATS first. Whether it also shows up on a big aggregator depends on whether someone paid to syndicate it, and how fresh the aggregator’s copy is. The ATS version is always there, and is sometimes the only one.

• You land on the real application form. ATS results are direct apply pages — not an aggregator redirect that may 404 or be weeks stale.
• Fewer duplicates. Aggregators republish the same role many times over. The ATS page is the canonical one, which also makes it obvious when three “different” listings are the same job.
• It is where our own agent looks. The domain list and the rules below come from what actually returned results in our nightly production searches — not from a generic SEO listicle.

The basic pattern

A site: filter restricts Google to a single domain. Combine it with a quoted job title and a location:

site:jobs.lever.co "backend engineer" Milano

Quote the title so Google requires the exact phrase rather than matching each word separately. For remote roles, quote the geography too — a bare remote buries you in US-only postings:

site:boards.greenhouse.io "data analyst" ("remote Europe" OR "remote EMEA")

Then add a recency filter: in Google, Tools → Any time → Past week. ATS listings expire quickly, and an unfiltered search will happily hand you roles that closed months ago.

The ATS domains worth searching

These are the platforms whose hosted career pages we have confirmed are indexed and return individual listings. Coverage varies enormously by country — the third column matters more than the platform’s global size.

Note the subdomains. site:personio.de and site:personio.com/jobs both return nothing — the listings live on jobs.personio.de. The same applies elsewhere: target the hosted careers subdomain, never the vendor’s marketing site.

Five rules that decide whether a site: query works

These come from running these searches every night at scale and watching which ones come back empty.

• Use site: sparingly. Most of your searches should be plain keywords plus a location, with no filter at all. Stacking three or four domain-restricted searches just concentrates you on one platform and returns the same listings twice. Two per session is plenty.
• Never combine site: with a multi-part OR clause. site:greenhouse.io ("ML engineer" OR "data scientist") reliably underperforms the same two searches run separately. Narrow the domain or the terms, not both at once.
• Never point site: at a company’s own website. site:medtronic.com engineer or site:helmholtz.de researcher looks clever and returns nothing usable — Google does not index those career sections as job pages. To target one employer, search Company careers <role> with no filter at all.
• Drop site: entirely for niche roles. For research scientists, narrow verticals and deep technical R&D, no single platform holds enough listings for a domain-restricted search to survive. Broaden the job title instead.
• Quote the geography for remote roles. remote on its own matches US-only postings. "remote Europe" or "remote EMEA" as a quoted phrase forces the listing to actually say it.

Boards that look fine and return nothing

A site: search that fails is indistinguishable from there being no jobs — which makes dead sources expensive. These we have probed and confirmed are not worth a query:

• Italy — InfoJobs.it closed permanently on 31 December 2025 (Adevinta), and the listings were not migrated anywhere. Monster.it, Jobrapido.it and TrovoLavoro return effectively nothing to site: queries. What does work: bakeca.it, subito.it, iprogrammatori.it (IT roles), it.jooble.org, plus the staffing-agency portals — randstad.it, adecco.it, gigroup.it, manpower.it — which carry a large share of the Italian market.
• Germany — glassdoor.de returns salary and review pages, not jobs. monster.de, karriere.de, heise.de/jobs, t3n.de/jobs, ingenieur.de and adecco.de all return zero individual listings, and indeed.de returns nothing fresh under a past-week filter. What works: stepstone.de (dominant), jobware.de, stellenanzeigen.de, kimeta.de, xing.com, randstad.de.
• UK — uk.indeed.com and glassdoor.co.uk index category and salary pages more than job detail pages. What works: reed.co.uk, cv-library.co.uk, and the ATS platforms above, which have far stronger UK penetration than they do in Italy or Germany.
• Everywhere — breezy.hr and recruitee.com are real ATS platforms, but both came back empty on German queries, and Personio has almost no Italian footprint. A platform being popular somewhere does not mean it is populated in your country.

Sources verified via automated search probes (Italy re-checked March 2026, Germany March 2026, UK March 2026). Boards do change — if a source returns nothing twice, treat it as dead rather than as bad luck.

Language traps

A search engine does not know you meant a job title. Three collisions that cost real time:

• Do not search for “AI” in Italian. ai is the Italian preposition “to the”, so Google matches it nearly everywhere and the results are noise. Use intelligenza artificiale, machine learning or deep learning instead.
• “LLM” collides with Master of Laws. Search LLM engineer or large language model, never LLM on its own.
• Run local job titles alongside English ones. In Italy, sviluppatore as well as developer, ingegnere as well as engineer — and add the province abbreviation for regional roles (Milano MI, Roma RM, Torino TO). In Germany, Software Engineer and Softwareentwickler surface genuinely different listings.

Questions people actually ask

Does the site: operator still work on Google in 2026?

Yes — it is the backbone of our own nightly search. What has changed is that it is less forgiving than it used to be: combine it with a long boolean clause and you get an empty page rather than a partial match, which is exactly why the rules above matter.

How do I find a company’s ATS page if I don’t know which platform they use?

Search the company name with no filter at all — Acme careers software engineer — and look at which domain the result sits on. Once you know they are on, say, Lever, site:jobs.lever.co Acme gives you their entire board.

Is this better than just using LinkedIn or Indeed?

It is a different net, not a strictly better one. The big boards have volume and a convenient interface; ATS searches reach roles that were never syndicated and land you on the real application form. Most people who do this well run both.

How long does doing this properly take?

Roughly 30 to 60 minutes a day, every day. That is the honest catch — see below.

The catch

None of this is difficult. It is just repetitive: a handful of query variants per role, across several platforms and both languages, re-run under a past-week filter, with the dead sources skipped and the aggregator duplicates discarded — every day, because ATS listings expire fast. The days you skip are the days the good roles pass through. That loop is exactly what Knowledge Gatherer automates. It runs these patterns against your profile every evening, all seven days, screens what comes back, and emails you the single best match — one email, not another feed to check. €12/month daily, €5/month weekly, cancel any time.

Sign up and we run a real search on your profile and email you the result. No card, no obligation.