Skip to content
Back to blog

Learning note

What I learned from improving ecommerce SEO pages in a real CMS

Practical lessons from improving ecommerce pages with metadata, page structure, internal links, image optimisation and CMS constraints.

20 May 20265 min read
SEOAnalyticsCMSCommercial WebLearning

SEO work is not only writing text

Working on ecommerce pages taught me that SEO is not only about writing product descriptions or adding keywords.

Good ecommerce SEO also involves page structure, metadata, internal links, image optimisation, category context, user intent and technical constraints. A page needs to make sense for search engines, but it also needs to help a real customer understand what they are looking at.

That balance is especially important on ecommerce sites because the page has a business purpose. The goal is not just traffic. The goal is useful, relevant traffic that can understand the product or category.

CMS constraints change the way you build pages

A normal development environment gives you a lot of control. A CMS often does not.

Sometimes the available editing area is limited. Sometimes styling needs to be done inside existing content blocks. Sometimes the HTML has to work around templates that cannot easily be changed.

That means the work becomes more practical. The question is not always “what is the ideal implementation?” Sometimes it is “what is the best reliable implementation inside this system?”

That helped me think more about maintainability and constraints.

Metadata needs to be specific

One lesson from product and category page work is that metadata should be specific enough to describe the real page.

A weak meta title or description can be too generic. A better one should explain what the page is about, include useful commercial keywords, and still read naturally.

For ecommerce pages, that often means thinking about:

  • product type
  • use case
  • audience
  • important specifications
  • buying intent
  • category wording

The best metadata is clear, useful and not overstuffed.

Internal links help users and search engines

Internal links are easy to underestimate.

They can help users move to related products, categories, guides or supporting pages. They can also help search engines understand how pages connect.

The most useful internal links are not random. They should support the page topic and give the user a sensible next step.

For example, a guide page can link to relevant products, and a product category can link to related tools or supplies. That creates a better journey than leaving every page isolated.

Image optimisation matters

Ecommerce pages often rely heavily on images. Large or poorly prepared images can hurt page speed and make the user experience worse.

Image work can include:

  • reducing file size
  • using clear filenames
  • writing descriptive alt text
  • adding useful image title text where appropriate
  • checking that images support the page content

The main lesson is that images should not be treated as decoration only. They are part of the page content.

Analytics helps avoid guessing

SEO work should not be based only on assumptions.

Analytics tools and search data can help show what users are doing, what pages are visible, and where issues might exist. They do not always give a perfect answer, but they help guide decisions.

One important lesson is to compare data sources when something looks wrong. A drop in one analytics tool might mean real performance changed, but it might also mean tracking, consent or configuration changed.

That makes investigation and context important.

What I learned overall

Commercial web work has helped me see the connection between development, SEO, users and business goals.

A technically valid page is not always a useful page. A good page should be structured clearly, load well, explain the product or topic, link to useful next steps and fit within the constraints of the system it is built in.

That is one of the reasons I think SEO and web operations experience is useful for software development. It teaches practical thinking, attention to detail and the need to understand the user, not just the code.