Bilingual website launch checklist.
Before you launch an English and Spanish website, check five areas: search setup, language pairing, forms and lead routing, analytics, and mobile performance. This checklist covers each one with the specific items that most often break on launch day, and who should sign off.
Book a scoping call →SEO checks
Before launch, confirm canonical URLs, hreflang tags, sitemap coverage, robots rules, page titles, meta descriptions, heading hierarchy, schema markup, redirects, image alt text and internal links. For bilingual sites, every important English page should have a clear Spanish equivalent or an intentional reason not to. Hreflang annotations must be reciprocal: if the English page points to the Spanish one, the Spanish page must point back, and each page should list itself. Make sure the canonical URL uses one consistent host name, with or without www, and that the other version redirects permanently to it.
The pre-launch checklist
Use the table as a sign-off sheet. Each row names the check, how to test it and who is usually responsible. Run it on the staging site first, then again within an hour of going live, because configuration often differs between environments.
| Area | Check | How to test |
|---|---|---|
| Canonicals | One canonical per page on a single host | View source on five key pages in each language |
| Hreflang | Reciprocal es, en and x-default tags | Open each pair and confirm both point to each other |
| Sitemap | Every public page listed, no staging URLs | Open /sitemap.xml and spot-check twenty URLs |
| Redirects | Old URLs return a permanent redirect to the new page | Request a sample of old URLs and read the status code |
| Forms | Each form delivers to the right inbox and CRM | Submit a test in English and in Spanish |
| Analytics | Events fire for forms, calls, WhatsApp and bookings | Use the analytics debug view while testing |
| Language switch | Toggle goes to the equivalent page, not the home page | Click the toggle from five deep pages |
| Performance | Mobile loads fast with stable layout | Run a mobile performance test on key templates |
Conversion checks
Test every form, email route, WhatsApp link, Calendly link, phone link, analytics event and thank-you state. A bilingual website can rank and still fail if leads disappear after submission or if Spanish-speaking users are routed to an English-only follow-up path. Submit one test lead in each language and follow it all the way to the person who will answer it: confirm they receive it, in the right language, with the source page recorded. Check auto-reply emails for both languages and make sure currency, phone formats and addresses are correct for each audience.
Performance and QA checks
Run mobile QA first. Check Core Web Vitals, font loading, image weight, sticky headers, tap targets, contrast, layout shifts and form usability. Most business owners review websites on desktop, but many buyers arrive from mobile search or ads. Also read both versions out loud, or have a native speaker do it: Spanish copy that was machine-translated tends to feel off, and that costs trust faster than a slow page does.
- Tap targets large enough for thumbs and visible focus states
- Text contrast that passes accessibility guidelines in both themes
- Images sized for mobile and compressed
- Native-speaker review of both languages
After launch: the first two weeks
Submit the sitemap in Search Console, watch indexing for both language versions, and review the first batch of real form submissions. Check your 404 reports for old URLs you missed and add redirects for them. Review analytics by language to see whether visitors reach the right version and where they drop off. A short post-launch review in week two usually catches the issues that testing did not.
Frequently asked questions
Do I need separate URLs for English and Spanish?
Yes, for search. Separate URLs for each language, linked with reciprocal hreflang tags, let search engines show the right version to the right audience.
Is machine translation good enough?
It is a useful first draft, but have a native speaker adapt the copy. Messaging, objections and calls to action usually need local rewriting, not literal translation.
What breaks most often at launch?
Redirects from old URLs, form delivery, analytics events and the language toggle sending users to the home page instead of the equivalent page.
Can Cloudsoft run this checklist for us?
Yes. We use this checklist on bilingual builds, and we can audit an existing site against it as a short engagement.