12 min read
Short answer: Put your willingness to relocate on the resume header, on the same line as city and state, and repeat it once in your LinkedIn About section. US corporate reqs in Workday and Greenhouse often filter on location before anyone reads your bullets. A cover letter alone doesn't feed that filter, so qualified files disappear while you're waiting for a human who never got the file.
You're not imagining it when a Denver posting ghosts you while you're in Miami with perfect skills. The screen's often geographic, not merit-based. Before you rewrite bullet one again, check your resume for free with the posting pasted in and confirm your header parses as contact data, not as part of your job title.
Below: why location fields beat cover letters in the queue, when relocation lines backfire, copy-paste header and LinkedIn phrasing for four scenarios, and what to match in the application portal so your story stays consistent.
Quick wins
- Put Open to relocation on the same line as city and state in the resume header.
- Mirror that line once in LinkedIn About; keep Location as your real current city.
- Match the portal location question to the header before you upload.
- Skip relocation language on fully remote US roles with no hub named.
Why US reqs filter on location before your bullets
Most corporate pipelines are not one recruiter reading every PDF top to bottom. The req opens in Workday, Greenhouse, Lever, Taleo, or iCIMS with a location tag: Chicago onsite, hybrid three days in Austin, relocation assistance available. Recruiters set filters on metro, state, or radius. Candidates outside the fence never surface in the short list, even when they'd move tomorrow.
Your resume header is the earliest machine-readable location signal. Parsers grab the first lines as contact data. City and state import into a location field. A relocation note on that same line gives the human a reason to override a mismatch. A relocation note buried in a cover letter does not exist to the filter at upload time.
Cover letters help after you're in the maybe pile. They rarely rescue a file the ATS sorted out because your Miami header did not match a Boston req. That's the gap most relocation advice skips. It tells you to sound eager in prose while the system never saw your eagerness.
LinkedIn runs a parallel filter. Recruiters search by metro and compare profile location to resume location when both exist. One honest About sentence closes the loop. A profile that says Nashville while your resume says Open to relocation to Seattle with no Nashville line reads like you're hiding something or spraying applications.
I've screened batches where the Miami header never matched a Boston req and the cover letter never loaded into the location field. Job searching is draining when silence feels personal. Often it's geographic plumbing. You deserve to know the pipe exists so you stop polishing bullets on files that never entered the recruiter's queue.
Read how recruiters actually scan resumes in the USA for what happens after you clear location. This page gets you past the filter layer first.
When relocation lines backfire
Stating you're open to move is not free. Wrong placement or fake geography burns trust faster than saying nothing. These four cases are where relocation language hurts more than it helps.
Exception: faking a city you do not live in. Listing Chicago, IL in the header when you're in Tampa to pass a filter breaks the moment someone checks the portal, runs a background address, or schedules a same-week onsite. Use your real current city plus Open to relocation to Chicago instead of a false present address.
Exception: fully remote with no hub named. When the posting says remote anywhere in the US and never names an office, relocation language adds noise. Remote | US is the header. Save relocation budget talk for roles that mention hubs or relocation assistance.
Exception: you're not actually willing to move. Saying yes to clear a filter and backing out at offer wastes everyone's time and follows you on referral networks. If you need sixty days or family alignment first, say Relocating within 60 days of offer, not Immediate relocation with no plan behind it.
Exception: relocation as a Skills bullet. Open to relocation listed between Excel and Python reads like keyword stuffing. It does not import into a location field and recruiters skim past Skills on the first pass anyway. Keep relocation on the contact line only.
Before: Skills section lists Salesforce, SQL, willing to relocate anywhere, Tableau.
After: Header: Miami, FL | Open to relocation: Boston, MA or Remote hybrid with quarterly travel.
Compare with should you include address on a resume in 2026 for what belongs in the header besides relocation. Street address still does not belong. City and relocation do.
Where willingness to relocate belongs on resume and LinkedIn
Run these four edits in order tonight. Each step includes a before/after pair you can paste against your file. Don't open the summary section until the header line is done.
Step 1: Add one header line beside your real city
Open your master resume. Under your name, keep your real current city and state. Add a pipe and a relocation phrase that names the posting metro when you apply. Same font as phone and email. No icons, no text boxes, no right-column sidebar for contact data.
Before: Header shows only Portland, OR with no relocation note on a Seattle onsite req.
After: Portland, OR | Open to relocation to Seattle, WA on one line under the name.
Step 2: Mirror the line on LinkedIn About
Profile Location stays your real city. About gets one sentence with the same target metro you put on the resume for that search batch. Do not change Location to a city you do not live in. Recruiters notice the mismatch in search results before they click in.
Before: About discusses skills only; Location says Raleigh; applying to Denver roles with no relocation mention anywhere on profile.
After: About opens with: Open to relocation to Denver, CO for operations and supply chain roles. Location still Raleigh, NC.
Step 3: Match the application portal
Workday and Greenhouse forms ask current city, work authorization, and sometimes willing to relocate yes or no. Answer yes when you mean it. Portal city should match resume current city. Target metro belongs in the header phrase and in optional free-text fields, not as a fake current address in the legal address block.
Before: Resume says Dallas; portal current city says Dallas; willing to relocate left blank on a Chicago req.
After: Resume header Dallas, TX | Open to relocation to Chicago, IL; portal willing to relocate yes; cover letter notes 45-day move timeline if true.
Step 4: Paste-test the header into Notepad
Export single-column PDF. Copy the header. Paste into Notepad. Name, phone, email, city, and relocation phrase should appear in reading order with no skills rail between contact lines and Experience. If relocation landed below your first job title, rebuild the header in Word with left alignment and re-export.
Copy-paste: relocation header templates
Target one metro (onsite req):
Sam Okonkwo
Atlanta, GA | Open to relocation to Charlotte, NC | [email protected] | (404) 555-0182
Two metros you'd actually accept:
Jordan Lee
Phoenix, AZ | Open to relocation: Denver or Salt Lake City | [email protected] | (602) 555-0194
Relocation with timeline:
Priya Nair
Austin, TX | Relocating to Chicago within 60 days of offer | [email protected] | (512) 555-0133
Remote role with hub travel:
Marcus Cole
Remote | US | Open to quarterly onsite in Seattle | [email protected] | (206) 555-0177
LinkedIn About (one sentence):
Open to relocation to [City, ST] for [function] roles; based in [current city] today.
Before/after: registered nurse, travel-ready
Before: Header Cleveland, OH only; applying to Phoenix hospital system with no relocation line; cover letter mentions moving in paragraph four.
After: Cleveland, OH | Open to relocation to Phoenix, AZ | Active RN license OH, eligible for AZ endorsement; bullet one: Managed 1:4 patient ratios on 28-bed telemetry unit with 96% satisfaction scores on HCAHPS rounds.
Before/after: warehouse operations lead
Before: Header lists city only; Skills row says willing to relocate; bullet one still opens with helped with shipping.
After: Memphis, TN | Open to relocation to Nashville or Louisville | bullet one: Supervised 14 pickers on 180K sq ft floor; held order accuracy at 99.1% through peak season 2025.
Before/after: software engineer, hub hybrid
Before: Remote | US header on a hybrid req that names San Jose office three days weekly; no relocation or commute signal.
After: Boise, ID | Open to relocation to San Jose, CA for hybrid role | bullet one: Shipped payments API in Go serving 2.1M daily transactions with 99.97% uptime in Q2 2025.
Edge case: international candidate targeting US metro
Keep your real country and city on the header when you're abroad. Add Open to relocation to [US metro] and put work authorization in the portal, not a fake US address on line two. Visa timing belongs in recruiter conversation after screen, not as a five-line block above Experience.
Before: Header lists a US city the candidate has never lived in to look local.
After: Toronto, ON | Open to relocation to New York, NY | TN visa sponsorship required; authorization noted in Workday form.
Edge case: confidential search while employed
If your employer monitors profiles, skip relocation on the public LinkedIn until you're ready to be visible. Resume header can still carry Open to relocation for direct applications where the file won't circulate internally. Mention timing on the recruiter screen, not on a document that might forward.
See how to fix location and dates mapping errors in US ATS when your header parses into the wrong field after upload.
Test the header against the posting
Relocation lines only work when the rest of the file is worth sending. A clean header with weak bullets still loses after you parse. Score your job match on the posting you have open. The scan flags missing duty terms in Experience when Skills looks full. It won't write your relocation line for you. It shows whether bullet one still gaps after the header is fixed.
Rebuilding from a two-column template that scrambles contact data? Build a plain single-column resume once, drop the header templates above in, and tailor only bullet one and the relocation metro per req instead of redesigning the whole layout each time.
When the portal asks for a cover letter, use it for move timing only. Generate a cover letter from the posting after the header carries your relocation line.
Clear the location screen first
Your willingness to relocate belongs in the resume header and one LinkedIn About sentence, not only in a cover letter the filter never reads. Name the metro you'd actually move to. Keep your real current city honest. Match the portal yes/no box when Workday asks.
Open your file tonight. Add one header line. Mirror it on LinkedIn. Paste-test into Notepad. Tailor the target city per posting. You'll still see silence when reqs close or teams pause hiring. You won't lose as often to a geographic filter you could have cleared in ten minutes.
Run a free ATS resume check on the next posting before you upload. Fix the header on your side. Let queue timing explain the rest.
Read more
Frequently asked questions
Put it on the resume header when the posting names a different metro than where you live. Many US reqs filter on location before a recruiter opens the PDF, and a cover letter alone never feeds that filter. One plain-text line under your city is enough. Use the cover letter to add timing detail, not to carry the only relocation signal.
On the same line as city and state, directly under your name or beside your phone number. Format: Denver, CO | Open to relocation to Chicago, IL. Do not bury it in Skills, a summary paragraph, or a footer. Parsers and recruiters scan the contact block first. A relocation note in bullet five under a 2019 job does not clear a location filter on upload.
Add one sentence in About: Open to relocation to [target metro] for the right role. Update the Location field to your real current city, not the city you hope to work in. Recruiters compare profile location to resume location. Faking a hub city on either file breaks trust at the screen call.
You can when you mean it. Nationwide reads vague to some hiring managers and broad to others. Naming two or three target metros you would actually move to reads more serious: Open to relocation: Austin, Denver, or Raleigh. Match the posting city when you apply so the filter and the human story align.
Skip relocation language when the posting says remote anywhere in the US and names no hub office. Use Remote | US in the header instead. If the ad says remote with quarterly onsite in Seattle, mention willingness to travel or relocate to that hub only when you would actually go. Mixed signals between remote preference and relocation lines confuse screeners.