01Check that Google is allowed in
One launch-day mistake is easy to check and costly to miss: a switch left over from the build. A page with a noindex tag is dropped from Google Search results entirely, and Google's documentation adds that a page blocked in robots.txt never has its noindex rule read, so it can still appear through links from elsewhere. Open your robots.txt and view the source of your homepage before you announce anything. Search for the word noindex. If it is there and you did not put it there on purpose, remove it.
- View the homepage source and search for noindex
- Open yourdomain/robots.txt and confirm it does not block the whole site
- Repeat on one inner page, not only the homepage
- Source: Google Search Central, 'Block Search indexing with noindex', developers.google.com/search/docs/crawling-indexing/block-indexing
02Submit the sitemap from your own Search Console
Google's sitemap documentation says you can submit a sitemap in Search Console or add a Sitemap line to robots.txt, and that submitting is merely a hint, not a guarantee that Google will fetch it. So do it, but expect no date. Verify the Search Console property in an account you own, not the builder's, so the data stays with you. Our /seo page lists verifying the property and submitting the sitemap as the second step of SEO work. The 48-hour build includes a basic SEO structure.
- Add the property in Search Console under an account you own
- Submit the sitemap, or add a Sitemap line to robots.txt
- Expect a hint, not a guarantee: no date for indexing
- Source: Google Search Central, 'Build and submit a sitemap', developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap
03Click everything a customer will touch
Do this on your own phone first, then on a laptop. Tap every menu item, every button and every phone, email or map link. Fill in the contact form and confirm the message arrives in an inbox someone reads. Check that the address starts with https and shows no warning. Look at the page title and the icon in the browser tab. Our 48-hour build covers a responsive layout, working forms and calls to action, hosting and SSL. You are the one who knows which phone number is the right one.
- Send a test message through every form and confirm where it lands
- Tap every phone number, email address and map link
- Confirm the address starts with https and shows no warning
- Read every price, address and opening hour against the real ones
04If the site replaces an old one, test the redirects
Skip this section only if the domain is new. If the old site had pages Google already knows, each old address should send visitors to its new equivalent with a 301 redirect, otherwise they land on an error page. List the old pages that mattered: services, prices, contact. Then type five old addresses into a browser and confirm each lands where you expect. The case below shows what a full set of redirects looks like on a real rebuild.
- List the old pages that mattered: services, prices, contact
- Each one gets a 301 to its closest new page
- Type five old addresses into a browser and check where they land
05Write down who owns what
On launch day, write down where three things live: the domain registration, the hosting account and the code, and confirm they are in your name. At PROOF48 the client owns the code, the domain, the hosting account and the content. Then agree how changes work. Our terms say standard builds include one round of minor adjustments after the preview, so collect your notes into one list before sending them. Ask what upkeep costs. PROOF48's Maintenance plans start at 27 EUR a month, and there is no mandatory monthly fee.
- Domain, hosting account and code: all in your name
- One list of changes after the preview
- Ask what monthly upkeep costs and whether it is optional
- Keep the logins somewhere your business can reach, not in one person's head
06Where PROOF48 is the wrong choice
This checklist is for a business website: up to about five pages, or one landing page. An online store has a longer one. Cart, checkout, order emails and delivery rules all need testing, and our 48-hour offer does not cover a store. Stores cost 2,500 to 4,500 EUR on their own timeline (Rotiseria, with checkout and pickup slots, went live inside a week). Web apps start at 5,000 EUR. Sites in more than two languages, or waiting on photography that does not exist yet, also get their own timeline. And if nobody can decide the content, building first will not work.
- Online stores with cart and checkout: 2,500 to 4,500 EUR, own timeline
- Web apps: from 5,000 EUR, own timeline
- More than two languages, or photography that does not exist yet: own timeline
- Content that nobody can decide: building first does not work
What a launch on a live domain needed
The SCP Shine & Style case page lists what a launch on a live domain needed: the rebuilt site live since August 2026, every old WordPress URL redirected with a 301, each of 21 salon video clips declared in the sitemap so Search Console counts them, and a booking flow pointing at the salon's live booking platform. That last item is a launch-day check of its own: tap the booking link and confirm it opens a real slot. The page publishes no revenue or booking counts, because we do not measure them.
See the build: SCP Shine & StyleQuestions, answered
How soon does the site go live once I approve the preview?
On our /website-in-48-hours page, approve the preview and we point your domain at it the same day. If you do not approve it, you owe nothing.
Does submitting a sitemap guarantee Google will index my new site?
No. Google's documentation calls submitting a sitemap merely a hint. Submit it anyway, and expect no date.
Who owns the domain and hosting account?
You do, along with the code and the content. Confirm on launch day that all three are in your name.
Is the 48-hour timeline the same for an online store?
No. 48 hours covers a business website of up to about five pages, or a landing page. Stores cost 2,500 to 4,500 EUR and run on their own timeline.
Do I need a cookie banner or a privacy page before launch?
It depends on what runs on your site, and the wording is yours to confirm with a lawyer. Our guides on cookie banners and privacy policies go through the questions to ask.
Where PROOF48 fits
Launch day is a short list: Google allowed in, the sitemap submitted from your own Search Console, every form and link tested on a phone, old addresses redirected, ownership written down. PROOF48 previews the site at hour 48, you pay after you approve it, and the domain is pointed at it the same day. Stores and apps are a different, longer list.
Cosmin Tiu · Founder, PROOF48
Cosmin has worked in online marketing and software development since 2018, and has built with AI every day since January 2023. He still writes code from scratch daily, in Python, React, Rust and C#. PROOF48 ships business websites in 48 hours and invoices afterwards, so every opinion on this blog was paid for in real builds, not in theory.