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

# Owned Content Overview

> Browse your crawled site tree, inspect page details, compare versions between crawls, and see which pages AI bots crawl and reference most often.

Owned Content is the workspace for reviewing your crawled site footprint. Its main interface, Content Explorer, organizes pages into a searchable sitemap tree, shows rendered page content, tracks version history across crawls, surfaces AI traffic data per page, and reports technical AEO health for your primary domains.

## What Owned Content Answers

Owned Content helps answer three practical questions:

1. **What content do AI platforms actually see on my website?**
2. **What changed between crawls?**
3. **Which pages get the most AI bot attention or AI referral traffic?**
4. **Are there technical crawlability issues that could stop answer engines from using my content?**

## Why Content Explorer Matters

### See your site through AI eyes

The rendered markdown that Content Explorer displays is the content extracted from your site for crawler-oriented analysis. Reviewing this content helps you:

* Spot rendering or extraction issues
* Audit content quality and structure
* Understand what AI systems are likely to consume

### Connect content to traffic

Owned Content pairs page content with AI traffic signals so you can see whether the pages getting crawled or cited are also the pages getting visited.

### Monitor material change over time

Owned Content keeps the latest crawled page fast to browse, and stores history snapshots when a page is first observed or when a later crawl detects a material content change. This keeps the timeline focused on meaningful changes instead of duplicate crawl records.

### Audit technical AEO health

The AEO health report checks whether AI crawlers and answer engines can discover, fetch, extract, and understand your primary brand domains. It combines existing crawl data with lightweight live checks for crawler access, sitemaps, homepage HTML, metadata, sitemap freshness, markdown extraction, and optional `llms.txt` guidance.

Each domain gets its own score, findings, affected URLs where available, remediation advice, and copyable agent prompts for website-scoped fixes.

## Layout

The main Content Explorer interface uses a two-pane workspace:

### Explorer pane

The left pane shows a collapsible sitemap tree organized by domain and path. It includes:

* Search / filter
* Sorting by **Path**, **Bot traffic**, **Referrals**, **Relevance**, or **Words**
* Page-level traffic badges

### Details pane

The right pane shows the selected page and its metadata, then lets you switch between:

| Tab         | What It Shows                                                              |
| ----------- | -------------------------------------------------------------------------- |
| **Content** | Rendered markdown content with headings, lists, code blocks, and structure |
| **History** | Version timeline showing baseline and material content-change snapshots    |
| **Traffic** | AI bot crawl and AI referral context for the selected page                 |

## How It Works

1. You configure the relevant owned domains and project setup
2. DevTune crawls the website and extracts markdown content from each page
3. Content Explorer builds a sitemap tree from the crawled pages
4. DevTune runs technical AEO checks after crawls and on a regular refresh schedule
5. Each page can then be inspected for content, history, traffic context, and related AEO findings

## Prerequisites

Owned Content requires crawled domain data. If no pages have been crawled yet, the page shows an empty state that points you back toward configuration and refresh.

## Getting Started

1. **[Browse Content](/content-explorer/browsing-content)** - Navigate the tree, search pages, and inspect page details
2. **[Technical AEO Audit](/content-explorer/aeo-audit)** - Understand scores, checks, findings, and remediation prompts
3. **[Version History](/content-explorer/version-history)** - Compare page versions and track changes

## Next Steps

* **[Browsing Content](/content-explorer/browsing-content)** - Learn how to navigate and search the sitemap tree
* **[Technical AEO Audit](/content-explorer/aeo-audit)** - Review crawler-readiness checks and remediation guidance
* **[Version History](/content-explorer/version-history)** - Understand the version timeline and diff viewer
* **[AI Traffic](/ai-traffic/overview)** - Track AI bot and referral traffic across your site