Staging (preview URL)

What's the difference between staging, a preview and the live site?

Staging and previews are addresses for checking the site before it goes live to customers, while the live address (the production environment) is the one customers see. Some agencies use "preview" and "staging" to mean the same thing.

Hosting service documentation usually describes three stages: the developer's computer (local), the preview, and the live launch (production). Moving the screens you checked in the preview to the live address is called deployment.

A preview runs the same code as the live site, but some values may be set separately for each environment, like the number that receives notifications or the payment settings. So even if notifications worked fine in the preview, it's safest to test once more on the live address right after launch.

Many small websites don't have a separate staging server and finish checking with a single preview link. What matters more than the name is seeing the site once, before launch, exactly as customers will see it.

What does a preview URL look like?

A preview URL is usually a long address generated automatically by the hosting service, or a sub-address like "staging.yourbusiness.com." It may look unfamiliar at first, but that's normal.

Some hosting services create a new preview URL every time a change is made. Opening an old link may show an outdated version, so always check using the most recent link the agency sent.

Preview URLs are sometimes protected with a password or login. If you need to check with your staff, ask ahead of time how to get in.

When you share a preview link somewhere like a staff group chat, let people know it's a pre-launch version. If the link spreads, prices or wording still being reviewed could be mistaken for real information.

What should I check on staging, and in what order?

It's best to check staging twice: once as "a first-time customer" and once as "the owner." As a customer, look at the information and buttons; as the owner, look at notifications and the admin panel.

Plan your checking schedule backward from the launch date and leave a day or two of slack. You need time to fix problems found on staging and check again.

Showing the preview to family or staff and asking them to "try making a booking" also works well. First-time visitors often get stuck on things the people who built the site take for granted.

1. 01Open the latest preview link the agency sent on your phone.
2. 02Scroll from the first screen to the bottom and check text, prices and business hours.
3. 03Tap every menu and button, plus the call and directions links.
4. 04Submit an inquiry or booking yourself, marked "test."
5. 05Check that the notification text or email arrives on your phone.
6. 06Send the link on KakaoTalk and see whether the preview image and title show up correctly.
7. 07Put all the problems you found into one list and send it at once.

What if my preview URL shows up in search results?

As a rule, preview URLs should carry a "don't put this in search" tag (noindex). Google explains that this tag can be added in the page's meta tags or in the server's response header.

One catch: if you block access entirely with robots.txt, Google can't read the noindex tag. To remove an address that's already in search results, use noindex rather than blocking it with robots.txt.

Hosting services like Vercel say they add noindex to preview URLs by default, but if you connect a separate custom address to the preview, you may need to set it yourself. If you see your business's pages at an unfamiliar address in search, tell the agency right away.

At launch, it's the opposite: check that no noindex tag is left on the live address. If preview settings carry over to the live address, your website won't show up in search.

What happens to test bookings or orders made on staging?

As a rule, delete any test bookings, orders and inquiries before launch. If you leave them, they mix with real customer records and skew your stats, or trigger notifications for bookings that don't exist.

Websites with payments are usually checked first using the test mode provided by the payment gateway. If you need to try a payment with a real card, cancel it right away and confirm that the cancellation goes through properly too.

It's best not to enter real customers' names or contact details on staging. A Pilates studio could book a class under the owner's name, and a craft studio could sign up for a class with the owner's contact details.

For features that actually send text notifications, like hair salon bookings, check that the receiving number during testing is your own. If it's set up wrong, test notifications could go to the wrong person.

What should I ask a web agency at the staging stage?

Staging is the last safety net before launch, so agreeing in advance on what to check and when the site can go live keeps launch day calm.

If you have a fixed date for announcing a new class, as a craft studio might, set a deadline for staging checks too. If checking runs late, the launch slips by the same amount.

Once the launch date is set, also decide who checks what on launch day. For example, the developer checks the domain connection and search settings, and you check prices and booking notifications.

• Whether the preview URL is blocked from search
• Whether the preview and live address run on the same settings (notifications, payment, maps)
• Who deletes test data before launch
• When and how you should confirm "check complete" for the site to go live
• Whether the site can be rolled back to the previous version if something goes wrong after launch