LinkedIn's Frequent Viewer Tag: How Recruiters Research With One Visit
LinkedIn is testing a Frequent Viewer tag that flags repeat profile visits. Here's what it shows candidates and how recruiters can research with one visit.
If you open a candidate's profile while sourcing, again before the intake call, and once more before outreach, LinkedIn may now label you a "Frequent Viewer" before you've written a word. That is ordinary recruiting work, and the tag makes it visible to the candidate as circling.
On November 11, 2026, WIRED reported the test and LinkedIn confirmed it. The fix isn't hiding. It's moving the research somewhere else and making the LinkedIn visit the last thing you do before you send.
What is LinkedIn's Frequent Viewer tag?
LinkedIn's Frequent Viewer tag is a label in Who Viewed Your Profile that marks people who keep coming back to the same profile. LinkedIn confirmed the test on November 11, 2026, and has said almost nothing else about how it works.
Who Viewed Your Profile is LinkedIn's list of members who opened your profile, with their names and titles unless they browse privately. WIRED broke the story and Social Media Today covered it the same day. Krista Mollion, founder of the creative agency Unignorable Brands, had spotted the tag a month before WIRED's report.
LinkedIn has not disclosed:
- How many visits it takes to trigger the tag
- The time window those visits have to fall within
- How big the test is, which markets it covers, or when it ends
- Whether tagged visitors are told they've been tagged
- Whether visits made in private mode count
One detail contradicts the early coverage. The first reports called it Premium-only, but users in the test don't need a Premium subscription. So a candidate on a free account might see the tag too.
Does LinkedIn show who viewed your profile multiple times?
For members in the test, yes. LinkedIn now flags repeat visitors automatically, so candidates no longer have to spot them by hand. The pattern was always in the data. The tag just puts it on the surface.
Before the test, a candidate who wanted to know who kept checking them had to scroll the viewer list, read job titles, and remember who had shown up last week. The tag turns that manual triage into an automated flag. Once spotting a pattern costs nothing, you should assume the candidate has noticed it.
The history behind the tag is long. As part of Premium, LinkedIn shows visitors from the past year.
What does a repeat visit tell a passive candidate?
It tells them someone is interested but hasn't decided. A passive candidate is someone who is employed and not applying, but would take the right call. To that person, a recruiter who checks back three times without writing looks either undecided or like they're building a file.
Mollion described the tag as a good way to find low-key visitors who may be considering her for an opportunity. That's the passive candidate's reading, and the tag makes it easy. A recruiter who opens the profile on Monday, Wednesday and Friday shows up as a pattern with a company name next to it.
How that pattern reads depends on what comes next:
- Visits followed by a well-researched message: this looks like diligence. The candidate sees you did the work.
- Visits with no message: this looks like hesitation. The candidate wonders why you keep looking and don't write.
- Visits from several people at the same company: this looks like a hiring loop the candidate wasn't invited into.
Looking twice isn't the problem. Looking twice without writing is.
Why the usual recruiter routine now gives you away
The standard research-then-outreach routine produces several visits per candidate, and LinkedIn logs every one. Each step has a good reason behind it. Put together, they make exactly the pattern the tag was built to flag.
A typical sequence looks like this:
- Sourcing pass. You open the profile to decide whether it fits.
- Intake prep. You open it again before the call with the hiring manager.
- Hiring-manager review. The manager opens it too, from their own account.
- Pre-outreach check. You open it again to personalize the message.
- The reopened role. The req comes back months later and you start over.
Having a LinkedIn Recruiter seat doesn't exempt you. Some third-party guides say Recruiter views are invisible, and they contradict each other (onestoplinkedin.com and hyperclapper.com disagree). LinkedIn's own Recruiter help page settles it: viewing a profile "is treated as a profile view that may result in a notification being sent to the member whose profile you viewed, depending on your settings." Assume the candidate can see every one of those visits.
The candidates you want most have the clearest view of you
The engineers recruiters compete hardest for are the ones most likely to see who keeps coming back, because so many recruiters are looking at them. In Refolk's index of professional profiles, there are about 57 US technical recruiters and sourcers for every US software engineer who puts "open source" in their headline.
| Segment | Count | Note |
|---|---|---|
| US technical recruiters and sourcers | 22,130 | Refolk's index |
| UK technical recruiters and sourcers | 785 | Floor; the sample has some off-target titles |
| US engineers with "open source" in headline | 391 | Software, Senior and Staff titles |
| US recruiters per open-source engineer | ~57:1 | 22,130 ÷ 391 |
| UK sample based in London | 56% | 14 of 25 |
On the US side, 19 of a 25-profile sample hold the plain title "Technical Recruiter." Their employers range from agencies like K2 Partnering Solutions and Experis to in-house teams at Snowflake, Apple, Google, Faire and H2O.ai. In the UK, the biggest employers are Monzo, Meta, Capgemini and Randstad Digital. The 391 open-source engineers work at places like Red Hat, Docker, Uber, Rippling and the OpenTelemetry project.
This matters because headlines undercount open-source work. A headline keyword is a weak proxy for what someone actually ships, which is also why so few profiles call themselves maintainers on LinkedIn. The real evidence (commits, review history, maintainer roles, conference talks) lives on GitHub and event sites. So the extra looks you need should happen there, where nobody gets a notification.
Is LinkedIn private mode the fix for recruiters?
No. Private mode hides your name, but it costs you things recruiters rely on, and LinkedIn hasn't said whether private visits count toward the tag. Treat it as a tradeoff, not a fix.
Private mode is a LinkedIn setting that shows your visits as an anonymous member instead of your name and title. It has two costs:
- Reciprocity. On a free account, switching to private mode means you stop seeing who viewed your own profile. Recruiters who treat their own viewers as inbound leads lose that signal.
- No soft introduction. An anonymous visit can't serve as an introduction, because the candidate can't see who you are. A named visit followed by a message is half your opener. An anonymous one adds nothing.
| Approach | What the candidate sees | What you give up |
|---|---|---|
| Visit freely, message later | Your name, possibly a Frequent Viewer tag | The candidate's first impression of you |
| Private mode | An anonymous visitor | Your own viewer list on free accounts, and the soft intro |
| One visit right before sending | Your name, then your message | Nothing, if the research happened elsewhere |
The third row is the only one that doesn't trade one problem for another.
How to research candidates without viewing their LinkedIn profile
Do the deep research where the work actually lives (GitHub, personal sites, talks, commit history), write the message, then open LinkedIn once to confirm current details and send in the same sitting. The profile visit becomes the last step, not the first.
Here's the routine:
- Start from the work. Look at commits, merged PRs, code reviews and issue threads. For senior engineers, review activity often tells you more than authorship, which is the idea behind a reviewer-first senior engineer slate.
- Read what they've published. Personal sites, blog posts, conference talk pages and slide decks tell you what they care about in their own words.
- Map the projects. If they maintain something, look at the repo's contributors and how active it is. The open source repositories and their maintainers are public without anyone being notified.
- Draft the message completely. Reference one specific piece of work. Leave a placeholder only for their current title.
- Open LinkedIn once. Confirm employer and title, fill in the placeholder, and send before you close the tab.
- Save a snapshot. Put a copy of the profile in your ATS and share that with the hiring manager instead of the link.
The hard part is step one: finding people whose work fits before you know their names. A people search engine that indexes GitHub and the open web, not just LinkedIn, helps here. It's also the gap Refolk closes: you describe the person in plain English and get back a ranked shortlist with links to their repos, sites and talks, so the dossier exists before you go near the profile.
Step six matters more than it looks. If the hiring manager gets a snapshot instead of a link, the company's visit count stays at one even when three people review the candidate.
A slow hiring process leaves the longest trail
The longer a req stays open, the more visits pile up in a candidate's history, and that history goes back 365 days. LinkedIn hasn't disclosed the tag's time window, but every pass you make through the same profiles is logged.
The worst case is the hard-to-fill role. Sourcing drags on, the hiring manager rejects the first slate, the req freezes for budget, and it reopens a quarter later. You run the same search, open the same profiles, and the candidates you never wrote to now see a recruiter who has looked at them across two seasons without ever saying hello. That isn't diligence. It's a recruiter who can't make up their mind.
The fix is to work from the copy you saved in step six. When the role reopens, start from your ATS records, not fresh profile views. Two caveats apply. First, saved profiles raise their own data-protection questions, which the saved-profile notice read covers. Second, saved records shouldn't sit around forever. Set a hold-or-delete rule before the next freeze.
The privacy fight over who-viewed data
Viewer data is already legally contested, so a sourcing routine shouldn't depend on how LinkedIn exposes it this quarter. On May 5, 2026, the privacy group noyb filed a complaint with the Austrian Data Protection Authority against LinkedIn Ireland over the paywall around profile visitor data (case C104, with Martin Baumann named in coverage of the filing).
The complaint is about who gets to see visitor data and at what price, not the Frequent Viewer tag itself. But it shows the feature is unsettled. The paywall could change, the tag could roll out to everyone or be dropped, and the threshold could move. A routine built on one visit right before sending holds up under any of those outcomes. A routine built on private mode or on guesses about Recruiter-seat invisibility doesn't.
FAQ
Will a candidate see that I viewed their LinkedIn profile multiple times?
If they're in the test, they may see a Frequent Viewer tag next to your name in Who Viewed Your Profile. LinkedIn hasn't said how many visits trigger it or over what time window, and free users are in the test as well as Premium subscribers. Assume any candidate could see a repeat-visit pattern, and keep your visits to one per candidate, right before you send.
Does LinkedIn Recruiter hide my profile views?
No. LinkedIn's Recruiter help page says viewing a profile from Recruiter is treated as a profile view that may send a notification to the member, depending on your settings. Third-party guides that say otherwise contradict each other. Go by LinkedIn's own documentation and assume your Recruiter views are visible.
Should recruiters switch to private mode to avoid the Frequent Viewer tag?
Probably not. On a free account, private mode hides who viewed your own profile, and an anonymous visit can't work as a soft introduction because the candidate can't see who you are. LinkedIn also hasn't said whether private visits count toward the tag, so you'd be giving those things up for a protection nobody has confirmed. Researching off-platform and visiting once is a cleaner fix.
How many visits trigger LinkedIn's Frequent Viewer tag?
LinkedIn hasn't said. It also hasn't disclosed the time window, the size of the test, or which markets it covers. Any number you see quoted is a guess. Plan as if a second visit might be enough, which means doing your research on GitHub, personal sites and talk pages and saving one ATS snapshot for everyone else on the hiring team.
The data behind this
Try it on the search you came here for
Stop building boolean strings. Just describe the person.
Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.
01Describe them
One plain sentence. Role, city, stack, stage, whatever matters to you.
02I read the web live
GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.
03You read the shortlist
Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.
- Staff backend engineers in NYC who shipped Rust in production
- Series A fintechs in SF under 50 people, growing headcount this year
- Maintainers of fast-growing Rust web frameworks on GitHub
- No boolean, no filters, no seat to buy. One box.
- Read at search time, so a profile updated yesterday counts today.
- Every step visible as it runs, every name with its reason.
500 free credits on sign-up. No card, no demo call. See real searches.