Site Image Map

Relationship model

• Tracks page to image and image to pages relationships.
• Counts reuse across templates, product pages, and repeated banners.
• Keeps classification for content, logo, icon, background, preview, and product assets.

Async scope

• Designed for wider crawls that exceed a single synchronous request.
• Suitable for sitemap-driven discovery and later graph visualization.
• Natural fit for duplicate-asset analysis and change detection over time.

Site overview

• Pages crawled, unique images, relationship count, first seen, and last seen markers.
• High-frequency assets surfaced for navigation logos, banners, or repeated hero art.
• Duplicate candidates separated from truly shared canonical assets.

Views

• Image list with preview, URL, pages count, and usage context.
• Page view showing which assets appear on a specific URL.
• Graph-ready export for later visualization layers.

Large site redesigns where assets need to be traced back to owning templates or pages.

Migration projects that need a list of repeated images before moving media to a CDN.

Content audits that need to know where a given asset is used across a site.

Why is this an async job instead of an instant tool?

A true site image map usually needs multiple pages, deduplication, and relationship storage, which makes it a better fit for background processing.

Can it help identify duplicates with query strings?

Yes. One of the intended outputs is duplication insight around the same base asset appearing with unstable parameters.

Is a visual graph required for MVP?

No. A strong table view with exportable relationships is enough for the first useful version.