Skip to main content
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, and surfaces AI traffic data per page.

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?

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 change over time

Every crawl creates another point in the page’s history, making it possible to see what changed and when.

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:
TabWhat It Shows
ContentRendered markdown content with headings, lists, code blocks, and structure
HistoryVersion timeline showing every crawl snapshot and content diff entry
TrafficAI 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. Each page can then be inspected for content, history, and traffic context

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 - Navigate the tree, search pages, and inspect page details
  2. Version History - Compare page versions and track changes

Next Steps