There is no checkbox in Drupal that raises a Domain Authority score, because that number is produced by a software vendor watching links between domains — not by your content management system, and not by Google. What a CMS genuinely decides is narrower and far more useful: whether the links other people have already given you keep working when your site changes.
This page used to list score bands and a factor count. Those came from no source that can be checked, so they have been removed rather than repeated. What remains is the part that is verifiable: what the metric is, and which Drupal behaviours sit underneath the thing it estimates.
What an authority score actually is
Moz publishes Domain Authority; other vendors publish their own equivalents under their own names. Each is a vendor's model of how likely a domain is to rank, fitted mostly to the pattern of links pointing at it. Three consequences follow, and they are the ones that matter to a site owner:
- It is an estimate, not a measurement. Nobody outside the vendor can reproduce it, and two vendors will give the same domain different numbers on the same day.
- No search engine consumes it. It is calculated from a third party's own crawl of the web, and it is an output of that crawl, not an input to anybody's ranking.
- It is comparative and relative. The number on its own says nothing; the direction over a year, against sites in the same field, says a little.
The internals of any particular vendor's model are not something I can verify from source, so nothing here describes how one is calculated. Treating a score as a diagnostic tool is the mistake — it is a summary of a cause, and the cause is other people linking to you.
The part that is a CMS problem: link continuity
If the metric is driven by inbound links, then the one contribution a CMS makes is keeping those links alive. A link earned in 2019 is worth nothing if the URL it points to now answers 404, and Drupal has a specific, well-documented way of quietly breaking exactly that.
Renaming content deletes its old address by default
Pathauto regenerates a URL alias from a token pattern when content is saved. Its shipped configuration (pathauto.settings.yml) sets update_action: 2, and in the module's own interface that constant is UPDATE_ACTION_DELETE — defined at src/PathautoGeneratorInterface.php line 28, alongside UPDATE_ACTION_LEAVE (1) and UPDATE_ACTION_NO_NEW (0).
In plain terms: edit a headline, save, and the previous address stops existing. Nobody is warned. The page is fine, the new URL is fine, and every inbound link, bookmark and citation aimed at the old one is now pointing at nothing.
Redirect is what makes the rename survivable
The Redirect module exists for this, and Pathauto says so itself: its .info.yml carries a recommends: redirect:redirect line. With Redirect installed, redirect_path_alias_update() (redirect.module, line 87) fires whenever an alias entity changes, compares the old alias to the new one, and creates a redirect from the old address to the new path. The shipped redirect.settings.yml has auto_redirect: true and default_status_code: 301, which is the permanent status that tells a crawler to move its record over.
That machinery is running on this site, and it can be seen from outside without any admin access. Requesting /node/45 today returns 301 with a Location header pointing at the article's alias and a response header reading X-Drupal-Route-Normalizer: 1 — a header set in the module's own request subscriber (src/EventSubscriber/RouteNormalizerRequestSubscriber.php line 142). One request, and you know the module is installed and enabled.
What a score is guessing at, and where to check the real thing
| What the tool infers | The fact underneath it | Where you check that in Drupal |
|---|---|---|
| Links pointing at your domain | Whether those URLs still answer 200 | The redirect list, and the site's 404 log |
| Site trustworthiness | Whether one page has one address | The canonical tag in the served page source |
| Crawlability | Whether pages are reachable and listed | robots.txt and the generated sitemap |
| Content depth | Whether pages answer a real question | Nothing automatic can tell you. Read them. |
The left column is somebody else's guess. The middle column is either true or false about your site right now, and the right column is where the answer lives. Sorting out which of those are broken is a two-hour job on most sites and a sensible thing to buy as a short Drupal consulting engagement rather than a retainer.
What to watch instead
- Google Search Console, because it is first-party. Impressions and average position for queries you care about are measurements of your actual pages, not a model of your domain.
- Your 404 log, weekly. Repeated 404s on old URLs are the exact damage an authority score would take a year to reflect, visible immediately and fixable in minutes.
- The redirect table after any restructure. If you moved a section and it is empty, the redirects were not created and the links are gone.
- Whether anyone new linked to you at all. That is the underlying event. No configuration produces it; work that is worth citing does.
Common questions
- Does a low authority score mean my site is penalised?
- No. It usually means few sites link to yours, which is a marketing fact rather than a technical fault. Nothing in Drupal is misconfigured because of it.
- Will moving to Drupal change my score?
- Only through the URLs. A migration that preserves every address with 301s changes nothing; one that renames everything without redirects does real, lasting damage, and the score will eventually show it.
- Should I buy links to raise it?
- No. Paid link schemes are what search engines' spam policies are written about, and the score they target is not consumed by any search engine anyway.
- I have to change a URL. How do I do it safely?
- Make sure Redirect is installed before the edit, not after. The redirect is created from the alias that existed at save time, so installing afterwards cannot recover an address that has already been deleted.
- How long should I wait to see a change?
- Long enough that watching the number weekly is wasted attention. Check quarterly, spend the rest of the time on pages worth linking to.
Where this fits with the rest
Two neighbouring pages deliberately answer different questions: which Drupal modules emit which search-visible tags, and what free SEO tools can and cannot see through a Drupal front end. If URL structure is the live question, the decisions worth getting right before a rebuild are set out on the Drupal architect page.
Written by Alaa Haddad — web development since 2005, author of Drupal modules and themes, with the code public on the drupal.org profile. If you are about to restructure a site and want the redirect plan checked before the URLs change rather than after, that is the cheapest hour in the whole project.