Before you launch a new website: a technical and SEO checklist

The week a new website goes live is when most avoidable damage happens. Rankings built over years disappear because old URLs were never redirected. Google Ads keep running but conversion tracking silently stops. The staging site's "noindex" setting gets copied to production, and the new site vanishes from search.

None of these problems is difficult to prevent. They happen because launch is rushed and nobody owns the final checks. Use this checklist with your developer or agency, and agree who signs off each section before the domain is switched.

It helps to run through the list twice: once on the staging site a week before launch, and again on the live domain within an hour of going live.

Are search engines allowed to crawl and index the new site?

They must be, and this is the check most often missed. Staging sites are usually blocked from search engines, and those settings sometimes carry over to production.

• Remove any "noindex" meta tag or X-Robots-Tag header from live pages.
• Check robots.txt does not contain "Disallow: /" for all user agents.
• Remove password protection from the live domain.
• Confirm the site uses HTTPS, with one preferred version (with or without www) and the others redirecting to it.
• Generate an XML sitemap that lists only live, indexable pages, and reference it in robots.txt.
• Make sure the staging site stays blocked so it does not compete with the live one.

How do you protect existing rankings with redirects?

Map every old URL that receives traffic or has backlinks to its closest new equivalent with a 301 redirect. If you are replacing an existing site, this is the most important step on the whole list.

Build the redirect map

1. Export all URLs from the old site using a crawler, the old sitemap and Google Search Console's pages report.
2. Add URLs with traffic from Google Analytics and backlinks from a link tool.
3. Match each to the most relevant new page. Avoid sending everything to the homepage.
4. Implement redirects server-side as single hops, not chains.
5. After launch, crawl the old URL list and confirm each returns a 301 to a live page.

Bilingual sites need both language versions mapped. If Arabic URLs change from /ar/ to a subdomain, for example, every Arabic page needs its own redirect. For a deeper walkthrough, see how to redesign your website without losing SEO rankings.

Is on-page SEO and structured data in place?

Every indexable page should have the basics right before launch, because fixing hundreds of pages afterwards is slow.

• One clear H1 per page, with a logical H2 and H3 structure.
• A unique title tag and meta description for each page.
• Self-referencing canonical tags, and hreflang tags linking English and Arabic versions.
• Descriptive alt text on meaningful images.
• Clean, readable URLs in lowercase with hyphens.
• Internal links from main pages to key services, with no links pointing at staging or old domains.
• Structured data for your organisation or local business, services, FAQs and articles, validated with Google's Rich Results Test.

Check that your business name, address, phone and WhatsApp number match your Google Business Profile exactly. Consistency here supports local rankings and helps AI tools describe you correctly.

How fast should the new website be?

Aim to pass Google's Core Web Vitals on mobile for your key templates: Largest Contentful Paint (loading), Interaction to Next Paint (responsiveness) and Cumulative Layout Shift (visual stability). Test the homepage, a service page, a blog post and a contact page in PageSpeed Insights.

• Serve images in WebP or AVIF, sized for how they are displayed.
• Lazy-load images below the fold, but not the main hero image.
• Limit third-party scripts such as chat widgets, heatmaps and multiple tracking pixels.
• Use caching and a CDN, especially if you serve visitors across the GCC.
• Test on a mid-range Android phone over mobile data, not just on office Wi-Fi.

Our explainer on Core Web Vitals for business owners covers what each metric means.

Is tracking working from day one?

Tracking must be tested on the live domain, because many tags are tied to the old site or to staging. Missing a week of data after launch makes it hard to judge whether the new site is performing better.

If you collect personal data through forms, review your privacy policy and consent approach in light of the UAE's personal data protection law (Federal Decree-Law No. 45 of 2021), and take advice on what applies to your business.

Is the site accessible and the content ready?

A final usability pass catches issues that tools miss.

• The site can be navigated with a keyboard, with visible focus states.
• Text has enough contrast and forms have proper labels and clear error messages.
• Animations respect the reduced-motion preference.
• Arabic pages display right-to-left correctly, including forms and menus.
• No placeholder text, test products or "lorem ipsum" remain.
• Contact details, opening hours and prices are current.
• A custom 404 page helps lost visitors find their way.

What should you do in the first 30 days after launch?

Monitor closely and fix issues quickly. Launch is the start of improving the site with real data, not the finish line.

1. Day 1: re-run the crawl, redirect and tracking checks on the live domain.
2. Week 1: watch Search Console for crawl errors, 404s and pages not indexed.
3. Weeks 2 to 4: compare traffic and conversions with the old site, and review real-user Core Web Vitals.
4. Ongoing: keep plugins, frameworks and security patches up to date, and review performance monthly.

Some ranking movement is normal in the weeks after a migration. Significant, sustained drops usually point to a redirect, indexing or content gap worth investigating straight away.

How Upscaleads can help

Our website development projects include a pre-launch audit and redirect mapping as standard, and our SEO team can review a launch handled by another developer. Contact us before your go-live date and we will help you check the details.