RankAnvil Pro
Technical SEO & AI Readiness

🏥 Technical Site Auditor

Your practical guide to the 100-check RankAnvil Site Auditor: from starting a crawl to understanding evidence, prioritising fixes and sharing a client-ready PDF report.

100 registered diagnostics Up to 500 pages per crawl Actionable recommendations A4 PDF export

🌐 1. Launch a fresh site crawl

Open Site Auditor (Agency) from RankAnvil's Technical & AI tools. Enter the target website in Target Domain to Audit, choose the appropriate Target Region, and select Analyze Data.

RankAnvil Site Auditor selected in the tools dashboard, showing the target website field, region selector and Analyze Data button
Know the scope: Each new audit requests a crawl of up to 500 pages. This is a ceiling, not a guarantee that all pages on a larger site will be covered. New crawls can incur provider usage costs.

⏳ 2. Follow the crawl progress

Once you launch the audit, RankAnvil displays a progress indicator and crawl status. The current tool advises allowing roughly 1–30 minutes, depending on the number of pages and how the site responds. Keep the workspace open until completion, as advised by the interface.

Site Auditor showing the crawl in progress at 30 percent

The progress bar indicates processing progress; it does not represent an SEO quality score.

📊 3. Read the report overview

When the crawl completes, the summary header displays the target domain, pages crawled and the provider's on-page score. Beneath it are four useful counters: registered checks, checks with findings, total findings and high-priority checks.

Completed site audit overview with on-page score of 92, 100 registered checks, 23 checks with findings, 189 total findings and 2 high-priority checks
On-page score

A score supplied by DataForSEO. It is not calculated from RankAnvil's 100-check diagnostic registry.

Checks registered

The number of diagnostic rules available in this report, including those with zero detected findings.

Checks with findings

How many distinct diagnostic groups produced at least one observation.

Total findings

The combined number of reported observations. This is not necessarily the number of unique affected pages.

🔍 4. Understand findings, evidence and recommendations

Each diagnostic card identifies its severity and category, and shows how many observations it contains. Select Show evidence to expand a card, or Hide evidence to collapse it. Expanded cards explain What this means, give a Recommended action, and list the relevant URLs or asset-level evidence.

Critical Broken Pages diagnostic with explanation, recommended action and affected URL

For example, a Broken Pages finding highlights a page the crawler could not successfully retrieve. Check the response and either restore the page or update links pointing to a suitable replacement.

Expanded Redirecting Pages diagnostic showing the reason, suggested action and affected URLs
Important distinction: A redirect can be intentional; a missing H1 may be appropriate on certain page types (eg: thin content); and not every advisory warning requires a change. Use the provided evidence and your knowledge of the website before making edits.

🧭 5. Filter and prioritise your diagnostics

Use the category filter to focus on a particular area, including Technical SEO, On-page SEO, Security, Content quality, Performance or AI readiness. The adjacent findings filter lets you focus on checks with findings; Expand visible evidence opens the evidence for the currently displayed items.

Category filter listing Technical SEO, On-page SEO, Security, Content quality, Performance and AI readiness

A sensible order of attention

  1. Critical: Check access, crawling failures and other severe problems first.
  2. High: Review significant issues, especially on important pages.
  3. Medium: Consider structural, content and performance improvements in context.
  4. Low: Review optional and heuristic-based suggestions when useful.

The impact and effort labels shown in a diagnostic help with planning, but they are general guidance rather than a site-specific cost estimate.

📄 6. Export a client-ready PDF

Use the workspace's PDF report export control after the audit is complete. The downloaded A4 report brings together the domain summary, executive priorities, findings in severity order, explanatory guidance, supporting evidence and an appendix of checks without detected findings.

First page of a RankAnvil Site Audit PDF showing executive priorities and detailed technical findings
For agencies: Review the recommendations for client-specific context before sharing the document as an action plan. An exported report reflects the crawl that was performed, not a live continuous scan.

✅ 8. A practical approach to fixing the issues

  1. Start with Critical and High findings, particularly those affecting commercially important pages.
  2. Open the evidence, visit the affected URLs and verify whether the reported condition still exists.
  3. Apply the recommended action where appropriate, using your website's CMS, theme, developer or hosting controls depending on the error(s).
  4. Record what you changed and share the PDF between colleagues to maintain an effective history.
  5. Run a fresh audit when you need to validate the changes; which would be a new crawl, not an automatic refresh of the original findings.
The RankAnvil approach

Find the issue. Understand the evidence. Decide what matters. Take informed action.

© 2026 Tech Fusion AS · RankAnvil Academy · Technical Site Auditor