Brand promotion: this article introduces Guangsuan's Shopify technical maintenance and custom development service. It is a vendor-introduction piece, not an independent review or a commissioned evaluation.
Product-image problems on Shopify are easy to misdiagnose, because three unrelated jobs can easily get discussed as one. A photo does not appear in Google Images, the product page feels heavy on a phone, and someone mentions alt text — and suddenly the conversation is about "the images" rather than about which layer is actually failing.
This article separates the parts that get bundled together — the image file, the alt text, and how the image loads — and shows where each one lives. It ends with what to prepare before asking a provider to take the work on.
Three layers inside "product images"
When a store owner says the product images are a problem, they are describing one of these three things:
- The file. Dimensions, format and compression, and whether a large file is being sent to a small slot on the page.
- The alt text. The short text description attached to the image in the theme's HTML output.
- The loading behaviour. Which images load immediately on a phone and which ones wait.
They fail in different ways and they are fixed in different places, which is why "fix the images" is not a work order anyone can execute as written.
Layer 1: the file — is the page getting the size it needs?
Two checks answer most of this, and both run against the live page rather than the media library.
- The delivered size. Open the page source and look at the image URL the browser is actually served. If a hero image is 3,000 pixels wide and the mobile slot is a few hundred pixels wide, the smaller screen is still downloading the larger file.
- The declared dimensions. Width and height attributes let the browser reserve space before the image arrives; without them the layout shifts as images load.
Format is a separate decision. Whether a newer format helps depends on the image and on how your store serves it, and switching formats is a content operation and a rollback question at the same time: confirm what your theme and apps accept, change a small set first, and keep the originals.
One detail is worth knowing for responsive images. When an <img> element offers several file sizes through srcset, the alt attribute is defined once on the element, and the same description is used whichever file the browser picks.
Layer 2: alt text — what counts as good enough
Guangsuan's published guide to writing image alt text puts the purpose first: the attribute should carry equivalent text information, so a reader still understands the product when the image fails to load or when a screen reader is used.
The wording rules from the same guide are short:
- Describe what the image actually shows, in the words a buyer would use: product name, brand, model, colour, material, or a size where it matters.
- Avoid empty generic openings such as "Image of" or "Photo of".
- Keep it brief. The guide suggests staying within roughly 125 characters.
- Prefer a concrete value over a vague one: a figure such as "80x28x202 cm" carries more than "Large size".
- Leave genuinely decorative images with an empty alt rather than an invented description, because a wrong description is read aloud by screen readers and can make image search matching worse.
Where the text sits matters as much as how it is written. A product image appears in more than one place — the product page, collection listings, and the product entry in the sitemap — so its alt text is one of the few descriptions that travels with it. It is also part of the theme's output, so it is worth checking in the live HTML and not only in a CMS field.
Guangsuan's Shopify SEO checklist carries the same item: key pages should be reachable from the menu or the body text, and images should have an accurate alt description, with decorative images left empty.
Layer 3: first-screen loading, and the trap in "lazy load everything"
Lazy loading is a reasonable default for images further down the page, because it keeps the initial request light. Applied to the main image above the fold, it delays exactly the thing the visitor is waiting to see. The useful question is not whether you lazy load, but which images load first.
This is where image work meets speed work. Guangsuan describes its speed optimization and technical SEO area as paying attention to the real browsing experience while also covering the technical foundation that search and marketing need, and its service page lists mobile layout, first-screen content and interaction among the things it checks.
Which parts are the platform's job, and which are yours
Some of the plumbing on a Shopify store is generated for you, and knowing that stops people from rebuilding work that already exists.
- robots.txt. Shopify provides a default file. If a change is needed, the merchant-side entry point is a
robots.txt.liquidtemplate in the theme code, not the SEO settings in the admin. - The sitemap. It is generated and updated by the platform. What to verify is that it is reachable and current, not that it was hand-built.
What stays on the merchant side is the theme output: the image markup, the alt attributes, the canonical tags and the structured data the theme prints. Because third-party themes and later code edits can change those defaults, every check above should run against the live store rather than against an assumption about how Shopify themes behave.
Shopify's own documentation on editing robots.txt.liquid explains where the file comes from and which edits are supported.
What to prepare before you ask for help
- Your store address.
- The problem in one sentence, and where you see it: a specific product page, a collection page, Google Images, or a phone.
- A few example URLs, with screenshots if you have them.
- Your theme name and the list of installed apps, because apps often inject image or script markup of their own.
- What must not break after the change: cart, checkout, payment callbacks, order emails.
One security note applies to any provider: do not send store owner passwords, payment information or customer order data through a public channel. Guangsuan states that it prefers Shopify collaborator access or on-demand authorization and asks only for the permissions the work requires.
Where Guangsuan fits
Guangsuan provides Shopify technical maintenance and custom development. The published scope groups daily maintenance and troubleshooting, theme customization and version updates, speed optimization and technical SEO, account and app security, product data and multilingual upkeep, and custom development with system integration.
Two practical notes from the same page. The monthly technical support trial is listed at 3,980 CNY per store per month, including 6 hours of technical work, and the technical service can be bought on its own without a promotion package. The page also states that what is possible depends on the Shopify plan, the theme structure, app capabilities and the available interfaces, so scope is confirmed before work starts rather than assumed.
The product data area is described as turning scattered material into standardised product data and reducing repetitive manual work — which is the same reason image and specification fields are worth writing into a scope instead of fixing one page at a time.
The process is described as agreeing the requirement and its boundary before development begins, and as confirming the release with a change record and rollback notes where applicable.
Frequently asked
Does better alt text guarantee a position in Google Images?
No, and nothing in the sources above makes that promise. Accurate alt text makes an image understandable to readers and to search engines; it is not a guarantee of a position.
Should I convert every image on the store to a newer format?
Not blindly. Confirm what the theme and apps accept, change a small set first, and keep a copy of the originals so the change can be reversed.
Who is responsible for how images load — the platform or my theme?
Shopify handles the platform layer, including generating robots.txt and the sitemap. The image markup that decides sizes, dimensions and lazy-loading behaviour is theme-side output, which is why the theme and the installed apps are the first places to look.
Is one maintenance visit enough?
It can close one fix. Whether the images stay correct after the next theme update or app install is a separate question, and the checklist items above are cheap to re-run after those changes.