Before you start
When Rankora reports a successful collection publication but shoppers cannot see the text.
- A published field and visible storefront content are separate checks.
- Automatic integration needs the Rankora block; Custom integration needs your theme's own field rendering.
- The active theme and the exact assigned collection template must be checked.
Steps to follow
- Open the collection in Rankora and confirm the publication result and destination.
- For Automatic integration, open Theme Editor and find the Rankora block on the template assigned to this collection.
- For Custom integration, confirm that the theme reads the selected field's exact namespace and key. Ask your developer if needed.
- For legacy description mode, verify the normal collection description and its theme display.
- Save the intended theme changes and preview the same collection. If it is still invisible, contact support with the collection and integration model.
For example
A block added to the default template will not display text on a collection assigned to a different custom template.
What happens next
Correct rendering can show content that was already saved. There is no need to buy another generation merely to place that existing text.
A useful tip. Check whether you are previewing an unpublished theme instead of the live storefront.
Take care. Do not switch to the normal description unless you actually want to replace that description.
Common questions
Should I generate again?
Not just for a display problem. Verify the saved value and theme rendering first.
Does Ready setup prove every collection is visible?
No. Different collections can use different templates, and an empty field has no text to display.
Is custom integration handled by the Rankora block?
Custom integration stops at the selected field. The store's theme or developer handles its display.
If you are still stuck
- Keep the collection URL, active theme name, template and integration model for support. Hide private data in screenshots.