Source: https://docs.amadalis.ai/site/readiness/

# Check site readiness

Checked against the product’s code on 7 November 2026.

Before launching your site, open **Site** > **Readiness** to see **Readiness report**. It combines a scan of the public home page with the site’s current bot and agent access policy.

The scan reads the site’s public home page at its main address. Publish the intended home page and choose the correct [front page](https://docs.amadalis.ai/site/site-setup/#choose-the-front-page-and-header-button) before using the report to assess that content. Other pages need their own review.

## Read the report

1.  Choose **Rescan** to request a fresh reading.
    
2.  Read the score and status.
    
3.  Read the checks beneath them. For each row, read **Status**, **Check** and **Detail** together.
    
4.  Review any scan warnings.
    
    [![Readiness report after Rescan: 68/100 (at-risk), scanned https://demo-store.sites.amadalis.ai/, ten checks with Pass, Fail or Warn.](https://docs.amadalis.ai/images/steps/S091-readiness-demo-root-after-rescan.png)](https://docs.amadalis.ai/images/steps/S091-readiness-demo-root-after-rescan.png "Open full-size image")
    
    A fresh scan of the served root.
    
    The demo store’s home address scores 68 out of 100 in this picture, and the Pass, Fail and Warn rows show the checks behind that score.
    
5.  Correct the named content or configuration in its owning screen.
    
6.  Return to **Readiness**.
    
7.  Choose **Rescan**.
    

The score is out of 100 and combines the checks beneath it. Read each **Detail** to see what passed, failed or needs attention. A higher score describes this scan; review the individual findings before deciding what to change.

Rescan reads the site; it does not make the proposed fixes. Use [SEO](https://docs.amadalis.ai/site/seo/) for search metadata, [the Composer](https://docs.amadalis.ai/composer/composer/) for page content and [redirects](https://docs.amadalis.ai/site/redirects-and-404s/) for old addresses.

The report can refresh after a copilot change that affects the served site. If it says that refresh failed, use **Show the latest** or **Rescan** before relying on the old report.

[![Readiness report for the company site root with Rescan and checks marked Pass, Fail or Warn.](https://docs.amadalis.ai/images/owners/platform-site-seo-and-ai-readiness-show-readiness-report.png)](https://docs.amadalis.ai/images/owners/platform-site-seo-and-ai-readiness-show-readiness-report.png)

Read Pass, Fail or Warn beside each check, then read its Detail. The score and findings belong to this scan of the public home page. [Open full size](https://docs.amadalis.ai/images/owners/platform-site-seo-and-ai-readiness-show-readiness-report.png).

## Review crawler and agent access

**[Bot & agent access policy](https://docs.amadalis.ai/reference/glossary/#bot--agent-access-policy)** shows the applied policy, its last application when recorded, the current `robots.txt` text and any site-wide indexing header.

An approved policy changes the live crawler instructions and headers. Its Undo restores the prior policy.

1.  Describe the access you want to the copilot.
2.  Read **Apply this bot-access policy?**.
3.  Choose **Apply bot policy** to approve or **Keep the current policy** to decline.

A crawler instruction does not provide access control for private content. Protected content also needs the site’s access controls. See [the machine-readable site guide](https://docs.amadalis.ai/developers/machine-readable-site/) for the published files and their roles.