This might be a rookie question and I apologize in advance for taking up everyone’s time.
We have a website hosted by Webflow. We are adding a new practice area which contains extensive content. Instead of changing the current site, I thought about building a new site and forward it to a subdomain of the main site. For example, www.abclawfirm.com will have subdomain of practicearea.abclawfirm.com. A new site will be built under practiceareabclawfirm.com and hosted by webflow and forward it to the subdomain. Questions:
Is this possible to do? I created a subdomain which seems to be working. I tried to 301 Redirect for an existing site (another unrelated site) to test and it does not seem to work. The Subdomain is forwarded to the main site.
Do you have any other suggestions to address our objective?
Hey @S_Ron_Alikani — welcome to the forums! Not a rookie question at all.
You can indeed connect a subdomain (or many subdomains) to a Webflow website. For your use case, I think what you are planning on doing (building a new website and using a subdomain to point to that new website) would be best. In fact, that’s pretty much what the Webflow University recommends — see here:
Can I publish different pages to different subdomains?
It’s not possible to publish specific pages to specific domains or subdomains. If you need to publish different pages to different subdomains, you’ll need to set up separate projects for each page. Then, you’ll add a separate site plan to each project and add the specific custom domain(s) or subdomain(s) to each project.
In regards to your redirect not working, I’d be happy to help take a closer look at what’s going on if you can provide domain details. (Feel free to PM me!)
Just wondering if this has been simplified yet?
I’m creating a new version of my website,… and I’m wondering if I indeed need a new project + hosting or if I can do this under the current site.
Here is a related question. I have a site there there are three sets of cohorts or groups:
Public visitors
Artists
Nonprofits
The public visitors will interact 90% of the time through a mobile device. They will access the site via a QR code typically in a public setting and not in their home or with a laptop computer.
Artists and nonprofits, on the other hand, will access the site via a home or business computer. Probably through an email link or search bar.
It is cumbersome to say the least to create one platform or website that hopes to accommodate all three groups with adaptive design.
It makes more sense to create a default site with “mysite.com” or “www.mysite.com” that receives 95% of the web traffic and then a subdomain like “admin.mysite.com” to focus on the needs of desktop users - artists and nonprofits.
Distinctions will be evident how content is displayed probably in a grid. In the default site the grid will be one column for phone or tablet portrait mode. The admin subdomains would offer the same content but in a two or three column grid so the content can be easily edited.
So there is identical content in the default domain and the admin subdomain, but the CSS and page layout will be different.
How should I proceed making this happen? Do I:
Duplicate the project so make modifications to the css that does not create conflicts with the default domain. I am assuming this is necessary and the right way forward. Or