SEO
On-page SEO for ecommerce stores in 2026
On-page SEO for an ecommerce store in 2026 is still the work on the URL itself: keyword intent, title, headings, copy, images, schema and internal links on product and collection pages. Platform features moved. The page still has to make sense as a document. This note is for Magento, Shopify and WooCommerce catalogues, not for a blog that ranks one article at a time.
I am Alan Vo, a Gold Coast web developer. Eighteen years of storefronts, including Magento operations where year-on-year sales rose $2.5 million over three years, taught me that on-page SEO fails in templates, not in a keyword spreadsheet. Google’s SEO starter guide still starts with helpful, unique pages. A SKU grid with the same 12 words in every title is not that.
Why on-page SEO still decides whether a product page ranks
On-page SEO still decides whether a product page ranks because Google and AI systems have to understand that URL as a match for a query, and a catalogue will not do that work in the sitemap alone. Crawl gets the bot in. The document has to be distinct.
Ecommerce is harder than a brochure site because thousands of URLs share a template. The H1 is a product name. The first paragraph is a manufacturer blurb pasted into Magento. The title is {name} | {store}. Collection pages have no copy. Related products are a carousel with “Add to cart” as the only anchor text. That is an on-page problem even when Core Web Vitals are green.
What “on-page” covers on a store:
- Query and intent: the URL should match how people shop (product, category, problem), not only the internal category code
- Title and meta description: unique, accurate, not stuffed
- URL path: readable, stable, not a filter accident
- Headings: one H1, then H2s for specs, delivery, materials
- Copy: enough unique language to distinguish SKUs that share a parent
- Images: real filenames and alt that describe the product, plus dimensions for LCP
- Schema: Product and Offer on PDPs, BreadcrumbList, no fake reviews
- Internal links: breadcrumbs, related products with descriptive anchors, hub categories
What it does not cover: buying links, changing your theme for fashion, or a blog strategy that never touches the catalogue. Those can wait until the template is honest.
Why on-page SEO changed for stores in 2026
On-page SEO changed for stores in 2026 because AI answers cite product HTML, Google still wants unique documents, and thin Magento or Shopify collections look identical to a machine. The old “300 words on every category” advice was clumsy. The new failure is zero words and a filter tree.
AI search does not replace on-page work. It raises the cost of duplicate titles and missing offers. If five colour variants use the same description, an answer engine will mash them. If the collection has no intro, it may cite a competitor’s category that does.
Platform notes I actually use:
Shopify: titles and descriptions in admin, plus theme JSON-LD. Metafields for unique spec copy. Collection description is not optional if you want that collection to rank. I wrote platform specifics in the Shopify collection notes when that post is the right next click. Here the rule is the same: unique documents.
Magento: layered navigation can create extra documents you never wrote. On-page work includes saying which URLs are allowed to exist. See the Magento facet post from this site when filters are the mess.
WooCommerce: product short description in the template vs long description below the fold. Put the distinguishing facts where they render in HTML for a guest, not only in a tab that a page builder hides.
Consent and speed sit beside on-page. A product page that cannot paint because of tags will not be a good document. I still treat copy and headings as on-page, and JS weight as performance, and I run both on the same PDP.
How on-page SEO works on a catalogue, not a blog
On-page SEO on a catalogue works by making each indexable template type a unique, crawlable document, then repeating that in the theme so merchandisers cannot accidentally ship 8,000 clones. You do not hand-write every SKU first. You fix the template, then you write exceptions.
I group URLs:
Homepage: brand and purpose. Title that is not only the legal entity name plus “Home”.
Collections / categories: one primary keyword family per URL. Intro copy that names the products and the differentiator. Filters as UX, not as a thousand extra indexable pages.
Products: H1 is the product name people search. First paragraph says what it is, who it is for, and the fact that separates it from the next SKU. Specs in HTML. Price and stock visible. Schema that matches.
CMS and guides: only if they earn links into collections and products. An orphan “buying guide” is a blog with extra steps.
Then I write titles. 50 to 60 characters is still the practical window for what Google often shows, though Google rewrites titles. Unique matters more than packing the brand at the front of every SKU. Details are in title tags and meta descriptions that get clicks.
Then headings. One H1. Collection H1 should match the category name, not a marketing slogan that never appears in the title. Product H1 should not be a different poetic line from the title unless you like mixed signals.
Then body. I am not chasing a word count for its own sake. I am chasing uniqueness. Two configurables that differ only by size can share a parent URL. Two materials that shoppers search separately need different sentences. Magento simples that are indexable each need a reason to exist as a document.
Then schema. Product, Offer, Breadcrumb. Articles on the journal. The how-to is in schema markup for product and article pages. On-page SEO without markup still ranks sometimes. Markup without unique on-page content is a decorated empty box.
Then internal links. Category to child products with the product name as the anchor. Product to parent category and to two or three related SKUs that are actually related. Breadcrumbs that match schema. No “click here”. No sidebar of every manufacturer.
Images: filename and alt from the product, width and height, modern formats. Alt is not a keyword dump. It is a description of the image.
I check the rendered HTML as a guest. Page builders and apps love to put the unique copy in a tab that never makes it into the first HTML payload. Google can render JS. AI crawlers are less patient. Server-rendered facts win.
Production checklist for store on-page SEO
- List template types: home, collection, product, CMS, search (search should usually be
noindex).
- Crawl titles and H1s. Duplicate titles are the first finding. Magento and Shopify defaults cause most of them.
- Write a title pattern per template that includes the product or collection name, a modifier only when it is true, and the brand only where it helps.
- Give every indexable collection a unique intro in HTML, even if it is short.
- Give every indexable product a unique first paragraph or a unique spec block. If you cannot, consider consolidating URLs.
- One H1 per page. Match it to the title closely.
- Put specs, delivery and materials in H2s with HTML, not only in PDFs.
- Add Product JSON-LD that matches price and availability. Remove duplicate graphs.
- Fix breadcrumbs and related-product anchors so they use names, not “Learn more”.
- Alt text on product images. Empty alt only for true decorative chrome.
- Canonical matches the URL you want indexed. Variants follow the Magento or Shopify variant policy you actually use.
- Spot-check ten PDPs and ten collections in view-source after every theme release.
What breaks on-page SEO on stores
Automation breaks it. A rule that appends “Buy online” to 20,000 titles looks clever until Google rewrites all of them.
Facets break it. Indexable filter URLs with the parent collection’s copy are duplicate documents.
Apps break it. Shopify and Magento SEO apps inject extra H1s, extra JSON-LD, and popups that steal the first heading.
Translation breaks it. A WPML or Magento store view that copies English titles into another locale is not a localised document.
Out of stock breaks it if you noindex every zero-qty SKU that still has demand. Sometimes you keep the URL with availability in schema. That is merchandising plus on-page, together.
Legal pages in the sitemap do not help product ranking. They also should not steal internal link crawl from collections.
I do not invent on-page conversion percentages. Where I have published numbers, they are store-level: Their Nibs after a Shopify rebuild, and the Magento retail conversion work. On-page was part of those systems. It was not a isolated “we added 150 words” experiment.
How to measure on-page SEO on a store
You measure on-page SEO on a store with Search Console queries landing on product and collection URLs, duplicate title coverage, rich-result validity, and whether AI citations show the right product name and price. Rank tracking on the homepage only is vanity.
I export pages with duplicate titles and missing meta descriptions. I sample snippets. Google rewrite rate is a clue that titles are boilerplate.
I look at landing pages in analytics: collection vs product vs home. Stores that dump everyone on home have an information architecture problem as much as a copy problem.
Content experiments belong on a collection that already has traffic. Do not A/B a title on a SKU Google never crawled.
Related work on this site
On-page SEO at catalogue scale is what I ran as Ecommerce Manager and SEO Coordinator on the Magento retail conversion work, where year-on-year sales increased $2.5 million over three years across three stores. The daily work was titles, category copy, merchandising and measurement together. On a luxury Shopify catalogue the same rules apply with more photography and less SKU noise, which is why I also point at Tamannaah Fine Jewellery: the PDP still has to name the piece, hold the image, and stay trustworthy on a phone.
On-page SEO FAQ
What is on-page SEO for an ecommerce store?
On-page SEO for an ecommerce store is the unique title, headings, copy, images, schema and internal links on each indexable product and collection URL. It is not a homepage rewrite and a blog calendar. If two SKUs share the same document, you do not have two landing pages.
Does on-page SEO still matter if we use AI search?
On-page SEO still matters if you use AI search, because those systems read the same HTML and JSON-LD. Thin, duplicate catalogue pages get skipped or mashed. Clear product names, offers and unique specs are what get cited.
Can a plugin replace on-page SEO on Magento or Shopify?
A plugin cannot replace on-page SEO on Magento or Shopify. It can output titles from a pattern and inject schema. It cannot invent a reason for a collection to exist or make 4,000 identical descriptions unique. Templates plus merchandising still do that.
How long does on-page SEO take on a live catalogue?
On-page SEO on a live catalogue is a template fix in days and a uniqueness programme in months. Duplicate titles you can clear in a release. Unique product copy you do in batches by collection, starting with the URLs that already earn impressions in Search Console.
Keep reading
Contact if you want this kind of work on a live store.