Skip to main content
Sometimes the data you want is on a website, not in a feed: a supplier’s catalog, your own store on another platform, or a reference range you want to match. The WISEPIM browser extension imports those products straight from the page you have open. It reads the name, SKU, brand, price, images, specifications, variants and FAQs, and sends them to the project you pick. There is no file to prepare and no API to connect. What acting on it enables: onboard a supplier or an existing storefront in minutes instead of asking for a feed, and bring products into WISEPIM where you can enrich, translate, and publish them. Where to find it: Import on the Products page > From a website or URL > Configure the browser extension. The extension page is also listed under Integrations. The From a website or URL step of the import dialog, pointing to the browser extension with Configure the browser extension and How it works The From a website or URL step of the import dialog, pointing to the browser extension with Configure the browser extension and How it works
The old URL import, where you pasted a category page, sitemap or list of URLs and a WISEPIM server crawled the site, is retired. The browser extension replaces it. Saved URL import profiles and automation import steps that used it no longer run. XML feed imports through Feed Hub are not affected.

​
Connect the extension

The extension works in Chrome, Edge and Firefox. You connect each browser once, for your whole account.
1

Install the extension

On the Connect this browser page, choose Add to Chrome, Add to Edge or Add to Firefox. Then click I’ve installed it.
2

Connect this browser

Click Connect this browser. WISEPIM shows “Paired as” with your email. The browser appears under Connected browsers with All projects and when it was last used.
3

Pick the project when you import

The extension asks which project to import into each time. One connected browser can import into any project you have access to.
Connecting creates a key for this browser only, scoped to your account. The key is never shown, the extension never sees your password, and Disconnect stops it immediately. You can have up to 20 connected browsers. A browser connected before pairing became account-wide shows “Legacy: paired to one project”. Click Reconnect to import into any project.

​
Import products from a page

1

Open the page

Open a product page, or a category or search page with several products, in your browser.
2

Open the extension

The popup shows the products it found, with a project switcher at the top. On a listing page, load more products as you go. If the extension can’t recognize a product, it offers Import this page as a product.
3

Choose the options

Read in browser (on by default) sends the page as your browser loaded it. Enrich runs the steps from Import by Scraping Settings on this import. Your Enrich choice is remembered.
4

Import

Select the products and import them. The import runs in the background. Follow it in the Process Tracker.

​
What the extension reads

  • Shop data first. On Shopify, WooCommerce, Magento 2, Lightspeed eCom, Squarespace, Shopware 6, BigCommerce, Wix Stores, PrestaShop 1.7 and higher and Shoplazza, WISEPIM reads the shop’s own product data where the shop publishes it. You get the full description, all variants and all images, without AI. A Shopify collection or WooCommerce category page imports from the shop’s product list.
  • Structured data and AI. On other sites WISEPIM reads the page’s structured data and uses AI only for what is still missing. The AI answer for an unchanged page is reused for 14 days, so importing the same page again costs no AI usage.
  • Specifications in tabs. Specs inside tabs, accordions and drawers are read as attributes.
  • FAQs. A page’s FAQ section becomes the product’s FAQs, up to 50 questions. That includes FAQ markup and visible FAQ headings, tabs and accordions in English, Dutch, German, French and Spanish. The FAQ block is removed from the description, and importing the page again doesn’t add the same questions twice.
  • Same product, same SKU. A page you imported before under another SKU updates that product instead of creating a copy.
What happens to specs and breadcrumbs that don’t match your data model depends on the Data model switches in Import by Scraping Settings. The import report lists what was left out and which setting caused it.

​
Limits

​
When a site blocks automated access

Some webshops sit behind bot protection, such as Cloudflare or DataDome. Because the extension sends the page your own browser already loaded, that protection doesn’t apply. When WISEPIM has to fetch a page itself, for example a page too large to send, and the site answers with a block (403, 429, 503, a bot wall or a challenge), WISEPIM tries once more through a residential connection in the site’s own country. It never retries a page that doesn’t exist (404 or 410), a page robots.txt excludes, or an address that isn’t public. When the fetch still fails, the import names the cause, for example the bot protection vendor, a login or age gate, a timeout or a page that only works with JavaScript. A blocked or “not found” page is never imported as a product.
You can’t import pages of WISEPIM itself.

​
Classify scraped products automatically

If your project has adopted classification standards, imported products can file themselves into them. Configure this under Settings > Import by Scraping, in the Classification section:
  • Assign families from ETIM (on by default): a product that matches one of your adopted ETIM classes gets that class’s family, with all its attributes, the moment it lands.
  • Match categories to GS1 GPC (on by default): scraped breadcrumbs land in your adopted GPC categories instead of creating a duplicate tree next to them.
  • Adopt missing classes during import (off by default): when a product clearly matches a class or category you haven’t adopted yet, adopt it on the spot. Creating ETIM attributes also needs Create missing attributes, and new GPC categories need Create missing categories.
Classification is free and structural. It costs no credits, runs before the enrichment chain below, and does nothing until you’ve adopted at least one standard.
The family assigned here decides which attributes the enrichment chain can fill. Adopt your ETIM classes first, and a scraped product arrives with the standard’s attribute slots ready for web research and enrichment to complete.

​
Enrich scraped products automatically

A product page rarely carries everything you want. WISEPIM can close that gap the moment an import finishes, without you selecting anything. WISEPIM import by scraping settings with project language and trusted website setup links, web research and Bulk Enrich WISEPIM import by scraping settings with project language and trusted website setup links, web research and Bulk Enrich Go to Settings > Import by Scraping and turn on Enrich scraped products automatically. It runs in order on every import the extension brings in:
  1. Web research gathers facts about each product from the web. Researching every import needs the Pro plan or higher. Without it you can still run web research by hand from the products table.
  2. Bulk Enrich writes the fields you choose: descriptions, short descriptions, titles, SEO title and meta, and attributes. Each field uses your project’s default prompt unless you pick a different one.
Switch off Enrich in the extension to skip the chain for a single import. Useful when you grab one product just to look at it and don’t want to spend credits enriching it.

​
Act on what you find

Open a single product page instead of a listing, or use Import this page as a product. Outcome: the page still lands as a product, and you can fix any gaps afterwards.
Check the import report in the Process Tracker. When it says creating attributes or categories is off, switch on Create missing attributes or Create missing categories in Import by Scraping Settings and import the page again. Outcome: the specs land as attributes instead of being dropped.
Some sites bury data in scripts or images. Fill the gaps with Enriching Products with AI or turn on the enrichment chain. Outcome: a complete catalog even when the source page was thin.
If the supplier can give you an XML or CSV feed, prefer Feed Hub or a file import for repeated updates. Use the extension when no feed is available. Outcome: the right tool for each source.

​
How it compares

Import by Scraping Settings

Decide what runs after every extension import.

Importing Products

File and platform imports when you have structured data.

Feed Hub

Import from and publish to XML and feed sources.

Web Research

Research products on the web to enrich what you already have.