93 results found

1. Better deletion of customers in admin: after opens a customer a delete button is needed

   Currently, only in the customer overview, while selecting the three dots you can delete the customer.

   The problem: if you search customer by exact name or mail address it is not possible to highlight the customer in the overview so can't easily delete the customer account. If you have many customers and some requests to delete the account, there is a problem (time consuming) the finish this task.

   So please add the function to delete the customer account after open the customer account.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable app extensions to use advanced prices for precomputation

   Currently, it's not possible to use advanced prices in apps for purposes such as indexing and displaying them in the storefront, e.g. in an app that provides a custom search. The reason is that the app doesn't know the applicable rules, e.g. the rule can change while browsing.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Native Multi-Vendor Marketplace Engine + Next.js Headless Support

   Shopware 6 is excellent for single-vendor eCommerce, but it lacks core features required to build true multi-vendor marketplaces like Amazon, Etsy, or Alibaba. I propose a Marketplace Engine as a core module or premium extension with:

   Vendor Accounts: Sellers can register and manage their own products, orders, and store settings from a dedicated dashboard.

   Split Payments & Commissions: Automated payment distribution using Stripe Connect, PayPal Payouts, etc., with platform-level commission control.

   Product & Seller Reviews: Customer reviews for products and vendors with moderation workflows, boosting trust and SEO.

   Search Personalization: Intelligent search with vendor filters, ratings, and behavior-based ranking. Ideal for large catalogs and vendor competition.

   Additionally, I recommend official Next.js storefront support for better performance (SSG/ISR), React developer adoption, and edge rendering via Vercel. While Shopware PWA is great, Next.js would accelerate frontend development and modernize the developer experience.

   Use Cases:

   A retailer wants to build a regional platform where independent artisans can sell directly to consumers, with the platform managing logistics, payments, and reviews.

   An eCommerce enterprise needs a scalable platform for thousands of vendors offering competitive pricing, search-filtered by seller, and user-driven trust signals.

   These features would position Shopware as a strong alternative to Magento or Shopify Plus for multi-vendor businesses and open doors to large-scale SaaS and marketplace use cases.

   Shopware 6 is excellent for single-vendor eCommerce, but it lacks core features required to build true multi-vendor marketplaces like Amazon, Etsy, or Alibaba. I propose a Marketplace Engine as a core module or premium extension with:

   Vendor Accounts: Sellers can register and manage their own products, orders, and store settings from a dedicated dashboard.

   Split Payments & Commissions: Automated payment distribution using Stripe Connect, PayPal Payouts, etc., with platform-level commission control.

   Product & Seller Reviews: Customer reviews for products and vendors with moderation workflows, boosting trust and SEO.

   Search Personalization: Intelligent search with vendor filters, ratings, and behavior-based ranking. Ideal… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  B2B  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Migration: Automatic placeholders for missing values

   Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.

   For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.

   To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.

   Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration that many customers experience during a migration.

   Customer migrations are tedious and involve a lot of work, as data records are often not transferred to Shopware 6 because they are missing from Shopware 5.

   For example, if the salutation of a customer is not filled in Shopware 5, but the field has become a mandatory field in Shopware 6. Or the first name.

   To make migrations much easier, the migration wizard should store a meaningful placeholder in such cases so that the data is transferred correctly.

   Within Shopware 6, you can then search for these placeholders and adjust the entries. This takes away the frustration that many… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Migration & Im-/Export  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. B2B Suite - Make orders more visual

   Already placed orders should be able to be filtered by products as well. A list of all products that also shows the product with a picture makes repeat ordering easier than having to search for the desired product from an old order.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   DECLINED  ·  0 comments  ·  B2B  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Whitelist-Based Cache Key Handling for URL Parameters

   Currently, Shopware allows excluding certain URL parameters from the cache key to save storage. However, this exclusion list keeps growing, making maintenance cumbersome. Instead of excluding parameters, a whitelist approach could offer more control and efficiency.

   Analysis:

   I tracked URL parameters in a default Shopware installation—from listing to PDP, filtering, and placing an order. These 19 parameters were captured (more possible):
   cluster, keys, language, limit, locale, manufacturer, max-price, min-price, no-aggregations, order, orderId, p, paid, properties, rating, redirected, slots, timezone, search

   Instead of maintaining an ever-growing exclusion list, switching to an allowlist approach would ensure that only essential parameters impact the cache key.

   Proposed Solution:

   • Allowlist Configuration – Define a clear set of parameters that should be part of the cache key instead of excluding specific ones.
   • Event for developers – Introduce an event to allow developers to modify the allowlist dynamically.
   • Control by config – Provide a config option to adjust the allowlist as needed.

   This approach simplifies maintenance, optimizes cache storage, and ensures that only relevant parameters affect cache variations. 🚀

   https://github.com/shopware/shopware/blob/d8e5f78c01ed7c349993d116e37611ac3494ad05/src/Core/Framework/Resources/config/packages/shopware.yaml#L19

   Currently, Shopware allows excluding certain URL parameters from the cache key to save storage. However, this exclusion list keeps growing, making maintenance cumbersome. Instead of excluding parameters, a whitelist approach could offer more control and efficiency.

   Analysis:

   I tracked URL parameters in a default Shopware installation—from listing to PDP, filtering, and placing an order. These 19 parameters were captured (more possible):
   cluster, keys, language, limit, locale, manufacturer, max-price, min-price, no-aggregations, order, orderId, p, paid, properties, rating, redirected, slots, timezone, search

   Instead of maintaining an ever-growing exclusion list, switching to an allowlist approach would ensure that only essential parameters impact the… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. More possibilities for SEO

   The basic approach and usability are quite good, but it fails in details that have a big impact:
   - Files are made visible along with ID in the URLs, this provides dead links when files are updated. We provide datasheets that are kept up to date. Currently we have 2,000 dead links and had to have the URL adjusted ourselves.
   - With reference to point 1: There is no tool for redirects.
   - The ID issue also exists with images.
   - The image files are too large due to the zoom on the product detail page, unless you use webp as the format.
   - The technical SEO still has a lot of play: pages in different languages are often not recognized as separate pages, load times are too large, etc.
   - Canonical tags are not always recognized by search engines
   - You can't deindex pages in the backend (e.g. notepad, shopping cart, or pages behind the login), this must always be done via htaccess. Here, however, usually only the agency has access
   - Not all pages of the store can be accessed and managed, e.g. notepad.
   - URLs for products are taken over on the basis of the name, but should be written exclusively in lower case.
   - A blog is still on the roadmap

   The basic approach and usability are quite good, but it fails in details that have a big impact:
   - Files are made visible along with ID in the URLs, this provides dead links when files are updated. We provide datasheets that are kept up to date. Currently we have 2,000 dead links and had to have the URL adjusted ourselves.
   - With reference to point 1: There is no tool for redirects.
   - The ID issue also exists with images.
   - The image files are too large due to the zoom on the product detail page, unless you use webp… more

   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  SEO  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. New rules for rule builder based on products searches and sold

   Permit to use the rule builder to define a dynamic group of products based on the YTD sold or on the most searched products. This will help creating Cross-Sell and Up-sell dynamic groups with the most interesting products automatically

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Products, Prices & Properties  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Change product detail page layout for more than 25 items

   EN
   
   If a separate layout has been designed for some products, for example because these products have a special property for which there should be an explanation, then I can select the products under Content > Experience worlds > Layout assignment > Assign layout. However, the selection list is limited to 25 elements. To do this, we have added a filter to filter the selection for additional products. However, this only works as long as the search terms are different.

   If I have 80 products with, for example, ‘variant’ in the name, I can only select 25, after which further products could only be selected if there was another unique criteria with which further products could be selected. The only other alternative is to select each product individually and then change the layout manually.

   It is not possible to link the products to the layout via a dynamic product group and it is also not possible to set a new layout in the additional change.

   DE
   
   Wenn für einige Produkte ein eigenes Layout entworfen wurde, beispielsweise weil diese Produkte eine spezielle Eigenschaft haben, zur der es eine Erläuterung geben soll, dann kann ich unter Inhalte > Erlebniswelten > Layout-Zuweisung > Layout zuweisen die Produkte auswählen. Jedoch ist die Auswahlliste auf 25 Elemente beschränkt. Dafür haben wir den Filter eingebaut, mit dem die Auswahl auf weitere Produkte gefiltert wird. Das funktioniert aber nur so lange, wie die Suchbegriffe unterschiedlich ausfallen.

   Haben ich 80 Produkte mit zum Beispiel "Variante" im Namen kann ich nur 25 auswählen, danach gingen weitere nur noch, wenn es ein weiteres eindeutiges Kriterium gäbe, mit dem weitere Produkte ausgewählt werden können. Die einzige andere Alternative jedes Produkt einzeln auszuwählen und dann das Layout manuell zu ändern.

   Es ist nicht möglich die Produkte über eine Dynamische Produktgruppe mit dem Layout zu verbinden und auch in der Mehränderung kann kein neues Layout gesetzt werden.

   EN
   
   If a separate layout has been designed for some products, for example because these products have a special property for which there should be an explanation, then I can select the products under Content > Experience worlds > Layout assignment > Assign layout. However, the selection list is limited to 25 elements. To do this, we have added a filter to filter the selection for additional products. However, this only works as long as the search terms are different.

   If I have 80 products with, for example, ‘variant’ in the name, I can only select 25, after which… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  User Experience  ·  Delete…  ·  Admin →
   How important is this to you?

   Nice to have You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Zusätzliche Spalte und Kommentarfeld bei SW6 Backend Bestellungen I Additional column and comment field for SW6 backend orders

    Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.

    In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.

    Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen, da die Datenbank dann scheinbar nach einem nichtvorhandenen Eintrag sucht und die Eingabe nicht abgeschlossen werden kann.

    Gibt es dafür eine Lösung?

    Ebenfalls fehlt in dieser Ebene der Backend Bestellung noch ein Kommentarfeld, z.B. für Kundeninterne Nummern, Export-Angaben, etc… In SW5 gab es dafür die Freitextfelder.

    Das Kommentarfeld steht erst im nächsten Schritt zur Verfügung. Um dahin zu gelangen, muss man die Bestellung speichern, woraufhin jedoch schon die Bestellbestätigung versendet wird. Auf der man eben gern noch ein paar Angaben gemacht hätte, bevor sie zum Kunden gesendet wird.

    Gibt es dafür eine Lösung?

    ---

    There is currently only one field available for SW6 backend orders, with a dropdown menu for searching by article number or article name. Or the empty item line.

    In SW5 there was one column for article number and one for article name, price, tax, etc. for backend orders. You could use the article number, edit the article name, price, tax etc. and create the order with the overwritten data. This meant that everything was organised and could be transferred cleanly to customers, warehouses, etc.

    This additional column in the backend orders is missing in SW6. This means that you no longer have both fields available and can no longer make any changes, as the database then appears to search for a non-existent entry and the entry cannot be finalised.

    Is there a solution for this?

    A comment field is also missing at this level of the backend order, e.g. for internal customer numbers, export details, etc... In SW5 there were free text fields for this purpose.

    The comment field is only available in the next step. To get there, you have to save the order, after which the order confirmation is sent. You would like to have entered a few more details before it is sent to the customer.

    Is there a solution for this?

    Aktuell steht bei SW6 Backend Bestellungen nur ein Feld, mit Dropdown Menü für die Suche nach Artikelnummer oder Artikelname zur Verfügung. Oder die leere Positionszeile.

    In SW5 gab es bei Backendbestellungen je eine Spalte für Artikelnummer und eine für Artikelname, Preis, Steuer, etc. Man konnte die Artikelnummer verwenden, den Artikelnamen, Preis, Steuer etc. bearbeiten und die Bestellung mit den überschriebenen Daten anlegen. Damit war alles geregelt und konnte sauber an Kunden, Lager, etc. übergeben werden.

    Diese weitere Spalte bei den Backend Bestellungen fehlt in SW6. Damit hat man nicht mehr beide Felder zur Verfügung und kann keine Änderungen mehr vornehmen,… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Orders & Customers  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Retail Media Capabilities

    Challenge/Problem:
    What is Retail Media: https://www.criteo.com/blog/wtf-is-retail-media-guide/

    Selling paid content within a shop. Currently, it would involve a lot of custom & manual effort to create & maintain paid content in SW6.

    Possible Constraints for retail media:
    * Different methods how to defining prices such as KPI based (by CR, by Traffic, by Clicks, etc.) or fixed prices
    * Time limitation of active content (fixed period, max. number of Klicks/CR/Traffic, etc.)
    * Legal requirements (paid content and product position must be clearly indicated as an advertisement)
    * Integration of third-party system
    * Integration of external admin users (e.g. paid influencer who writes a blogpost and pushes it to SW6)

    Possible use cases for retail media:
    * Teaser and Banner (PLP, PDP, Homepage, Navigation, Blogposts, LPs)
    * Paid rankings (Search, search results, PLP sorting, Recos)
    * Paid blog posts
    * Paid brand category pages
    * Paid LPs

    Solution/Approach:
    Some sort of management for marketing to create, maintain and automate paid content within admin.

    Target Group:
    Beyond
    Retail media requires a certain size and reach of an online shop within its industry in order to be attractive for brands so that their paid content would lead to significant higher sales of their products in the corresponding onlineshop.

    Challenge/Problem:
    What is Retail Media: https://www.criteo.com/blog/wtf-is-retail-media-guide/

    Selling paid content within a shop. Currently, it would involve a lot of custom & manual effort to create & maintain paid content in SW6.

    Possible Constraints for retail media:
    * Different methods how to defining prices such as KPI based (by CR, by Traffic, by Clicks, etc.) or fixed prices
    * Time limitation of active content (fixed period, max. number of Klicks/CR/Traffic, etc.)
    * Legal requirements (paid content and product position must be clearly indicated as an advertisement)
    * Integration of third-party system
    * Integration of external admin users (e.g. paid influencer who… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Content management  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    DECLINED  ·  AdminJonas Fuchs (Product Manager Data & Services, shopware AG) responded

    Thank you for sharing this idea with us and for your patience while it’s been on the portal. After reviewing it again, we’ve decided not to move forward—There is not enough interest. Please keep the feedback coming; your insights continue to shape what we build next!

12. Optimization of plugin management and configuration in Shopware 6 Admin

    We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.

    Note from Shopware Support:
    We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and where these are configured.

    Main Issues:

    Scattered Apps: Apps are spread out across various sections of the admin area (e.g., Marketing, System, Settings), making them difficult to find.

    No Clear Function Assignment: After installation, it is often unclear which plugin is responsible for which function. Only after disabling a plugin does it become apparent what it was doing.

    Challenges with CMS Plugins: With multiple CMS plugins active at the same time, it’s almost impossible to figure out which plugin is being used in which Shopping Experience without manually testing each one.

    Shopify Example:
    We find that Shopify has a clear structure where all apps are centrally located under one "Apps" section, with direct access to configuration, making it super easy to manage.

    Use Cases for Clarification:

    1 - Finding an App:
    If i want to configure a recently installed plugin. However, it is scattered across the admin area (e.g., partly under Marketing, partly under System), and there is no central overview. The user wastes time searching for the app.

    Use Case 2 - Unclear Function Assignment:
    As a shop owner, i noticed a functionality in our shop (e.g., "Products in saved shopping carts" under Marketing) but does not know whether it’s part of the core system or added by a plugin. Suggestion: Clearly indicate which function is provided by which plugin.

    Wanted improvements:

    Introduce a central "Plugin" section where all installed extensions are listed and can be configured.

    Clearly label in the admin area which functions belong to which plugins. Maybe with an Icon and text on hover.

    Improve the identification of CMS plugins within Shopping Experiences.

    We are having difficulties finding and managing the apps and plugins installed in Shopware 6 within the admin area. Since many standard features from SW5 have been removed and must now be replaced by apps, there is no central overview for these extensions. The apps are spread out across different sections, without a clear indication of which plugin provides which functionality. This leads to issues with managing and identifying extensions.

    Note from Shopware Support:
    We think it's a very good idea. For many colleagues in support, it is often very difficult to find out which plugin inserts which functions and… more

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  System & Settings  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. I am trying to customize SEO URL slugs and encountered an issue

    When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.

    This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when we are using inheritance for all the descriptions and stuff. But when I turn it on, you force me to pick one of the variants. But I don't logically want it to be one of the variants, i want it to be main product. That leads me to another problem that I tried to solve with you: main product cant have the same product number as variant. So I cannot create variant as main product - so I cannot use it as main product for canonical URL. BUT! I think you would tell me: change storefront presentation, lets go to Product-Variants-Storefront presentation-Product lsitings and instead of Main product you could pick one variant and go with it. But I don't want to do it, because if I choose it as "Main product" in the storefront it is more beneficial since it shows, that there are more variants and price starts at.... You know what I mean? I don't want the specific size of the product be as main variant, you actually told me not to, since you require variant and main product to have different product number.

    This is actually really frustrating. Because I want it (as it should be):
    - main product - main URL - it is main product page that I want to be crawled by search engines
    - variants - url with whatever slug added to the main product URL, but I don't want Google to crawl it.
    Sounds pretty easy, right? And it even works like that, just not in case if I want to use MetaTitle as a slug.

    You give me these:
    - main product - main URL (i want to use meta title for that and you allow it since it is in the list of supported variants)
    - variant - can't use meta title - it makes it different url, which is ugly and not practical
    - seo canonical - can use only variant, not meta title, so basically I have many duplicate pages and it takes us down from Google.

    When I use variable meta-title in the url template, it works only for main products, not for variants, even if there is meta title inheritance enabled. But even when I check html of the variant page, meta title is not there. I don't know if you made it on purpose or it is a bug, but it means: I cannot use meta title variable for variants when creating a url.

    This lead to my other thought: let's turn Use single canonical URL for all variants - because of course we do not want google to mark it as duplicates when… more

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  SEO  ·  Delete…  ·  Admin →
    How important is this to you?

    Nice to have You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating