Use a custom domain for Deploy and CMS Preview builds

Add A/B testing by branches like Netlify

Some sites pull data from sources that don't have webhooks on changes. For these, it'd be great if Gatsby Cloud had an easy way to setup triggering builds once an hour, or whatever would make sense for a given site.

There is a chance that the *. gatsbyjs.io domain gets crawled and indexed by search engines, which may be unwanted behaviour, especially if a custom domain is configured.

Show build status in Gatsby Cloud contentful app ( https://www.contentful.com/marketplace/app/gatsby/ ). This would be useful information for content authors who do not have access to gatsby cloud.

Gatsby Cloud does not support automatic 301 redirects to URLs with trailing slashes. …/blog/guide-to-fast-websites to …/blog/guide-to-fast-websites/ Again, another very important feature that has us blocked on a current project. Google is penalizing us for duplicate content because of this.

Gatsby Cloud does not support placeholder redirects. This is what I would expect to be a pretty standard feature and required for many enterprise migrations. /news/:month/:date/:year/:slug /blog/:year/:month/:date/:slug This would redirect a URL like /news/02/12/2004/my-story to /blog/2004/02/12/my-story.

For sites hosted on Gatsby Hosting, allow for locale(country)-based redirects in createRedirect.

Currently lighthouse reports are generated only for the home (/) page. It would be useful to have this configurable. Example use case: all of our regional gatsby sites have the'/' redirected to /xx/ page (replace xx with regional ID). Due to this, lighthouse reports are not generated in gatsby cloud.

Build previews use hostnames like this: https://build-12345678-9abc-def0-1234-56789abcdef0.gtsb.io/ https://siteprefix-branchname.gtsb.io/ These would be better: https://build-12345678-9abc-def0-1234-56789abcdef0.siteprefix.gtsb.io/ https://branchname.siteprefix.gtsb.io/ The use case here is whitelisting OAuth domains. I can't safely whitelist all Gatsby build domains. With the prefix as the third-level domain, I could safely whitelist *. siteprefix.gtsb.io for authentication operations.