01.
Separate URLs per language
A subfolder such as /es/ on your own domain, so the Spanish pages inherit the authority the domain already has instead of starting from zero.
Bilingual website design for U.S. businesses: English and Spanish sites with their own URLs and hreflang
English + Spanish · From $850 · For reference only
Bilingual website design for U.S. businesses
English and Spanish websites where each language has its own pages, its own URLs and hreflang declared both ways, so Google shows each customer the right version. Designed and built by our in-house team, whose working language is Spanish. Landing pages from $850, corporate sites $1,200 to $2,400 and online stores from $1,750. Figures shown are for reference only.
What makes a bilingual website work in search
A bilingual website is really two sets of pages that share one design. The English pages answer English searches and the Spanish pages answer Spanish ones, and each page has its own address. A toggle that swaps the text on the same URL does not do this: Google indexes one version, and the other one never appears in results.
The Spanish side also has to be written for Spanish queries. A translated page keeps the English headings, and those headings answer a question the Spanish-speaking customer did not type. We write the Spanish pages from Spanish keyword research and build the English ones alongside them.
Then there is the path to contact. If a Spanish page leads to an English form, an English confirmation email and an English follow-up call, the customer drops off right when they are deciding. Forms, notices and automatic emails ship in both languages from launch.
Included in every bilingual build
What a bilingual website from 3R Core includes
02.
Hreflang declared both ways
Every page points at its counterpart and back. When this is missing or one-sided, Google guesses, and it often serves the English page to Spanish searchers.
03.
Spanish written, not translated
Spanish pages built from Spanish keyword research by native Spanish writers on our team, with headings that match how the question is asked.
04.
Forms and emails in both languages
Contact forms, confirmations and notices follow the language the visitor chose, so nobody gets switched to English halfway through.
05.
Technical SEO in both languages
Semantic structure, schema markup, sitemap, meta tags, image optimization, page speed and a mobile-first layout, on the English and the Spanish side.
06.
Yours from day one
Domain, hosting, repository and analytics registered in your name. The first year of domain, SSL and hosting is included.
How a bilingual build runs
From first call to launch
- 01.
1 · Discovery call, in English or Spanish
Who your customers are, how many of them search in Spanish, and what the site has to produce: calls, quote requests or orders.
- 02.
2 · Keyword map in both languages
English and Spanish queries researched separately, with one page assigned to each group so your own pages do not compete.
- 03.
3 · Design and build
Design in Figma, then development on Next.js, WordPress, Shopify or WooCommerce depending on the project. Two revision rounds before launch.
- 04.
4 · Launch with measurement
Analytics and conversion tracking installed before go-live, with Spanish and English traffic reported separately.
- 05.
5 · Handover
An admin panel for text, images and posts, a recorded handover session and thirty days of warranty on anything that breaks after launch.
Bilingual website vs. translated website
| Bilingual website | Translated website (plugin or toggle) | |
|---|---|---|
| URLs | One URL per page and language, e.g. /es/ | Often the same URL, text swapped in the browser |
| What Google indexes | Both versions, linked with hreflang | Usually one version |
| Spanish copy | Written from Spanish keyword research | Translated from the English page |
| Forms and emails | In the visitor's language | Often still in English |
| Ranking in Spanish | Possible on its own queries | Rare |
Reference prices and timelines for a bilingual website
| Type of site | Reference price (USD) | Typical timeline |
|---|---|---|
| Landing page | From $850 | 2 to 3 weeks |
| Corporate site, 5 to 8 sections | $1,200 to $2,400 | 4 to 6 weeks |
| Online store (Shopify or WooCommerce) | From $1,750 | 6 to 10 weeks |
Figures shown are for reference only. The exact figure, including the second language, is confirmed in a written quote.
For a first estimate of your own project, try the website cost calculator.
Ready for a written figure? Request a quote and we reply during U.S. business hours.
After launch: ranking the Spanish side
A bilingual site gives the Spanish pages a place to rank. Getting them to rank is ongoing work: keyword research, new pages, internal links and the Google Business Profile in Spanish.
For any U.S. business adding Spanish, that is our Spanish SEO services plan.
For Hispanic-owned businesses whose customers search in both languages, see SEO for Hispanic businesses.
FAQ
Bilingual website design, frequently asked questions
Bilingual website design is building a site in two languages, usually English and Spanish in the U.S., where each language has its own pages and URLs and the two versions are linked with hreflang. That setup lets Google show the Spanish page to people searching in Spanish and the English page to people searching in English.
3R Core's published starting prices apply: a landing page from $850, a corporate site of five to eight sections between $1,200 and $2,400, and an online store from $1,750. The second language is part of the scope we confirm in a written quote after a first call. Figures shown are for reference only.
A landing page takes 2 to 3 weeks, a corporate site 4 to 6 weeks and a full online store 6 to 10 weeks, depending on complexity. What usually stretches a timeline is waiting on copy, photos and access, so at kickoff we tell you exactly what we need and when.
For a U.S. business, a subfolder such as example.com/es/ is the right default. It inherits the authority your domain already has, which a subdomain or a separate domain would have to build from nothing, and it leaves one property to maintain. Whatever the choice, each language needs its own URL and hreflang declared both ways.
A plugin gives you a Spanish version of each English page, so the Spanish page still targets what the English page targeted and keeps headings written for English searches. Machine translation also tends to read as foreign to U.S. Hispanic customers. It is a stopgap, not a way to rank in Spanish.
Hreflang is the markup that tells Google which language version of a page to show to which searcher. Each version needs its own URL and each must point at the other. When it is missing or one-sided, Google picks on its own and often serves the English page to a Spanish-speaking user, which wastes the Spanish page.
Yes. The site ships with an admin panel for text, images and posts in both languages, plus a recorded handover session. Ongoing maintenance is available as a separate service, but it is optional.
Yes. We build Shopify or WooCommerce stores with the catalog in both languages, the payment gateway you use (Stripe, PayPal or the platform's own) and state-level sales tax calculation set up. Online stores start from $1,750. Figures shown are for reference only.
Bilingual website design for U.S. businesses, in English and Spanish
3R Core designs and builds bilingual websites for U.S. businesses, with English and Spanish pages on separate URLs, hreflang declared in both directions and Spanish copy written from Spanish keyword research. Reference prices: landing pages from $850, corporate sites $1,200 to $2,400 and online stores from $1,750. Figures shown are for reference only.
The difference between a bilingual site and a translated one shows up in search. A translated page answers the English question in Spanish words. A bilingual page built for Spanish queries answers the question Spanish-speaking customers actually type, and in most U.S. service categories far fewer competitors have built those pages.
Every build includes the technical base in both languages: page speed, clean URL structure, metadata, structured data and analytics wired up at launch. Forms and automatic emails follow the visitor's language, and the first year of domain, SSL and hosting is included.
Timelines are 2 to 3 weeks for a landing page, 4 to 6 weeks for a corporate site and 6 to 10 weeks for a full online store. Payment is in U.S. dollars, usually half at kickoff and half at launch, invoiced through our U.S. subsidiary.
Once the Spanish side is live, it can be pushed further with monthly Spanish SEO, which is a separate service from $500 per month (reference price).
Our Clients
Companies that trust our vision and results.
Contact Us
Click to interact