Do exotic TLDs hurt SEO? What Google actually says

No — an exotic TLD does not hurt your Google rankings, and a familiar one doesn’t help them. That isn’t hopeful guesswork; it’s Google’s officially documented position. The company’s Search Central blog post “Google’s handling of new top level domains,” published in 2015 and never superseded, states that Google’s systems treat new gTLDs like other gTLDs such as .com and .org, and John Mueller has reaffirmed the same point repeatedly ever since, as recently as 2025. If you’ve been holding off on a .dev, .app, .ai, or .studio domain because you heard Google punishes anything unusual, you can let that go. What’s worth understanding instead are the nuances people mistake for “SEO”: one real geotargeting mechanism, and a couple of indirect effects that have nothing to do with Google’s algorithm but still deserve a seat at the table.

What has Google actually said about TLDs?

The record here is unusually clear and unusually consistent. In the 2015 Search Central post, Google stated that new gTLDs are treated “like other gTLDs (like .com & .org)” and that no TLD is given preferential treatment in ranking — a .BRAND extension gets no more and no less weight than .com. The same post addressed the keyword angle directly: “Keywords in a TLD do not give any advantage or disadvantage in search.”

Mueller has kept repeating the message in the decade since. In an official Webmaster Central office-hours session he put it plainly: “The TLD is not something we take into account.” And as recently as late 2025, asked whether a .music domain would help a music site rank, Mueller has said there is absolutely no SEO advantage from using a .music domain.

That’s one documented position, held steady for over ten years, restated across blog posts, office hours, and public Q&A. Very few SEO questions have an answer this unambiguous.

Does a keyword in your TLD help rankings?

No — and this myth is worth killing from both directions, because people overcorrect in both:

• “A keyword TLD boosts rankings” is false. Registering something.shop for a shop or something.music for a music project gives you no ranking benefit. If a keyword-matching TLD ever seems to help, the lift is a human effect — brand recall, recognition, maybe click-through — not a signal Google’s algorithm rewards.
• “New gTLDs are penalized” is equally false. There is no sandbox, no discount, no trust deficit applied to newer or less common extensions. A well-built site on .pizza can outrank a weak site on .com, and per Google’s stated position, the extensions themselves contribute nothing either way.

If you’re curious what the hundreds of newer extensions actually are and how they came to exist, our guide to new gTLDs covers the landscape.

What about country-code TLDs and geotargeting?

Here is the one genuine, Google-documented way a TLD affects search: geotargeting. A normal country-code TLD — .de, .fr, .jp — tells Google your site primarily targets that country, automatically. That’s usually what a local business wants, but it’s a real constraint if you buy a ccTLD purely for the branding: a .de domain signals Germany whether you meant it to or not.

The important exception: Google maintains a list of roughly 20 ccTLDs it treats as generic — because users worldwide see them as generic rather than country-bound. As of 2026, that list includes .io, .co, .me, .tv, and .ai, among others. Domains on these extensions get no automatic geotargeting; they behave like .com, and if you do want to target a specific region you’d use hreflang and Search Console settings instead. Note the “as of 2026”: Google has changed this list before (.ai was reportedly added in 2023 as the extension’s meaning shifted), so check the current documentation before relying on it.

This is why founders can build global products on .io, .ai, or .co without accidentally telling Google they’re targeting the British Indian Ocean Territory, Anguilla, or Colombia.

So why do exotic TLDs feel like they hurt SEO?

Because two real effects exist that get mislabeled as ranking problems:

• Human trust and click-through. Google doesn’t care about your TLD, but people scanning a results page or an email might. An unfamiliar extension can read as less established to some audiences, which can shave click-through and word-of-mouth. That’s a perception effect, not an algorithmic one — and it varies enormously by audience. Developers don’t blink at .dev; a conservative B2B buyer might hesitate at .icu.
• Email deliverability and spam-filter reputation. Spam filters and security tools do track abuse rates by TLD, and recent Spamhaus data shows some cheap, high-churn extensions carry genuinely poor reputations because a large share of their registrations are malicious. Sending cold email from a domain on one of those extensions is a real handicap — it just isn’t a Google ranking factor. We break down which budget extensions hold up and which carry baggage in our guide to cheap TLDs that don’t look cheap.

Neither of these should be called “SEO” — but both are legitimate inputs to a naming decision.

How should you actually choose, then?

Take rankings off the table entirely — Google has done that for you — and weigh what’s left: what the extension signals to your specific audience, whether you need automatic geotargeting or deliberately want to avoid it, what it costs to renew, and how it sounds when said aloud. Those are branding questions, and they belong in the same conversation as the name itself — our guide on how to name a startup walks through that process.

The myth-free summary: pick the TLD that fits your brand and your audience, because Google genuinely does not care. If you want to see how a name idea looks across .com, .io, .ai, and the more adventurous extensions before you commit, Domain Yoga generates names and checks availability across TLDs in one search.