Skip to main content

Web Search enrichment

Web Search enrichment uses publicly available online information to help populate structured product attributes in SKULaunch.

S
Written by SKULaunch Support
Updated over 4 months ago

Web Search enrichment uses publicly available online information to help populate structured product attributes in SKULaunch.

It works by searching the web using the product details you already have, then extracting relevant values for the attributes you’ve selected.

This agent is designed for data enrichment, not content generation.

When to use Web Search enrichment

Web Search enrichment is a good choice when:
• The product has a clear brand and model
• Information is publicly available online
• Official product pages or listings exist

It works best for well documented products with consistent naming.

What Web Search enrichment is good at

Web Search enrichment is commonly used to populate:
• Product type or classification confirmation
• Core specifications
• Materials and features
• Common dimensions or ratings

It is especially useful early in enrichment, when filling missing core data.

What it is not good at

Web Search enrichment should be avoided when:
• Product information is private or restricted
• Data only exists in PDFs or images
• Specifications are highly technical or inconsistent
• Products are poorly named or generic

In these cases, another enrichment agent will be more effective.

What Web Search enrichment uses as input

This agent relies on the information already on the product, such as:
• Product name
• Brand
• Manufacturer part number
• Existing identifiers

The clearer this information is, the better the results will be.

How results should be treated

Values returned by Web Search enrichment are:
• Suggestions, not final values
• Always reviewable and editable
• Intended to speed up enrichment, not automate decisions

You should review and approve enriched values before publishing or exporting.

Tips for better results

• Ensure products are classified into the correct family first
• Enrich a small set of attributes at a time
• Start with mandatory or high impact attributes
• Avoid running Web Search enrichment on poorly defined products

Did this answer your question?