diff --git a/apps/www/_blog/2022-11-18-fetching-and-caching-supabase-data-in-next-js-server-components.mdx b/apps/www/_blog/2022-11-18-fetching-and-caching-supabase-data-in-next-js-server-components.mdx
index e819b684120..e713a38ca07 100644
--- a/apps/www/_blog/2022-11-18-fetching-and-caching-supabase-data-in-next-js-server-components.mdx
+++ b/apps/www/_blog/2022-11-18-fetching-and-caching-supabase-data-in-next-js-server-components.mdx
@@ -103,6 +103,8 @@ export default createClient(
 )
 ```
 
+> For automatically adding types to the Supabase client, check out [how to generate types](https://supabase.com/docs/reference/javascript/typescript-support).
+
 Okay, let’s look at some different data fetching and caching strategies.
 
 # Static
@@ -379,6 +381,8 @@ export default function ClientPosts() {
 }
 ```
 
+> Again, check out [how to generate types](https://supabase.com/docs/reference/javascript/typescript-support) to add proper typing for Post.
+
 But now we have loading spinners! Yuck!
 
 # Realtime