AI VisibilityAudit AI Crawler Coverage of Important Pages

Audit AI Crawler Coverage of Important Pages

Use Hardal AI Visibility to review which product, pricing, and content pages receive recorded AI crawler visits.

An AI page-coverage audit asks whether identified agents are reaching the public content your team considers important. Start with a defined page list so popular pages do not hide missing coverage elsewhere.

Define the page set

Create a small list outside Hardal with the exact public paths you want to review. For a product website, include pricing, key product pages, implementation guides, and high-priority articles. Record why each path matters and whether it existed throughout the reporting period.

Use recorded paths consistently. If a page moved or redirected, keep the old and new paths in your review rather than assuming the report combines them.

Inspect coverage in Pages

Set the scope

Open AI Visibility → Pages. Choose the source, date range, and timezone, and keep AI Focus on for an AI-only review.

Find each important path

Search Page Report for the path. Expand its row to inspect the recorded agents, platforms, categories, visits, and share.

Compare activity over time

Use Page Paths in the page-visit chart to compare selected paths. Record whether visits are spread across the period or concentrated on a day.

Use the right denominator

The Pages Covered scorecard counts distinct visited paths in its report scope. It does not know the size of your external priority list.

If 8 of 12 priority paths have recorded AI visits, your manual priority-page coverage is 8 ÷ 12, or about 66.7%. Label this as your team's calculation, keep the list fixed, and do not present it as Hardal's built-in coverage percentage. Total visits answer a different question: one frequently requested page can account for many requests.

Follow up on an absent path

Check that the page is public and internally linked, then verify that the collection layer covers requests to it. An empty row can reflect scope or collection gaps as well as no recorded eligible requests. Absence alone does not diagnose robots rules or access failures.

Use AI Visibility Setup for collection checks and monitoring content updates for a planned change. Coverage records access; it does not establish indexing or inclusion in answers.