What is the Snapshot Asset Test?

A DataJelly Edge support tool that validates whether Snapshot asset references resolve and return usable HTTP status codes.

Why does DataJelly use a base href tag in Snapshot HTML?

It ensures relative asset paths resolve to the correct customer origin in bot-facing static Snapshot HTML.

Why do assets work in my app but fail in the Snapshot?

Runtime app context may differ from static Snapshot delivery, causing relative paths to resolve against the wrong origin.

When should DataJelly Edge customers run this test?

After enabling Edge, after migrations, and after deploys that change asset paths or filenames.

Snapshot Asset Test

Verify DataJelly Snapshot Asset Resolution

Snapshot Asset Test verifies that images, stylesheets, videos, and other resources inside a DataJelly Snapshot resolve correctly after the Snapshot is served as static HTML to search bots and AI crawlers. It checks Snapshot HTML, base href tag behavior, relative asset paths, resolved asset URLs, HTTP status, and broken vs working assets.

Asset Guide

Verify Snapshot asset resolution

A Snapshot can contain correct text but still look broken when CSS, images, or media resolve to the wrong origin. Relative asset paths often fail in bot-facing HTML without a valid base href. This test is used for snapshot QA after setup or migration.

What this tool does

Fetches the DataJelly Snapshot for a domain
Extracts asset references from Snapshot HTML
Resolves relative paths using the Snapshot base URL
Checks whether each resolved asset returns usable HTTP status
Reports Type, Raw Path, Resolved URL, and Status
Detects missing base href tag

How to use for DataJelly Edge setup

Test the domain after enabling DataJelly Edge
Confirm the Snapshot includes a base href tag
Check that CSS resolves from the customer domain
Check that images and media return 200
Find broken relative paths before bots see the Snapshot
Re-test after moving hosting providers or changing asset paths

Common problems this catches

Missing base href tag
CSS resolves against the wrong origin
Images return 404 inside the Snapshot
Asset paths work in the live app but fail in the static Snapshot
Vite or React assets use relative paths that need base URL correction
Old hashed asset filenames after a deploy
CDN paths blocked or unavailable to bots
Snapshot HTML is valid but visually unstyled
Social preview image or hero image fails to load

How to read the results

Total Assets:: number of asset references found in Snapshot HTML.
Working:: assets returning usable HTTP status.
Broken:: assets returning 4xx/5xx, timeout, or failed resolution.
Base Tag:: whether Snapshot includes base href for relative-path resolution.
Raw Path:: path found in Snapshot.
Resolved URL:: destination after base-tag resolution.
Status:: HTTP status returned by resolved asset.

Recommended workflow

1Enter the customer domain
2Check whether the Snapshot has a base href tag
3Review broken assets first
4Confirm the resolved URL points to the expected customer domain or asset CDN
5Open failed asset URLs directly
6Fix missing base href, wrong asset path, stale build output, or blocked CDN access
7Re-run the Snapshot Asset Test
8Use HTTP Bot Comparison or Visibility Test to verify full bot-facing output