SEO: search visibility, metadata, and redirects

Control discovery settings and fix common search presentation issues.

Before you start

Have a public-ready storefront. Search engines decide when and how to index pages.

On a phone? Open the admin menu to find the same section. Screenshots below show the desktop view; tap “Open full size” for a closer look.
STEP 1

Review indexing

Open Online Store → SEO & AI. Review Search engine indexing and save the intended setting.

  • A private or unfinished store should not be treated as ready for public discovery.
Lulu Guide Demo
SEO: search visibility, metadata, and redirects — Lulu demonstration admin
Actual Lulu admin · Demonstration store and sample dataOpen full size ↗
STEP 2

Set search appearance

Review the home page title, meta description, and social-sharing image in SEO & AI or Preferences.

  • Describe your business accurately.
  • Use a local uploaded sharing image and check the preview.
STEP 3

Review crawler choices

In SEO & AI, review AI crawler and answer-engine controls separately from search-engine indexing.

  • Choose the access policy you actually want; enabling a crawler does not guarantee a mention.
STEP 4

Repair old paths

Use Online Store → Preferences → URL redirects for changed addresses. Enter the old path and intended destination.

  • Open the old URL to test the result.
  • Use SEO health to review remaining product issues.

CHECK YOUR WORK

You’re ready when…

  • Indexing and crawler choices are intentional.
  • Titles, descriptions, and redirects have been checked.

IF SOMETHING DOESN’T LOOK RIGHT

Troubleshooting

Why is my store not appearing in search yet?

Check password protection and indexing first. Search-engine discovery is not immediate or guaranteed; changes in Lulu do not force a search-engine update.

Why is a control missing or unavailable?

Confirm that you are in the correct store and that your role allows this action. Optional apps and channels may require installation, a plan, or activation. Share the screen name and error with support if access is still unclear.

Keep going

Get help with this step ↗