> ## Documentation Index > Fetch the complete documentation index at: https://docs.athenahq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Site Health – Staging Checks (Release Comparisons) > Lets a team set up and review comparisons between live production pages and their public staging copies before shipping a template or site release, to catch SEO regressions. `app.athenahq.ai/site-health/releases` ## Purpose Staging checks allow marketing and SEO teams to compare their live production pages against public staging copies before releasing a major template update or site redesign. By reading both versions of a page, this tool catches critical SEO regressions - like missing titles, dropped structured data, or broken canonical links - before the changes go live and impact search rankings. It differs from everyday page edits in that it is designed for batch-verifying structural or template-level changes across a sample of important pages. ## What's on the page * **Page header:** Displays the "Staging checks" title and description. Includes a "Back to Site Health" button to return to the main overview, and a "New comparison" button (if the user has write access and crawl scopes are set up) to start a new check. * **Saved comparisons list:** A paginated history of all release comparisons run for this website. Each clickable row shows the release name, the date it was created, how many pages were checked, and a status badge ("Report ready", "Failed", or "Comparing"). * **Release report:** Appears below the list when a saved comparison is selected. Shows the release name, a high-level readiness summary (e.g., "Blocking regressions", "Review warnings", "No blocking regressions", or "Incomplete"), and a tally of issues found. * **Report findings (per page):** A collapsible row for each page pair checked. Expanding a row reveals direct links to the production and staging pages, timestamps for when they were captured, and a side-by-side breakdown of the specific SEO regressions detected (like "Page title changed" or "Search directives changed"). * **New comparison dialog:** A modal that opens when starting a new check. It asks for a release name, which crawl scope to use, the public staging root URL, and an optional list of specific pages to check. It generates a preview of the exact page pairs before anything runs. ## What you can do here * **Start a new comparison:** Click "New comparison" to open the setup dialog. Fill out the details, click "Preview page pairs" to verify the URLs that will be checked, and then click "Compare N pages" to start the run. * **Review a report:** Click any row in the "Saved comparisons" list to load its detailed report below. * **View specific page regressions:** In the report, click a page's row (e.g., `example.com/docs/setup`) to expand it and see the exact before-and-after text or code that triggered the warning. * **Rerun a comparison:** Click "Rerun same baseline" inside a report to kick off a fresh comparison using the exact same settings and page list, comparing the current live site against the current staging site. * **Share a report:** Click "Copy report link" to grab a direct URL to the currently selected report. (Note: The recipient must be logged in and have access to the website to view it.) * **Set up a crawl scope:** If the site has no crawl scopes configured, click the "Set up a crawl scope" button in the empty state to navigate to the setup page. * **Paginate through history:** Use the "Previous" and "Next" buttons below the saved comparisons list to view older checks. ## Data shown * **Saved comparisons:** Historical records of staging checks executed for the current website. * **Reports & Findings:** Point-in-time snapshots of how your live pages compared to your staging environment, evaluating SEO elements like titles, meta descriptions, canonical tags, heading hierarchy, structured data, and search directives. * **Crawl scopes:** Configured site boundaries that tell the comparison tool which live pages are important and available to check. ## Common workflows **Starting a new staging check:** 1. Click the "New comparison" button. 2. Enter a "Release name" (e.g., "September template update"). 3. Select a crawl scope under "Live pages from". 4. Enter the base URL of your staging environment in "Public staging root" (e.g., `https://staging.example.com`). 5. Either leave "Pages to compare" blank (the tool will auto-select up to 20 important pages) or paste in specific live URLs you want to check. 6. Click "Preview page pairs" to ensure the live URLs correctly match up with their staging equivalents. 7. Click "Compare N pages" to launch the check. **Reviewing and resolving regressions:** 1. Click a completed run in the "Saved comparisons" list. 2. Review the top summary to see how many blocking issues or warnings were found. 3. Scroll down and expand any page row marked with "blocking" changes. 4. Review the side-by-side evidence (e.g., seeing that the staging site dropped the canonical URL). 5. After your developers fix the issue on the staging site, return to this report and click "Rerun same baseline" to verify the fix. ## Empty, loading, and error states * **No crawl scopes:** If the site hasn't been crawled yet, you'll see a "Set up a crawl scope first" empty state. A comparison cannot be built without one. A "Set up a crawl scope" button is provided. * **No comparisons:** If scopes exist but no checks have been run, a "No comparisons yet" empty state appears, inviting you to start one. * **Loading:** Skeleton blocks appear while the comparisons list or the selected report fetches data. If a comparison is actively processing, the report status will read "Comparing pages". * **Errors:** If data fails to load, you will see a red callout banner (e.g., "Crawl scopes could not be loaded" or "Saved comparisons could not be loaded") with a "Try again" button. Form errors (like invalid URLs) will appear as toast messages at the bottom of the screen. * **Feature unavailable:** If the SEO monitoring feature isn't enabled for the account, or if the user is in a restricted partner environment, a "Site Health is not available here" message is shown and the rest of the page is hidden. ## Linked from / links to * **Linked from:** The main Site Health overview page, specifically from the "Options" (three-dot) menu in the page header by clicking "Staging checks". * **Links to:** The Site Health Overview (via "Back to Site Health") and the Crawl Scope Setup page (via "Set up a crawl scope"). Clicking a Production or Staging URL in the report opens that external webpage in a new tab. ## Common support questions * **Why is the "New comparison" button missing?** You must have "Analytics: Write" permissions to create a comparison. If you only have view access, you can read existing reports but cannot start new ones. The button is also hidden if no crawl scopes exist yet. * **How does it pick pages if I don't paste any in?** If you leave the "Pages to compare" box blank, the tool automatically selects up to 20 pages for you. It does this by picking one page from each major section of your site, prioritizing the homepage and high-priority pages. * **Why did my staging check fail?** Staging checks require your staging URL to be publicly accessible over HTTPS. If your staging site is behind a password, a VPN, or uses HTTP, the comparison tool will fail to read it. * **Why is "Rerun same baseline" disabled?** This button is disabled if the comparison is currently running, if another rerun is already in progress, if you lack write permissions, or if any page in the report failed to capture a production snapshot during the initial run. * **Can I check more than 50 pages?** No, each comparison is capped at 50 pages. This is intended to test templates and key structural layouts rather than auditing every single URL on a site.