Bulk generation lets you review everything before it goes live. Automatic optimization goes one step further: you pick a number of pages and Fexa handles the rest. It selects your priority products, rewrites them, publishes only the fields that pass its checks, and sets everything else aside, with the reason, in a delivery report.
In short: 10, 25 or 50 pages in one click, 1 credit per page actually published, a before/after report, an e-mail at the end, and every page can be undone in 1 click.
Starting an automatic optimization
- Open the Dashboard and find the Automatic optimization card.
- Under Number of pages, choose 10, 25 or 50.
- Click Optimize. The batch runs on our servers: you can close the tab, it carries on without you.
- Follow progress with Follow the batch, or wait for the end-of-batch e-mail.
A few conditions before you start:
- your catalog must have been scanned at least once;
- your balance must cover the number of pages requested (a batch of 25 needs 25 available credits at launch);
- one job at a time per store: if a scan, a translation or another batch is running, wait for it to finish.
Automatic optimization is available on every plan, including the free account: up to 25 pages per batch on Free, up to 50 pages on paid plans.
Which pages are picked?
Fexa only handles products (not categories or CMS pages), in your store's default language. It ranks them by priority:
- Urgent pages: SEO score below 50, or not scored yet.
- Quick wins: products on Google's page 2 (positions 11 to 20) with at least 20 impressions, one push away from page 1.
- Highly viewed but weak pages: at least 50 impressions and a score below 70.
- Other pages that need work (score below 80), weakest first.
Within the same priority, the pages with the most impressions go first. Fexa leaves out:
- pages you have edited by hand in PrestaShop;
- pages already optimized in the last 30 days;
- pages that are already good (score of 80 or more) and are not quick wins.
If there are fewer priority pages than the number requested, the batch is simply shorter.
What is published, what is held
For each page, Fexa can rewrite five fields: the Google title, the Google description, the short description, the description and the FAQ. Image ALT tags are not part of the batch.
Each field is checked on its own:
- Published: it passed every check and is written to your store, after a restore point is saved.
- Already fine: nothing to change (the proposal matches your text, or your field already meets the bar).
- Held back: it is not published. It waits for you in the report, with its reason.
These are the possible reasons for holding a field:
| Reason shown | What it means |
|---|---|
| Quality too low for automatic publishing | The proposal's quality score is below the required threshold: nothing on that page is published automatically. |
| A fact needs your check | Fexa's engine flagged a doubtful fact (inconsistent source, duplicated composition…): nothing on that page is published automatically. |
| Too few product attributes | Not enough product data to write reliable text: the Google title and description can go live, the page texts wait. |
| Unsourced claims were removed from the text | The anti-invention safety net cut sentences out: the page texts wait for your review. |
| The proposal would remove an existing list or table | Your page has a data list or table that the proposal would drop. |
| The proposed text has no accents | The text seems to have lost its accents: it is not published as is. |
| The proposal is much shorter than your current text | Your current text is long and the proposal would keep less than 60% of it. |
| The proposal would lower the page's SEO score | Publishing this field would lower the page's score: Fexa holds the page texts first, then everything else if needed. |
The delivery report
Every batch has its own delivery report (open it with See the last delivery report on the dashboard). For each page you will find:
- its status: Published, Held back, Already fine, Failed, Not processed or Undone;
- for each published field, the text before and after;
- for each held field, the reason, your current text and the unpublished proposal;
- a View the page link to check the page on your store. After publishing, Fexa checks the live page and warns you if your theme does not display the saved title.
"Publish anyway"
You have read a held field and it suits you? Once the batch is finished, the Publish anyway button publishes the held fields of that page. It costs 1 credit if nothing had been published on that page yet, nothing more otherwise.
The end-of-batch e-mail
When the batch ends, you receive a summary e-mail: how many pages were published, held back, already fine or failed, and the credits used. Then just open the report to review the held pages.
Undo: one page or the whole batch
The original version of each page is saved before anything is written. From the report:
- Undo this page restores the original version of one page;
- Undo the whole batch restores every page the batch published.
Undoing is free and is also available from the History & undo page. It does not refund the credit of a page that was already published.
How much does it cost?
- 1 credit per published page, however many fields were published on it.
- A page where nothing is published (everything held or already correct) costs nothing.
- If your credits run out along the way, the remaining pages are not processed and show as Not processed in the report.
Stopping a running batch
While it runs, the Stop the batch button in the report interrupts the optimization. Pages already published stay live (and can still be undone); the next ones are not processed and cost nothing.
FAQ
Can Fexa publish without me asking? No. A batch only starts when you click Optimize, and it only publishes the fields that passed its checks. Everything else waits for your decision in the report.
In which language are pages rewritten? In your store's default language. For other languages, use translation.
Can a page I edited myself be overwritten? Pages flagged as edited by hand in PrestaShop and pages optimized in the last 30 days are excluded from the selection.
See Also
- Run Batch Optimizations — when you would rather review everything yourself
- Rollback: undo an optimization in 1 click — restore a page from the history
- Understand the Credits System — cost of each action and per-plan quotas