A medium.com/me address is a signed-in shortcut rather than a specific person's shareable profile address. It redirects relative to the account signed in on that browser. Ask a willing contact for their actual public profile URL. An owner may open their own profile while signed in and copy the resolved public URL; the important distinction is the destination, not whether the browser was signed in.
Find public social profile clues with our TraceSeek app.
What medium.com/me actually points to
Medium's profile pages hold published stories and editable profile names, pictures and bios. The /me path is different: it redirects to the account currently signed in, so it is not an individual's shareable profile URL. That single fact explains the symptom you saw. The link was never your match's page; it was a shortcut that resolves relative to whoever is signed in. When you opened it in your browser, it correctly showed you. Nothing about the other person's account was involved, so do not read the result as evidence about them. [Medium Help: your profile page]
How to get a shareable public profile URL
Open your own Medium profile and wait for the redirect to finish. Copy the resulting public profile URL that identifies your account, rather than the generic /me shortcut or a settings URL. The public profile can be opened by another reader without handing over credentials. If a contact sent the generic shortcut, ask once for their current public profile URL; do not request login details. [Medium Help: your profile page]
Keep the owner view out of the conversation
Being signed in does not make every page a private settings page: your public profile remains a public destination. Keep private settings screens, session links and account details out of screenshots. For a comparison, use the actual public profile URL and describe only the visible profile. If the destination cannot be reached, note that limit rather than requesting more access. [Medium Help: your profile page]
What you should not request
Never ask for a password, a login code, a session link or a signed-in browser view to resolve a profile mix-up. Those requests are not needed to view a public profile, and satisfying them would hand over account control rather than information. If someone offers credentials unprompted, decline and suggest the public profile address instead. This is a protective boundary, not a judgment about the person. The same rule applies to you: do not hand over your own login details to let someone else check a page on your behalf. [Medium Help: your profile page]
Observation, limit, and next step
Separate what you observed from what it means. You observed that the link opened your account. That observation is consistent with a signed-in shortcut and inconsistent with a shareable profile URL. It does not establish anything about your match's account, activity or identity, and it is not proof that they sent the wrong link on purpose. The practical move is small: request the public profile address, open it, and compare the visible profile with what was claimed. If the address does not resolve to a public profile, stop and ask one plain question.
| observation | limit | next step |
|---|---|---|
| The /me link opened your account | A /me address resolves to the signed-in account; it says nothing about the other person | Ask for the public profile address their page displays |
| The link was shared as if it were a profile | This may be a simple copy of a browser-bar address, not intent | Request the public address once, without accusations |
| No public profile address is available | You cannot verify the profile from inside your own session | Record unavailable and stop at the access boundary |
| You are the owner sharing your page | The generic /me address is a signed-in shortcut; a resolved public profile URL is different | Copy the public profile address from your profile view |
A hypothetical walk-through
Suppose a hypothetical reader receives a message saying "here is my profile" with a /me address attached. They open it and see their own name and stories. Applying the steps above: they recognise the address as a signed-in shortcut, they do not screenshot their own settings page, and they reply with one neutral request for the public profile address shown on the sender's own profile page. If the sender supplies it, the reader opens that address and reads the visible context. If not, the reader notes that verification was unavailable and leaves the matter there. This is a hypothetical example. [Medium Help: your profile page]
A couple more questions
Why did a medium.com/me link show my account instead of my match's?
Because /me redirects to the account currently signed in. The address is a personal shortcut, not a shareable profile URL, so it resolves against your browser session rather than pointing at a specific person.
Should I send a screenshot of what the link showed me?
No. What it showed you is your own signed-in view, which reveals nothing about your match and may expose your account context. Ask for their public profile address instead and describe only what is publicly visible.
Is it reasonable to ask my match for their login so I can check the page?
No. A public profile can be viewed without anyone's credentials. Asking for a password or session access is an unnecessary account risk; decline if it is offered and request the public profile address instead.
I am the owner. How do I share my profile correctly?
Open your own profile, wait for it to resolve and copy the actual public profile URL. Do not share the generic /me shortcut or a settings/session link.
Sources & editorial notes
Official references checked on October 23, 2026. Checklists, comparison tables and example wording are DateClues editorial tools, not official tests or validated risk scores.
General information. No guide or tool can certify a person’s identity, intentions or safety. Read our editorial standards.