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

# Snapshots

> Weekly automated re-runs of the full audit pipeline. Track how your content and technical scores change as you implement recommendations.

A **snapshot** is a complete re-run of the audit pipeline for every URL in your project: fresh crawl, fresh AI responses, fresh analysis. Snapshots are what make zued a measurement tool, not just a one-time audit.

## What happens in each snapshot

1. **Re-crawl** — every URL is fetched fresh with a real browser
2. **Re-chunk** — page content is re-segmented and re-processed
3. **Re-dispatch** — all prompts are sent to AI engines again, 10 times per engine (fresh responses)
4. **Re-analyze** — alignment and technical scores are recalculated against the fresh content

**Prompts are never regenerated.** The same prompts run every week. This is what makes the trend line meaningful — you're measuring the same thing each time.

## What you can track

* **Alignment Score** per URL over time — did a content update move the needle?
* **Technical Score** changes — did fixing a `robots.txt` issue resolve the bot accessibility problem?
* **Quick Wins resolved** — which recommendations have been actioned, and did scores improve?
* **Visibility trends** — Share of Voice and Citation Share over time

## Snapshot history

Your trend lines and per-URL scores are kept long-term, so week-over-week comparisons stay intact. The full underlying detail for older snapshots — the individual AI responses and their analyses — is eventually pruned once a snapshot ages out of the retention window.