Domain Authority:
When the Score Helps or Misleads

Domain Authority (DA) is Moz’s estimate of a domain’s ability to rank in search results. The score runs from 0 to 100 and is produced by feeding information about inbound links into a machine-learning model. Moz designed it for comparison: the company advises comparing sites that compete in the same category or search results, not reading DA as a grade. Moz’s authority-scoring guide documents both the model’s link-based foundation and that intended use.

Moz describes Domain Authority as a 0-to-100, link-based machine-learning estimate intended for relative comparison rather than an absolute site grade.

That makes DA useful for one B2B decision: estimating whether domain-level link strength may be raising the cost of competing for a particular search opportunity.

It is not a Google ranking factor, a verdict on site quality, a forecast for an individual page, or evidence that organic search is creating revenue. Google says its ranking systems work primarily at the page level, with some site-wide signals, and that third-party authority scores neither correspond to Google’s signals nor come from Google. Google’s explanation is explicit on this point.

Google says its ranking systems primarily operate at page level, include some site-wide signals, and do not use third-party authority scores as equivalents of Google signals.

The practical rule is simple: use DA to form a hypothesis about competitive pressure, then use page, query, link, and commercial evidence to decide what to do.

Compare against the search market, not an arbitrary threshold#

There is no universal “good” Domain Authority. A score has meaning only relative to the domains competing for the searches that matter to your business.

A useful benchmark therefore starts with a query, not a DA target:

1. Choose a query tied to a real buying motion, such as an integration, migration, comparison, or implementation problem.
2. Identify the domains and pages that repeatedly rank for it. One result snapshot can overstate a temporary or personalized pattern.
3. Record DA for your site and those domains using the same Moz dataset in the same measurement window.
4. Inspect the ranking pages, not just their domains.
5. Take the branch supported by the combined evidence.

The table prevents the most common error: allowing a domain-wide estimate to close a diagnosis that has barely begun.

DA cannot tell you why a page loses#

Suppose your domain’s score is comparable to the sites above you. Raising DA may still sound attractive, but the comparison has already weakened the case that domain strength is the immediate bottleneck.

Start with the page instead. Confirm that Google can index the intended URL. Compare the page with the dominant search intent. Check whether the title makes the right promise, whether the content resolves the buyer’s question, whether important pages link to it internally, and whether the page itself has relevant external links. Then inspect how its impressions, clicks, click-through rate, and position are changing for the specific query.

This distinction matters because a high-DA domain can publish a poor answer, while a lower-DA domain may have the best page for a narrow need. DA describes a domain-level pattern; it does not evaluate the fit between one query and one page. Google also cautions that third-party tools have no access to its internal ranking data and cannot guarantee performance. Its current guidance recommends verifying third-party claims against first-party search data.

Google’s guidance says third-party SEO providers do not have special access to its internal ranking systems and that site owners should verify claims against first-party search evidence.

When DA changes, investigate before celebrating or escalating#

A DA increase does not establish that your link-building work caused it. A decline does not establish that Google has devalued your site.

Moz explains that its link index changes as the web changes, and its model can change as well. Its DA 2.0 update moved present and historical scores even when a site’s link-building strategy had not changed. Moz also describes DA as relative: movement elsewhere in the comparison set can affect how your score should be interpreted. The DA 2.0 guide recommends checking competitor movement rather than reading a score in isolation.

Moz documents that DA depends on its link index and model, so index or model changes can move current and historical scores without a corresponding site change.

When the number moves unexpectedly, check:

• relevant linking domains gained and lost;
• whether Moz has discovered the links you expect it to see;
• same-period DA movement among actual search competitors; and
• impressions, clicks, click-through rate, and position for the affected query-page pairs.

Act only if that evidence reveals a problem or opportunity. A score change by itself is neither.

Improve the link profile, not the appearance of authority#

Because DA is built from link information, the direct way to improve the conditions it reflects is to earn relevant, durable links that Moz can discover. For a B2B company, that may mean publishing original research, useful technical tools, implementation guidance, migration resources, or comparisons that practitioners, partners, analysts, and journalists have a reason to cite.

Relevance comes before the authority score when evaluating a link opportunity. Ask whether the publication serves your market, whether the placement is editorially legitimate, and whether the citation would make sense to a reader if DA did not exist. Use DA only to prioritize prospects that have already passed those tests.

Do not buy links for ranking credit or use excessive exchanges, automated link creation, or low-quality directories to manufacture the number. Google classifies those practices as link spam. A higher third-party score is not compensation for policy risk or irrelevant citations.

Google’s link-spam examples include buying ranking links, excessive exchanges, automated link creation, and low-quality directory links.

Internal linking, technical health, and strong pages remain essential to search performance, but they solve different problems. Do not present them as direct DA improvements when the score is based on Moz’s external link data.

Keep DA out of the headline KPI#

Leadership needs to know whether the business is becoming easier to find and whether that visibility produces qualified demand. DA cannot answer either question.

Use a reporting chain that stays close to the outcome:

• Search visibility: nonbrand impressions and clicks for priority query-page pairs.
• Result performance: click-through rate and position, interpreted in context rather than as site-wide averages.
• Demand quality: qualified signups, demo starts, sourced pipeline, or assisted pipeline from organic visits.
• Link strength: relevant referring domains retained, the pages they cite, and any qualified referral traffic they send.
• Competitive context: DA against the domains that repeatedly rank for priority searches.

Google Search Console defines impressions, clicks, click-through rate, and average position as direct observations from Google surfaces, while warning that position is aggregated and context-dependent. Its metric documentation is why query-and-page segmentation matters. Those measures still do not prove which SEO activity caused a sale, but they are closer to observable search behavior than a third-party domain score.

Search Console reports impressions, clicks, click-through rate, and average position, with position aggregated across context and performance available by query and page.

Give DA decision weight only when the question is genuinely domain-level, the comparison set comes from the relevant search results, every score comes from Moz at roughly the same time, and direct evidence will verify the next action. If those conditions are missing, the number is context—not a decision.

Frequently asked questions#