Streaming live at 10am (PST)

Hosting on a new domain or use a subdomain pros/cons


#1

I am working with this production company tremblingvoid.com I have already done the production site in Webflow using the CMS. They are launching a sales campaign for one of their projects. www.welovetheswitch.com The question is am I better off to start new hosting for the project or use a subdomain and direct the old domain name to point there?

I'm thinking more for SEO purposes because I don't think the existing domain name welovetheswitch is anything special to hang onto. BUt would love to keep the existing SEO power.

Looking for expert thoughts to see if I am missing something if I choose to use a sales page within the prodcution company site?

thanks in advance
Jeremy


#2

I would just redo it in Webflow and point the domain name when done. There isn't much content juice on the existing site.

Of course, you have to set up the page meta tags/improve on the existing one as well:

<title>Trailer view page - The Switch: A Fantastic Transgender Sitcom</title><meta property="og:site_name" content="The Switch: A Fantastic Transgender Sitcom" />
<meta property="og:title" content="Trailer view page" />
<meta property="og:description" content="The Switch: A Fantastic Transgender Sitcom" />
<meta property="og:image" content="http://www.welovetheswitch.com/uploads/4/3/2/8/43287673/9759349.png" />
<meta property="og:url" content="http://www.welovetheswitch.com/trailer-view-page.html" />

#3

Thanks Sam. Can I point the domain to the actual page eg tremblingvoid.com/theswitch not just the main domain tremblingvoid.com ? That is the part I am a little foggy on. I have pointed plenty of domains now but not to a subdomain if that is what the terminology is.


#4

You cannot host a project as a subdirectory of another. If you really want that, the site has to be created inside the tremblingvoid.com project.

Otherwise, if you want to keep it as separate projects, then you could go the subdomain route.

What about the welovetheswitch.com domain? If it's not going to be used anymore, you could just do a 301 redirect to wherever you decide.


#5

the domain still exists, and there are old links pointing to it. SO the 301 redirect I guess is the way to handle that. I think eventually it can be phased out. Not really sure at the steps to do that effectively.

I have set up plenty of domain pointing to webflow hosting but not used the 301 redirect before. Nelson sent me something that works for godaddy it must be similar with other domains

Do you have anything to add to that?


#6

Hmm... Then in that case both options are still available to you.

Option 1: If you want to keep both separate projects, you can just add theswitch.tremblingvoid.com as the primary domain, and www.welovetheswitch.com as a secondary domain to the new project.

Option 2: Only if domain name registrar supports this level of forwarding to a subfolder within another domain name like the image below (Google Domains), then you can just create the theswitch site within tremblingvoid.com's project in a subfolder "theswitch". This will redirect all existing pages in welovetheswitch.com to the subdirectory tremblingvoid.com/theswitch

Both options will still allow SEO to be preserved as you can create redirects if needed (if page name and/or extension is to be changed, page removed, etc.).

For example, for The Story page,

For option 1:
you need to add a redirect for "/the-story.html" -> "/the-story"
this would make http://www.welovetheswitch.com/the-story.html redirect to http://theswitch.tremblingvoid.com/the-story

For option 2:
you need to add a redirect for "/theswitch/the-story.html" -> "/theswitch/the-story"
this would make http://www.welovetheswitch.com/the-story.html redirect to https://tremblingvoid.com/theswitch/the-story