Version History & Diffs

Track owned content changes across DevTune domain crawls with a visual page version timeline and side-by-side diff comparison between any two crawl snapshots.

DevTune keeps a fast latest copy of each crawled page, then saves historical snapshots when a page is first observed or when a crawl detects a material content change. The History tab in Owned Content shows those snapshots as a visual timeline and lets you compare versions side-by-side.

Version Timeline

Select a page in the sitemap tree, then click the History tab to see its version timeline.

Timeline Layout

Versions appear in a vertical timeline ordered from newest to oldest. Each version shows:

Element	Description
Date and time	When this version was crawled
Word count	Total words in the page at this point in time
Change indicator	Whether content changed from the previous version
Latest badge	Marks the most recent version

Change Indicators

The timeline uses visual cues to show what changed between consecutive versions:

• Green arrow up with a positive number - Content was added (word count increased)
• Red arrow down with a negative number - Content was removed (word count decreased)
• Blue equals with “structure changed” - The content hash changed but the word count stayed the same, indicating structural changes like reformatted headings or reordered sections
• “no changes” in muted text - Reserved for snapshots with matching content hashes

Node Markers

Timeline nodes use different visual styles:

• Solid primary dot - The latest (most recent) version
• Smaller primary dot - A version where content changed from the prior crawl
• Hollow circle - A version with no content changes

Single Version

If only one version exists, the timeline shows the baseline snapshot. This can mean the page has only been crawled once, or that later crawls did not produce a material content change.

Comparing Versions

Each version in the timeline (except the oldest) has a Compare with previous button. Clicking it opens a full-screen dialog with a side-by-side diff.

Diff Viewer

The diff dialog shows:

• Stats bar at the top with lines added (green), lines removed (red), and net word count change
• Side-by-side diff powered by a code-diff renderer, with added lines highlighted in green and removed lines highlighted in red
• File labels showing the page URL and the date of each version

The diff viewer treats page content as markdown text. It highlights line-level additions and removals, making it straightforward to see exactly what changed between two crawls.

Reading the Diff

• Green highlighted lines are content that was added in the newer version
• Red highlighted lines are content that was removed from the older version
• Unchanged lines provide context around the changes

The stats bar provides a quick summary:

Stat	Meaning
+N (green)	Number of lines added
-N (red)	Number of lines removed
+N words or -N words	Net change in word count

Use Cases

Tracking Content Updates

After updating pages on your website, run a new domain crawl and check Owned Content to verify the changes were captured correctly. The diff viewer confirms exactly what AI platforms will see in the updated content.

Monitoring Competitor Content Changes

If your domain crawl configuration includes competitor domains, use the version timeline to track how their content evolves over time. Word count trends and change frequency reveal how actively a competitor maintains their content.

Identifying Unintended Changes

Sometimes website deployments introduce unintended content changes (broken formatting, stripped sections, duplicated text). The diff viewer helps you spot these issues by comparing the pre-deployment and post-deployment crawl snapshots.

Auditing Content Freshness

The version timeline shows the crawl date for each snapshot. Pages that have not changed across multiple crawls may need updates. Sort the tree by relevance or bot traffic to prioritize which stale pages to refresh first.

How Versions Work

What Creates a New Version

DevTune does not store a full duplicate version for every crawl. A new history snapshot is created when:

• The page is first observed
• The extracted page content changes enough to pass material-change filtering

Crawls that see the same content, or only minor extraction drift, update the latest page state without adding noise to the version timeline.

Content Hash

DevTune computes a content hash for each crawled page body. Hash differences are then checked against a materiality filter so small crawler or rendering differences do not automatically become visible page changes. Two snapshots can have the same word count but different hashes if text was reworded without changing length.

Data Retention

Material page snapshots are retained for history and diffing. The current page row remains optimized for fast browsing, while historical content is kept separately so the Owned Content list does not scan large version history.

Troubleshooting

No History Available

If the History tab shows “No version history available,” the page may not have version data associated with it. This can happen if:

• The page was crawled before snapshot history was available and has not been backfilled
• There was a data issue during the crawl

Only One Version

A single baseline version is normal when later crawls have not detected a material content change.

Diff Shows Unexpected Changes

If the diff shows large-scale changes that do not match your actual content edits, the cause is usually:

• Rendering differences - Dynamic content (dates, personalized elements) changes on every crawl
• JavaScript loading variations - Single-page app content may render slightly differently between crawls
• Third-party embeds - Embedded widgets and ads can inject different content each time

Next Steps

• Browsing Content - Navigate the tree and view page details
• Owned Content Overview - Understand the feature and how it fits into DevTune
• AI Traffic - Track AI bot and referral traffic across your site