Discover website images and rendered sections inside the exact root domain, subdomain, or product folder provided, with source provenance and approval before reuse.
A manual discovery run is deliberately rate-limited and reports progress, additions, unchanged items, captures, and failures.
Website asset discovery is a bounded, asynchronous workflow that stays inside the root domain, subdomain, or product folder the customer provides. It prioritizes product, pricing, feature, and integration pages, then can use documentation, changelog, other first-party pages, or bounded trust pages when the useful visual library remains short. Blogged can recognize sections in semantic and modern component-based layouts, normalizes accepted visuals to WebP, records provenance and fingerprints, and places discovered items in a private review queue.
Each control keeps the difference between discovery, eligibility, exact placement, and generation context visible.
A bounded crawl stays inside the exact website scope provided and evaluates first-party pages rather than treating the entire web as an asset source.
Rendered public sections from semantic or div-based component layouts are stored with page type, capture kind, viewport, timestamp, and renderer provenance.
Content hashes, source records, and last-seen timestamps keep repeat discovery useful without filling the library with silent duplicates.
Only authorized workspace roles can start discovery, every run is tied to the active site, and a cooldown prevents accidental repeat work.
The workflow preserves site scope, provenance, eligibility, and editorial control instead of turning every image into automatic generation context.
Blogged validates the configured site, creates a site-scoped run, and queues the bounded discovery work.
Useful files and rendered sections become WebP assets with dimensions, source evidence, content hashes, and run-level progress.
New candidates enter Needs review, where the team can correct metadata, approve, bulk-approve, or discard them.
Discovery reduces manual hunting, but it deliberately stops before reuse. Public availability does not prove that a visual is useful, current, accessible, or appropriate for a specific article; the workspace review decision remains required.
Clear answers about discovery, approval, provenance, privacy, placement, and generation boundaries.
No. Discovery uses bounded page, attempt, and accepted-asset budgets. It is designed to build a useful review queue, not create an unlimited mirror of the site.
A website image is a file found in page markup. A website capture is a rendered public page section. Captures retain their page and renderer provenance and are not mislabeled as native product UI.
Blogged fingerprints normalized content and records source relationships. An unchanged fingerprint refreshes last-seen evidence instead of creating another asset, while changed source content can preserve a supersession link.
No. Discovered files and captures enter a pending-review state. They become eligible for normal reuse only after an authorized workspace member approves them.
Manage a private SaaS product asset library with review queues, visible approvals, undo, bulk decisions, alt text, provenance, and safe archiving.
Explore workflowUse approved SaaS product screenshots and diagrams in valid article sections, with high-confidence recommendations, preview control, and stable post copies.
Explore workflowGuide SaaS article-image generation with up to three approved visual references, site-scoped eligibility checks, exact logo compositing, and provenance.
Explore workflowBuild the library, approve what is actually useful, and choose exact placement or reference-guided generation based on the evidence the article needs.