diff --git a/apps/docs/content/guides/auth/social-login/auth-google.mdx b/apps/docs/content/guides/auth/social-login/auth-google.mdx
index eaa07a8ecaa..f9c814c232a 100644
--- a/apps/docs/content/guides/auth/social-login/auth-google.mdx
+++ b/apps/docs/content/guides/auth/social-login/auth-google.mdx
@@ -778,3 +778,11 @@ chrome.identity.launchWebAuthFlow(
 
 </TabPanel>
 </Tabs>
+
+## Google consent screen
+
+![Google Consent Screen](/docs/img/guides/auth-google/auth-google-consent-screen.png)
+
+By default, the Google consent screen shows the root domain of the callback URL, where Google will send the authentication response. With Supabase Auth, it is your Supabase project's domain `(https://<your-project-ref>.supabase.co)`.
+
+If that is not preferable, you can use a [Custom Domain](https://supabase.com/docs/guides/platform/custom-domains) with your Supabase project. You can use it as your project's domain when creating the Supabase client in your application and initiating the authentication flow. It will then show up in the Google consent screen. If you want your app name and the logo on the consent screen, [you must submit your app to Google for verification](https://support.google.com/cloud/answer/10311615).
diff --git a/apps/docs/public/img/guides/auth-google/auth-google-consent-screen.png b/apps/docs/public/img/guides/auth-google/auth-google-consent-screen.png
new file mode 100644
index 00000000000..76942f3b74d
Binary files /dev/null and b/apps/docs/public/img/guides/auth-google/auth-google-consent-screen.png differ