Skip to main content

πŸ”Ž Search Atlas Site Auditor: How to Use Page Explorer

Explore individual crawled pages, filter technical page data, create segments, and review page-level SEO details from one workspace.

Updated over 2 weeks ago

The Page Explorer section in Search Atlas Site Auditor is where you move from site-level reporting into page-level analysis. Instead of reviewing your audit as a whole, this view lets you inspect individual URLs, compare technical page attributes, apply filters, build segments, and open a detailed page record with health scores, issue groups, indexability data, content elements, integrations, and structured page insights.

This area is especially useful when you need to analyze specific pages instead of only reviewing the audit summary.

🧭 How to open Page Explorer

To access this section:

  1. Go to the left sidebar

  2. Click AI SEO

  3. Under Site Audit, open the audited project

  4. Click Page Explorer

Once opened, the page displays the total crawled pages for the current audit, shown in the header as Crawled X out of X.

πŸ–₯️ What you see at the top of the page

At the top of the main content area, the page shows the heading Page Explorer followed by the current crawl coverage count, such as Crawled 97 out of 97.

On the right side of the top action bar, the visible controls include:

  • Create Segment

  • Share Audit

  • GSC/GA

  • Export

  • Manage Columns

This makes Page Explorer both a review area and a workspace for sorting, organizing, and drilling into page-level data.

πŸ“‹ The main table view

The center of the page is dominated by a table listing crawled pages.

Visible columns in the captured UI include:

  • Page

  • Depth

  • Type

  • Importance

  • Page Health

  • HTTPS

  • Status

  • Title

Each row represents a single crawled URL.

This table is the main entry point for technical page analysis across the site.

πŸŽ›οΈ Filter and sort the page table

The table header includes both sorting indicators and filter controls.

Sorting

Some columns display sorting arrows in the header, indicating that the list can be ordered by that field.

Filters

Under the column labels, Page Explorer includes filter inputs and range controls depending on the data type:

  • text/dropdown-style filters for columns like Page, Depth, Type, HTTPS, Status, and Title

  • slider-style filters for Importance

  • slider-style filters for Page Health

This makes it possible to narrow the page list visually and focus on the pages that match a specific technical pattern.

πŸ“Œ What the visible table columns mean

Page

This column shows the crawled URL path.

Depth

This indicates the crawl depth level for the page.

Type

This shows the page resource type, such as text/html; charset=UTF-8.

Importance

This column displays a numeric importance score, shown with a pill-style visual.

Page Health

This column uses a horizontal health bar to summarize each page’s health.

HTTPS

This indicates whether the page is served over HTTPS.

Status

This displays the HTTP status code, such as 200.

Title

This shows the page title detected for that URL.

Together, these columns provide a compact technical snapshot of each page without needing to open the detail view first.

🧩 Create a segment

The Create Segment button opens a segment-building interface that splits the screen into two working areas:

  • a left configuration panel

  • the page table on the right

At the top-left of this mode, the page header changes to Exit segment editor, showing that you are inside segment setup mode.

What is visible in the Segment panel

The left-side Segment panel includes:

  • Segment name

  • Icon

  • Color

  • Column filters (optional)

  • Column to sort on

  • Direction

    • Top

    • Bottom

  • Selection

    • Pages

    • Percent %

  • Quantity

  • a count line showing how many pages are included in the segment

  • a Create Segment button

  • a Clear inputs option

This setup suggests that segments can be built by sorting and selecting a subset of pages based on table data and filter logic.

🧱 Manage visible columns

The Manage Columns control opens a panel titled Columns with the instruction:

Select and re-order the columns you want to see

The visible categories in the captured UI include:

  • Fundamentals

  • GSC Insights

  • Content

  • Social

  • Indexability

  • Relations

  • Lighthouse Web Vitals

  • Google Analytics

  • Conversions

  • Schema.org

Each category shows a selected count such as 7/12 or 4/4, indicating how many fields are currently active within that category.

This means Page Explorer can be customized to show different data groups depending on what the user wants to inspect.

πŸ”— Google integrations from Page Explorer

The GSC/GA button opens a modal titled Google Integration Settings.

In the visible UI, this modal includes:

  • the selected property or domain at the top

  • Location

  • GSC Property

  • GA4 Property

  • + Connect new GSC account

  • + Connect new GA4 account

  • Cancel

  • Update

This lets users manage connected Google data sources directly from Page Explorer without leaving the page-level analysis area.

πŸ‘οΈ Open an individual page detail view

When a specific page is opened, Page Explorer changes from list mode into a detailed page-level record.

The top section of the page detail view includes:

  • the full page URL

  • the detected page title

  • a short page description snippet when available

  • action buttons:

    • Recrawl Page

    • Share Audit

    • Export

  • a page preview thumbnail on the right

  • Last page update information

This creates a much more detailed SEO inspection view for one URL.

πŸ“ˆ Page Health panel

On the right side of the page detail view, the UI shows a vertical summary panel with:

  • Page Health shown as a score out of 1,000

  • grouped issue categories

  • grouped compliant categories

The issue categories visible in the screenshots include examples such as:

  • Content

  • Links

  • Twitter Meta

  • Page Headers

  • OG Meta

  • Images

The compliant categories visible include examples such as:

  • Meta Description

  • Schema

  • Canonical Link

  • Sitemap

  • Robots

  • Uniqueness

  • Hreflang

  • Page URL

  • Analytics

  • Page Title

This right-side panel acts like a navigation and status summary for the page.

🚨 Page Issues workspace

When expanded, the page issues area displays a section titled Page Issues with a two-column layout:

  • a left category rail

  • a right issue detail panel

Left category rail

The left side lists categories such as:

  • Content

  • Links

  • Twitter Meta

  • Page Headers

  • OG Meta

  • Images

and a separate Compliant section with categories such as:

  • Analytics

  • Schema

  • Meta Description

  • Sitemap

  • Canonical Link

  • Hreflang

  • Robots

  • Page URL

  • Uniqueness

  • Page Title

Each category card may display counts for issues and compliant items.

Right issue detail panel

When a category is selected, the right panel shows:

  • the category name

  • a summary like X issues found and Y compliant

  • a horizontal status bar

  • an issue table with columns such as:

    • Issue

    • Health Gain

  • action buttons on each row such as:

    • How to Fix

    • Details

  • an Ignore all option at the top of the section

Once you click the "How to fix" button you see recommendations like this:

This is the main corrective-action view for page-level issue review.

🟒 Indexability section

The page detail view includes a card labeled Indexability.

Visible fields in this section include:

  • Indexable

  • HTTPS

  • Status Code

  • In XML Sitemap

  • Download Time

  • Canonical URL

  • Meta Robots

  • Meta Googlebot

  • Robots.txt

  • XML Sitemap

This section provides a compact technical snapshot of crawlability, indexability, and related signals for the selected page.

πŸ“ Content section

Below Indexability, the page detail includes a Content card.

Visible fields include:

  • Title

  • Meta Description

  • Headers

    • H1

    • H2

    • H3

A Show all tags link is visible in the headers section when additional heading entries exist.

This area is useful for reviewing on-page content structure without leaving the audit interface.

πŸ“Š Google Search Console Insights

The page detail also includes a Google Search Console Insights card.

Visible metrics in the captured UI include:

  • Total Keywords

  • Avg. Position

  • Impressions

  • Organic Traffic

  • CTR

These appear as compact metrics paired with mini line charts, providing a quick organic search snapshot for the selected page.

πŸ”— Relations section

The Relations card shows internal and external linking relationships for the page.

Visible fields include:

Incoming

  • Internal Links

  • Canonical (On-page)

  • AMP Variant

Outgoing

  • Internal Links

  • External Links

This helps users understand how the page is linked within the site and what canonical state is being reported.

πŸ“ˆ Google Analytics section

The page detail includes a Google Analytics card with page-level engagement and traffic metrics.

Visible metrics in the screenshot include:

  • Total Users

  • New Users

  • Engaged Sessions

  • Bounce Rate

  • User Engagement Duration

  • Screen Page Views

  • Ecommerce Purchases

  • Average Session Duration

  • Event Count

  • Total Revenue

This gives a behavioral layer that complements the technical audit data.

🧬 Schema.org section

The Schema.org card shows structured data extracted for the page.

The visible view includes structured fields such as:

  • @context

  • @graph

  • @id

  • @type

  • dateModified

  • datePublished

  • description

  • image

  • inLanguage

  • isPartOf

  • name

  • potentialAction

This section helps users inspect schema markup directly from the page detail view.

⚑ Lighthouse Web Vitals section

The page detail also includes a Lighthouse Web Vitals card.

Visible data includes:

  • Last update

  • Performance Score

  • Speed Index

  • First Contentful Paint

  • Largest Contentful Paint

  • Time To Interactive

  • Cumulative Layout Shift

  • Total Blocking Time

This section adds performance-focused diagnostics to the technical page review.

🌐 Social section

The Social card includes Open Graph-related fields.

Visible items in the screenshot include:

  • Open Graph Type

  • Open Graph URL

  • Open Graph Title

  • Open Graph Description

  • Open Graph Image

A Show full social link appears at the bottom of the section for expanded review.

πŸ”„ Recrawl, share, and export a single page

Once inside the page detail view, the visible top action buttons are:

  • Recrawl Page

  • Share Audit

  • Export

This means users can re-audit a single page, share the page-level report, or export the current detail view directly from Page Explorer.

🧠 What Page Explorer is best for

Use Page Explorer when you need to:

  • inspect individual URLs instead of only site-level summaries

  • filter pages by technical or content-related fields

  • compare status, importance, and page health across URLs

  • create page segments from filtered data

  • customize visible columns by data category

  • review page-level indexability and metadata

  • analyze page health and issue groups

  • inspect GSC, GA, schema, lighthouse, and social details for a specific page

It is the most detailed page-level analysis area visible inside the Site Audit flow.

The Page Explorer section turns Site Auditor from a site-wide reporting tool into a page-level investigation workspace. It combines filtering, segmentation, customizable columns, integrations, and detailed page diagnostics so users can move from broad audit monitoring into precise URL-by-URL analysis.

For deep technical review, this is one of the most information-dense areas in Site Auditor.

Did this answer your question?