LeGuide: The French Market CSE Playbook

Q: What is the preferred feed format for LeGuide?

LeGuide supports both CSV and XML formats. CSV is often used for simplicity, while XML is recommended for catalogs with complex variant structures.

Q: Is an EAN code mandatory for LeGuide?

Technically optional for feed acceptance, but practically mandatory for performance. EANs enable product grouping, which is the primary way users find products on LeGuide.

Q: How do I track clicks from LeGuide?

The most effective way is by appending UTM parameters to your product URLs using transformation rules in a tool like 42feeds.

Q: Can I send multiple images for one product?

Yes, especially in XML format. Providing multiple high-quality images improves conversion rates by giving shoppers more visual information.

Q: Does LeGuide support international shipping from outside France?

Yes, but you must accurately map the shipping_cost and delivery_time attributes to ensure transparency and maintain customer trust.

LeGuide (part of Kelkoo Group) has been connecting French shoppers with products since 1998. That's staying power. But this mature market means competition is fierce.

Basic product lists won't win here. Here's how to dominate LeGuide. In this guide, we will explore the technical architecture of LeGuide.com product feeds, focusing on the engineering requirements and optimization strategies necessary to dominate the French CSE space.

The Strategic Importance of LeGuide in France

LeGuide.com serves as an umbrella for several regional brands, including Ciao and Dooyoo, providing merchants with a broad reach across France and beyond. In a market where consumers are highly research-oriented, being present on LeGuide isn't just about the immediate click; it's about being part of the technical "consideration set" during the buyer's journey.

A technically sound feed on LeGuide ensures your products are correctly categorized and searchable, allowing you to compete effectively against both local French giants and international retailers.

Technical Feed Architecture: Requirements and Standards

LeGuide.com accepts product data primarily through CSV or XML formats. While the platform is flexible, adhering to its specific field standards is non-negotiable for stable indexing.

Mandatory Attribute Breakdown

The following fields form the structural core of a LeGuide feed. Missing data in any of these will result in product rejection or significantly degraded search performance.

Attribute	Requirement	Technical Specification
`product_id`	Mandatory	A unique, persistent internal identifier (SKU). Max 50 chars.
`product_name`	Mandatory	The product title. Max 250 characters.
`product_description`	Mandatory	Full product description. Avoid excessive HTML; use plain text or CDATA.
`category`	Mandatory	Full category path (e.g., Maison > Mobilier > Canapés).
`product_url`	Mandatory	Direct link to the product page with tracking parameters.
`image_url`	Mandatory	Absolute URL to the primary product image (min 300x300px recommended).
`price`	Mandatory	Current selling price in EUR (numeric, use dot for decimal).

Recommended and Optional Attributes

To improve your ranking and provide a better user experience, the following technical identifiers and attributes should be mapped whenever possible:

ean (GTIN): The most critical technical identifier for grouping and price comparison.
brand: The manufacturer name. Critical for brand-specific searches.
mpn: Manufacturer Part Number, useful for technical product matching.
crossed_price: Used to show discounts and "sale" badges on the platform.
availability: Must be one of: in stock, out of stock, or preorder.
shipping_cost: Shipping price in EUR. Transparency here is a major conversion factor in France.
condition: One of: new, used, refurbished.

Advanced Optimization Strategies for LeGuide.com

1. Semantic Title Engineering

LeGuide's search algorithm is highly dependent on the product_name. In the French market, titles should be descriptive but avoid the "keyword stuffing" common in some other regions. French consumers appreciate clarity and technical precision.

Recommended Structure: [Marque] + [Modèle] + [Type de Produit] + [Attribut Clé (Taille/Couleur/Matière)]

Example: Weak: "Chaussures de running" Technical: "Nike Air Zoom Pegasus 39 - Chaussures de Course Homme - Bleu/Noir - Taille 42"

By including the specific model (Pegasus 39) and target audience (Homme), you capture higher-intent traffic from users who know exactly what they are looking for. Furthermore, ensure that the most important keywords appear in the first 50 characters, as LeGuide's mobile view may truncate longer titles.

2. Category Mapping and Taxonomy Alignment

LeGuide uses a proprietary taxonomy that is critical for how its "Shopping Guides" are structured. While you can submit your own categories, mapping your CMS categories to LeGuide's specific structure will significantly improve your products' discoverability.

Technical Tip: Use transformation rules to create a mapping table. For example, if your store uses "Home Office > Desks," map this to LeGuide's equivalent "Maison & Jardin > Bureau > Table de bureau." This ensures your products appear in the correct filters for size, material, and price range.

3. Leveraging the ,[object Object], for CTR

French consumers are highly responsive to promotions, particularly during the government-regulated "Soldes" (Sales periods). If you are running a discount, ensure both the current price and the original crossed_price are sent. LeGuide will use this data to display "X% OFF" badges, which can increase Click-Through Rate (CTR) by over 30% during peak shopping periods.

4. Image Quality and Composition

LeGuide is a visual engine. While it technically accepts images as small as 180x180px, you should aim for at least 800x800px on a pure white background. Avoid using lifestyle images as the primary thumbnail; keep those for the product page. Ensure the product occupies at least 85% of the image frame to maximize visibility in the grid view.

5. Managing Out-of-Stock Products

LeGuide does not update as fast as a real-time marketplace. If you leave out-of-stock products in your feed, you will continue to pay for clicks that result in a 404 or a "Product Unavailable" message. This not only wastes budget but also triggers LeGuide's quality penalty.

Technical Implementation: Data Mapping Examples

Domination on LeGuide requires more than a simple export. You must engineer the data to meet the platform's logic.

Scenario A: Clean Image Pipeline

LeGuide requires high-quality images without watermarks. Logic: FILTER [additional_images] -> SELECT [0] -> ENSURE [url] IS HTTPS -> MAP TO image_url

Scenario B: Dynamic Shipping Rules

Shipping costs often vary by weight or price in your CMS. Logic: IF [total_price] > 100 THEN MAP 0.00 TO shipping_cost ELSE MAP [default_shipping] TO shipping_cost

Scenario C: French Localization of Descriptions

If your source data is in English but you are targeting LeGuide.fr, you must provide French descriptions. Logic: MAP [description_fr] TO product_description (Ensuring no raw HTML breaks the CSV structure).

Technical Implementation with 42feeds

Managing a LeGuide feed manually, especially when dealing with currency conversions or category mapping, is a recipe for technical debt. 42feeds provides the infrastructure to automate this pipeline.

Step 1: Source Integration

Connect your e-commerce platform (Shopify, Shopware, Magento, etc.) to 42feeds. We import your raw product data into our normalized internal schema.

Step 2: Transformation and Validation

For LeGuide, we apply specific logic:

Character Encoding: We ensure all French special characters (é, à, ç, etc.) are correctly encoded in UTF-8 to prevent garbled text.
EAN Formatting: We validate that EANs are 13 digits and remove non-numeric characters.
Price Logic: We automatically handle the decimal separator requirements of the LeGuide platform.

Step 3: Automated Synchronization

Our system generates the final LeGuide export (CSV or XML) and hosts it at a persistent URL. You simply provide this URL to your LeGuide merchant representative.

Common Pitfalls and Troubleshooting

"Produits Non-Indexés" (Unindexed Products)

This usually occurs when the ean is missing or invalid. LeGuide relies heavily on GTINs to group products. Solution: Audit your source data for missing EANs and use 42feeds to fill gaps using supplemental data.

Category Mismatch

If your products are appearing in the "Others" or "Divers" category, your visibility will be near zero. Solution: Review your category mapping rules and ensure you are using at least 3 levels of hierarchy.

Price Inconsistency

LeGuide monitors merchant feeds for price accuracy. If the price in the feed doesn't match the landing page, your account may be suspended. Solution: Increase your update frequency in 42feeds to ensure your feed reflects your latest CMS changes.

Why Automation Matters for Regional CSEs

The French e-commerce landscape is famous for its seasonal "Soldes" (Sales). During these weeks, prices change rapidly. Manual feed management cannot keep up with the pace of the market. Automation allows you to:

Instant Updates: Reflect price drops in your feed minutes after they happen in your CMS.
Inventory Protection: Automatically remove products from LeGuide when they go out of stock to avoid paying for dead clicks.
Rule-Based Titles: Dynamically append "Promo" or "Nouveauté" to your product titles based on internal tags.

Conclusion: Dominating LeGuide and Beyond

Success on LeGuide.com is a direct result of technical data quality. By providing a clean, EAN-rich, and correctly categorized feed, you position your brand as a reliable player in the French market.

Ready to scale your French e-commerce operations? Tools like 42feeds simplify the complexity of regional feed management, allowing you to focus on strategy while we handle the technical delivery.

Expanding Your European Reach

Once your LeGuide feed is optimized, you are well-positioned to expand into other European markets. The same high-quality data used for LeGuide can be easily adapted for Idealo.de in Germany, Trovaprezzi.it in Italy, or PriceSpy in the UK and Nordics.

Frequently Asked Questions (FAQ)

1. What is the preferred feed format for LeGuide?

LeGuide accepts both CSV and XML. For most merchants, CSV is easier to debug, but XML is better for handling complex product variants and hierarchical attributes.

2. Is an EAN code mandatory for LeGuide?

While the feed might be accepted without EANs, your products will suffer from poor visibility. EANs are the primary identifier LeGuide uses for product grouping and comparison.

3. How do I track clicks from LeGuide?

You should append UTM parameters to your product_url (e.g., ?utm_source=leguide&utm_medium=cse). You can automate this in 42feeds using our URL transformation rules.

4. Can I send multiple images for one product?

Yes, LeGuide's XML format supports multiple images. While only the primary image_url is mandatory, providing additional images can improve the user experience on the product detail page.

5. Does LeGuide support international shipping from outside France?

Yes, but you must clearly state the shipping costs and delivery times in your feed. French consumers have high expectations for delivery speed, so transparency is key.