Evidence first
Pages prefer official careers pages, active postings, employer policy pages, government references, and public filings.
Methodology
How HireTea reviews sources before a page is indexed
HireTea is built from public employer sources, government references, active posting language, and structured fact sheets. This methodology explains how evidence is weighed for the 74 company hubs and 438 hiring guides in the current published guide set, what gets kept out, and what applicants should still verify before relying on any hiring page.
74 company hubs in this review scope
438 indexed hiring guides in scope
1084 public source links reviewed
1100 claims checked in source audits
Quick answer
How does HireTea decide whether a hiring page is ready?
A page is strongest when it combines a current public source, company-specific hiring context, a clear limitation note, and applicant-focused next steps. Official employer pages and current postings carry the most weight. Secondary sources can help identify what applicants ask about, but they do not override employer language or current public instructions.
Limits stay visible
When details vary by role, location, department, property, franchise, or posting, the page says so directly.
Weak pages wait
Pages with thin evidence can stay out of the index until the source trail is strong enough for applicants.
Review scope
What this methodology currently covers
The numbers below describe the same company set currently used by the public sitemap. The purpose is not to claim perfect coverage of every employer. The purpose is to keep the published guide set focused on pages with enough public evidence, clear caveats, and applicant value to support real application decisions.
| Methodology signal | Current count | How it is used |
|---|---|---|
| Company hubs in scope | 74 | Defines the employer set used for published company, category, benchmark, and hiring-guide pages. |
| Indexed hiring guides in scope | 438 | Defines the topic pages included in the XML sitemap, human sitemap, and LLM content map. |
| Public source links reviewed | 1084 | Shows whether pages are grounded in public references rather than only broad archetype assumptions. |
| Preferred-source signals | 1077 | Counts sources that are not classified as low-confidence signals by the source-quality filter. |
| Lower-confidence signals | 7 | These can identify questions to verify, but they should not be used as the final rule by themselves. |
| Source-backed topic facts | 564 | Counts fact-sheet entries that connect a hiring topic to a public source and access date. |
| Audited source rows | 1451 | Counts Source Register rows reviewed during the 2026-05-24 company source-verification cycle. |
| Curated audit sources added | 434 | Counts audit sources promoted into company fact sheets after filtering to official, regulator, vendor, or operator evidence. |
| Checked hiring claims | 1100 | Counts claims classified as keep, keep with caveat, drop, or needs recheck in the source-verification files. |
| Claims separated for follow-up | 208 | Counts drop and needs-recheck items kept out of page copy until a separate review resolves them. |
| Latest source access date | 2026-07-02 | Helps readers judge whether a page should be rechecked before a high-stakes decision. |
Verification process
How the 2026 source-verification audit is used
The 2026-05-24 audit reviewed public source registers and claim-verification tables for every published company hub. Audit rows do not automatically become page copy. HireTea promotes only a curated subset into fact sheets, keeps caveated claims labeled, and separates drop or needs-recheck items for a later cleanup pass before they can affect applicant guidance.
| Audit verdict | How it is used | Public-page effect |
|---|---|---|
| KEEP | The claim or source can support a fact-sheet source trail when it matches the current page context. | Eligible for source badges, citation metadata, and source-depth scoring. |
| KEEP_WITH_CAVEAT | The source is useful, but role, location, time, or policy limits must remain visible. | Shown with caveat language rather than treated as a universal rule. |
| DROP | The item should not support public copy without replacement evidence. | Separated into cleanup notes instead of silently changing applicant-facing facts. |
| NEEDS_RECHECK | The item may be useful but needs a fresh source, current page, or stronger confirmation. | Held out of stronger claims until a later review resolves it. |
Source hierarchy
Which sources get the most weight
Official employer sources
Careers pages, active postings, benefits pages, policy pages, press releases, recruiting pages, and public company materials are preferred because they are closest to the employer's current process.
Public authority sources
Government labor, civil-rights, consumer, and workplace references are used when a page needs legal-rights or state-specific context. They explain applicant rights, but they do not replace the current posting.
Current posting evidence
Active postings can clarify pay range, schedule, location, certification, role title, department, remote status, travel, and first-week expectations. Saved posting evidence is often the best local detail.
Secondary signals
Review sites, scraped listings, forums, and short social posts can reveal questions applicants ask, but they are treated as prompts for verification rather than final proof of a company-wide rule.
Indexing gates
Review gates that protect the published guide set
HireTea uses page gates to avoid publishing every possible page as if it were equally useful. A page can be reachable by direct link while still being held out of the published guide set. This keeps search-facing pages focused on answers that are specific, sourced, and useful to an applicant making a real decision.
| Gate | What must be true | Why it matters for applicants |
|---|---|---|
| Company fit | The employer is part of the current published guide set and has a structured fact sheet. | Readers get company-specific language instead of a generic career article. |
| Source-backed topic | The topic has a public source, access date, and clear caveat when local practice can vary. | Applicants can check the source trail before changing their plan. |
| Useful page body | The page includes decision guidance, evidence to save, comparison notes, and next-step context. | The page helps with an application decision rather than only repeating a short answer. |
| Safe published guide set | Higher-risk or thin pages are kept out of the published guide set until they are stronger. | The public site avoids foregrounding pages that could be misunderstood or lack enough context. |
| Correction path | Every public page links to contact and editorial pages so source updates can be sent for review. | Readers have a clear way to report outdated public information. |
Source mix
Most common source domains in the current indexed set
Domain counts are not quality scores by themselves. A domain can appear often because it hosts many current job postings, benefits pages, or recruiting pages. The useful question is whether the source is close enough to the employer's own process to support the specific claim on the page.
| Source domain | Links | Lower-confidence signals | Example company coverage |
|---|---|---|---|
| careers.fedex.com | 20 | 0 | FedEx |
| chick-fil-a.com | 18 | 0 | Chick-fil-A |
| careers.microsoft.com | 17 | 0 | Microsoft |
| hiring.amazon.com | 17 | 0 | Amazon |
| careers.bankofamerica.com | 16 | 0 | Bank of America |
| careers.nike.com | 16 | 0 | Nike |
| careers.walmart.com | 15 | 0 | Walmart |
| jobs.dominos.com | 15 | 0 | Domino's Pizza |
Category coverage
How source coverage differs by category
Some categories have centralized employer careers pages. Others depend more on store, property, franchise, facility, or location-level postings. That is why HireTea pages separate broad company preparation from details that must be verified in the current posting.
| Category | Company hubs | Public source links | Source-backed facts | Examples |
|---|---|---|---|---|
| Retail | 24 | 362 | 216 | Walmart, The Home Depot, Target, and Kroger |
| Restaurant | 12 | 189 | 84 | McDonald's, Chipotle Mexican Grill, Starbucks, and Chick-fil-A |
| Grocery | 2 | 32 | 11 | Trader Joe's and Aldi |
| Warehouse | 3 | 61 | 29 | Amazon, FedEx, and UPS |
| Hospitality | 10 | 158 | 71 | Marriott International, Walt Disney Parks, Hilton Worldwide, and American Airlines |
| Tech | 7 | 126 | 46 | Alphabet / Google, Microsoft, Meta, and Nvidia |
| Consulting | 3 | 41 | 21 | Deloitte US, PwC US, and EY US |
| Finance | 2 | 32 | 16 | JPMorgan Chase and Bank of America |
| CPG | 1 | 23 | 7 | PepsiCo |
Reader use
What applicants should still verify
A sourced page is a starting point, not a substitute for the active posting. Before applying or accepting an offer, verify the exact role title, job ID, pay language, schedule, location, department, required documents, candidate-portal messages, and written next steps. If a posting or recruiter message conflicts with a HireTea summary, follow the current employer instruction and send the source so the page can be reviewed.
Use company pages for preparation
Company hubs explain the likely hiring context, terminology, manager filters, and source-backed topics to review.
Use benchmarks for planning
Benchmarks show patterns across indexed hubs, but they are not promises about a specific location or manager.
Use resources for evidence
Save postings, portal messages, interview notes, and offer details before links expire or instructions change.
Use updates for corrections
Send the page URL, current public source URL, and date viewed to jeongyuseck@gmail.com.