Show your own domain at Google sign-in: Cloudflare Workers on your own domain

Your Worker serves yourapp.com, but Google says “to continue to <project>.firebaseapp.com”. On Cloudflare Workers on your own domain you can change that. We ran this route in our lab on 24 Oct 2026, and Google named our domain.

Under 10 seconds · read-only

The route

First, the two console steps you do yourself:

  1. Google Cloud → APIs & Services → Credentials → the auto-created Web client → Authorised redirect URIs: add https://yourapp.com/__/auth/handler. Without it Google shows Error 400: redirect_uri_mismatch.
  2. Firebase → Authentication → Authorised domains: add yourapp.com. Without it sign-in fails with auth/unauthorized-domain.

Then the code change:

  1. Proxy /__/auth/* in your Worker to https://<project>.firebaseapp.com/__/auth/*. Forward the request as-is; Firebase’s docs say this “cannot be done via a 302 Redirect.” Proxying /__/firebase/init.json is optional: it returns 404 on new projects, and the proxy works without it.
  2. Set authDomain: "yourapp.com" in your Firebase config and redeploy.

What you should see

Google’s chooser says “to continue to yourapp.com”. If your app is on app.yourapp.com, Google shows yourapp.com. On *.workers.dev, Google shows your workers.dev account address, not your brand, so add a Custom Domain to your Worker.

What the free check tells you

When your config states the authDomain literally, the card names what Google will show; otherwise it says “Google sign-in name: not confirmed”. It lists your redirect or popup sign-in calls. Workers detected on workers.dev hosts, owner confirms on a custom domain. A workers.dev address can’t show your own domain at sign-in. You need a domain you own.

For Cloudflare Workers on your own domain, the Signhome fix pack (one-time) has the Worker code, a paste-ready prompt for your AI agent and the owner checklist for steps 1–2. The code lives in the pack, not on this page. Your price is shown with your result.

FAQ

What if it doesn’t work for me?

On Cloudflare Workers, it works or you get your money back within 14 days. Our refund policy says: “Works or your money back. If within 14 days you've followed the pack and Google's sign-in still doesn't show your domain, email support with your re-check link. We'll help you fix it, and if we can't, we refund you in full.” It covers apps served by Cloudflare Workers, the hosting setup we’ve tested, and sits alongside your rights under UK consumer law. Full terms: https://pewterkit.com/refunds

Do I need to be a developer?

Your fix pack has a paste-ready prompt for your AI builder, the exact snippet we tested, and a re-check that runs the free check on your app again, so you can see the name Google’s sign-in shows after your change.

Is the check safe?

It’s read-only. It reads your public page and its same-origin scripts, the same page any visitor can open, and sends no cookies. It never asks for a sign-in, a password or access to your accounts.

Which hosts does it cover?

Cloudflare Workers on your own domain. In our lab on Cloudflare Workers, Google’s sign-in showed our own domain (re-checked 24 Oct 2026). A workers.dev address can’t show your own domain at sign-in. You need a domain you own. On Cloudflare Pages, Firebase Hosting, Vercel or Netlify, run the free check, pick your host and leave your email: we’ll email you once when yours is ready.

What’s in the fix pack?

It’s built from the check we ran on the domain you entered: the exact snippet we tested for your host, the two console settings to change with the click path to each, a paste-ready prompt for your AI builder, and a re-check. One-time payment, no subscription.