“SEO domain” is an informal description of a name being considered partly because of its previous web presence, links or search-related evidence. It is not an official Google classification, and it does not establish that a buyer will inherit traffic or rankings.
You can discover scheduled names in UK drop search and make a deliberate UK WHOIS lookup for public registration details. Those tools do not supply an SEO score, valuation or evidence that rankings will pass to a new registrant. The useful task is to inspect the evidence behind the claim: what was measured, by whom, when, and whether it remains relevant to the proposed use. This guide explains that task without recommending a score threshold or treating a domain as a guaranteed search shortcut.
Separate backlinks from referring domains
A backlink is a link to a target from another page. A referring-domain count groups the source domains from which links are observed. Many links can therefore come from one domain. Ahrefs explains the distinction in its backlinks and referring-domains documentation.
Neither count tells you, by itself, why the links exist or whether the pages remain accessible. Inspect a meaningful sample of source pages, including the largest concentrations. Note the surrounding text, the actual destination and whether a link appears editorially useful, sitewide, outdated or unrelated to the name's former purpose.
Check direct links, redirects and scope
Ask whether the report covers the exact hostname, every subdomain, a single URL or a broader set. Check whether links point directly to the name or reach it through another domain's redirect. If a redirecting name is outside the proposed acquisition, its future behaviour is not something the buyer controls.
Read the provider's inclusion rules. “Live”, “historical”, “lost” and “all” reports can describe different evidence sets. Do not add totals from different tools or report modes and present the sum as one independent link count. Retain the original export or permitted evidence reference and its measurement settings.
Annotated fictional metrics example
Teaching example only. These numbers belong to no real domain, provider report or DomainSabre listing. The rows deliberately show overlapping subsets and must not all be added together.
| Fictional observation | Count or state | What the buyer should investigate |
|---|---|---|
| Total links in one report | 18,000 links from 120 referring domains | The headline total does not show the distribution or route |
| Links counted through redirecting domains | 16,500 links from four source domains | Most of the total depends on an indirect route; inspect it and establish which assets are included |
| Direct links to the subject | 1,500 links from 116 source domains | This is the remaining subset under the fictional report's rules, not a separate total to add |
| Repeated footer links within the direct subset | 1,200 links from two source domains | A few sources account for most direct link instances |
| Editorial pages manually inspected within the direct subset | 18 pages across 17 source domains | A useful sample of context, not a verification of every unexamined link |
| Vendor authority-style score | 53 on that fictional provider's scale | A vendor assessment whose definition must be checked; it is not a Google metric |
| Current organic traffic | Unknown; no first-party access supplied | Unknown is not zero, and the link counts do not fill the gap |
The investigation may still find useful relevant material. The point is that the largest number alone could lead to a very different decision from the underlying evidence. Record confirmed observations separately from the questions still open.
Treat vendor scores as vendor scores
Metrics such as Domain Rating belong to the tool that defines them. Ahrefs' own explanation of Domain Rating and search engines says there is no evidence that search engines use that score as a ranking factor.
A score can help organise investigation within a consistent dataset. It does not establish the price of a name, the authenticity of a seller's traffic claim, the absence of spam or Google's assessment of a future website. Compare like-for-like observations and keep the provider name visible alongside a number.
Inspect previous content and relevance
Use archived pages and visible link context to understand what readers originally expected. A link to a former technical manual, a school resource or a local event may have a specific purpose. Ask whether the proposed new site could serve a useful audience without pretending to be the old operator.
Follow the history-check guide for a dated timeline. A long span of captures does not prove continuous registration, and an old link does not prove it still receives visits. Record substantial topic changes, periods with little evidence and source pages whose content cannot be verified.
Keep unknown traffic separate from zero traffic
An estimated-traffic figure is not the same as an export from an authenticated analytics or search account. Ask what the dataset covers and whether the observer had access to the actual site. A blank field may mean the tool did not measure the site, the query failed or no relevant data was returned.
If first-party evidence is available, inspect the dates, source of visits and any dependence on material outside the sale. A historical traffic peak does not establish continuing demand. Avoid predicting future visits by multiplying a backlink count or vendor score by an assumed conversion rate.
Redevelopment, rights and search policies
Useful redevelopment requires a coherent purpose and content that helps its readers. Google's spam policies identify expired-domain abuse where an expired name is repurposed primarily to manipulate rankings with little or no user value. They also address manipulative link practices and scaled low-value content. These policies should not be read as saying that every ordinary domain resale is abusive.
Buying a name does not guarantee that old signals or rankings continue. Nor is an archive capture permission to republish another operator's text, photographs or code. Establish the rights needed for any reused material; GOV.UK's copyright overview explains the protection that can apply to those works.
Evidence checklist before relying on a claim
- Record the provider, report scope, filters and observation date.
- Separate links from referring domains and direct routes from redirects.
- Inspect concentrations and representative source pages, not only a total.
- Compare historical use with the intended new purpose.
- Distinguish verified traffic, estimates, missing data and failed queries.
- Identify assets and permissions that the transaction actually includes.
- Write down remaining uncertainties and the decision they affect.
Apply the result alongside the valuation guide and auction guide. If a name is expected to drop, use the backorder guide to assess an external request and the drop-catching explanation to understand the uncertainty. Explore the guide directory for the rest of the research process. These are evidence checks, not a DomainSabre score, product category or ranking promise.