Landing page logo row: show the logos your site already has
Commander can add a row of logos to a landing page: press that featured you, certifications and awards you hold, or partners you work with. It takes the logos from your own home page and About page. It never adds one that your site does not show. You see the row on the page after Commander writes it. To create pages, see Landing pages.
Problem and intended user
The ecommerce manager (the person who runs the store) knows that a row of recognised logos helps a first-time visitor trust a page. A landing page that comes from an ad is a new place for that proof, and it starts without it. A missing logo row sends visitors to a page that looks less established than the store.
Current workflow
Without Commander, the ecommerce manager or an agency downloads each logo, uploads it to the Shopify files, and places it in a section of the page in the theme editor. Each logo needs a name for accessibility, and each change on the home page needs the same change on the landing page.
Prerequisites
- A landing page that Commander writes for your store.
- Logos on your own home page or About page, in a row under a heading such as "As seen in", "Featured in", "Certified", "Awards" or "Partners". Commander also finds a certificate, award or seal image in your site header or footer when the name of the image says what it is.
- A name for each logo. Commander uses the alt text of the image. Without alt text, it uses the title of the image or its file name when that file name says something.
How Commander works
Fixed rules read your home page and About page when Commander captures your store for a page. They find the rows of logos and note, for each logo, its kind (press, certification or partner), its address and its name. AI does not decide which logos exist. Commander offers the list to the AI that plans the page and to the AI that writes it. When your pages show logos, the plan can include a section with a row of exactly those logos, each in the order Commander found it. The AI that writes the page then builds that row and no other.
The AI shows each logo with the name Commander found for it, keeps the name exactly, and says nothing more about the logo than the row itself. A row of press logos gets a heading such as "As seen in". A row of certifications gets "Certified". A row of partners gets "Our partners". A row with mixed kinds gets no heading, or a neutral one.
The owner of the claim is you. Commander does not check that a publication featured you, that a certificate is valid or that a partnership exists. It shows what your site already shows. The page needs no approval step apart from the review you do for any generated page.
Get a logo on a landing page
- Add the logo to your home page or About page, in a row under a heading that names it, for example "As seen in".
- Give each image alt text that names the logo, for example the name of the publication.
- Generate the landing page. Generating a page uses credits, and the dialog shows the cost.
A page that exists keeps the logos it was made with. Commander does not read your home page and About page every time it writes a page. It keeps what it found and reuses it until one of two things happens:
- Your live theme changes. A saved change to the theme, or publishing another theme, makes Commander read your pages again the next time it writes a page.
- You write a page for a different product than the one before. Commander reads your pages again for the new product.
If you have just added a logo to your site and Commander has not read your pages since, the next page shows the logos it found earlier, or none. Nothing in Commander lets you ask for a new read, and no schedule does it. To get the new logo onto a page, save a change to your live theme, then write the page.
Exact output
A single row of logos on the landing page, under a heading that fits their kind. Each logo is an image with its name as alt text. Commander does not add the row when it found no logo, and it does not replace any other part of the page with the row.
What to do with it
| What you see | Decision or action | Owner |
|---|---|---|
| A logo row with the right logos | Keep it. Check that you may show each logo. | ecommerce manager |
| A logo you do not want on the page | Remove it from your home page or About page and generate the page again, or remove the section in the Landing page editor. | ecommerce manager |
| No logo row | Add the logos to your home page or About page as described above, then generate the page. | ecommerce manager |
| A logo with a wrong name | Fix the alt text on your own site and generate the page again. | ecommerce manager |
Expected value and measurement
Visible proof can help a new visitor trust the page. It is not a promise of a higher conversion rate.
To check, compare the conversion of the page with a page without the row, in your own analytics. You cannot isolate the row from other changes that ran at the same time, such as new ads or offers.
Limitations and exceptions
- Commander shows only logos that it can find and name. An image with no useful name is left out, because a logo that Commander cannot name is a logo it would have to guess a name for.
- Payment and social icons are not logos for this row and are left out.
- A limit applies to how many logos Commander keeps. A long list is cut.
- Commander reads your pages again only in the two cases under Get a logo on a landing page. A store whose first read found no logos keeps finding none until then. Adding a logo to your site does not change a page that Commander has already written.
- Commander reads the home page and About page only. A logo that lives on another page, or is set in a slide or a script that the page does not show as an image, is not found.
- The AI that writes the page can leave the row out even when Commander found logos. The row never replaces another part of the page.
- Commander plans the sections of most pages before it writes them. The plan can include a logo row when your pages show logos, and it puts the logos in a section of their own. The AI that plans the page can still leave the row out, so a page for your store may have none even when Commander found logos.
- You are responsible for each claim. Show only logos you may use.
- In Demo Mode, the list shows fixed sample pages, and they show a logo row. Commander reads no store, so the logos on a sample are examples. See Demo Mode.