Troubleshooting

The request URL shows "Not generated yet"

SEO URLs are created by the indexer. Under Settings → System → Caches & Indexes click Update indexes or trigger the indexer repertus_landingpage.indexer specifically, then reload the landing page. With queue indexing enabled the message consumer has to run.

"No domain for the current language"

The sales channel has no domain for the language selected at the top. Either create a domain for this language under Sales Channels → (sales channel) → Domains and update the indexes afterwards, or switch the language.

No URL is created for a sales channel although a domain exists

The landing page's category is not part of this sales channel's navigation tree (neither below the entry category nor below footer or service navigation). Either choose a suitable category, enable Use category from the sales channel navigation in Standard mode, or give the variant its own category in Per sales channel mode.

The landing page returns a 404 error in the shop

Possible causes, check in this order:

1. The landing page is inactive (General tab, Active switch).
2. The sales channel is not assigned, or in Per sales channel mode no variant exists for it.
3. The landing page has no category.
4. The URL was changed but the indexes have not been updated yet.

The landing page is empty in the shop

The landing page has no layout. Assign a Shopping Experience layout with a product listing in the Layout tab.

The redirect from the listing does not happen

The redirect requires an exact match. Check:

• Is the landing page active and assigned to the sales channel?
• Is the current category the landing page's category?
• Are exactly the landing page's properties and manufacturers set, and nothing else (no price filter either)?
• Is the customer on page 1?

A listing that is reachable in the shop without filters cannot trigger a redirect: the check only runs on filter changes.

Canonical URL "Not resolvable"

The landing page points to an address for which no canonical SEO URL exists in the current language, for example because the target was deleted or the indexes have not run after an import. Update the indexes; if the hint stays, choose another target or clear the field so the landing page points to itself again.

The landing page is read-only

For a generated page, see generator write protection.

Otherwise, the landing page is in Per sales channel mode, but the corresponding extension is not active. In the Settings tab either Reactivate extension or Switch to standard mode, see Per sales channel configuration.

The landing page does not appear in the sitemap

Check whether the landing page is active, assigned to the sales channel, has a request URL and Exclude from sitemap is not set. Shopware regenerates the sitemap on a schedule; bin/console sitemap:generate rebuilds it immediately.

The menu item is missing in the admin

The user has no permissions for the module. Under Settings → System → Users & permissions → Roles enable the role SEO Filter Landingpages in the Marketing section, see Permissions.

The generator is visible but cannot be edited

The Landing page generator is a separate in-app purchase. Check the active purchase and user permissions. The Per sales channel configuration extension alone does not unlock the generator. Already generated pages remain reachable when the generator is inactive; see behaviour without an active extension.

A generation run stays pending or running

First check whether another rule is still running: only one generation run is processed at a time. If the queue is stuck, check the CLI worker and scheduled tasks. Keeping the Administration open is not sufficient for long runs. The Message queue not running? banner is based on waiting time, not a direct process check. See Automatic runs and workers for setup and troubleshooting details.

The run has completed, but landing pages are missing

Open the run report in the Generator log and check the counters and Reasons. Common causes include too few products, an existing page with the same category and filter combination, an occupied URL or a template error. Also check categories, facet values, patterns and translated title and meta title templates. Stopped at the upper limit means that the configured limit was reached.

Generated pages are hidden by default in the landing page list. Enable Show generated landingpages in the right filter sidebar.

A generated landing page cannot be edited

A page is read-only while it belongs to a generation rule. Change the rule's templates or page settings and run it again. For individual changes, select Detach. Subsequent runs leave the page untouched as long as its category and filters still occupy the original combination. See Managing generated landing pages.