← Blog

Moz Domain Unification: How to Align www and Non-www Campaign Tracking

2026-11-16 · IndexNowFast Team
Moz Domain Unification: How to Align www and Non-www Campaign Tracking

Quick Answer

Moz domain unification is best understood as configuring Moz Pro to track the correct versions of your website consistently. Moz supports different campaign tracking scopes, including domain and subdomain configurations. However, its documented settings do not allow you to change a campaign's tracked URL or scope after creation. You may need to create a new campaign with the correct configuration.

Key Takeaways

  • Moz Pro lets you configure campaigns for a root domain or specific website sections.
  • The www hostname is a subdomain of your root domain.
  • Moz's documented campaign settings do not allow you to edit the tracked URL or scope after creation.
  • A redirect outside a restricted campaign's scope can interrupt crawling.
  • Website redirects and canonical tags solve a different problem from Moz campaign configuration.
  • Google makes its own decisions about canonical URLs and indexing.

What Does Moz Domain Unification Actually Mean?

When people search for Moz domain unification, they usually want to understand how to track different versions of their website without splitting their SEO monitoring across inconsistent configurations.

For example, imagine your business website uses these addresses:

  • example.com
  • www.example.com
  • blog.example.com

All three use the same registered domain, but they represent different hostnames or subdomains.

A hostname is the part of a web address that identifies a particular server or website location. The root domain is the main registered domain, while a subdomain adds another label before it.

The www version is technically a subdomain. The same applies to blog.example.com.

This distinction matters when configuring an SEO campaign. A campaign that tracks a particular subdomain may not have the same crawling scope as one configured to track the broader domain.

An important distinction: Moz's documentation describes campaign setup and tracking-scope options. It does not establish an automatic feature that merges multiple existing campaigns or combines their historical reports into one.

Therefore, the practical goal is to align your campaign configuration with the hostname structure you actually want to monitor.

How Moz Handles www, Non-www, and Subdomains

Moz Pro provides campaign setup options that let you define which part of a website you want to track.

According to Moz's official Track a Site documentation, you can enter a website domain without including the HTTP or HTTPS protocol. Its example uses the non-www version of a domain.

The setup also provides advanced options for tracking subdomains and subfolders.

Understanding these choices helps prevent an incorrect campaign configuration.

Root-domain tracking

Suppose your website uses example.com as its preferred public domain.

You want to monitor the broader website rather than restrict your campaign to one particular section.

In that situation, review the domain-wide tracking option during campaign creation and check the available subdomain settings.

Do not assume that every campaign automatically includes every hostname. The selected tracking scope matters.

Subdomain tracking

Now imagine that your company operates a separate blog at blog.example.com.

You might want a campaign specifically for that blog because its content, technical performance, and SEO priorities differ from the main website.

A restricted subdomain campaign can be useful for this purpose.

However, it also introduces a limitation: if the campaign is restricted to one hostname or section, a redirect to another hostname may take the destination outside its configured scope.

Why www and non-www settings matter

Consider a website that receives requests through both:

  • example.com
  • www.example.com

If your website redirects one version to the other, your SEO crawler needs to be able to follow the resulting destination within its configured scope.

Otherwise, the campaign may not crawl the website as expected.

The solution is not necessarily to change your website's hostname. First, understand the difference between the campaign's tracking scope and the website's actual URL configuration.

Can You Merge or Change an Existing Moz Campaign?

This is one of the most important questions to resolve before changing your configuration.

Moz's Campaign Settings documentation states that the tracked URL and campaign scope cannot be edited after a campaign has been created.

If you need to track a different URL or website section, the documented solution is to create a new campaign.

This means you should not expect to correct an incorrectly configured campaign simply by editing its original domain setting.

What to do when your campaign tracks the wrong domain

Follow this practical sequence:

1. Identify the existing campaign URL.

Check which hostname or website section the campaign currently tracks.

For example, determine whether it uses blog.example.com, example.com, or another version of your website.

2. Decide what you actually need to monitor.

Determine whether your requirement is domain-wide monitoring or tracking a particular subdomain or subfolder.

3. Check your website's redirect behavior.

Open representative URLs and identify their final destinations. A campaign's configured scope should make sense for the URLs it needs to crawl.

4. Create a new campaign if the original scope is incorrect.

Use the appropriate tracked URL and scope during the new campaign setup.

5. Review your reporting workflow.

Compare the information available in the old and new campaigns before changing your reporting process.

Do not assume that historical reports, campaign data, or measurements will automatically transfer or merge. The cited Moz documentation does not establish that capability.

This approach avoids relying on an unsupported campaign-merging process.

Why Redirects Can Stop Moz From Crawling Your Website

A redirect sends a visitor or crawler from one URL to another.

For example:

https://example.com/page/

might redirect to:

https://www.example.com/page/

This is often a normal website configuration. However, it can create a crawling problem when the destination falls outside the campaign's permitted scope.

Moz explains this situation in its official crawl troubleshooting documentation.

Its example involves a campaign restricted to a subdomain that redirects to www. Because the destination falls outside the restricted campaign scope, crawling cannot continue as expected.

How to diagnose the problem

Check the following items before changing your configuration:

  1. Original URL: Which hostname does the campaign attempt to crawl?
  2. Redirect destination: Where does the original URL send the crawler?
  3. Campaign scope: Is the campaign restricted to a particular subdomain or subfolder?
  4. Destination compatibility: Does the final hostname fit the campaign's configured scope?
  5. Other crawl problems: Are there additional HTTP errors, blocked resources, or redirect loops?

A redirect outside the campaign scope is different from a server error or a robots.txt restriction. Identifying the actual problem helps prevent unnecessary configuration changes.

Which campaign configuration should you use?

Moz's troubleshooting guidance describes two relevant approaches:

  • Create a campaign restricted to the destination subdomain when you only need to monitor that section.
  • Create an unrestricted campaign that tracks the relevant sites within the domain when you need broader coverage.

Choose according to the website structure and monitoring objective, rather than assuming that one configuration is suitable for every project.

Moz Campaign Configuration vs Actual Website Domain Consolidation

There is an important difference between unifying your Moz tracking and consolidating your website's URLs.

Changing a campaign configuration affects SEO monitoring. It does not automatically change the website's redirects, canonical tags, or search-engine indexing decisions.

These are separate processes.

ComponentWhat it controlsWhat it cannot do
Moz Pro campaignTracking configuration and crawler scopeChange your website's URL structure
Permanent redirectSends visitors and crawlers to another URLChange Moz campaign settings
Canonical tagCommunicates a preferred URLGuarantee Google's canonical selection
XML sitemapHelps search engines discover preferred URLsOverride conflicting or stronger canonical signals
Google Search ConsoleReports search performance and indexing information for properties you manageMerge Moz campaigns

Google explains these distinctions in its documentation about consolidating duplicate URLs.

Use redirects to establish a preferred hostname

Suppose your business decides that https://www.example.com should be its main public website address.

You can configure permanent redirects from the non-www version to the preferred www version.

For example:

https://example.com/services/

redirects to:

https://www.example.com/services/

The redirect communicates where visitors and crawlers should go.

Make sure the destination works correctly and that the redirect does not create a loop or an unnecessary chain of multiple redirects.

Use canonical tags consistently

A canonical tag is an HTML signal that identifies the preferred version of a page when similar or duplicate URLs exist.

For example, the following HTML indicates that the www version is preferred:

``html <link rel="canonical" href="https://www.example.com/services/"> ``

The canonical URL should match the version you intend search engines to recognize as preferred.

Google treats permanent redirects and canonical annotations as strong canonicalization signals. Sitemap inclusion is a weaker signal.

Google also recommends consistent internal links pointing to the canonical URL.

These signals should support the same preferred URL rather than contradict one another.

Do you need Google's Change of Address tool?

Not for an ordinary www-to-non-www or non-www-to-www change.

Google explicitly explains that its Change of Address tool is not intended for switching between www and non-www versions of the same domain.

Redirects and canonical signals are the appropriate mechanisms for communicating the preferred version.

A genuine move to a different domain or subdomain is a separate migration scenario. For that situation, follow Google's site move guidance, including URL mapping, redirects, and monitoring.

A Practical Moz Domain Unification Decision Matrix

The easiest way to choose the correct solution is to identify which system is causing the problem.

Your situationRecommended actionWhat to verify
You need consistent tracking across www and non-wwwReview root-domain campaign configuration and available subdomain settingsActual campaign tracking scope
Your campaign tracks only a restricted subdomainCheck whether the redirect destination falls outside its scopeFinal redirect destination
You selected the wrong tracked URLCreate a new campaign with the correct configurationNew campaign URL and scope
Your website serves multiple versions of the same pageConfigure appropriate permanent redirects and consistent canonical signalsPreferred destination and canonical URL
You have changed the website hostnameMonitor representative URLs in Google Search ConsoleCrawlability, canonical selection, and indexing observations

A simple example

Imagine an agency manages a website with the following configuration:

  • Main website: example.com
  • Preferred public version: www.example.com
  • Blog: blog.example.com

The agency has a Moz campaign restricted to blog.example.com.

Later, the website changes its redirect configuration, and some URLs now redirect to www.example.com.

The agency notices that Moz is no longer crawling those destination pages as expected.

Here is how to approach the problem:

First: Check the actual redirect destinations and compare them with the campaign's restricted scope.

Second: Decide whether the agency still needs a blog-only campaign or wants broader domain monitoring.

Third: If the existing campaign's tracked URL or scope is unsuitable, create a new campaign with the required configuration.

Fourth: Separately check whether the website uses consistent redirects and canonical URLs.

Finally: Monitor representative destination URLs through Google Search Console and compare observed indexing information over time.

This separates the Moz tracking issue from the website's technical URL configuration.

How to Verify Your Domain Changes After Configuration

Correcting the campaign configuration is only one part of the process. You should also verify that the website behaves as intended.

Use this checklist:

  • Open the preferred www or non-www homepage.
  • Test representative internal URLs.
  • Check that redirects reach the intended final destinations.
  • Look for redirect loops and unnecessary chains.
  • Inspect canonical tags on important pages.
  • Confirm that internal links use the preferred hostname consistently.
  • Check that important pages are accessible to search-engine crawlers.
  • Review sitemap URLs for consistency.
  • Monitor indexing information in Google Search Console.

For a larger group of public URLs, the IndexNowFast Google Index Checker provides a way to check URLs in bulk and export observed results to CSV.

Its results are point-in-time observations. A URL's indexing status can change, and a non-indexed result is not by itself a complete technical diagnosis.

For websites you manage, Google Search Console's URL Inspection tool provides Google's indexed information and a separate Live Test of the current page.

The important thing is to verify actual website behavior instead of treating a successful Moz campaign setup as proof that Google has consolidated every URL.

Frequently Asked Questions

What does domain unification mean in Moz?

It generally refers to configuring Moz Pro to monitor the correct versions of a domain consistently. Moz documents campaign tracking and scope settings, but the phrase should not be treated as the name of a verified automatic domain-merging feature.

Does Moz automatically combine www and non-www domains?

Do not assume that it does. Moz provides campaign configuration options for domain and subdomain tracking. You should review the selected scope and confirm that it covers the hostnames you intend to monitor.

Can I merge two Moz Pro campaigns?

The available official documentation does not establish a feature for automatically merging two campaigns or combining their historical reports. Do not promise that existing campaign data will transfer. If the tracked URL or scope needs to change, Moz documents creating a new campaign as the appropriate approach.

Can I change the domain of an existing Moz campaign?

Moz's Campaign Settings documentation states that the tracked URL and campaign scope cannot be edited after creation. Create a new campaign with the correct URL and scope instead.

Why does Moz stop crawling after a redirect?

One possible reason is that the redirect sends the crawler to a hostname outside the campaign's restricted scope. Check the final destination and compare it with the campaign configuration. Other technical crawl errors may also need investigation.

Should I use a 301 redirect or a canonical tag?

They serve different purposes. A permanent redirect sends visitors and crawlers to another URL. A canonical tag communicates which URL should be treated as the preferred version when duplicate or similar pages exist. Use the appropriate method for your website situation and keep your signals consistent.

Does Moz domain unification improve Google rankings?

Correct campaign configuration improves the accuracy and usefulness of your SEO monitoring. It does not directly improve rankings. Website redirects and canonical signals can help search engines understand preferred URLs, but Google independently determines canonical selection, indexing, and ranking.

Final Thoughts

Moz domain unification is primarily a campaign-configuration question, not a shortcut for combining website URLs or changing Google's indexing decisions.

Start by identifying the hostname and crawl scope your Moz Pro campaign actually uses. If its tracked URL or scope is incorrect, create a new campaign with the appropriate configuration. Then handle website redirects and canonical signals separately, making sure they consistently identify your preferred public URLs.

Keeping these responsibilities separate makes SEO troubleshooting easier. You can monitor the correct website sections in Moz while independently verifying that your website and search-engine signals reflect the URL structure you intend to use.