You want a remote job precisely because location should not matter. So it stings to discover that the little location field on your LinkedIn profile still decides which recruiters ever see you. You are competing for jobs you could do from anywhere, and an address line is quietly filtering you out of searches you never knew happened.
Here is how the location field actually behaves, what your honest options are, and why the tempting shortcut, listing a city you do not live in, is the one move that reliably blows up at the worst possible moment.
Why location still gates remote hiring
"Remote" almost never means "anywhere on Earth." Most remote roles come with restrictions the job post may only half explain:
- Legal and payroll reality. A company must be registered to employ people in your state or country, handle its taxes, and follow its labor laws. Many companies only support a specific list.
- Time zones. Teams often require overlap hours, so they hire within a band of time zones.
- Pay bands. Plenty of companies set salary partly by the cost of labor where you live.
- Hybrid ambitions. Some "remote" roles quietly prefer people within reach of an office.
Because of all this, recruiters searching LinkedIn for remote candidates still filter by geography: country at minimum, often state or metro. Your location field is the data those filters run on. If it is blank, vague, or wrong, you fall out of searches silently. The same mechanics operate on the application side too, covered in can your location get you filtered out.
How the field actually works as a filter
Two things are worth understanding mechanically:
- It is a hard filter, not a ranking factor. When a recruiter limits a search to "United States" or "Greater Denver Area," profiles outside that setting do not rank lower. They do not appear at all. There is no partial credit.
- Broader honest settings catch more searches. LinkedIn lets you set a metro region rather than an exact town. "Greater Boston" appears in more radius searches than a small suburb label, and it is equally true.
This means your location strategy is not about persuasion. It is about being present in the right result sets, which is the same logic behind the rest of optimizing your LinkedIn for recruiter search.
The honest options, ranked
1. Your real metro area (the default answer)
Set your location to the broadest truthful region: "Greater Minneapolis-St. Paul Area," not "Shakopee, Minnesota." You appear in metro-wide searches, national searches, and remote searches filtered to your state or country. This is the right setting for the large majority of remote seekers, because most remote-eligible roles filter at the country or state level, and your real metro satisfies both.
2. Real metro plus explicit remote signals
Location alone does not say "I want remote." Add the signals LinkedIn actually indexes:
- In Open to Work, add "Remote" as a location type and list target titles. Set it to recruiters-only if you are employed and searching quietly.
- In your headline, say it plainly: "Customer Success Manager | Open to Remote (US)."
- In your About, one line on your setup: time zone, years of remote experience if you have them, home office reality.
These do the work people wrongly expect the location field to do.
3. Planning a real move: say so, both places
If you are genuinely relocating, keep your current location set truthfully and state the move explicitly: "Relocating to Austin, TX in March" in your headline or About, plus the target city in Open to Work locations. Recruiters treat a committed move with a date as close to local. What they do not forgive is discovering the move was theoretical. The resume side of this situation has its own playbook: how to write a resume for out-of-state jobs before you relocate.
Why listing a city you do not live in backfires
The temptation is obvious. If remote roles filter to certain hubs, why not set your location to one of them? Because the lie has an expiration date, and it expires at the worst moment: offer stage.
Here is the sequence. Your application clears screening. You spend weeks interviewing. Then the offer process begins, and suddenly your real location matters in ways you cannot dodge:
- Payroll and tax setup requires your actual work address. Companies cannot legally pretend you work somewhere you do not.
- Background checks surface address history.
- Pay bands may be tied to the location they believed. Discovering the truth reopens the number, downward.
- Eligibility itself may vanish. If the company is not set up to employ people in your actual state or country, there is no version of the offer that survives.
The best case is an awkward renegotiation that starts with the company learning you misrepresented something. The common case is a withdrawn offer and weeks of interviewing wasted. And unlike a thin skills section, this failure is invisible until you have already paid the full cost. If pay-band geography is your real concern, that is a negotiation topic, not a profile field, and it is better handled openly, as covered in how to negotiate remote or hybrid work into an offer.
Special cases, honestly handled
- Digital nomads. List your legal tax base, because that is what employment eligibility runs on. Mention the travel in About if it is relevant; do not make a recruiter guess which country they would be employing you in.
- Splitting time between two places. Pick the one where you legally reside and work most, and mention the second if it helps ("based in Portland, regularly in the Bay Area").
- International seekers targeting US-remote roles. Your country field is doing exactly what you fear, and hiding it does not change your employability. Target companies that hire in your country or use an employer-of-record; your profile should make you findable for those, not for roles you cannot legally take.
- Rural candidates. Use the nearest recognized metro if LinkedIn offers it truthfully ("Greater Boise Area" covers a lot of Idaho). Otherwise your state-level presence still catches country and state filtered remote searches, which is where most remote sourcing happens anyway.
Location gates the search. Your resume decides the shortlist.
Getting the location field right earns you one thing: presence in the searches you belong in. What happens next depends on the rest of the profile and, once you apply, almost entirely on your resume. Every application, remote or not, gets parsed by software that extracts your location, your titles, your skills, and your history, and recruiters filter applicant lists with the same hard-gate logic you just read about.
Before you spend another week applying, look at what that software actually sees. The free scan at careerbounce.io runs entirely on your device (your resume never leaves your computer) and shows you the parsed result: whether your location line reads correctly, whether your remote experience registers, whether your skills survive extraction. It cannot promise you a job, and neither can any location setting. But it makes the first gate visible, and visible problems are fixable.