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

.com vs .com.br: Which Domain to Choose and What Changes for SEO

.com.br gives a Brazil signal and local trust; .com is neutral and suits global products. Requirements, price, SEO impact, and when to register both.

.com vs .com.br: Which Domain to Choose and What Changes for SEO
COVER · Comparisons

You registered the domain, the product is live, and someone asks: "why .com and not .com.br?" — or the other way around. It looks cosmetic until you realize the extension changes the geographic signal Google receives, how much people trust the link in search results, and even who is allowed to register the name. And switching later, with organic traffic built up, is expensive.

The short answer, before the details:

  • A business that sells and serves only in Brazil: .com.br.
  • A product born global, priced in dollars or documented in English: .com.
  • A brand with real traffic and some budget: register both and 301-redirect one to the other.

If you haven't been through registration itself, the post on how to register a domain covers the mechanics — registering, DNS, renewals, transfers. This post is about the decision that comes first: which extension makes sense and what it changes for SEO.

What Google does with .com.br and .com

.com.br is a ccTLD (country-code top-level domain), Brazil's country-code domain. Google's documentation on multi-regional sites says a ccTLD provides "a strong signal to both users and search engines that your site is explicitly intended for a certain country". In other words, Google treats .com.br as a relevance signal for searches made in Brazil, with nothing for you to configure.

.com is a gTLD (generic top-level domain) with no country attached. For a .com, Google works out geographic relevance from the other signals the same documentation lists:

  • hreflang annotations (in the HTML, in HTTP headers or in the sitemap);
  • server location, which Google itself calls "not a definitive signal" because of CDNs;
  • local addresses and phone numbers on the page, local language and currency, links from local sites, and the Google Business Profile.

Google also says it ignores locational meta tags like geo.position. And here is the correction many articles on this topic still haven't made: Search Console no longer has a country targeting setting. The International Targeting report was deprecated in 2022, and the Search Console help page says country targeting "is no longer supported". hreflang still works. If someone tells you to "set geotargeting to Brazil in Search Console", the option isn't there.

In practice:

  • .com.br → strong Brazil signal, automatic;
  • .com → neutral; Google infers the country from Brazilian Portuguese content, hreflang, address, phone, currency and links;
  • neither one ranks better by magic. Content, links and relevance still weigh far more than the extension.

What actually changes for SEO

If your .com is a site in Portuguese, with prices in reais, a Brazilian phone number and links from Brazilian sites, Google has no trouble understanding that it's relevant to Brazil. If the site serves more than one country, declare the versions with hreflang:

<link rel="alternate" hreflang="pt-BR" href="https://example.com/br/" />
<link rel="alternate" hreflang="pt-PT" href="https://example.com/pt/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Each version has to list all the others and itself; an annotation that isn't returned (page A points to B, but B doesn't point back to A) is ignored.

The strongest argument for .com.br isn't ranking, it's clicks. The domain shows up in the search result, and for many people .com.br says at a glance "Brazilian site, prices in reais, support in Portuguese". I couldn't find a solid public study measuring that effect, so treat it as a product judgment, not a law: if your audience includes people who are not comfortable shopping online, the national extension removes one doubt from the path. To compare both options side by side, build the result with the same title and description in a SERP preview tool and see how each URL looks on desktop and mobile — showing that to three or four real customers tells you more than arguing about it in a meeting.

Cost and who can register

.com.br at Registro.br: Registro.br advertises .br domain registration at R$ 40 per year (checked in November 2026). That's the price when you register directly with them; resellers and hosting companies charge their own price, sometimes with a first-year promotion. To register, you must be an individual (CPF) or a company (CNPJ) legally represented or established in Brazil. Individuals can register .com.br normally. Some other .br categories have their own ownership rules — Registro.br's category list shows what each one requires.

.com at international registrars: no Brazilian document required. Prices vary a lot between companies, and the classic trap is a $1 first year followed by a renewal of $20 or more. Cloudflare Registrar charges what the registry and ICANN charge, with no markup — for .com, that's around $10–11 per year. Always look at the renewal price, not the first-year one.

Both together: R$ 40 for the .com.br plus about $10.50 for the .com comes to roughly R$ 100 per year, depending on the exchange rate. That's little compared to someone else registering the other extension of your name.

When .com.br is the right choice

E-commerce that ships only within Brazil, clinics, law firms, real estate agencies, schools, local service providers: any business where the country is part of the product. .com.br delivers the geographic signal for free, matches the audience and avoids the "is this from here?" question.

It's also the natural choice when the .com of the name is taken and the .com.br is free. A clean .com.br beats a .com with a hyphen or an invented suffix.

When .com makes sense even for Brazil

Three scenarios where I'd pick .com without hesitation, even with an initial audience that is 100% Brazilian:

1. The product may expand abroad. Moving from .com.br to .com once the site has traffic means redirects, Google reprocessing the site, external links pointing to the old domain and weeks of fluctuation. Starting on .com avoids the move.

2. The audience is technical. Developers don't need to see .com.br to trust a tool; much of what they use every day lives on .com, .io or .dev. A dollar-priced SaaS on .com.br creates a localization expectation the product may not meet.

3. The .com.br for the name you want is taken. If perfectname.com.br has an owner and perfectname.com is free, use the .com with Brazilian Portuguese content, a Brazilian address and phone number, and hreflang when there's more than one version. That beats perfect-name-official.com.br.

Register both and redirect

For a brand with real traffic, register .com.br and .com, pick one as primary and 301-redirect the other to the equivalent URL on the primary (not everything to the homepage). Keep links, sitemap and canonical tags pointing only to the primary. If you need to set up the pointing, the post on how to point a domain to your hosting walks through it, and the one on DNS A, AAAA, CNAME and MX records explains each record type.

If you ever need to change the primary, Search Console has the Change of Address tool, which tells Google about the migration — it doesn't replace the 301 redirects, it only speeds up the process.

Subdomain, subdirectory or one domain per country

If you serve several countries, there are three structures: one ccTLD per country (product.com.br, product.pt), subdomains (br.product.com) or subdirectories (product.com/br/). Google's documentation sums it up: a ccTLD makes the country clear, but costs more, needs more infrastructure and each one targets a single country; subdomains and subdirectories are quick to set up, but users can't always tell the country from the URL. The SEO comparison between the last two is in the post on subdomain vs subdirectory. For a new project with a single market, none of these structures is worth the complexity: pick one extension and move on.

Frequently asked questions

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

Not automatically. .com.br gives a strong signal that the site is aimed at Brazil, which helps with locally-intended searches, but it doesn't guarantee positions. A .com in Portuguese, with local signals and good content, competes normally. Content, links and relevance weigh far more than the extension.

Can individuals register .com.br?

Yes. Registro.br accepts CPF and CNPJ, as long as the person or company is legally represented or established in Brazil. Some .br categories have their own ownership restrictions; .com.br accepts individuals.

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

Yes, but it has a cost: a 301 redirect for every URL, updating integrations (email, OAuth, webhooks, certificates), notifying Google through Search Console's Change of Address tool, and a few weeks of organic fluctuation. On a new site with no accumulated authority it's easy; on a site with years of traffic, only migrate if the gain is clear.

.pt or .com.br to reach both Portugal and Brazil?

Each ccTLD signals one country: .pt for Portugal, .com.br for Brazil. For both markets, either keep one domain per country or use a .com with /br/ and /pt/ versions declared with hreflang pt-BR and pt-PT. Portuguese differs between the two countries in vocabulary and spelling, so adapted content is worth it, not the same page at two addresses.

Decide the extension before you register

Choose .com.br if the business is local and your audience includes people who trust what is clearly Brazilian. Choose .com if the product has global ambitions, a technical audience, or it's the only one available for the name you want. Register both when the brand justifies it and 301-redirect the secondary. And forget the country setting in Search Console: it no longer exists. What Google reads today is the extension, hreflang and the site's own local signals.

RD
Author
Rafael Duarte
Backend developer with a background in fintech and B2B SaaS — worked on teams that scaled APIs from zero to millions of requests. Carries enough production scars to hold strong opinions on tools, patterns and architecture decisions. Not an academic: he read the UUID RFC when he had to choose between v4 and v7 for a write-heavy table.
View profile