Before you start
Before your first collection publication or when intentionally changing its integration.
- Automatic integration uses a dedicated field and Rankora's Theme App Extension.
- Custom integration writes an existing compatible field; the theme or developer displays it.
- Legacy collection description mode writes the normal collection description and can replace it.
Steps to follow
- Open Collection SEO and read Publishing & storefront.
- Use Automatic integration when you want the dedicated Rankora field and app block.
- Use Custom integration only for a compatible field that your theme or developer will render.
- Choose the legacy normal-description destination only when replacing that description is intentional.
- Verify the selected destination before publishing and check one collection on the storefront.
For example
A dedicated field can hold additional text below the products while the original collection description stays at the top.
What happens next
Future publications use the selected destination. A destination choice does not prove that existing content was moved or that every template displays it.
A useful tip. Keep the storage destination and storefront display as two separate checks.
Take care. Do not confuse Automatic integration with the Product Meta or ALT automatic publication setting.
Common questions
Can I keep my original description?
Yes, by publishing the additional text to a separate compatible field instead of the normal description.
Can I change integration later?
Yes, but check existing field values and theme placement. Do not assume an automatic migration of old text.
Why is saved text invisible?
The chosen field still needs to be rendered by the correct collection template.
If you are still stuck
- If content is missing from the storefront, check the destination and rendering before regenerating the text.