> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up and use Organic

> Verify a site and read the available organic visibility, search, and audit evidence.

**Organic** reviews one site at a time. It can help you inspect crawl findings, search context, and available visibility evidence. Features beyond setup depend on the site's Organic entitlement and connected data.

## Start in Setup

1. Open [Organic → Setup](https://www.autoady.io/organic?tab=setup).
2. Add the domain you want to inspect, then publish one of the ownership proofs supplied by the product: the DNS record or verification file.
3. Run the ownership check and confirm the verified site and method.
4. Read the Organic add-on state. Site registration and verification can be available while paid analysis remains unavailable. Only the workspace owner can purchase the add-on when offered.
5. Connect the relevant search or analytics source through the provided setup controls if the work needs it. Check the chosen property and site.
6. Open the supported analysis tab and inspect its source, timing, coverage, and missing-data messages.

## Choose the evidence you need

**Overview** brings together available site evidence. **Audits** and **Pages** help inspect crawl findings. **Visibility**, **Rankings**, and **AI Traffic** answer different measurement questions. **Questions** and **Content** support research and drafting. **Fixes** contains supported proposed changes.

An audit score is an assessment of what was checked, not a promise of search rankings. A mention in a measured answer and a visit from an AI referral are different observations. Read coverage and collection periods before comparing them.

## Review before publishing

Inspect any proposed fix or content against your website and business facts. Confirm the supported publishing action only after its scope is clear. A draft or recommendation does not prove that your website changed.

## Resolve unavailable data

An unverified site needs ownership proof. An add-on refusal needs the displayed entitlement path. A missing search property or analytics connection needs the correct source, not a guessed result. If the product says the add-on is not on sale yet, registering the site does not activate paid analysis.

If an audit failed, inspect its error and retry the offered read or run. Keep the domain and run reference if you [contact support](/help/contact).

For visitor-event tracking rather than organic analysis, use [Websites](/websites/install).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.