How WageScope Uses BLS OEWS Data

Official inputs

Four BLS workbooks keep national, state, metro, and nonmetro facts apart

WageScope uses the official May 2025 OEWS national, state, metro, and nonmetro products. National and state values come from their own source files. MeritLog does not rebuild them by adding local rows. That avoids a false total and keeps each BLS source class intact.

The source packet pins the official download URL, archive byte count, SHA-256 digest, workbook name, release date, and retrieval time. A changed byte fails the refresh until the new file is reviewed. A file with a missing or duplicate workbook also fails.

The server source index stores 830 detailed occupations and 584 state or local area rows. Public discovery uses 583 unique places after the duplicate Guam row is removed. The browser does not receive the full government workbook or source archive.

Evidence: bls-oews-may-2025 · Rule: official-workbook-separation · source-byte-pin · server-only-shards

Who the data covers

OEWS covers wage and salary jobs in its survey scope

OEWS covers wage and salary workers in covered establishments. It leaves out people who work for themselves. It also has source rules for industries and workers in scope. The page source note links to the BLS method so a reader can check the full boundary.

Employment is a job estimate, not a head count of unique people. One person can hold more than one job. The field is also not the number of open posts. Current public jobs appear in a separate block with their own source and seen date.

Wage fields do not include every part of pay. Benefits are not in the shown wage. A role can also have tips, bonus pay, stock, or hours that need careful source reading. WageScope does not add a missing pay type to the BLS row.

Evidence: bls-oews-may-2025 · Rule: oews-covered-workers · employment-job-definition · wage-scope-limits

Wage math

Median, mean, and percentiles keep their source meaning

Median is the middle wage point. Mean is the sum of wage values divided by the number of jobs behind the estimate. Percentiles are rank points in the spread. WageScope does not turn a percentile into a worker level or a time-based career step.

Annual and hourly fields stay apart. A page uses annual when the source publishes the annual field. It uses hourly when annual is not the supported field. Annual-only rows do not get a made-up hourly value. A comparison requires the same field on both sides.

Wage gaps use a plain percent formula: value minus base, divided by base, times 100. A positive sign means above the base. A negative sign means below it. WageScope reports the gap but does not name a cause that the rows cannot support.

Evidence: bls-oews-may-2025 · Rule: wage-field-definitions · annual-hourly-separation · percent-difference-formula

Missing data

Blank and top-coded values never become zero

BLS can leave a field not available or not released. WageScope keeps that state. It does not put zero in the chart, rank, prose, or schema. A missing local row leads to a clear recovery path instead of a soft page with a guessed wage.

Some high wage fields are top coded. WageScope shows the approved lower-bound label, such as at least the top-code mark. It does not claim an exact value above that mark. A top-coded field can also be left out of math that needs a precise number.

Ranks use only rows with the matching published field. The denominator says how many rows qualified. A missing row is not placed last. This stops absence from being read as low pay and keeps the rank tied to actual source values.

Evidence: bls-oews-may-2025 · Rule: missing-state-preservation · top-code-lower-bound · rank-eligible-denominator

Survey care marks

RSE belongs to the field beside it

RSE means relative standard error. It is a survey precision flag. A smaller value often means less sampling uncertainty. It is not the chance that one person's pay is right or wrong. It is also not a quality score for a place or role.

Employment RSE stays with the employment estimate. Mean-wage RSE stays with the mean. BLS does not give the same field for the median and each percentile. WageScope does not move a mean RSE onto the median or use an employment RSE as a wage care mark.

A local row can have more survey uncertainty than a broad national row. The page keeps the exact RSE values visible when BLS supplies them. It does not hide a large value or turn it into a confidence claim.

Evidence: bls-oews-may-2025 · Rule: rse-definition · rse-field-scope · no-confidence-overclaim

Price-level math

BEA price data stays separate from BLS wages

The current pinned BEA file has 438 exact BLS state or metro matches. The United States price level is 100. All items is the broad index. Housing, goods, utilities, and other services remain separate source fields.

The national-price-dollar proxy is nominal wage divided by the all-items index divided by 100. Equivalent nominal pay holds one proxy fixed and applies the other place's index. These are deterministic formulas. They do not call a model or use a hidden place score.

The proxy is not take-home pay or a personal budget. It leaves out taxes, benefits, household size, debt, commute, and taste. An exact BEA match is required. If no match exists, the BLS page stays available and the price block stays absent.

Evidence: bls-oews-may-2025 · bea-rpp-2024 · meritlog-bounded-comparison-v1 · Rule: rpp-us-baseline · price-proxy-formula · exact-rpp-match

Public job method

Discovery is broad; embedded wage-page matches are strict

MeritLog's public job search can use fuzzy discovery to help people find work. A WageScope card adds a narrower title check. The employer title must pass a reviewed occupation plan. Unclear or cross-role rows are removed even when that leaves no cards.

The match does not say BLS classified the post. It is a MeritLog employer-title match. A place filter is used only through an exact approved public place identity. When a safe place match is absent, the page says the cards are not narrowed to that area.

Only approved public fields reach the card. Private jobs and pasted descriptions never enter WageScope. Job descriptions are not copied into page prose. Job-card words do not help a page reach the depth or unique-content gate.

Evidence: meritlog-public-job-boundary-v1 · Rule: strict-employer-title-match · exact-public-place-match · public-field-projection

Index gate

Useful visible words must pass before a page enters discovery files

A valid data page is not always an index page. MeritLog requires at least 1,500 useful visible words in stable primary content. Navigation, tables, chart ticks, job cards, CTAs, hidden text, schema, and repeated source notes do not count. A thin page can still help a direct visitor, but it stays noindex.

The release checks every page for plain language, source and rule IDs, repeated paragraphs, route-specific coverage, and five-word-shingle overlap. Reviewers also test a risk-based set of pages at four screen widths. The sitemap, robots view, and LLM guide all read the same approved catalog.

Google has no preferred word count. The 1,500-word floor is a MeritLog coverage rule, not a ranking claim. It cannot cause filler, made-up duties, copied job text, or repeated method notes. A page that lacks enough source-backed facts remains outside the index.

Evidence: bls-oews-may-2025 · Rule: useful-visible-word-floor · full-batch-uniqueness · no-word-count-ranking-claim

Source clock

Why the date stays beside the answer

May 2025 OEWS estimates is the wage source used across WageScope. The reference period is May 2025. BLS published the release on May 15, 2026. A current job post may have a newer date, but that does not make the government wage row newer. Each source keeps its own clock.

MeritLog checks the official BLS tables each week. A newer complete release blocks the word latest until the new files are pinned, checked, and reviewed. The old page does not change its date to look fresh. A source update can replace the data only after the new bundle passes the same row, field, and page checks.

BEA price-level data has a separate clock. The current WageScope price source is for 2024. It was published on February 19, 2026. WageScope shows the wage and price periods together when both are used. It never says the two sources describe the same month.

Evidence: bls-oews-may-2025 · bea-rpp-2024 · Rule: visible-source-period · independent-source-freshness · no-false-freshness

Jobs stay separate

What a current listing can and cannot add

A public job card can add an employer, title, place, source, and seen date. WageScope keeps only strict employer-title matches for a reviewed occupation. It may show no cards even when the wage row is complete. A false negative is safer here than a card for the wrong role.

A listing may show posted pay. That range belongs to one employer post. It never enters the BLS median, mean, percentile, employment count, or price-level proxy. A list of posts also does not become a hiring score. The BLS row and the public catalog answer different questions on different clocks.

The stable content gate ignores job-card words. Jobs can change at any time, so they cannot decide whether an evergreen page has enough depth or unique source-backed text. When the catalog is empty or down, the wage page stays available and says what happened. It does not insert sample jobs into an indexable page.

Evidence: bls-oews-may-2025 · meritlog-public-job-boundary-v1 · Rule: strict-employer-title-match · posted-pay-separation · jobs-excluded-from-content-gate

Public and read only

What WageScope does with a visit

A WageScope page reads public government facts and eligible public job fields. It does not read Career Memory, private jobs, a pasted job description, exact private pay, or a saved résumé. Opening a role or place does not create a private fact. A public GET request does not start a model task.

The page does not save a search, role, place, wage, or job card to build a private MeritLog profile. While public analytics are on, GA4, Ahrefs, and Meta may receive the public page URL; Your Privacy Choices or Global Privacy Control turns that off. WageScope can work for a visitor who never signs in.

Résumé work begins only after a person chooses a job and enters the governed MeritLog path. The person confirms the work facts used in a draft. A BLS wage, area rank, job count, or price proxy cannot become a résumé claim. The public page remains useful even when the private workspace is closed.

Evidence: bls-oews-may-2025 · meritlog-public-job-boundary-v1 · Rule: public-private-separation · no-get-write · confirmed-resume-evidence

The official row stays the official row.

Four controls before a number reaches the page

Pin the source bytes

Preserve source level

Keep suppression visible

Recheck the release

Useful context, with hard limits.

Who OEWS covers

Why percentiles are not averaged

Employment RSE and mean-wage RSE

What an area rank means

How MeritLog jobs join the page

How WageScope handles the data

Tailor for a real target role job, not a generic wage number.

Four BLS workbooks keep national, state, metro, and nonmetro facts apart

OEWS covers wage and salary jobs in its survey scope

Median, mean, and percentiles keep their source meaning

Blank and top-coded values never become zero

RSE belongs to the field beside it

BEA price data stays separate from BLS wages

Discovery is broad; embedded wage-page matches are strict

Useful visible words must pass before a page enters discovery files

Why the date stays beside the answer

What a current listing can and cannot add

What WageScope does with a visit

Privacy choices

The official row stays the official row.

Four controls before a number reaches the page

Pin the source bytes

Preserve source level

Keep suppression visible

Recheck the release

Useful context, with hard limits.

Who OEWS covers

Why percentiles are not averaged

Employment RSE and mean-wage RSE

What an area rank means

How MeritLog jobs join the page

How WageScope handles the data

Tailor for a real target role job, not a generic wage number.

Four BLS workbooks keep national, state, metro, and nonmetro facts apart

OEWS covers wage and salary jobs in its survey scope

Median, mean, and percentiles keep their source meaning

Blank and top-coded values never become zero

RSE belongs to the field beside it

BEA price data stays separate from BLS wages

Discovery is broad; embedded wage-page matches are strict

Useful visible words must pass before a page enters discovery files

Why the date stays beside the answer

What a current listing can and cannot add

What WageScope does with a visit