Landing page comparison: show the table from your product page
Commander can add a comparison table to a landing page: your product against a generic standard, taken from the comparison table your own product page already shows. Commander writes the table itself from your page and never names another brand. You see the table in the section that gives the reasons to choose your product, after Commander writes the page. To create pages, see Landing pages.
Problem and intended user
The ecommerce manager (the person who runs the store) has a product page with a table that sets the product against an ordinary alternative, and the table helps a visitor decide. A landing page that comes from an ad starts without it. A visitor who lands there sees claims but no side-by-side proof, and the page looks thinner than the product page.
Current workflow
Without Commander, the ecommerce manager copies the table from the product page into a section of the landing page in the theme editor, row by row, and keeps both copies in step when a row changes. Deciding what the table may say about a competitor is a manual call each time.
Prerequisites
- A landing page for a product, written by Commander. A page for your brand alone has no comparison table.
- A comparison table on your own product page, with a header row and two columns of values: yours and a generic standard.
- One column header that names a generic standard, such as "Standard vitamin D". A header that names a brand, or that holds "vs" or "like", is not used.
- Rows with a tick or a cross in both columns. A tick or cross can be a character, the word yes or no, or an icon whose accessible name says yes or no.
- A page in English, German or Romanian.
How Commander works
Fixed rules read the comparison table on your product page when Commander captures your store for a page. AI does not write the table and does not choose its rows. The AI that plans the page can give the section that gives the reasons to choose your product a comparison table only when your page passes the rules below. The AI that writes the page may add a heading and one sentence. Commander then writes the table itself.
Commander accepts a table when all of these hold:
- Exactly one column header names a generic standard.
- The header words are short, hold no anonymised text and name no brand.
- Enough rows have a tick or a cross in both columns.
- The page is in a language Commander can check.
- The page has no section that makes regulated claims.
Commander leaves out a row whose words name a health or body effect, and it removes footnote marks from the headers and the row names. It uses your own column names and your own ticks and crosses. It adds a fixed note under the table: "As stated by the store on the product page, compared with a generic standard. No other brand is named." The note follows the language of the page.
If the AI leaves the table out of the section, Commander adds it at the end of the section. Commander removes any other comparison table on the page. Nobody approves the table, and you review the page as you do for any generated page.
Get a comparison table on a landing page
- Open the product in your store and check that its page shows a comparison table with a header row.
- Name one column header for the generic standard, for example "Standard vitamin D", and make sure each row has a tick or a cross in both columns.
- For icons, give each icon an accessible name such as "yes" or "no".
- Generate the landing page. Generating a page uses credits, and the dialog shows the cost.
A page that exists keeps the table it was made with. Commander reads your product page again only when it captures your store for a new page, and it does not read it on a schedule. After you change the table on your product page, generate the page again.
Exact output
A section with a heading and, at most, one short sentence, then a table with your column names and a row for each comparison, with a tick or a cross in each cell. Under the table is a small fairness note. The table is built from your page, so the words and the marks are yours.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| A comparison table that matches your product page | Keep it. Check that each row is true today. | ecommerce manager |
| A row you do not want | Remove it from your product page table and generate the page again, or remove the section in the Landing page editor. | ecommerce manager |
| No comparison table | Check the list under Prerequisites, fix your product page and generate the page again. | ecommerce manager |
| A tick or cross that is wrong | Fix your product page table and generate the page again. | ecommerce manager |
Expected value and measurement
A comparison that a visitor can read at a glance can help a new visitor see why your product differs. It is not a promise of a higher conversion rate.
To check, compare the conversion of the page with a page without the table, in your own analytics. You cannot isolate the table from other changes that ran at the same time, such as new ads or offers.
Limitations and exceptions
- Commander uses only a table that your own product page shows. It never writes a comparison with AI and never names another brand.
- Many stores have no table that qualifies, so a page for your store may well have none. A table whose headers name a brand, or whose cells are neither ticks nor crosses, is not used.
- Commander can read an icon as a tick or a cross only when its accessible name says yes or no in the language of the page. Any other icon counts as an empty cell, and the table may then be too short to use.
- The table is written only for pages in English, German or Romanian. Another language shows no table.
- A page with a section that makes regulated claims shows no table.
- A row about a health or body effect is left out, even when your product page states it.
- Commander does not check that a row is true. You are responsible for each claim on your product page and on this page.
- The AI that plans the page can leave the table out even when your page qualifies.
- Commander captures the table when it writes a page. A later change to your product page does not reach a page that exists.
- In Demo Mode, the list shows fixed sample pages, and each one shows a comparison table. Commander reads no store, so the tables are examples. See Demo Mode.