Website Launch
How your new website goes live.
Your existing website keeps running while we build a replacement separately. You review the new site, approve it, and we coordinate the switch.
That might mean new hosting or a separate website installation on your existing server. We prepare and test it before changing what visitors see.
Who’s involved
- DOT ROSI
- Development, staging, launch coordination, and verification.
Client- Review, feedback, and final approval.
- IT / Admin
- Hosting, domain access, and technical coordination when needed.
From first build
to live site.
Only the launch affects your public website. Everything before that happens separately.
- 01
Build locally
We develop and initially test the new site on our computers, away from your live website.
DOT ROSI - 02
Review on staging
We put a preview online so you can review the new site, request changes, and check content. We test and revise it before launch.
DOT ROSIClient - 03
Approve for launch
We finish testing and confirm the site is ready. You approve the final version and launch timing.
DOT ROSIClient - 04
Go live and verify
We coordinate the switch, work with IT when needed, and check the public website.
DOT ROSIIT / Admin
Your address stays.
The website changes.
Think of your domain as the address people visit. At launch, we connect that address to the newly prepared website.
Before launch
Visitors keep using your existing site.
New site on staging
Available separately for feedback and testing.
After launch
Visitors now reach the approved new site.
Previous website
Retained temporarily when feasible.
How the switch works.
When the new website is approved, we update your domain to point to the new website instead of the old one. Your web address stays the same, but visitors now see your new site. DOT ROSI coordinates this transition with your IT team when needed.
Some projects use a production deployment on the existing hosting rather than a domain settings (DNS) change. Separate hosting or an isolated website instance is generally preferred for larger redesigns, reorganizations, and migrations. A new server is not always needed.
A few launch questions.
Will my existing website stay online while you work?
Yes. We build the replacement separately so visitors can keep using your current website during development and staging review. The public transition happens at launch.
Do I need to purchase a completely new server?
Not always. We can use new hosting or a separate installation on your existing server. For smaller updates, working within the current site may be appropriate. We confirm the setup with you before starting.
What is a staging website?
It is a separate online preview of your new website. You receive a staging link to review content, test the site, and share feedback before it replaces your public website. Access restrictions are agreed for the project.
Who approves the new website?
You do. DOT ROSI finishes testing and confirms readiness, then the client approves the final website and launch timing before the public transition.
Will my domain name change?
No. We connect your existing domain to the approved new website. Visitors keep using the web address they already know.
What happens to my old page URLs?
When URLs change, we can redirect old addresses to relevant new pages where needed. We agree the redirect scope and check those links as part of launch.
What happens to my current users and plugins?
Necessary users, content, and plugins can be migrated or recreated based on the project requirements. This is not automatic: we confirm which features, accounts, and integrations the replacement site needs.
Will there be downtime?
We prepare and test the replacement before the switch to keep disruption limited. A short interruption may be needed, depending on the setup. Some visitors may briefly see the previous site while domain updates take effect. We agree timing and recovery steps before launch.
Optional details
For your IT team.
The practical coordination points, for whoever manages your hosting or domain.
Exact technical steps depend on the website and agreed project scope. These notes describe our typical transition to a prepared replacement site.
Before launch: hosting, access, and backups
DOT ROSI prepares the new production installation, either on new hosting or a separate instance on existing hosting, and confirms the approved site is ready to serve the public domain. We test staging beforehand and identify the administrator for any hosting or domain changes.
We confirm the required hosting, deployment, CMS, and domain access through agreed secure channels. Backups, recovery steps, and any temporary retention of the previous site are determined before launch.
Launch day: production deployment and domain cutover
After client approval, we deploy the approved site to production or coordinate website-related DNS changes if hosting is changing. The client or authorized IT team may need to apply or approve those changes. Not every launch needs a DNS change or a new server.
Some visitors may reach the previous site briefly while cached records update. We verify the result from the public domain after the transition.
Content, users, plugins, and redirects
We agree which content, accounts, plugins, forms, and integrations are still needed and which will be transferred, recreated, or replaced. Where old URLs change, DOT ROSI maps and verifies approved redirects to relevant new pages.
Sites with changing orders, memberships, or other live data need a specific final synchronization plan.
ClientAfter launch: checks and recovery planning
We check HTTPS, key pages, navigation, forms, redirect behavior, and agreed analytics and search setup. We avoid retiring previous hosting before the transition is confirmed stable where practical.
If an issue appears, we use the agreed recovery plan. Keeping a previous installation available is one option where feasible; it does not replace a tested backup and recovery plan.
Scope, deliverables, responsibilities, and any required migration work are defined by the project agreement.
Talk through your launch