Skip to main content

Open in AthenaHQ

app.athenahq.ai/site-health/properties

Purpose

The Property Pages view lets customers explore the complete inventory of pages discovered within a specific Site Health crawl scope. It provides a folder-by-folder view of the site, allowing users to drill down into specific URLs, filter by known problems, launch targeted audits, and review detailed evidence for any issues found on a page.

What’s on the page

  • Page Header: Displays the property’s name and root URL. It houses the main actions for navigating away or starting audits.
  • Audit progress / Crawl coverage card: Tracks the status of the current or most recent run. It includes a status badge (e.g., “Auditing”, “Complete”, “Failed”), a progress bar for live audits, and exact counts for pages Discovered, Scanned, Skipped, Blocked, and Failed.
  • Filter row: A set of controls to narrow down the page list:
    • Filter by problem: A dropdown that lists all known SEO/visibility issues and how many pages suffer from them. Selecting one filters the tree to only those pages. Defaults to “All problems”.
    • Search pages: A text input to find specific URLs.
    • Count line: Shows the total number of pages matching your current search or filter.
  • Page tree: A nested folder view of the website’s crawled URLs. Folders show the total number of pages inside them. Individual page rows show:
    • Audit status: “Checked”, “Blocked”, “Could not read”, “Skipped”, or “Not checked yet”.
    • AI citation rate: The percentage score for retrievability.
    • Win rate vs top pages: The percentage score for citability.
    • Open issues: The number of unresolved findings on the page.

Page Evidence Drawer

Clicking any page row opens a side panel detailing its specific data:
  • URL: A clickable link to view the live page in a new browser tab.
  • Findings: A list of every issue identified on the page. Each finding explains the problem, recommends a fix, and lists the exact evidence detected.
    • Verification badge: Shows whether the issue is “Verified fixed”, “Still present”, or “Not verified”.
  • Measurement summary: The data snapshot captured during the audit, including Title, Description, Canonical, HTTP status, Words, and Indexable.
  • Server and rendered content: An explanation of how the page loads.
    • Compare main content excerpts: A collapsible section showing the exact text extracted from the “Server” read versus the “Rendered” read.
  • Measurement experiment settings: A collapsible section containing the Control group checkbox, which allows you to intentionally exclude this page from optimization so it can be used as a baseline to compare against.
  • Additional audit coverage: Technical metrics like Mobile PageSpeed (LCP, INP, CLS) and Hreflang annotations.

What you can do here

  • Back to Crawl scope: Returns to the main crawl setup list.
  • Site Health issues: Navigates to the centralized issues board.
  • Cancel run: Stops an active audit or crawl. This button only appears when a run is actively in progress.
  • Audit all pages: Starts a full audit over every page in the property’s inventory.
  • Audit a sample: Starts a lightweight audit that reads up to 25 pages from each site section, plus any high-priority pages.
  • Audit N selected: When you check boxes next to pages in the tree, the sample/full audit buttons are replaced by this button, which audits only the specific pages you selected (up to a maximum of 100 pages at a time).
  • Clear N selected: Deselects all currently checked pages.
  • Clear filters: Shown when a search or filter yields no results; clicking it resets the view.
  • Show more: Loads the next batch of search results if there are more pages than fit on the screen.
  • Open page evidence: Click anywhere on a page’s row in the tree to slide out the evidence drawer.
  • Close details: Closes the evidence drawer.
  • Fix with Athena: Located inside the evidence drawer. This opens the Ask Athena chat panel and automatically provides the AI with the page’s context so it can draft a fix for the open findings.
  • Open in Issues: Located on individual findings in the drawer. Jumps directly to that finding in the Site Health Issues view.
  • Rerun check: Kicks off an audit specifically to re-verify a finding.
  • Control group checkbox: Toggles the page’s status as a measurement control.
  • See results: Jumps to the Site Health Results view.
  • Try again: Buttons that appear on error callouts to retry loading data.

Data shown

This page displays your tracked website pages as discovered by the crawler for this specific property scope. The metrics, text excerpts, and findings reflect the exact state of the site during the most recent AI-visibility audit.

Common workflows

  1. Running a baseline audit: Open a newly set up property and click “Audit a sample”. Watch the progress bar in the coverage panel until it completes, then review the initial findings.
  2. Targeted bulk auditing: Search for a specific sub-folder (e.g., your blog pages), select the checkboxes for the top 10 articles, and click “Audit 10 selected” to check them without scanning the whole site.
  3. Fixing an issue: Use the “Filter by problem” dropdown to isolate pages suffering from missing titles. Click a page to open its drawer, review the finding, and click “Fix with Athena” to have the AI write a new title.
  4. Setting up a control group: To prove the value of your optimizations, open a few representative pages, expand the “Measurement experiment settings” in their drawer, and check “Control group”. These pages will be explicitly ignored during bulk optimizations.

Empty, loading, and error states

  • Empty inventory: If the crawler hasn’t found anything yet, you will see “No pages found in this crawl scope yet” and an action to “Open crawl setup”.
  • Live but empty: If a crawl is actively running but hasn’t returned pages yet, it displays “The crawl is still running”.
  • No filter matches: If your search yields no pages, the screen shows “No pages match these filters” with a “Clear filters” button.
  • Loading: Skeleton UI boxes appear while the crawl scope, tree folders, or page evidence are being retrieved.
  • Errors: If data fails to load, red callouts appear stating “This crawl scope could not be loaded”, “These pages could not be loaded”, or “Page evidence could not be loaded”, alongside a “Try again” button.
  • Linked from: The Crawl scope setup page, and the Site Health header menu.
  • Links to: The Crawl scope setup page, Site Health Issues, Site Health Results, and the Ask Athena chat.

Common support questions

Why can’t I click the audit buttons? If the property is toggled off (disabled) in your crawl setup, or if the crawler hasn’t discovered any live pages yet, you cannot start an audit. Why did the “Audit all pages” button disappear? If you select one or more checkboxes next to pages in the tree, the general audit buttons are replaced by an “Audit N selected” button. Clear your selection to bring the other buttons back. What exactly does “Rerun check” do? It triggers a fast, targeted audit to see if you have fixed the issue. For most findings, it only re-reads the single page you are looking at. However, for duplicate metadata issues (like several pages sharing the same title), it will quickly scan the entire property to ensure the duplication is gone. Why does the view change completely when I type in the search box? To make finding pages easier, typing in the search box flattens the folder tree into a fully expanded list of matching URLs. This ensures you don’t have to hunt through nested folders to find your search results.