D
Dan Moore
When utilizing "Custom native site domain" would be great if we could optionally configure ways to deduplicate the normal <BUCKETNAME>.eventive.org sites. Right now there are both user interface and SEO drawbacks to using the custom native site domain functionality.
For example say an organization has EXAMPLEBUCKET.eventive.org also showing up as eventive.EXAMPLE.com thanks to "Custom native site domain":
  1. For SEO purposes, have a way to choose in the "Custom native site domain" configuration which is the canonical version (https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls#rel-canonical-link-method). That
    rel="canonical"
    should show up on both the eventive.EXAMPLE.com and EXAMPLEBUCKET.eventive.org versions, but only one of either
    EXAMPLEBUCKET.eventive.org
    or
    eventive.EXAMPLE.com
    should be used on both so search engines know which to prefer. If you wanted to pick a single default rather than giving the users a choice, it seems likely that the explicitly chosen
    eventive.EXAMPLE.com
    would make more sense than the default
    EXAMPLEBUCKET.eventive.org
    .
The above would be a low-impact way to help with SEO without potentially breaking things. But what I really want is:
  1. For UI purposes, have a way to optionally choose in the "Custom native site domain" configuration to 301/302 redirect users from one version to the other. If you want to make it simpler, just a checkbox to "redirect users to custom native site domain" would probably suffice. But having the optional option to redirect from either to the other might come in handy too.
I'm asking for the above because I like control and there are lots of different use cases, but I think 99% of the situations would be solved by that simple checkbox that would cause the normal
EXAMPLEBUCKET.eventive.org
to get redirected to the custom native site domain
eventive.EXAMPLE.com
would work.