πŸ” Reading Existing Site Audit Results Safely

Camilo Aponte

Camilo Aponte

Last updated on Nov 11, 2026

πŸ”Ž What This Article Covers

This guide explains how to read the status, page count, and URL issues of a Site Audit that has already run. Reading results does not start a new crawl or change the audit, so it is safe to use at any time.

πŸ†” Finding Your Audit ID

Every Site Audit has a numeric ID that appears at the end of its dashboard address. For example, in the address /site-audit/83952, the audit ID is 83952.

To confirm an ID is valid for your account:

  1. Sign in to the Search Atlas dashboard.
  2. Open the address for the audit you want to check.
  3. If the audit page loads with its crawl summary, the ID is accessible to the signed-in account, or through a valid public share link. That does not by itself prove the audit belongs to the account.
  4. If you see a not-found response, the ID is not accessible to the signed-in customer account. Sign in to the account that owns the audit and try again.

πŸ“Š Viewing Status and Page Count in the Dashboard

The fastest way to read an audit's current state is in the dashboard itself:

  • Status: A finished audit shows a health result such as Healthy, Fair, or Poor. An active audit can show Crawling, Preprocessing, or Will recrawl soon, and a failed crawl shows Crawl failed.
  • Pages crawled: The audit list shows crawled pages against the crawl total, such as 630 of 1,500 pages. The overview shows the current crawled-page total.
  • URL issues: Issues are grouped by category and issue type, with Critical, Warning, and Notice severities. Open an issue to see the affected URLs.

Viewing these pages does not affect the audit or use a new crawl.

πŸ”Œ Reading Audit Data Through the API

If you want to pull audit status, page counts, or URL issues into your own tools, you can use the Site Audit read endpoints. Follow these rules to avoid accidentally starting a new crawl:

  • Use a plain GET when you only want to read results. POST, PUT, and PATCH can create or change audits, and GET /api/v2/site-audit/{id}/issues/?export=true queues an issues export instead of only returning results.
  • Do not call crawl-triggering endpoints such as POST /api/v2/site-audit/{id}/recrawl/ when you only want existing results. A path containing start, create, or recrawl is not by itself proof that it starts a crawl.
  • Use your own API credentials. Generate or locate your API key or token in your account settings, and send it in the authorization header format shown in your API reference.
  • Use the Site Audit v2 paths in your API reference. Query parameters such as scope and segment_id change which results are returned, but the paths do not vary by plan.

πŸ§ͺ Testing a Read-Only Request

When you test your request, check that it is a GET request and that the audit ID in the path matches the audit you want. Replace the placeholders below with values from your own account and documentation:

curl -X GET "https://[API_BASE_URL]/[SITE_AUDIT_READ_PATH]/83952" -H "Authorization: [YOUR_AUTH_HEADER]" -H "Accept: application/json"

A successful detail response includes the audit status and crawl summary fields. The issues response instead returns issues grouped by category and issue type. If the response does not match the endpoint you called, compare the request with your API reference before trying again.

⚠️ Troubleshooting Common Errors

  • 401 or 403: Your credentials are missing, expired, or do not have permission to read this workspace. Generate a new key or check the workspace you are using.
  • 404: The audit ID does not exist in the workspace linked to your credentials. Confirm the ID in the dashboard first.
  • 405 or unexpected crawl activity: The request method or path may be wrong. Use GET only and remove any start or recrawl path.
  • Empty or partial results: The audit may still be in progress. Check the status in the dashboard and try again once it is complete.

πŸ’¬ Need More Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and send your message. A member of our support team will reply in the chat.

Was this article helpful?