by StoreSEO (LX AI)
Open StoreSEO, provide the required inputs, run Demo to preview the workflow, then switch off Demo when a live key is configured.
SEO meta, alt text and rich-result snippets for every product page
Decision-support only — confirm before you publish or act.
When you open StoreSEO you see two main fields at the top of the screen. The first field expects a full URL to a product page that is reachable from the public internet. Paste the URL exactly as it appears in the browser address bar, including the https:// prefix. The second field asks for a primary keyword that best describes the product’s main purpose. Enter a short phrase of two to four words, avoid filler words such as “and” or “the”, and do not include punctuation marks.
Below the fields you find a toggle labelled Demo. Leave this toggle enabled while you are testing the flow. When Demo is on the tool uses a mock model that returns deterministic output, which lets you verify that the layout and the validation steps work without consuming any external quota. When you have a valid API key for the live model, switch the toggle off and paste the key into the settings panel that appears after you click the gear icon.
After you have filled both fields and set the Demo toggle as you need, press the large button labelled Run. The tool will start a short loading spinner, then display the results panel on the right side of the screen. If any field is empty or the URL is not reachable, an inline warning appears under the offending field and the run is blocked.
With Demo enabled and the inputs filled, clicking Run triggers a sequence of internal steps. First the tool performs an HTTP GET request to the supplied URL. It then parses the HTML response to locate elements that commonly hold product data: the <h1> tag for the title, elements with itemprop or schema attributes for price and availability, and image tags for the main product photo.
After the parsing phase the tool sends the extracted text and the primary keyword to a local mock generator. The mock generator creates a meta title that stays under sixty characters, a meta description that stays under one hundred sixty characters, five alternative‑text strings that each describe a different visual aspect of the product, and a JSON‑LD block that follows the schema.org/Product type.
The results appear in four separate cards. The Meta Title card shows the generated title and a character counter that turns red if the limit is exceeded. The Meta Description card works the same way for the description limit. The Alt‑Text card lists five suggestions, each with a copy button. The Schema card displays the raw JSON‑LD and offers a Validate button that runs a quick syntax check against the schema.org validator.
At the bottom of the panel you see a section titled 8‑Rule Listing Validation. Each rule is presented as a row with a label, a status icon, and a short explanation. A green check means the rule passes, a red cross means it fails, and a yellow warning indicates a condition that you may want to review but does not block publishing.
When you are satisfied that the Demo preview behaves as expected, locate the API key field in the Settings modal. Obtain a key from your provider’s dashboard, copy it to the clipboard, and paste it into the field labelled Live API Key. Press Save to store the key encrypted in the browser’s local storage.
After saving, toggle the Demo switch off. The label on the button will change from Run Demo to Run Live. Clicking Run Live now initiates a call to the external model endpoint. The request includes the extracted product data, the primary keyword, and the key in the Authorization header.
The live model returns the same set of outputs as the Demo: meta title, meta description, five alt‑text strings, and a schema.org/Product block. Because the model is non‑deterministic, you may notice variations in wording between runs. This is expected and reflects the model’s attempt to capture nuance.
If the request fails due to an invalid key, a network timeout, or a rate‑limit response, an error banner appears at the top of the results panel. The banner shows the HTTP status code and a short message from the provider. In that case verify the key, check your quota, and try again after a short pause.
When the live call succeeds, the validation rules are re‑evaluated against the fresh output. Treat any rule that shows a red cross as a signal to adjust either the input (for example, choose a different primary keyword) or to manually edit the generated text before you copy it to your store.
StoreSEO returns four distinct pieces of information that you can use directly in your product page’s HTML or in the SEO fields of your e‑commerce platform.
The Meta Title is intended for the <title> element. It should contain the primary keyword near the beginning, be compelling for click‑through, and stay within the sixty‑character limit shown in the UI.
The Meta Description goes into the <meta name="description"> tag. It should expand on the title, include a call‑to‑action or a unique selling point, and remain under the one‑hundred‑sixty‑character limit.
The Alt‑Text suggestions are meant for the alt attribute of product images. Use each suggestion on a different image (main view, angle, close‑up, lifestyle, and detail). If you have fewer than five images, pick the suggestions that best match the visuals you have.
The Schema.org/Product block is a JSON‑LD snippet that you paste inside a <script type="application/ld+json"> tag in the page head. It helps search engines understand the product’s name, image, price, availability, and optional ratings. Validate the snippet with Google’s Rich Results Test after you deploy it.
Each time StoreSEO finishes a run it evaluates the generated output against eight concrete checks that are derived from common e‑commerce listing guidelines. The rules are:
The UI shows a table that lists the rule number, a short description, the result (pass/fail/warning), and a note on what to adjust if the result is not a pass. Below is an example of the table as it appears in the tool.
| Rule | Description | Status | Note |
|---|---|---|---|
| 1 | Title length ≤ 60 | Pass | Title is 52 characters. |
| 2 | Description length ≤ 160 | Pass | Description is 138 characters. |
| 3 | Keyword in title | Fail | Primary keyword missing; add it at the start. |
| 4 | Alt‑text count = 5 | Pass | Five items present. |
| 5 | Alt‑text uniqueness | Pass | All five differ. |
| 6 | Schema name & image | Pass | Both properties found. |
| 7 | Price & availability | Warning | Price not detected on source page. |
| 8 | JSON‑LD valid | Pass | Parses without error. |
When a rule shows Fail you should edit the relevant field before you publish. When a rule shows Warning you may decide to accept the output or to improve the source data (for example, ensure the product page includes a price element). The tool never blocks you from copying the output; it only informs you of potential issues.
StoreSEO is a decision‑support aid. It does not promise that any generated meta title will rank first in search results. It does not guarantee that the alt‑text will satisfy every accessibility guideline. It does not replace a thorough SEO audit performed by a specialist.
The tool does not automatically push changes to your store. You must manually copy the output and save it in your platform’s admin area. It does not run in the background or schedule regular updates.
StoreSEO does not provide keyword research, back‑link analysis, or competitor tracking. It focuses solely on creating a first draft of on‑page elements for a single product page.
The outputs are not final. You should review each line, check for brand‑specific wording, and confirm that any claims about the product are accurate before you make them live.
There is no built‑in A/B testing feature. If you want to test two different titles you must create two separate runs and compare the results yourself.
The tool does not store your product data on external servers beyond the temporary processing needed for the run. When you close the browser tab the data held in memory is cleared.
SEO meta, alt text and rich-result snippets for every product page
Operators and builders who need a fast first draft or checklist from StoreSEO.
Yes in explicit Demo mode. Live AI requires a configured key.
No. Outputs are decision-support; you still review before publishing or acting.
Only if those features are implemented in this product build — do not assume them from marketing copy.
Runs may be stored locally under the product's .data/ boundary; treat demos as ephemeral.