By the Interim Headhunters team. Updated
- Assignment detail
- Where a rule depends on jurisdiction or a client's system, the copy should say that context matters.
- Assignment detail
- Assisted drafting can help organize a brief, but the content must describe that exact seat and make its limits clear to a buyer.
- Assignment detail
- Human review still needs to examine terminology, practical tradeoffs and whether the page says more than its sources support.
What sources do we use?
We prefer the body responsible for a credential, regulation or technical requirement. Search documentation comes from the search provider. Engagement guidance separates our own recruiting terms from general observations about hiring. A source should support the specific statement beside it, not merely mention the same broad topic.
We do not copy paragraphs from another recruiting brand. Reading how other firms describe a model does not establish that we use their terms or have their results. Pages do not use invented placements, client names or testimonials as evidence. Where a rule depends on jurisdiction or a client's system, the copy should say that context matters.
Where do templates and assisted drafting fit?
Templates provide a consistent layout for screening, sourcing, questions and intake. They are not permission to replace a title in a paragraph and call it a new page. Assisted drafting can help organize a brief, but the content must describe that exact seat and make its limits clear to a buyer.
The build checks unshared prose, page-specific editorial details, FAQ blocks and internal links. It also checks the site's restricted language. These checks can find repetition and missing material; they cannot prove that every statement is right. Human review still needs to examine terminology, practical tradeoffs and whether the page says more than its sources support.
How do pages move from draft to release?
Pages belong to release cohorts. The launch group is smaller than the complete library. Unreleased cohorts remain available but are not submitted for indexing. The admin release control requires confirmation of human review and moves through the groups in order, rather than exposing the entire library in one action.
The value floor is enforced at release. A page needs 250 unique words, three page-specific facts, a unique FAQ and its own internal links before its cohort can be released. Pages that fail stay live with noindex while we fix them. We do not remove pages because they have not been released. Only pages that can never pass are removed with a not-found or gone response. A redirect is appropriate only when another page truly replaces it. Release does not promise search-engine indexing.
How can you report an error?
Use the contact page and include the page URL, the sentence you question and the correction or source you believe applies. That is more useful than a general note that a page feels wrong. We review the issue against the original brief and source material before deciding what to change.
A content change updates the page's modification record. Cosmetic changes do not need a new editorial date. If a statement cannot be supported, it should be corrected or removed. We do not retain a claim just because it appears on other websites. This policy is dated and bylined to the Interim Headhunters team, not to an invented named specialist.
What counts as a page-specific fact?
A useful detail explains a real difference in the assignment, credential or system. It is not a claim that a familiar title always fits. Editorial details should identify what needs checking and why that check matters to the buyer. A plausible sentence is not evidence just because it sounds specific.
A construction accountant's work in progress is different from a fund accountant's capital calls. Those distinctions belong in the brief and the page. An editor should check whether the terminology is used correctly and whether the surrounding sentence makes a practical point. Adding initials or software names to generic copy does not meet that standard.
The automated floor records quoted screening details or identifiable scope statements. It does not certify technical accuracy or replace a person reading the page. A reviewer should correct weak detail before release even if the build passes. Where a statement needs an external source, the page should identify a source that supports it.
What do modification dates tell you?
A modification date records a real content change, not a routine build or a decision to expose another cohort to indexing. Changes to wording, questions or useful links can alter the content record. A new font or a repeated deployment should not make unchanged guidance look newly researched.
If a page uses a regulation or credential, check the responsible body's current requirements as well as the page date. We do not make a publication date do the work of a source. The date is context for the reader, not an assurance that every possible application has been checked.
What does a passing check not prove?
A passing build establishes that the specified mechanical checks ran successfully. It does not establish that a page will rank or that a candidate will fit. The editor still needs to read the reasoning. A search provider can describe its own recruiting process without inventing evidence about outcomes.