Product SEO + AI Beta: Keywords, URL and Save & Apply
Official guide · English · Version 9c253d0cf11816df
SEO + AI (Beta) is a separate product-content workflow next to the original AI generation controls. It plans keywords before generating a description. The original generator remains available without the pilot.
Before opening the pilot
Save the product first. The pilot uses saved information, including Quick Product Info, specifications and product images; unsaved edits in the surrounding form are not its source. Supply accurate facts, brand and model spelling. You can also add clear photos of specification tables, labels or dimension diagrams as product images. Select the intended content and URL language in the pilot.
Suggest keywords and URL
Choose Suggest keywords & URL. The pilot analyzes readable saved primary and additional images, including specification photos, and considers that evidence alongside product facts, the tenant's SEO keyword records and available Search Console data. Review the proposed primary keyword, supporting phrases, URL segment, explanation and evidence status. The panel shows how many saved images were analyzed. Missing or failed images do not stop generation: the pilot uses readable images and saved information, or saved information alone when image analysis is unavailable. A non-blocking warning explains partial or unavailable analysis.
Search Console shows observed performance for your connected site, not total market search volume. Not connected, unavailable or no matching rows does not mean no demand. Suggestions can use saved product facts; do not call them Search Console evidence when the panel says otherwise.
Review and approve the brief
Choose a specific primary phrase representing this product. Review conflicts with existing keyword owners and edit the phrase if another page owns it. Shared supporting terms are allowed; not every word must be unique across the store. Check facts, brand, model and native-script spelling in the proposed URL. Spaces become hyphens.
The pilot fills an empty slug, but does not silently replace a nonempty live product URL. The preview displays the existing URL when present. Duplicate new URLs receive a suffix. A localized URL does not guarantee better ranking.
Generate a preview
Choose Approve brief & generate preview. Review description, specification table, headings and SEO metadata. Suggestions and previews do not change the product. The complete workflow uses one description credit per newly generated product preview; keyword and URL suggestions are included without another charge. Suggestions require available text credits. Reusing or applying an existing preview uses no additional credit.
The main description must contain 800–1500 words without repeated sections. The preview displays its word count and whether it is within the allowed range. Existing writing style, section structure and factual rules remain. SEO title, meta description, Selling Points, Usage Notes and Alt Text retain their separate limits and do not count toward this range.
If Insufficient information appears, answer the displayed questions by adding verified details to Quick Product Info and specifications, save the product and request fresh suggestions. This status is reserved for a product whose identity or basic purpose cannot be established. A recognizable product that remains short or repetitive after correction is reported as Invalid description length instead. Optional missing details do not block the entire description. The assistant can add neutral category-level buyer guidance but must not present it as a specification of this exact product, invent facts, repeat claims or add generic filler to reach 800 words. Length corrections reuse the reserved description credit; up to two corrections are attempted before rejecting the result. Failed generation does not apply content and releases the reserved generation credit. Older previews below 800 words require a fresh generation before applying.
Content direction is independent of the dashboard display language. Newly generated Persian, Arabic, Urdu and Hebrew descriptions retain right-to-left direction in headings, paragraphs, lists and specification tables when saved and reopened. Other supported content languages use left-to-right. Product text fields, including name, Quick Product Info, Selling Points, Usage Notes and SEO/Alt Text, follow their own text direction. Numbers and full URLs remain left-to-right, and model/SKU characters are not reversed. Existing descriptions are not automatically regenerated; generate a new preview to use the updated content-depth instructions.
Readable specifications from images are used alongside Quick Product Info. Clearly visible features and supported benefits are included in the content and Selling Points. The preview also includes Product Usage Notes and Image Alt Text when there is supported information. Alt Text describes the primary image; if it is a specification sheet, it should describe the sheet, not pretend it is a product photograph. A product without images can still use saved text/specifications but does not receive new Image Alt Text.
Review extracted numbers, units, variants and product-versus-packaging dimensions. Unreadable or contradictory details must not be guessed, and a photograph alone cannot establish quality, rated power, safety or compatibility. Keep specification images clear and complete. Image analysis uses the configured Image Model and is reused within the same preview session, without an additional description credit. Provider usage is recorded separately. Starting new suggestions analyzes the current images again.
Save & apply to this product
Choose Save & apply to this product and wait for confirmation. This writes the approved description, storefront description, SEO metadata and keyword assignment to the saved product. It also fills empty Selling Points, Product Usage Notes and Image Alt Text when available; existing values and fields controlled by a linked hub are preserved. These saved fields appear in the product form. No second Save is required for those applied fields. Other unsaved form edits still require ordinary Save.
Name, price, inventory, images and Quick Product Info are not replaced. A custom visual product design can control the visible description; check that design if the storefront differs from the saved text. A refresh warning after a successful save is not a failed save: use the offered refresh retry rather than generating and paying again.
Troubleshooting
| Symptom | Action |
|---|---|
| Unsaved source changes | Save product information, then reopen the pilot. |
| No Search Console evidence | Check connection/status; use facts without inventing search-volume claims. |
| Keyword ownership conflict | Choose a specific primary phrase or review its current owner in SEO. |
| Existing URL unchanged | Expected for a nonempty product slug. |
| Preview exists but product unchanged | Click Save & apply and confirm success. Closing does not apply it. |
| Additional fields are still empty | Generate a fresh preview after the update and check whether supported information was returned. Old previews do not acquire new fields just by applying them. |
| Image cannot be read or image analysis is unavailable | Generation continues using readable images and saved facts, with a non-blocking warning. Review and apply the preview as usual. No visual facts or primary-image alt are invented for unread images. Correct images or ask the administrator to check the Image Model, then request fresh suggestions if you need image analysis. |
| Provider request fails | Preserve edits and retry when available. A network error is not a content-policy verdict. |
