The problem

Google Sign-In Not Working in the Instagram Browser? Why

Someone taps your link, hits “Continue with Google”, and gets a blank page or an “Access blocked” error. Your login works everywhere else. The problem is the browser the tap landed in.

October 7, 2026 · 3 min read

Google does not allow its sign-in page to load inside an embedded browser. Instagram, TikTok, Facebook and similar apps open links in exactly that kind of browser, called a webview. So when a visitor taps Continue with Google there, Google refuses the request. The error usually reads “Access blocked”, “Use a secure browser”, or Error 403: disallowed_useragent.

What it looks like for your visitor

A Google error page saying the app’s request does not comply with Google’s policies, with no way forward.
A blank or endlessly loading screen after tapping the Google button.
A login that loops: the visitor signs in, lands back on your page, and is still logged out.
Other social logins misbehaving too. Apple, Facebook and passkey sign-ins can fail or lose their session in a webview for the same reason.

In the app

Instagram browser

In the browser

Safari · Chrome

Same login button, same account. Different browser, different outcome.

Visitors can’t log in from your bio link? A Linkamy link opens in Safari or Chrome, where Google sign-in works. Free, no card, first link in about 30 seconds.

Start free

How to confirm it’s this and not your login

Open your own link from inside Instagram or TikTok, not from Notes or a text to yourself, and try the Google button.
Try the same page in Safari or Chrome. If it works there, the login is fine and the browser is the cause.
Compare sign-up rates for visitors from social bios against email or direct traffic. A big gap points here.

of in-app sign-ups can stall on a blocked or looping social login

Illustrative — the real number depends on your audience and platforms.

Illustrative. The real share depends on how many of your visitors rely on Google sign-in and arrive in-app.

You cannot fix this on your login page. The block is Google’s rule about where its sign-in can run, so the fix has to happen earlier: get the visitor into Safari or Chrome before they reach the login.

What you can do

Offer email sign-up next to Google. It always works in a webview, though it is slower for the visitor.
Tell visitors to open the page in their browser. The ⋯ menu in the in-app browser has an “Open in Chrome” or “Open in Safari” option, but most people will not find it on their own.
Route the tap out of the webview automatically so nobody has to find that menu.

How Linkamy fits

Every actionable link hands the tap to Safari or Chrome: automatic on Android, one clean tap on iOS.
Google, Apple and passkey sign-ins then run in a real browser, where they are allowed.
Click analytics show device and source app, so you can see how much of your traffic arrives in-app.

Free to start, no card. If sign-ups from social look low next to everything else, check this first.

Let people log in from your link

Send the tap to Safari or Chrome instead of the in-app browser, and Google sign-in stops being blocked. Free to start, no card.

Start free

Free plan · no card · no password

See how it works →