diff --git a/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap b/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap
index e8ca70911a884..8cd13d2fa5e44 100644
--- a/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap
+++ b/packages/gatsby/src/schema/__tests__/__snapshots__/rebuild-schema.js.snap
@@ -1363,7 +1363,7 @@ If you have explicitly defined a type for those fields, you can safely ignore th
 Otherwise, Gatsby will omit those fields from the GraphQL schema.
 
 If you know all field types in advance, the best strategy is to explicitly define them with the \`createTypes\` action, and skip inference with the \`@dontInfer\` directive.
-See https://www.gatsbyjs.com/docs/actions/#createTypes",
+See https://www.gatsbyjs.com/docs/reference/config-files/actions/#createTypes",
     ],
   ],
   "results": Array [
diff --git a/starters/gatsby-starter-wordpress-blog/gatsby-node.js b/starters/gatsby-starter-wordpress-blog/gatsby-node.js
index 0fac0eac41a32..e79dba10e627f 100644
--- a/starters/gatsby-starter-wordpress-blog/gatsby-node.js
+++ b/starters/gatsby-starter-wordpress-blog/gatsby-node.js
@@ -97,7 +97,7 @@ async function createBlogPostArchive({ posts, gatsbyUtilities }) {
       }
 
       // createPage is an action passed to createPages
-      // See https://www.gatsbyjs.com/docs/actions#createPage for more info
+      // See https://www.gatsbyjs.com/reference/config-files/actions/#createPage for more info
       await gatsbyUtilities.actions.createPage({
         path: getPagePath(pageNumber),