diff --git a/src/pages/graphql-js/object-types.mdx b/src/pages/graphql-js/object-types.mdx
index 404d15846..d2def51c4 100644
--- a/src/pages/graphql-js/object-types.mdx
+++ b/src/pages/graphql-js/object-types.mdx
@@ -135,7 +135,7 @@ When you issue a GraphQL query against an API that returns object types, you can
 }
 ```
 
-If you run this code with `node server.js` and browse to http://localhost:4000/graphql you can try out these APIs with GraphiQL.
+If you run this code with `node server.js` and browse to http://localhost:4000/graphql you can try out these APIs with [GraphiQL](https://github.com/graphql/graphiql/tree/main).
 
 This way of defining object types often provides advantages over a traditional REST API. Instead of doing one API request to get basic information about an object, and then multiple subsequent API requests to find out more information about that object, you can get all of that information in one API request. That saves bandwidth, makes your app run faster, and simplifies your client-side logic.