Domain extensions list for SEO: does your extension affect rankings, with the data and the aged-domain nuance

· Last reviewed · 18 min read

Run down any domain extensions list and the SEO question is the same for every entry on it: a domain extension does not directly change where a page ranks, and the registrar and SEO blogs that own this search result have repeated that one sentence for a decade without showing you the data behind it or the part of the answer that changes when you acquire a domain with history.

This guide does both.

It reads the question through sourced, dated evidence instead of adjectives.

Verisign’s registration data shows why .com dominates the namespace, and Spamhaus abuse counts explain why a cheap new gTLD carries reputational baggage.

The GrowthBadger trust study quantifies the click-through and recall gap between extensions, and Google’s own published position appears as a neutral fact inside our analysis instead of as the final word.

Then it covers the axis no incumbent touches: when you buy an aged or expired domain, the extension stops being a branding choice and starts interacting with retained link equity, drop-catch demand, and re-registration value.

The direct-ranking answer is settled. The decision that moves your outcome is which domain, with which history, on which extension, you choose to build on, and that is the question a screened aged-domain catalogue is built to answer.

This guide is general SEO and market education about domain extensions and the aged-domain market. It is not financial, investment, or legal advice, and it does not endorse or value any specific domain or extension.

Every figure cited is a sourced, dated data point from a named third party, not a prediction, a ranking score, or a per-domain number.

Google’s published TLD positions appear as dated neutral facts inside the SEO Domains analytical frame, not as the deciding authority on your individual case.

Does a domain extension directly affect SEO rankings

A domain extension does not directly affect SEO rankings. Google’s published position, stated in its 2015 Search Central guidance on new top-level domains and unchanged since, is that new gTLDs are treated the same as established gTLDs like .com and .org. Keywords inside a TLD give no ranking advantage or disadvantage.

A site on .xyz, .shop, or .ninja has the same direct ranking ceiling as the identical site on .com. The ranking systems read content, links, and user signals, not the string after the final dot.

The one structured exception is the country-code TLD, which Google reads as a geographic-targeting signal instead of a quality signal. That distinction is geography, not ranking power. The direct answer is settled, and the rest of this guide is about the indirect mechanics the one-sentence answer hides.

Google’s published TLD position is a dated neutral fact, not the arbiter of your decision.

The careful way to use Google’s statement is as one dated reference point inside an independent read, not as the close of the discussion. In July 2015 the Search Central blog addressed the wave of new generic extensions directly.

That guidance set out three points that have held through every core update since:

  • Google’s systems treat new gTLDs the same as established gTLDs like .com and .org.
  • A keyword inside the extension confers no search advantage or disadvantage.
  • Region and city extensions such as .london and .bayern are handled as generic, not geographically privileged.

That durability is why the registrar and SEO blogs ranking for this query all cite the statement. The analytical point those blogs miss is that a platform stating its own current behaviour is a fact about the platform, not a guarantee about a market.

That market also runs on trust, abuse reputation, and acquisition history. The SEO Domains analytical desk treats the published position as settled on the narrow question it answers, direct ranking, and then reads the wider decision the platform statement does not address.

The direct-ranking ceiling is identical across gTLDs, so the differentiator sits elsewhere.

Holding the direct answer fixed is what frees the analysis to be useful. If two identical sites on .com and .store reach the same ranking ceiling, then the extension is not where the SEO outcome is won or lost.

A guide that stops at “all TLDs are equal” has answered a narrow question and abandoned the reader at the decision that matters. The outcome is decided by the content, the backlink profile, the user experience, and, for an acquired domain, the history the name carries.

The extension contributes through second-order channels, each of which is measurable and each of which the data below quantifies:

  • Trust perception, the credibility a reader extends before the page loads.
  • Click-through behaviour, the rate at which a familiar extension earns the click.
  • Spam association, the skepticism an abuse-heavy extension inherits.
  • Geographic signalling, the country-targeting a ccTLD carries.

Reading the extension as a direct ranking lever is the misframe that produces a decade of thin advice. Reading it as an input to trust and risk, and reading the domain’s history as the larger lever, is the frame that produces a decision.

The mechanics of how a domain’s accumulated equity carries forward, independent of its extension, run through the Does domain age still matter for SEO in 2026 guide.

How a domain extension affects SEO indirectly through trust, CTR, and spam association

A domain extension affects SEO indirectly through four measurable channels even though it carries no direct ranking weight. None of the four is a ranking factor, and together they move the traffic and the links that are:

  • User trust shifts with familiarity. The GrowthBadger study rated .com the top-scoring extension for trust at 3.5 out of 5.
  • Click-through rate follows recall. People are 3.8 times more likely to assume an uncertain domain is .com, which sends type-in and remembered traffic to the familiar extension.
  • Spam association attaches to extensions where abuse concentrates, raising the filtering and human skepticism a new gTLD has to overcome.
  • Conversion and link-earning track the same trust gradient, because editors and customers extend credibility to the extension they recognise.

The extension does not rank you. It changes who clicks, who links, and who trusts, which is how it reaches SEO through the side door.

Channel 1 · user trust
Trust
.com rated most trustworthy at 3.5 out of 5
The GrowthBadger study of 1,500 people rated .com most trustworthy at 3.5, ahead of .co at 3.4, .org at 3.3, and .biz at 2.9. Trust is not a ranking input, and it governs whether a user proceeds or bounces. Sourced 2022 study.
Channel 2 · click-through and recall
CTR
Users are 3.8x more likely to guess .com when unsure
The same study found people 3.8 times more likely to assume an uncertain domain is .com, and scored .com most memorable at 44 percent. Recall drives type-in and remembered visits the SERP never logs. Sourced 2022 study.
Channel 3 · spam association
Risk
Abuse concentrates in a handful of low-cost extensions
Spamhaus recorded 211,406 .top abuse detections in six months. An extension where abuse concentrates raises the skepticism and filtering a new site has to overcome, independent of its own content. Sourced 2025 Spamhaus data.
Channel 4 · links and conversion
Equity
Editors and buyers extend credibility to the familiar extension
Link-earning and conversion track the same trust gradient, because an editor linking out and a customer converting both weigh the address they recognise. Links and engagement are ranking inputs the extension reaches through trust. Sourced framing.
Figure 1. The four indirect channels through which a domain extension reaches SEO: user trust, click-through and recall, spam association, and links and conversion. Trust, CTR, and equity raise outcomes for familiar extensions; spam association raises the skepticism a new gTLD overcomes. None is a direct ranking factor; each moves the traffic and links that are. Figures are sourced GrowthBadger (2022) and Spamhaus (2025) data points, not ranking scores.

Trust and recall move click-through and type-in traffic the SERP position does not capture.

The indirect channels matter because the traffic they move is real and the SERP rank does not account for it. When a user remembers a brand and types the address from memory, the recall advantage of .com routes that visit to the familiar extension.

The GrowthBadger finding that people guess .com 3.8 times more frequently than any alternative is a direct measure of where uncertain recall lands. The same study scored .com the highest extension for recall at 44 percent against .net at 25, a gap that compounds across every word-of-mouth referral a brand earns.

A site on a less familiar extension ranks identically in the algorithm and still loses the remembered visit and the confident click, because the extension changed the user’s expectation before the page loaded.

This is the channel registrar blogs gesture at with the phrase “user trust” and never quantify. Quantifying it is what turns a platitude into a decision input.

Spam association raises the skepticism a new-gTLD site has to overcome before content earns its place.

The risk channel runs in the opposite direction and is the one the anecdotal guides understate. An extension does not transmit a penalty to a clean site on it, and a clean site on an abuse-heavy extension still has to operate inside a reputational context its neighbours created.

When Spamhaus records 211,406 abuse detections on .top in six months, email providers, security filters, and human readers all calibrate their skepticism toward the extension. A legitimate new site inherits the cost of proving it is not part of the pattern.

The effect is concentrated, not universal. It falls hardest on the low-cost extensions where abuse clusters and barely touches the established gTLDs.

The practical reading is that choosing an abuse-heavy extension for a new build adds a trust tax the content then has to pay down. Choosing an established extension starts the same content from a neutral reputational position.

The per-extension distribution that separates the high-risk extensions from the neutral ones is the subject of the next section.

A domain extensions list by type: what the registration and abuse data say about each

The registration and abuse data sort extensions into a clear risk and trust profile by type. The data does not rank any extension for SEO. It profiles the trust and risk each type brings to the build:

  • Established gTLDs, led by .com at 161.0 million registrations, carry the deepest trust and the lowest abuse association, which is why they anchor recall and click-through.
  • Sector gTLDs such as .io and .ai carry a recognised technical or category premium without an abuse penalty, because their pricing and audience deter bulk abuse.
  • Low-cost new gTLDs such as .top and .xyz carry the heaviest abuse association, with .top alone recording 211,406 abuse detections in six months, which raises the reputational tax a clean site on them pays.
  • Country-code TLDs sit on a separate axis, valued for geographic targeting instead of trust.

Read the type, then read the specific extension’s reputation, before reading any SEO claim attached to it.

Extension typeTrust and recallAbuse associationFootprint signalSEO-relevant read
Established gTLD (.com, .net, .org)Highest; .com rated 3.5/5 and 44% recallLowest of the gTLD set.com base 161.0M of 386.9M total (Verisign, Dec 2025)Neutral reputational start; strongest type-in and recall
Sector gTLD (.io, .ai, .co, .dev)Strong inside the relevant audienceLow; pricing and audience deter bulk abuseCategory-concentrated, not mass-registeredRecognised premium in tech and startup contexts; no abuse tax
Low-cost new gTLD (.top, .xyz, and similar)Lower; less familiar to general usersHighest; .top 211,406 abuse detections in 6 months (Spamhaus).top +94%, .xyz +103% registration growth (Spamhaus, 2025)Reputational tax to overcome; viable for clean builds with extra trust work
Country-code TLD (.uk, .de, .ca)High within the home marketVaries by registry policyGeographic concentration by countryGeographic-targeting signal, not a quality signal; read on the geo axis
Figure 2. Domain extension types profiled by trust and recall, abuse association, registration footprint, and the SEO-relevant read. Trust and recall figures are GrowthBadger (2022); abuse figures are Spamhaus (Oct 2024 to Mar 2025, published 8 May 2025); registration figures are Verisign (31 December 2025) and Spamhaus growth data (2025). The profile reads trust and risk by type; it does not rank any extension for SEO or value any specific domain.

.com dominance is a market fact about user expectation, not a ranking signal Google applies.

The cleanest way to read the Verisign data is as evidence about people, not about the algorithm. A .com base of 161.0 million registrations sits inside a 386.9 million total recorded at the end of 2025.

Verisign-operated .com and .net together cover over 40 percent of the global namespace, which means .com is the default the average user has internalised.

That default is why the GrowthBadger recall and trust gaps exist. Familiarity is earned through ubiquity, and ubiquity is what the registration data measures.

The mistake the incumbent blogs make is to slide from “users trust .com” to “Google ranks .com higher,” which conflates a user-behaviour fact with a ranking claim the platform explicitly denies.

The disciplined read keeps them separate. The registration dominance is real and it shapes click-through and recall, and it does not buy a single position in the ranking.

The historical depth that makes the oldest .com names distinct as assets, separate from any ranking effect, is treated in Expired vs new registration for SEO.

Abuse concentration is the one extension signal that carries a real, sourced cost.

If any extension effect deserves to be called a cost instead of a preference, it is the abuse association the Spamhaus data exposes. The 211,406 .top detections in six months, a 50 percent rise driven by toll-road smishing, sit alongside a broader pattern in the same registration window:

  • 75 percent of the 43.5 million new domains registered between April and September 2025 were gTLDs.
  • .top registration volume rose 94 percent over the period.
  • .xyz registration volume rose 103 percent over the period.

High-volume, low-cost registration is the condition under which bulk abuse operates, and the extensions that offer it become the extensions abuse concentrates on.

For a site owner the consequence is concrete. An extension with a heavy abuse reputation raises the filtering and human skepticism a new domain has to clear, which is a real headwind even though it is not a ranking penalty.

The honest framing is that the extension does not damn the site, and the site on a high-abuse extension starts from a reputational deficit a site on an established gTLD does not. Treating that deficit as a known, sourced input is what separates this read from the anecdotal “new TLDs look spammy” line.

Which domain extension is best for SEO and how to decide

The best domain extension for SEO is the one that adds trust and removes risk for the specific build. For the typical broad-audience project that is .com, because it carries the deepest recall, the highest measured trust, and no abuse tax.

The decision is not a ranking calculation, because every gTLD shares the same direct ranking ceiling. It resolves to four reads set out in the cards below.

The extension never outranks a better domain with stronger history, which is why the decision sits below the choice of which domain to acquire.

Choose the extension that starts the content from the strongest trust position the budget and name allow, then spend the effort on the domain and the content where the ranking is genuinely won.

Decision 1
Default to .com when broad trust and recall drive the outcome
For a brand serving a general audience, .com starts from the deepest trust at 3.5 out of 5 and the highest recall at 44 percent, capturing the type-in and remembered traffic a less familiar extension loses. The direct ranking is identical; the recall and trust are not. This is the default for most trust-sensitive builds.
Decision 2
Accept a sector gTLD when the audience reads it as a category signal
In tech, AI, and startup contexts a .io, .ai, .co, or .dev reads as a deliberate category choice rather than a compromise, carries no abuse tax, and signals fit to the relevant audience. The trade is a slightly lower general-public recall against a stronger in-category read. Match the extension to where the audience already expects it.
Decision 3
Use a ccTLD when the target market is a single country
A country-code extension such as .uk, .de, or .ca gives Google an explicit geographic-targeting signal for the home market, which is a genuine advantage for single-country businesses and a constraint for international ones. Choose it on the geographic axis, not the ranking-power axis, and only when the country focus is real.
Decision 4
Avoid a high-abuse new gTLD for trust-sensitive builds
An extension with a heavy abuse reputation, such as .top with its 211,406 six-month detections, adds a trust tax the content has to pay down. A clean build can succeed on it, and the extra trust work is real, so reserve high-abuse extensions for cases where the exact name justifies the cost. For most builds the neutral start of an established gTLD wins.

Every gTLD shares the same ranking ceiling, so the choice is a trust and risk decision.

Reframing the question is what makes it answerable. Because the direct ranking is identical across gTLDs, “which extension ranks best” has no meaningful answer. The productive question is “which extension starts my content from the strongest trust position for this audience.”

The answer changes with who the audience is:

  • For a mass-market brand it is .com, because the recall and trust data point there and nothing competes with a default the whole user base has internalised.
  • For a developer tool it can be .io, because the audience reads the extension as a signal of fit and the trust gap against .com narrows inside that audience.
  • For a national service it is the ccTLD, because the geographic signal is worth more than marginal recall.

The decision is a portfolio of trust and risk reads, not a ranking lookup. Treating it as a ranking lookup is the error the “best TLD for SEO” articles encode by promising a winner that the platform’s own equal-treatment position rules out.

The extension never outranks a stronger domain, which is why the domain choice sits above it.

The hierarchy is the practical takeaway. A domain with relevant inherited links, a clean history, and a topic that matches the build will outperform a fresh registration on a more prestigious extension, because the inherited authority and the topical fit are the levers the ranking systems genuinely read.

The extension contributes its trust and risk profile on top of that, and it cannot substitute for the underlying domain quality.

This is why a disciplined acquisition process spends its attention on the domain’s history, its link profile, and its topical relevance first, and treats the extension as a final trust-and-risk check instead of the headline decision.

The documented outcomes from acquiring a domain for its inherited equity are collected in Why businesses buy an expired or aged domain: 7 SEO use cases with documented outcomes. The way third-party authority scores read across that decision is set out in What is a good Domain Authority score.

How the extension question changes when you acquire an aged or expired domain

The extension question changes meaning the moment you acquire an aged or expired domain, because the name now carries history the extension interacts with. On a fresh registration the extension is a forward-looking branding choice.

On an acquired domain it sits on top of retained link equity, a topical history, drop-catch demand, and a re-registration value the fresh name has none of.

The “extension does not directly affect rankings” answer still holds, and it stops being the interesting part. The inherited backlink profile and the domain’s prior topic now decide the SEO outcome, and the extension only modulates the trust and liquidity around them.

A .com with a clean, relevant inherited profile is worth more than a new gTLD with the same metrics, because the established extension carries deeper recall and a deeper resale pool. The history is the asset, and the extension prices the trust and liquidity wrapped around it.

When you buy a domain with a past, you stop choosing an extension and start reading an inheritance the extension sits on.

Equity
Retained link equity
An acquired domain carries an inherited backlink profile a fresh registration lacks, and that profile, not the extension, is the SEO asset. The extension is constant; the retained equity is what a buyer pays the aged premium for. Relevance and cleanness decide whether the equity is genuine.
Topical history
The domain’s prior topic carries forward and interacts with the build, independent of the extension. A same-topic continuation preserves inherited authority; a cross-topic repurpose triggers the March 2024 expired-domain-abuse policy discount the extension cannot offset.
History
Demand
Drop-catch demand
An expiring domain with retained value draws competitive drop-catch demand, and that demand concentrates on established extensions because the resale pool is deeper there. The extension sets how contested the name is at the drop, which is a liquidity fact, not a ranking one.
Resale
Re-registration value
An established extension carries a deeper resale market, so an acquired .com with inherited equity holds re-registration value a new gTLD with identical metrics does not. The extension prices the liquidity around the history; the history prices the SEO. Sourced framing, not a per-domain value.
Figure 3. The four ways a domain extension interacts with an acquired domain’s history that are absent on a fresh registration: retained link equity, topical history, drop-catch demand, and re-registration value. The extension modulates trust and liquidity around the inheritance; the inherited links and topic decide the SEO outcome. Framing draws on the Google March 2024 expired-domain-abuse policy and aftermarket liquidity patterns, not a value on any specific name.

On an acquired domain the inherited link profile decides the outcome the extension cannot.

The reason the extension recedes on an acquired domain is that a larger asset enters the calculation. A fresh registration on any extension starts with no links and no history, so the extension is one of the few differentiators it has.

An aged or expired domain arrives with an inherited backlink profile, a topical record, and an index history, and those carry the SEO weight the extension cannot. The condition on that inherited value is relevance and cleanness.

A profile concentrated in relevant, clean sources transfers authority forward regardless of whether the name sits on .com or .net. A profile padded with off-topic or engineered links discounts the name on any extension.

This is why a serious acquisition reads the link profile first and the extension last, and why the extension debate that consumes the new-registration audience barely features in the aged-domain decision.

The conditions under which an aged domain underperforms a fresh one despite a strong inherited metric are set out in Does domain age still matter for SEO in 2026.

The risk surface a careless acquisition exposes itself to is mapped in Risks of buying an expired domain: 7 costly mistakes and how to avoid them.

The established extension carries deeper drop-catch demand and re-registration value than a new gTLD.

The extension does reassert itself on the acquisition, through liquidity instead of ranking. An expiring domain with retained equity on an established extension draws more competitive drop-catch demand.

The pool of buyers who will pay for an aged .com is deeper than the pool for an aged new gTLD with identical metrics, and that demand sets how contested the name is when it drops.

The same depth governs re-registration value. An acquired .com holds a resale market a new gTLD does not, so the established extension prices the liquidity wrapped around the inherited history even though it adds nothing to the ranking.

For a buyer the practical reading is that the extension is a liquidity and trust modifier on top of the history, not a substitute for it, and that an aged domain on an established extension combines the inherited SEO equity with the deeper resale pool.

ICANN-accredited transfer applies to every acquisition regardless of extension, and the WHOIS sunset of 28 January 2025 moved the underlying diligence workflow to RDAP. The way search engines treat a re-registered domain’s inherited standing, independent of its extension, is set out in How search engines treat re-registered expired domains.

When a ccTLD affects SEO through geographic targeting

A country-code TLD affects SEO through geographic targeting, which is the single structured way an extension reaches the ranking systems. It is geography instead of quality.

Google reads a ccTLD such as .uk, .de, or .ca as a strong signal that the site is intended for that country, which helps the site in its home market and constrains it internationally.

The exception inside the exception is the set of vanity ccTLDs, such as .tv, .me, and .co, that Google treats as generic gTLDs because users read them as global, not country-specific.

A ccTLD is an advantage for a single-country business and a deliberate trade-off for one with international ambitions, because the geographic signal that helps at home limits reach abroad. The ccTLD does not rank a country site higher on quality; it tells Google which country the site is for.

Choose a ccTLD when the market is one country, and read it as a geo-targeting tool, not a ranking upgrade.

A ccTLD helps in its home market and constrains international reach by design.

The geographic signal is a feature with a built-in cost, and reading it as pure upside is the misframe. When Google treats .de as a strong indicator that a site serves Germany, the site gains relevance for German users and gives up the implicit global reach a gTLD carries.

The same signal that says “for Germany” also says “not for everyone else.” For a national retailer, a regional service business, or a government-facing site, that trade is worth it, and the ccTLD is the right tool.

For a business with cross-border ambitions, the ccTLD forces a choice between multiple country domains and a single gTLD with hreflang and Search Console targeting, and that architectural decision is larger than the extension itself.

The disciplined read treats the ccTLD as a geographic-targeting instrument with a known constraint, selected when the country focus is real and avoided when the addressable market is international.

Vanity ccTLDs read as generic, which is why .co and .me behave like gTLDs.

The vanity-ccTLD exception is where the rule gets practical for the startup and creator audience. Google treats a set of country codes that the market has adopted globally as generic gTLDs instead of country-targeted, because users and owners read them as global brands, not national sites:

  • .tv, the country code for Tuvalu, read globally as a video and streaming brand.
  • .me, the country code for Montenegro, read globally as a personal-brand extension.
  • .co, the country code for Colombia, read globally as a short company alternative to .com.

The consequence is that a .co or .me carries no geographic constraint and behaves like any other gTLD on the ranking axis, which is why they appear frequently in tech and personal-brand naming without a geo-targeting penalty.

The reading for a buyer is to confirm whether a country-code extension is treated as country-targeted or generic before assuming either behaviour, because the same two-letter pattern can mean “for one country” or “for the world” depending on how the market and the platform have come to read it.

The aged-ccTLD case, where an established country extension carries both geographic signal and inherited local authority, is a distinct acquisition angle that sits alongside the niche-specific reads in Finance niche expired domains.

Which domain-extension SEO myths to retire and the fact behind each

Four domain-extension SEO myths persist despite the data, and each maps to a sourced fact that corrects it. Retiring each one requires replacing an adjective with a sourced fact, and the matrix below traces all four from the false claim to the correction.

Name the myth, cite the fact, and the extension shrinks to the small decision it is.

Myth 1
.com ranks higher than other extensions
Why it persists
.com sites visibly dominate top results, so observers infer the extension causes the ranking, when the dominance reflects .com’s 161.0 million base, its age, and its link depth, not a ranking bonus on the suffix.
Sourced fact
Google treats all gTLDs equally for ranking; .com leads on recall (44%) and trust (3.5/5) per GrowthBadger, which moves clicks and links, not positions. Correlation is not the extension causing the rank.
Myth 2
A keyword extension like .shop boosts matching searches
Why it persists
A keyword in the extension looks like it should reinforce the topic the way a keyword in the path once did, so the intuition survives from the exact-match-domain era that has since faded.
Sourced fact
Google’s 2015 Search Central guidance states keywords in a TLD give no advantage or disadvantage, and region or city extensions are treated as generic. The keyword in the suffix carries no ranking weight.
Myth 3
Every new gTLD is penalised as spammy
Why it persists
Heavy abuse on a few cheap extensions gets generalised to all new gTLDs, so a clean .dev or .app inherits a reputation earned by .top and a handful of low-cost neighbours.
Sourced fact
Abuse is concentrated, not universal: Spamhaus ties 211,406 detections to .top in six months, while many new gTLDs carry no such load. The cost is a reputational tax on specific extensions, not a blanket penalty.
Myth 4
The extension is the decisive SEO choice
Why it persists
The extension is the easiest variable to have an opinion on, so it absorbs attention that the harder, higher-impact choice of which domain and history to build on deserves.
Sourced fact
The ranking is decided by content, links, and, for an acquired domain, inherited equity and topical fit. The extension modulates trust and liquidity around those; it does not substitute for them. The domain choice sits above the extension.

Each myth survives because correlation is read as causation across the extension data.

The pattern uniting the four myths is that each reads a real correlation as a causal ranking effect. .com sites do dominate top results, keyword extensions do exist, specific new gTLDs are abused, and the extension is a visible choice, so the intuition that the extension drives the outcome is understandable and wrong.

The correction in every case is the same move: trace the observed pattern to its actual cause.

  • .com dominates because of its base, its age, and its links, not its suffix.
  • Keyword extensions exist and carry no ranking weight.
  • Abuse is real on specific extensions and is a concentrated reputational cost, not a category penalty.
  • The extension is visible and is the smallest lever in the decision.

Replacing each adjective-driven myth with a sourced fact is the discipline this guide applies, and it is the discipline the incumbent blogs skip when they restate “Google treats all TLDs equally” without the data that makes the statement usable.

The anecdotal “new TLDs look spammy” line is the symptom of that skipped step, an adjective standing in for the Spamhaus distribution that would make it precise. The broader set of acquisition myths that distort buyer decisions, beyond the extension, is collected in Expired domain myths SEOs still believe.

5 frequently asked questions about domain extensions and SEO

The 5 questions site owners raise about domain extensions and SEO concern whether the extension affects rankings directly, which extension is best, whether .io and .ai are good for SEO, whether new gTLDs like .xyz hurt SEO, and whether changing an extension affects SEO.

The answers below are general SEO education about domain extensions, not financial, investment, or legal advice, and not a ranking verdict on any specific domain or extension.

Q1Does a domain extension affect SEO rankings directly?

No, a domain extension does not affect SEO rankings directly. Google’s published position, stated in its 2015 Search Central guidance and unchanged since, is that new gTLDs are treated the same as established gTLDs like .com and .org, and that keywords in a TLD give no ranking advantage or disadvantage.

Two identical sites on .com and .store reach the same direct ranking ceiling, because the ranking systems read content, links, and user signals instead of the string after the final dot.

The one structured exception is the country-code TLD, which Google reads as a geographic-targeting signal instead of a quality signal, so a .de helps a site in Germany without ranking it higher on quality.

The extension does reach SEO indirectly, through user trust, click-through and recall, and spam association, which move the traffic and links that are ranking factors. The direct answer is settled; the indirect mechanics are where the extension earns its small place in the decision.

Q2What is the best domain extension for SEO?

The best domain extension for SEO is the one that adds trust and removes risk for the specific build, and for the typical broad-audience project that is .com, because it carries the deepest recall and the highest measured trust with no abuse tax.

The GrowthBadger study of 1,500 people rated .com the top extension for trust at 3.5 out of 5 and the highest for recall at 44 percent, and found users 3.8 times more likely to guess an uncertain domain is .com.

Because every gTLD shares the same direct ranking ceiling, the choice is a trust and risk decision, not a ranking calculation:

  • Default to .com for broad-audience brands.
  • Accept a sector gTLD such as .io or .ai when the audience reads it as a category signal.
  • Use a ccTLD when the market is a single country.
  • Avoid a high-abuse new gTLD for trust-sensitive builds.

The extension never outranks a stronger domain with better history, so the domain choice sits above the extension choice. This is general SEO education, not a verdict on any specific name.

Q3Are .io and .ai good domain extensions for SEO?

Yes, .io and .ai are sound extensions for the right audience, because they carry a recognised category premium in technology, startup, and AI contexts without an abuse tax, and they share the same direct ranking ceiling as every other gTLD.

Inside their relevant audience these sector extensions read as a deliberate, on-category choice instead of a compromise, which narrows the recall gap against .com that a general-public audience would feel more sharply.

They do not rank a site higher than a .com would, because no gTLD outranks another, and they do not carry the reputational tax that concentrates on low-cost abuse-heavy extensions.

The trade is a lower general-public recall against a stronger in-category signal, so the decision turns on whether the audience already expects the extension.

For a developer tool or an AI product, that expectation makes .io or .ai a strong fit; for a mass-market consumer brand, the broader recall of .com usually wins. This is general SEO education, not a ranking claim about any specific domain.

Q4Do new gTLDs like .xyz hurt SEO?

A new gTLD like .xyz does not transmit a ranking penalty to a clean site, and it can carry a reputational tax when abuse concentrates on the extension.

Spamhaus data show abuse clustering on a handful of low-cost new gTLDs, with .top alone recording 211,406 abuse detections in six months and .xyz registration volume up 103 percent in 2025, the high-volume, low-cost condition under which bulk abuse operates.

The effect is reputational, not algorithmic: email filters, security systems, and human readers calibrate skepticism toward an abuse-heavy extension, so a legitimate new site on it has to overcome a trust deficit a site on an established gTLD does not face.

A clean build on .xyz can succeed, and it pays more trust work to get there. The honest reading is that the extension does not damn the site, and a trust-sensitive project starts from a stronger position on an established gTLD. This is general SEO education, not a verdict on any specific domain.

Q5Does changing your domain extension affect SEO?

Changing a domain extension affects SEO through the migration itself instead of through the new extension’s ranking power, because moving from one domain to another is a site migration that requires 301 redirects, updated internal links, and a Search Console change of address where applicable.

The destination extension carries the same direct ranking ceiling as the origin, so the move neither boosts nor penalises rankings on the suffix alone.

The risk lives in executing the migration cleanly so the inherited authority transfers, and a change from a ccTLD to a gTLD also changes the geographic-targeting signal for an international pivot.

The disciplined approach treats an extension change as a domain migration with all its redirect and authority-transfer mechanics, not as a cosmetic swap. For an acquired domain, the inherited equity transfers through the same redirect mechanics the extension does not alter. This is general SEO education, not advice on any specific migration.

How a screened aged-domain catalogue weighs the extension

Every layer above resolves to one operational point. The extension is the smallest lever, and the domain’s history and equity are the asset. The settled direct-ranking answer, the four indirect channels, the per-type registration and abuse data, the trust-and-risk decision, the aged-domain interaction, and the ccTLD geographic exception all point the same way.

SEO Domains weighs the extension exactly that way at intake. The curated catalogue screens each aged domain in a fixed order:

  • Its inherited backlink profile, read for relevance and cleanness.
  • Its topical history, read against the buyer’s intended use.
  • Its abuse and trademark exposure, surfaced before acquisition.
  • The extension last, read as a trust-and-liquidity modifier on top of that screen.

Domain Authority, Domain Rating, Trust Flow, and Citation Flow are reported alongside the inheritance read, so a buyer sources a name selected on the history that decides the SEO and the extension that prices the trust around it. The catalogue puts the extension in its place, below the inherited equity that carries the ranking.

Extension trap in an unscreened poolHow a raw listing leaves itWhat the SEO Domains catalogue screens for instead
Extension treated as the headline valueA name is priced up for its .com or hyped extension with no read of its historyThe screen reads the inherited link profile and topical history first, and the extension last as a trust-and-liquidity modifier
Spam-flagged extension passed off as cleanAn abuse-heavy new gTLD listing omits the reputational tax the buyer inheritsThe screen reads abuse and reputation exposure so a high-risk extension is visible before acquisition, not after
ccTLD mismatch to the buyer’s marketA country-code name is sold without flagging the geographic constraint it carriesThe screen surfaces the geographic-targeting signal so a ccTLD is matched to a real single-country use, not assumed global
Thin new-gTLD name with no real equityA metric-rich shell on a fashionable extension reads as value despite hollow linksThe screen reads link relevance and cleanness so inherited equity is genuine, not padded with off-topic or engineered links
History ignored in favour of the suffixThe inherited topic and standing go unread while the extension drives the priceThe screen prices the inherited equity that decides the SEO and treats the extension as the modifier it is
Figure 4. Each extension-hype trap in an unscreened pool against what the SEO Domains catalogue screens for instead. The catalogue reads inherited link equity, topical history, abuse exposure, and geographic fit before it reads the extension, and treats the extension as a trust-and-liquidity modifier on top of the history. The screen selects for a clean inherited profile; it promises no ranking or sale outcome on any name.

The catalogue reads inherited equity before the extension, which is the order the data demands.

The discipline SEO Domains applies is to invert the order the incumbent advice encodes. A raw listing prices a name on its extension and leaves the history unread.

The catalogue reverses that. It reads the inherited backlink profile for relevance and cleanness, reads the topical history against the buyer’s intended use, reads the abuse and trademark exposure, and only then reads the extension as the trust-and-liquidity modifier it is.

The 7-vector inheritance screen surfaces whether the inherited equity is genuine or a metric-rich shell, and Domain Authority, Domain Rating, Trust Flow, and Citation Flow are reported alongside it so a buyer reads the third-party metrics and the inheritance read together.

An aged domain on an established extension combines the inherited SEO equity that carries the ranking with the deeper resale pool the extension prices, and the screen makes both legible. ICANN-accredited transfer applies to every acquisition regardless of extension, and the underlying diligence runs on RDAP after the WHOIS sunset of 28 January 2025.

A buyer who understands that the extension is the smallest lever is the buyer best served by inventory screened on the history that is the largest one.

A screened catalogue raises a buyer’s confidence in the history, and it guarantees no ranking outcome.

The honest takeaway is two-sided. Extension hype, a spam-flagged TLD sold as clean, a ccTLD mismatched to the market, a thin new-gTLD shell, and a history ignored in favour of the suffix are real ways a domain decision goes wrong.

They concentrate in unscreened pools where a name reaches a buyer priced on its extension with its history unread.

A screened catalogue does not abolish the build work an aged-domain project carries.

It does not write the content, earn the new links, or run the conversion path the inherited equity rewards, it does not provide financial, investment, or legal advice, and it promises no ranking or sale outcome on any name or any extension.

What it does is read the inherited equity, the topical history, and the abuse exposure that decide the outcome, and place the extension where the data places it, as a trust-and-liquidity modifier on top of the asset.

A site owner who finishes this guide is equipped to stop overweighting the suffix and start reading the domain, because the ranking was never in the extension, and the asset was always the history the right domain carries.

The SEO Domains catalogue screens for that history, so the inventory a buyer reviews is selected on the lever that matters.

Hristo Bogdanov, Head of SEO at SEO Domains

Hristo Bogdanov

Head of SEO @ SEO Domains · CEO & Co-founder of SEO.bo

Hristo has spent 15+ years building aged-domain acquisition and SEO workflows for SEO professionals, domain investors, and brand acquirers.

He leads SEO at the SEO Domains marketplace, which screens its curated aged-domain catalogue on inherited link equity, topical history, and abuse exposure before the extension, and reports Domain Authority, Domain Rating, Trust Flow, and Citation Flow alongside a 7-vector inheritance screen.

Everything he publishes here is general SEO and market education about domain extensions and the aged-domain market, not financial, investment, or legal advice.

· Last reviewed