Common questions about JobSiteDir

Most directory sites are flat link lists. JobSiteDir is built as a comparison layer. We structure each site by market, hiring scope, audience, traffic signals, job listing signals, and platform fit so recruiters can judge where a board is useful before spending time or budget.

Because we classify sites from observed signals, not from brand slogans alone. A site may market itself one way, but public pages, job structure, geography, hiring patterns, or live listing behavior may point to a different practical classification.

We prefer consistent comparison rules over self-description. When a platform serves multiple markets, mixes audience segments, or has broad hiring coverage, we may use the most supportable label instead of the most flattering label.

We do not force a precise number when the public evidence is weak. If a site only exposes partial listings, unstable filters, gated search, or mixed signals, we prefer a cautious summary such as a range, activity signal, or no clear public count.

We do not treat every field as a fixed monthly overwrite. Different signals refresh on different cycles. High-change fields can refresh faster, while stable identity and category fields are only replaced when new evidence is strong enough.

No, not by default. Our update rules are designed to protect stronger existing facts from being replaced by weak signals such as blank pages, temporary access limits, crawler errors, or shallow snapshots.

We keep the latest useful truth, not simply the latest write. New data is compared against the current profile. If it is stronger, it can refresh the page. If it is weaker, partial, or contradictory without enough support, it is held back.

Yes. If a page is incomplete, outdated, or clearly wrong, owners and operators can contact us with verifiable details. We review correction requests, but we do not auto-publish claims that conflict with stronger observable evidence.