Weight, unit price and SEO in Eloshon Scraper

The Scraper does more than copy: for some columns, it works out a value from what the product page says, for example the total weight of a pack. This page tells you, column by column, what you will find there, and from which version.

In short

The weight, unit price and SEO columns appear in the Résultats (Results) tab of the extension's panel and in the exported CSV file. The specifications, documents and dimensions go into the job's products.json file, after ✓ Accepter (Accept), and that is where the Converter reads them.

The extension's panel only exists in French: the column names quoted here are the ones you will see on screen, with their meaning in English in brackets.

Poids (Weight) column

On a label, the weight is often written as a quantity: “4x90g” means 4 jars of 90 grams. From version 0.5.67, the column of a Poids field (role poids, or a field named “Poids”) shows the total weight of the pack. The format: “360 g” under one kilo, then “1 kg” or “1,5 kg”. After ✓ Accepter, the app understands weights written in these same ways for each product.

The product page says	The column shows
4x90g, 4 x 90 gr, 4x90 grammes, 90g x 4, 4 pots de 90 g	360 g
2x250g	500 g
6 x 4 x 125 g (a pack of packs)	3 kg
4+2 x 1L (the free units count)	6 kg
1L, 1 l, 1 litre, Litres : 1, 100 cl	1 kg: a litre counts as a kilo
75cl	750 g
1.000 g (a point to separate the thousands)	1 kg
½ kg, 1/2 kg	500 g
23pc, 36 stuks, 36 Stück, 12 pièces, lot de 4	empty: the weight of one piece is unknown (in every language from version 0.5.68)
300ml 12,34/l (a price per litre written right after it)	300 g: the price per litre is not taken for a weight
12,34/l on its own	empty
Taille M (no quantity)	the text as it is

Mesure (prix unitaire) and Prix unitaire columns (measure and unit price)

The unit price is the price per kilo, per litre or per piece: it helps you compare two packs of different sizes. From version 0.5.67, when a Poids column exists and at least one product has a price and a readable quantity, two columns are added, in the format that Google Merchant and Shopify expect:

Column	Examples
Mesure (prix unitaire)	“360 g”, “1 l”, “23 ct” (“ct” means piece: it is Google's unit)
Prix unitaire	“7.75 EUR/kg”, “1.98 EUR/l”, “0.48 EUR/ct”

A litre stays a litre here: a price per litre is never turned into a price per kilo. In the Converter, these two columns arrive as extra columns: by default, a metafield for Shopify, an attribute for WooCommerce, and the description for Wix and BigCommerce. You can change where they go at the column mapping step, in the Converter. They do not fill in the official unit price fields of Shopify or Google yet.

Titre SEO and Description SEO columns (SEO title and description)

Titre SEO is the title of the product page, the one in the <title> tag that shows in the browser tab. Description SEO is its description for search engines, the one in the meta description tag. They are copied exactly as the site writes them, and stay empty when the product page has none. They arrive after ✓ Accepter from version 0.5.70, and, on a site already learnt in the Fiche produit (Product page) tab, in the preview from 0.5.71. Only the 🔎 Analyser la page (Analyse the page) button suggests, when they are missing, the title and description used for sharing on social networks. The Converter cleans up these texts before the import: Eloshon Scraper files: weight, SEO, dimensions.

Specifications, documents and dimensions

From version 0.5.72, after ✓ Accepter, the job's products.json file receives:

The whole table of specifications. A product page that declares one or two specifications in its hidden data no longer stops its full table from being read.
The sections. The heading rows of a table, for example “Dimensions - Télécommande” (remote control), are kept as the section of the rows that follow them.
The documents. A row “Notice : PDF” (user manual) gives the address of the document, not the word “PDF”.
The product's dimensions. Those of a remote control or a controller are not taken for the product's own, when the row or the heading of its section names it. The centimetres the site writes next to the inches are kept; if they do not match the inches, the Converter flags it.
The order of the dimensions. Three numbers in a row, without saying which one is the length (“7.48 x 11.89 x 6.93 in.”), are kept in the order the site writes them, and the Converter flags it for WooCommerce and BigCommerce. Named rows (width, depth, height) are put in their place, with the depth used as the length.

Product pages read better, without pointing anything out

Product pages	Since	What changes
Badly written product data (JSON-LD)	0.5.70	A line break left as it is in the product's hidden data used to make the whole block unreadable: reference, barcode, brand, price. The block is now read.
JTL-Shop shops	0.5.70	Platform recognised. Its product pages are read through their product data; its options, with their price and their item number, are pointed out with 🎯.
BigCommerce shops	0.5.72	Reference (SKU), barcode (UPC) and the manufacturer's real reference read from the page's data; the reference is now the SKU, no longer the barcode; a missing weight is never written as 0; the collection is the most precise category path, without the shop's internal labels, and no longer shows the name of the product; names with quotation marks are decoded (for example 4").

All the platforms the Scraper can already read: Platforms and sites the Scraper already knows.

Limits

The panel has no screen to change the unit (kilos and pounds, gallons). The Converter then writes weights in grams for Shopify and in kilos for the other platforms, without knowing the unit set in your shop.
Dimensions drawn in an image are not read.
The barcode and the photo of each option, which some shops show on a separate page for each option, are not read.

Weight, unit price, SEO and dimensions: what the columns contain