diff --git a/website/src/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx b/website/src/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx
index 77d10212c770..eb6626f4c98c 100644
--- a/website/src/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx
+++ b/website/src/pages/en/subgraphs/developing/deploying/using-subgraph-studio.mdx
@@ -89,6 +89,8 @@ Once you are ready, you can deploy your Subgraph to Subgraph Studio.
 
 > Deploying a Subgraph with the CLI pushes it to the Studio, where you can test it and update the metadata. This action won't publish your Subgraph to the decentralized network.
 
+> **Note**: Each account is limited to 3 deployed (unpublished) Subgraphs. If you reach this limit, you must archive or publish existing Subgraphs before deploying new ones.
+
 Use the following CLI command to deploy your Subgraph:
 
 ```bash
@@ -104,6 +106,8 @@ After running this command, the CLI will ask for a version label.
 
 After deploying, you can test your Subgraph (either in Subgraph Studio or in your own app, with the deployment query URL), deploy another version, update the metadata, and publish to [Graph Explorer](https://thegraph.com/explorer) when you are ready.
 
+> **Note**: The development query URL is limited to 3,000 queries per day.
+
 Use Subgraph Studio to check the logs on the dashboard and look for any errors with your Subgraph.
 
 ## Publish Your Subgraph