What information do we research?
We research the title, setting, work, and credentials that make an opening different from related jobs. A medical ICU nurse and a cardiac recovery nurse need different screening discussions. An ASC administrator and a hospital administrator run different operations. The content should explain those differences in the employer's terms.
When a page discusses a certification or license, we look to the issuing body or state authority. General guidance stays general when the rules vary. We do not turn a preferred qualification into a universal legal requirement. Your credentialing and compliance teams should confirm what applies to your appointment.
Where do salary figures come from?
Salary figures come from published BLS Occupational Employment and Wage Statistics rows. The guide shows the reference period, occupation code, occupation title, and area. It also explains when a niche title maps to a broader occupation. A familiar job name is not proof that BLS reports it separately.
We keep unavailable figures distinct from published wages. Top-coded figures are labeled as lower bounds rather than exact amounts. The tools use the published values and the visitor's inputs. They do not invent a percentile between published points or adjust wages using a third-party benchmark.
What does a page template do?
A template provides a consistent place for the job explanation, screening points, sources, questions, and related links. It should help a reader find information. It does not make reused paragraphs useful or prove that a page answers a different hiring question. The content must carry that distinction.
We check the text against related pages before releasing it for indexing. Changing only a title or location is not enough. A page that cannot meet the value check needs more original material, a genuine merge, or removal. A large page count is not our standard for useful guidance.
What is checked before indexing?
Our build checks original wording, page-specific facts, the visible FAQ, and internal links. A page intended for indexing must meet the stated value floor. Pages are also assigned to release cohorts. Passing the content check does not mean every page is released into the sitemap at once.
Human review still matters. A script can catch a repeated sentence or a missing section. It cannot certify clinical accuracy or prove that wording sounds natural. We do not label a page clinically approved merely because a build passed. Errors found during review should be corrected before release.
Who is the guidance written for?
Client pages are written for the hiring manager, practice owner, or employer making the appointment. They discuss the work and what to check before an interview. Candidate pages have a separate purpose. We do not make an employer sift through job-seeker advice to understand how a search would work.
The voice should be plain. We prefer a concrete shift, procedure, system, or decision to a broad claim about excellence. We do not invent placements, testimonials, client names, or candidate stories. An illustrative format must be labeled, and it must not look like evidence of a real placement.
How do we use sources and quotations?
We link to relevant official material when a page explains data or a published rule. BLS definitions may be quoted as definitions, with their source identified. Hiring advice is labeled as guidance. A link does not mean the source endorses Healthcare Headhunters or has reviewed our recruiting service.
Our comparison pages describe general recruiting models fairly. They do not claim to know another firm's current fee, results, or service quality. Company names identify the models discussed and remain their owners' trademarks. We do not imply an affiliation with another firm or certification issuer.
How are updates dated?
Content dates change when the content changes, not whenever a build runs. A data page identifies the BLS release and reference period separately from the page's review date. Historical wage rows remain distinct from the current release. A new release should not overwrite the record used in an earlier edition.
We review affected mappings and unavailable area estimates when data change. The current website should explain the figure it is showing. A reader should not have to guess whether a wage came from a new edition, a previous release, or a fallback to a broader area.
How can you report an error?
Use our contact page or call 305-306-4829 to report an error. Include the page URL, the wording or figure you question, and the official source if you have one. Do not include patient information. A clear report lets us review the actual issue rather than guess which page you mean.
Ivan or a senior team member will reach out soon. We do not promise an automatic correction date or send a marketing sequence because you reported an error. If the issue changes a hiring decision, confirm the matter with the relevant state board, credential issuer, or your own clinical team.
What does this policy not promise?
This policy does not certify that website guidance covers every state rule or every hospital policy. It explains our research and publication approach. The employer remains responsible for its hiring, credentialing, and clinical decisions. We would rather state a limitation than present broad guidance as a complete legal checklist.
It also does not promise search rankings or citations by an AI assistant. Search engines and answer systems decide which pages to use. We make the site readable, crawlable where released, and honest about its sources. There is no special markup that can secure a citation.
Report an error BLS methodology and retrieval details Our recruiting fees How recruiting models differ Google guidance on helpful content Google guidance on AI search features
What if you find a problem on a page?
Tell us through the contact page and name the source you think the page conflicts with. We review the statement against that source rather than against opinion. The answers below cover disputed credential statements and what our automated checks do and do not confirm about a page.
Where should you send a disputed credential statement?
Send the page URL and the current issuing-body guidance through the contact page. We can review the statement against that source. Your credentialing team should still confirm the rules for your appointment.
Does passing a build check mean a clinician reviewed the page?
No. Automated checks test publication rules, not clinical judgment. This policy does not claim a clinical review that has not happened. A human reviewer should examine the meaning and source before a page is released.
What happens when BLS changes a wage estimate?
We keep the release separate from earlier data and update affected guide material. Reference periods remain visible. An unavailable estimate is not replaced with an invented local value.