A Moz Pro site audit is a crawl of a website for technical SEO, crawlability, redirect, metadata and content issues. To run one, create a Moz Pro Campaign, set the website and crawl limit, open Site Crawl, review the findings, fix the highest-priority problems, and recrawl the site.

Documentation checked: ****.

Moz uses its crawler, Rogerbot, to examine your site. The Campaign setup documentation covers the initial configuration.

Moz Site Audit Process at a Glance

Step Where to go in Moz Pro What to do
1. Create a Campaign Moz Pro Campaigns Add your domain and choose the crawl limit
2. Confirm the scope Campaign Settings Audit the full domain, subdomain or subfolder
3. Start the crawl Site Crawl Wait for the initial crawl to finish
4. Review the overview Site Crawl Overview Check pages crawled, new issues and total issues
5. Fix problems Issue categories Start with critical crawler issues
6. Verify changes Recrawl Confirm that resolved issues no longer appear

1. Create a Moz Pro Campaign

Log in to Moz Pro and create a new Campaign. Enter your domain without the or protocol, such as example.com.

Moz uses the Campaign to track your site and collect crawl data. During setup, it asks for:

  • The website you want to track
  • A crawl limit
  • Optional Google Analytics access
  • Search engines and locations
  • Keywords
  • Competitor websites

For a basic site audit, the website URL and crawl limit matter most. You can skip Google Analytics and connect it later through Campaign Settings. The Moz Campaign setup documentation explains these settings.

Choose the Correct Crawl Limit

Set the crawl limit close to the number of indexable pages you want Moz to inspect. Rogerbot stops when it reaches the selected limit or when it cannot discover any more pages, whichever happens first.

For example, a 5,000-page limit cannot cover a 7,000-page website completely. If the limit is too low, Moz audits only part of the site and the report may miss technical SEO problems elsewhere.

2. Choose the Correct Audit Scope

Moz Pro can crawl:

  • An entire domain
  • A specific subdomain, such as blog.example.com
  • A specific subfolder, such as example.com/blog

To audit a subfolder, enter that subfolder during Campaign setup. To restrict a Campaign to a subdomain, use Advanced Settings and select the option that excludes other subdomains.

Moz can only crawl pages it discovers within the selected scope. Choose the full-domain option for a complete website audit. Use a subfolder or subdomain Campaign when you need to isolate one section.

3. Open Site Crawl and Wait for the Audit

After creating the Campaign, select Site Crawl from the left-hand navigation in Moz Pro. This is where Moz shows the pages it crawled and the issues it found.

For websites with more than 250 pages, Moz may begin with an initial rush crawl of approximately 250 to 300 pages before starting a full crawl. Smaller websites may receive a full initial crawl immediately.

Wait for the relevant crawl to finish before assessing the results. Compare Pages Crawled with the approximate number of pages you expected Moz to find.

4. Read the Moz Site Crawl Overview

The Site Crawl Overview shows four main areas:

  • Pages Crawled: The number of pages Moz inspected
  • New Issues: Problems found since the previous crawl
  • Issues by Category: The types of problems reported
  • Total Issues: The complete number of reported problems

Select a page count to view the crawled URLs. Select an issue category to investigate the affected pages. The Moz Site Crawl overview describes these report areas.

Moz groups findings into categories such as:

  • Critical Crawler Issues
  • Crawler Warnings
  • Redirect Issues
  • Metadata Issues
  • Content Issues

5. Fix Critical Crawler Issues First

Start with problems that can stop users or search engine crawlers from reaching important pages. Moz identifies 5xx errors, 4xx errors and redirects to 4xx pages as critical crawler issues.

Review the findings in this order:

  1. 5xx errors: Investigate server failures and hosting problems.
  2. 4xx errors: Restore the page, redirect it to a relevant replacement, or remove internal links pointing to it.
  3. Redirects to 4xx pages: Change the redirect so it points to a valid, relevant URL.
  4. Redirect issues: Remove unnecessary redirect chains and correct incorrect destinations.
  5. Metadata issues: Review the affected page titles, descriptions and related metadata.
  6. Content issues: Inspect duplicate, missing or otherwise problematic content identified by Moz.

Click an issue title to view the affected URLs and Moz's explanation. Moz also provides recommended fixes for selected issue types in the Site Crawl interface.

Do Not Fix Every Warning Automatically

A warning is a diagnostic signal, not an instruction to change the site immediately. Open the affected URLs and confirm whether the issue affects an important page.

Some redirects, noindex instructions and duplicate pages are intentional. Check the page's purpose and the site's SEO strategy before changing them.

6. Export Crawled Pages for Detailed Analysis

Use All Crawled Pages when you need to work with the audit outside Moz Pro. Moz allows you to export crawled pages as a CSV file. The export can help you identify missing sections, review link counts and investigate redirect targets.

An export is useful when:

  • Moz crawled fewer pages than expected
  • A subfolder appears to be missing
  • Important pages have few or no internal links
  • Redirects lead outside the Campaign scope
  • Developers or content teams need a task list

A page with a link count of zero may prevent Rogerbot from discovering more pages through normal HTML links. The Moz crawl troubleshooting documentation covers crawled-page exports and crawl problems.

7. Fix Crawl Failures Before Interpreting the Results

A very small crawl can point to a configuration or access problem rather than a healthy website. Check these areas before reviewing the issue count.

Robots.txt Access

Open your domain's /robots.txt file in a browser and confirm that it loads correctly. Check that it does not block Rogerbot or all crawlers.

Moz also recommends checking server logs to see how the server responds to Rogerbot.

Redirects from HTTP to HTTPS

Moz starts crawling from the non-www HTTP version of the domain and follows redirects. If that version does not redirect correctly to the live HTTPS or www version, the crawl may stop before reaching the site.

Server and Firewall Blocks

A server-level block, forbidden response or Web Application Firewall rule can prevent Rogerbot from crawling the site. Check whether Rogerbot and Amazon Web Services traffic are blocked.

No-Follow Directives

A nofollow directive on the homepage can stop Rogerbot from following internal links. A homepage with noindex, nofollow may produce a one-page crawl report.

JavaScript-Heavy Websites

Moz states that Rogerbot may not parse JavaScript-heavy websites accurately. If JavaScript generates important links or page content, compare the crawl results with the links visible in the page source.

8. Recrawl the Site After Making Changes

After fixing the reported issues, return to Site Crawl and select Recrawl my site when the option is available. Moz states that manual recrawls are available on Medium plans and above.

Run a recrawl after:

  • Correcting robots.txt
  • Fixing server errors
  • Replacing broken internal links
  • Updating redirects
  • Resolving important metadata problems
  • Launching a redesigned website

Moz also attempts to crawl Campaign websites weekly, so Site Crawl can support ongoing monitoring as well as a single audit.

How to Judge the Audit Results

The total issue count is not the audit result. First, check whether Moz crawled the pages you expected. Then assess each issue by:

  • The type of problem
  • The number and importance of affected URLs
  • Its effect on crawling or indexing
  • Its effect on users
  • Whether the configuration is intentional

This prevents a low crawl count from looking like a clean report and stops intentional settings from being changed without a reason.