11 min read
You're qualified for roles in another metro, but your profile still reads like you'll never leave your current city. Recruiters filter on location before they open the resume. If Open to Relocate is off, or your headline still says on-site only in a town you're trying to leave, you won't show up in the search they run for Austin or Chicago reqs.
Check your resume for free on the same export you'll attach after you fix the profile. How to set LinkedIn Open to Relocate (US best practice) isn't a single toggle. It's three aligned signals: the Open to Work relocation list, a headline that names target metros, and a one-line relocation note on the resume and Greenhouse forms.
Below you'll see the bar weak profiles fail, before/after pairs across roles, what scrambled relocation signals share, and copy-paste lines for headline, summary, and application answers. Job searching is draining. This page is about matching filters recruiters already use, not debating remote-work policy.
If you've been applying to out-of-state reqs without touching Open to Work, fix the profile before you send another batch. The resume alone doesn't flip location filters sourcers run on day one.
Quick Wins
- Enable Open to Relocate with recruiter-only visibility.
- Name three to five real metros, not open to anywhere.
- Mirror those cities in your headline and resume summary line.
- Answer Greenhouse location questions with the same city list.
The bar your relocation signal must clear
US corporate sourcers run two filters before they read bullets: job title and location willingness. Open to Relocate is the profile-side switch. Your resume and application answers are the file-side proof. When they disagree, many recruiters pass even when the skills match.
The standard you're judged against: profile Open to Work lists specific US metros with recruiter-only privacy, headline names the same metros in plain text, resume contact block or summary includes one relocation sentence with a start window, and Greenhouse or Workday forms repeat those cities when asked.
A composite software engineer in Phoenix with Open to Relocate off and a headline that says Phoenix AZ only won't appear in a Seattle sourcer's filtered search. Same person with Open to Relocate set to Seattle WA, Portland OR, and Denver CO plus a resume line open to relocation to Pacific Northwest and Denver with April 2026 availability shows up in the filter and survives the first glance at the file.
I've passed on strong files when the profile said local only and the cover letter mentioned moving in six months. The mismatch reads like you didn't configure the profile or you're spraying applications. Fix alignment before you scale outbound.
Read how to pick US job titles that match your skills so the title in your headline matches the resume you attach. Title drift plus location drift is a double silent fail.
Edge case: hybrid roles that require one week per month on-site in a hub city. List that hub in Open to Relocate and on the resume. Don't mark nationwide relocation if you'd decline weekly travel.
Edge case: visa or work authorization limits where you can land. State authorization plainly on the resume. Open to Relocate doesn't replace work-eligibility fields in Workday.
Before/after pairs for Open to Relocate setup
Each pair shows a weak relocation signal, what recruiters tend to do with it, and the US best-practice fix. Swap in your cities and titles. Illustrative examples only.
Pair 1: Open to Work toggle left off
Before: Profile location shows current city only. Open to Work badge off. You apply to out-of-state reqs on company sites.
After: Open to Work on, Finding a new job selected, Open to Relocate enabled, recruiter-only visibility, cities added: Chicago IL, Minneapolis MN, Milwaukee WI.
Sourcers filtering Chicago won't see you with the toggle off even if your resume mentions Illinois once in an old job line.
Pair 2: Software engineer headline vs resume
Before: Headline: Backend Engineer | Python, AWS | Atlanta GA. Resume summary silent on relocation.
After: Headline: Backend Engineer | Open to Austin TX, Raleigh NC, Remote-US | Python, AWS. Resume line under contact: Open to relocation to Austin or Raleigh with June 2026 start.
Before: Applied to Austin reqs for three weeks with Atlanta-only signals.
After: Same applications after alignment; sourcer search filters match headline cities and resume line.
Pair 3: Nurse profile with vague anywhere language
Before: Open to Relocate on with no city list. Headline: RN, BSN | Will move anywhere for the right unit.
After: Cities listed: Phoenix AZ, Tucson AZ, Las Vegas NV. Headline: Staff RN, Med-Surg | Open to Phoenix, Tucson, Las Vegas | BSN, ACLS.
Hospital recruiters filter on license state and metro. Anywhere reads untargeted. Named metros with license noted in bullet one survive the first filter.
Pair 4: Product manager privacy slip
Before: Open to Relocate set to public. Current employer sees the badge. Candidate turns it off and never re-enables recruiter-only.
After: Open to Relocate on with Recruiters only visibility. Headline lists Denver CO and Salt Lake City UT without a public Open to Work banner if you prefer stealth mode with inbound only.
Privacy scares people off the toggle entirely. Recruiter-only keeps the filter benefit without the network broadcast.
Pair 5: Sales rep resume vs Greenhouse form
Before: Profile lists Dallas and Houston. Resume says local to Boston. Greenhouse form answer: Willing to relocate: No.
After: Profile, resume, and form all list Dallas TX and Houston TX with Q1 2026 availability. One master city list copied into each field.
Before: Enterprise AE | SaaS | Boston MA.
After: Enterprise AE | Open to Dallas and Houston | SaaS | Quota carrier FY24.
Pair 6: Data analyst applying remote-first but relocating
Before: Open to Relocate off because current role is remote. Target reqs say hybrid in Seattle two days per week.
After: Open to Relocate includes Seattle WA and Bellevue WA. Resume summary: Remote today; open to hybrid in Greater Seattle with 30-day relocation window.
Remote on your profile doesn't signal hybrid hub willingness. Name the hub city explicitly when the posting requires periodic on-site days.
Pair 7: Finance analyst headline keyword stack
Before: FP&A | Excel, Hyperion, relocation flexible | New York NY (current city only in location field).
After: FP&A | Open to Charlotte NC, Nashville TN | Excel, Hyperion | Month Year dated roles on resume with Charlotte listed in Open to Relocate preferences.
Flexible without a city string doesn't match metro filters. Spell the cities you'd accept an offer in.
Pair 8: Operations manager stale location after a move
Before: Profile location still shows Miami FL after a move to Orlando. Open to Relocate lists northeast cities from an old search.
After: Profile location updated to Orlando FL. Open to Relocate refreshed to Tampa FL, Jacksonville FL, and Atlanta GA with Q2 2026 availability on resume and forms.
Before: Operations Manager | Supply chain | Miami-based.
After: Operations Manager | Open to Tampa, Jacksonville, Atlanta | Supply chain | Month Year dates on resume showing current Orlando address line.
Stale metros send inbound from markets you already ruled out. Refresh Open to Work whenever your address or target list changes.
Copy-paste relocation alignment block
Paste and replace bracketed lines across profile headline, resume contact area, and optional cover letter closing:
Headline: [Title] | Open to [City, ST], [City, ST] | [Top skill from target reqs]
Resume contact line: Open to relocation to [City, ST] and [City, ST] · Available [Month Year]
Greenhouse / Workday form: Willing to relocate: Yes · Preferred locations: [City, ST]; [City, ST]
Open to Work: Finding a new job · Open to Relocate · Recruiters only · Cities: [same list]
See how to research salary for your role and city before you commit to metros with very different pay bands. Relocation without a comp check leads to offers you can't accept.
What weak Open to Relocate setups still share
Toggle on, cities empty. Open to Relocate without metros matches poorly and looks like an accidental click.
Every US city selected. Spam breadth hurts search quality. Recruiters trust three honest metros more than fifty boxes checked.
Public visibility by default. You turn the feature off after one scare and lose filter matches. Use recruiter-only instead.
Resume still shows old city only. Parsers and humans read the file first on many reqs. Profile-only fixes miss Greenhouse uploads.
Cover letter contradicts the profile. Letter says not open to move while Open to Relocate is on. Pick one story.
Applying to local-only reqs with relocation lines. Wastes screens and trains recruiters to ignore your signal.
Forgetting to update after a move. Stale city lists send you roles in a metro you already left.
Skipping the application location question. Many US forms ask separately from the profile import. Answer yes with the same cities every time.
This won't fix applying when you lack work authorization for the target state. It stops qualified candidates from vanishing in location filters because the toggle was off while the resume whispered relocate once in paragraph four.
Align the resume before you scale applications
Run the export through the free ATS checker with a target posting pasted in. Confirm your relocation line sits in the first screen of plain text, not buried after Skills.
Need a clean single-column base file with room for a contact relocation line? Build your resume, add the copy-paste block cities under your name, then download DOCX before you apply on Greenhouse or Workday.
Turn the toggle into a filter match
How to set LinkedIn Open to Relocate (US best practice) is alignment work. Enable the toggle with recruiter-only privacy, name three to five real metros, mirror them in your headline and resume contact line, and copy the same list into Greenhouse location answers.
Open your profile on desktop tonight. Add cities. Paste the copy-paste block into your resume export. Run a free ATS check on one target posting before you send the next batch.
Optional inbound isn't the same as outbound applications. For reqs you're actively submitting, the file and form answers matter as much as the profile badge.
Set a monthly calendar reminder to re-read Open to Work cities against your active application list. Drop metros where you've declined two screens. Add one new hub when your research shows demand in your lane. Filters only help when the list matches what you'd actually accept.
When a posting asks for a short note on timing, generate a cover letter that repeats your relocation window in plain text. Letter, resume, and profile should agree on cities and start date.
Read more
Frequently asked questions
Use recruiter-only visibility on Open to Work and relocation preferences so your network and current company do not see the badge. Double-check privacy after every profile edit because some mobile flows reset visibility to public. Your headline and resume still need an honest relocation line for US application forms even when the profile badge stays hidden from coworkers.
Pick three to five metros you would actually move to within your stated start window. Recruiters filter on city and state strings. A vague open to anywhere signal matches poorly and reads like spam in search. Name Chicago IL, Austin TX, and Denver CO if those are real options. Skip cities you'd decline after one phone screen.
No. US ATS forms and resume parsers read the file you upload, not your profile badge. Add one plain sentence under your contact block or in the summary: Open to relocation to [City, ST] with [Month Year] availability. Match the same cities you set on the profile so Greenhouse location questions and recruiter search filters agree.
On desktop, open your profile photo badge or Open to Work from the intro card, choose Finding a new job, enable relocation, and add cities under preferences. On mobile, the path hides under the Open to button on your profile header. Save on desktop once so you can read the full city list. Screenshot your settings after save so you notice if a mobile edit drops a metro.
Do not mark relocation for that req if you are not moving. Keep a separate resume version without a relocation line for local-only postings. Wasted screens happen when profile, resume, and application answers disagree. Filter your target list before you spend tailoring time on roles that hard-require on-site day one in a city you won't join.