All articles
74 articles · updated weekly See our Tools
All articles
Comparisons

.com.br vs .com: National or International Domain — Which to Choose

Your TLD determines automatic geotargeting, trust with Brazilian users, and who can register it. Here's when each extension actually makes sense.

COVER · Comparisons

You registered the domain, the product is live, and someone asks: "why .com and not .com.br?" — or the other way around. The question seems cosmetic until you understand it affects Google indexing, Brazilian user conversion, and who can register the domain in the first place. Choosing between a national and international TLD is a positioning decision, not just aesthetic preference.

If you haven't been through the registration process itself, the post how to register a domain covers the full mechanics — registrars, DNS, renewals, transfers. This post focuses on the decision that comes before: which extension makes sense for your case.

What Google does with ccTLD vs gTLD

.com.br is a ccTLD (country-code Top-Level Domain). Google treats ccTLDs as an explicit geographic signal. A site on .com.br automatically receives geotargeting for Brazil. The Googlebot will prioritize that domain in Brazilian search results, regardless of any Search Console configuration.

.com is a gTLD (generic Top-Level Domain) — no geographic affiliation. A .com site needs to be explicitly configured in Google Search Console (Property → International Targeting → Brazil) to receive the same geotargeting signal. Without that configuration, Google treats the .com as international and distributes traffic without geographic preference.

In practice:

  • .com.br → automatic geotargeting for Brazil
  • .com → neutral by default, configurable via Search Console
  • .com with correct hreflang + Search Console configured → behavior close to .com.br

The ccTLD is easier to get right. The gTLD is more flexible. Neither is magically better for rankings — content, backlinks, and domain authority still dominate. The TLD is one signal among dozens.

Cost and who can register

This part tends to get overlooked and creates unpleasant surprises.

Registro.br (.com.br): requires a valid Brazilian CPF (individual taxpayer ID) or CNPJ (company ID). Individuals can register .com.br normally — the CNPJ restriction applies to specific categories like .org.br and .ind.br. The price is currently R$ 40/year (set by Registro.br, no variation between registrars). There's no cheaper renewal in the second year — the price is fixed. Registro.br's interface has improved considerably, but transferring between domestic registrars still involves their Transfer Authorization bureaucracy.

Global registrars (.com): no documentation restriction. Anyone in the world can register a .com. Pricing varies — Namecheap and Cloudflare Registrar charge between $9–12/year for .com. Cloudflare Registrar is one of the few that charges wholesale price with no markup. Watch out for registrars advertising $1 in the first year and $25 on renewal — it's common practice and the impact only shows up later.

Registering both: for products with a Brazilian audience and eventual international aspirations, registering .com.br + .com is defensive and cheap. The combined total runs around R$ 150/year. The typical strategy is to use one as primary and 301-redirect the other, maintaining backlink and brand consistency.

Geographic SEO in practice: when the ccTLD actually matters

The strongest pro-.com.br argument isn't ranking — it's CTR in search results. Brazilian users, especially those less familiar with the digital world, have more trust in .com.br. The domain immediately signals that the site is Brazilian, prices are in reals, support speaks Portuguese. That converts into clicks.

For e-commerce, local services, law firms, clinics, real estate agencies — any business where location is part of the product — .com.br has a real credibility advantage in perception, not algorithm.

For dollar-priced SaaS, developer-first tools with English documentation, or products born global, .com makes more sense even if the initial audience is Brazilian. .com.br creates a localization expectation that may not match the actual product.

When .com makes sense even for a Brazilian audience

Three scenarios where I'd choose .com without hesitation, even with a 100% Brazilian audience:

1. A product that will (or could) expand internationally. Switching from .com.br to .com as the product grows costs months of SEO work. Building domain authority from scratch with a new domain is expensive. Choosing .com from the start avoids that.

2. A technical product where the audience already trusts .com. Developers don't need to see .com.br to know the service is Brazilian. GitHub, npm, and Stack Overflow don't have .com.br — the tech audience has already normalized .com for global tools.

3. The .com.br for the name you want is already taken. If perfectname.com.br is registered and perfectname.com is available, that's your domain. Registering perfect-name.com.br or perfectnameofficial.com.br is worse than using perfectname.com with geotargeting configured.

Trust and brand perception

There's empirical evidence worth mentioning without overstating it: UX studies in Brazilian e-commerce consistently show that users with less digital familiarity hesitate more before entering payment information on .com than .com.br. For that audience segment, the ccTLD works as a trust proxy — "it's Brazilian, so it understands my situation."

For a technical audience, the correlation is inverted or nonexistent. A developer who uses GitHub, Vercel, and Notion daily won't trust your product less because of the TLD.

The practical rule: identify the least-technical user profile who will use the product and think about what they see when they read the URL. If the TLD creates friction in the decision to use the product, that has a real conversion cost.

Alternative structure: country subdomain

Some products resolve this with a subdomain or subdirectory structure — br.product.com or product.com/br/. This approach works well with properly configured hreflang and separate Search Console properties per country, but adds SEO complexity that's rarely worth it for new projects. It's the solution for companies that already have a product on .com and want to improve performance in specific markets, not an initial strategy.

Frequently asked questions

Does .com.br rank better than .com in Google Brazil?

Not categorically. .com.br receives automatic geotargeting, which can help with locally-intended searches, but doesn't guarantee better positions. Content, backlinks, and domain authority carry far more weight than TLD. A .com properly configured in Search Console with correct hreflang behaves similarly to .com.br in Brazilian results. The TLD is one factor among dozens.

Can individuals register .com.br?

Yes. .com.br accepts registration with a CPF — no CNPJ required. You just need a valid document in Registro.br's system. Some .br subcategories have specific restrictions (.org.br for organizations, .ind.br for industries), but .com.br is open for both individuals and companies.

If I start with .com.br, can I migrate to .com later?

Yes, but it has a cost. A domain migration involves 301 redirects, updating external backlinks, temporary ranking loss, and reconfiguring all integrations (email, OAuth, webhooks, SSL certificates). For products under 6 months old with no accumulated authority, the migration is feasible. For products with years of backlinks and organic traffic, weigh carefully whether the gain justifies the risk. The ideal is making the right decision before registering.

Do I need to register both .com.br and .com to protect my brand?

For most small independent projects, no. For products with real traffic and an established brand, yes — the combined cost (~R$ 150/year) is low compared to the risk of someone else registering the other TLD and creating brand confusion or a malicious lookalike site. Redirect the secondary to the primary with a permanent 301.

.com.br or .com: the decision you can't undo cheaply

Choose .com.br if your product is explicitly local and the end audience includes users with less digital familiarity. Choose .com if the product has global potential, a technical audience, or the .com.br for the name you want is already taken.

What you can't do is treat the choice as a last-minute detail. Unlike the database, framework, or programming language — where you can refactor later with effort — changing the domain of a product with accumulated organic traffic costs months of SEO recovery. To generate name variations and check availability before committing, I use the QR code generator to create provisional business card versions with each option and show them to real users before registering — sometimes the reaction to the URL tells you more than any technical analysis.

Decide before registering. Register both if you have the budget. And if you go with .com, configure geotargeting in Search Console on the same day.

RD
Author
Rafael Duarte
Desenvolvedor backend com passagem por fintech e SaaS B2B — trabalhou em times que escalaram APIs de zero a milhões de requisições. Carrega cicatrizes de produção suficientes para ter opiniões fortes sobre ferramentas, padrões e decisões de arquitetura. Não é acadêmico: leu a RFC do UUID quando precisou escolher entre v4 e v7 para uma tabela de alta escrita.
View profile