Domain Authority

Domain Authority – or DA – is Moz's best guess at how likely a site is to rank in Google compared to every other site they've crawled. It runs on a 1 to 100 scale, and the number is driven almost entirely by [backlinks](/backlinks/): how many quality, independently owned sites link to you, and how authoritative those linking domains are themselves.

Here's what I've learned after six years of using it: DA is a comparative benchmark, not a ranking factor. Google has never confirmed using it, and their own documentation makes no mention of anything similar. DA is a correlation signal. Sites with strong link profiles tend to rank well, but the relationship isn't causal. I've seen a DA 75 site outrank a DA 90 site for the same query because the lower-DA site had better content and fresher [anchor text](/anchor-text/).

If you treat DA as a rough sketch of a domain's link profile strength, it's useful. If you treat it as a Google score, you'll waste months. In my outreach workflow, I use DA to sort a list of competitor backlinks quickly, but I never disqualify a site based on DA alone. A DA 30 blog in your niche can send more relevant traffic than a DA 70 general directory. The number tells you about link quantity and link authority in aggregate – it doesn't tell you whether the audience matches your own.

The best way to think about DA is as a starting filter. When I'm prospecting for guest posts or [editorial links](/editorial-links/), I'll pull a list of potential domains, sort by DA descending, and then manually audit the top 50 for relevance, traffic, and content quality. That saves hours. But the moment I rely on DA to make the final decision, I make mistakes.

One more thing: DA is relative – a DA of 40 in a competitive niche like finance is harder to achieve than a DA of 60 in a niche like local gardening. Compare within your vertical, not across the whole web.

DA matters most in two situations: link prospecting at scale and competitive monitoring over time.

When I'm running a [backlink audit](/backlink-audit/) for a client, I'll export their competitor's backlinks, run them through Moz's Link Explorer, and sort by DA. That gives me a quick heatmap of where the best link opportunities live. Without DA, I'd have to manually evaluate each domain's trustworthiness, which would take ten times as long. The speed gain is real. But I never trust the score blindly – I follow up with a traffic check and a content relevance scan. A DA 50 site that publishes regularly on your topic is worth more than a DA 70 site that hasn't updated its blog in two years.

Second, tracking your own DA month over month gives you a relative measure of link-building velocity. If your DA goes from 32 to 37 over six months while your competitors stay flat, you're probably earning better links. But the opposite isn't a panic signal: a flat DA can still coincide with rising organic traffic if your content is getting stronger. I've seen sites double their traffic while DA stayed the same because they focused on topical depth and internal linking rather than link volume.

Where DA falls short is in predicting rank changes. I used to think a DA jump of 5 points would push a page from page 2 to page 1. Rarely happens. Google's ranking algorithm cares about hundreds of signals, and DA captures only the link-based ones. If you want to move a specific page, you need to improve page-level factors: content, user intent match, page speed, and topic authority. DA is a domain-level metric. It doesn't tell you whether a particular URL is well optimised.

For day-to-day work, I also use DA when deciding whether to accept a [guest posting](/guest-posting/) opportunity. If the site's DA is under 20 and I'm not confident about its editorial standards, I pass. But if it's under 20 and it's the only site covering my niche, I'll still write for it. The link might not boost my DA, but it can bring targeted readers. That's often more valuable than a high-DA link from a spammy directory.

I made two big mistakes with DA. The first was treating it like a Google ranking factor. Early in my career, I told a client, 'We need to get your DA to 50 to rank for these three keywords.' That was flat wrong. Google doesn't use DA. I was confusing correlation with causation. The client spent money on link packages from directories and blog networks, and the DA went up by 8 points, but their organic traffic didn't budge. They lost faith in SEO, and I lost a retainer. Now I never set DA targets – I set traffic and conversion targets instead.

The second mistake was comparing DA across different tools. I'd see Moz give a site a 45 and Ahrefs give it a 55, then I'd try to figure out which tool was 'right'. They're both right – they just use different calculations. Moz's DA is based on their own link index and a machine learning model trained on their own ranking data. Ahrefs' Domain Rating is a different beast. Cross-tool comparison is meaningless. Pick one tool, stick with it, and only compare scores within that tool over time.

I also undervalued [social signals seo](/social-signals-seo/) and on-page quality when evaluating a site. I once rejected a DA 30 site for a link because its score was lower than another site at DA 55. Turned out the DA 30 site had a loyal audience that clicked through to my page and drove conversions, while the DA 55 site's link sat in a footer with zero traffic. DA told me about the link profile, but it said nothing about engagement. That decision cost me a month of real referral traffic.

Now I keep DA in its lane: a quick comparative gauge for link prospecting, nothing more. If I ever catch myself saying 'we need a DA of X', I stop and rewrite the sentence as 'we need more quality links from relevant, authoritative sites'. I keep Caspian Wilder on increasing domain authority open when I am checking how other independent desks frame the same problem.