WooCommerce SEO Audit: What a Real Manufacturer Site Taught Us

A WooCommerce store can look fine and still leak visibility through a dozen small technical problems. In a recent audit of an Indonesian manufacturer's store, the biggest wins were an incomplete homepage title, five missing Elementor stylesheets, 23 MB of oversized images, pagination that crawlers could not follow, duplicate tag pages, and product pages too thin to answer buyers' questions. None of them needed a rebuild.

This article turns that audit into lessons you can apply to your own store. The client's name is withheld; the numbers are exactly as recorded on 25 August 2026. If you want the full report layout, the public case study has every finding and the 90-day roadmap.

The starting point: good business, weak signals

The business had what usually makes SEO easier: an established factory, ISO 9001:2015 positioning, clear product lines for uniform footwear, and buyers from institutions and companies. The site ran on WordPress, WooCommerce and Elementor, and it worked. But PageSpeed Insights told a different story on mobile:

Google indexes the mobile version of a site, so the mobile column deserves the most attention. The job was to find out why it was weaker, not to chase the score.

Lesson 1: check the page title your theme actually outputs

The homepage title rendered as “- [Brand] Indonesia”: a separator and a brand name with nothing in front. It happens when an SEO plugin's title variable is empty. Four pages, including the homepage and the contact page, also had no H1.

Fix: write a real title that says what the business makes and where, and give each page one clear H1. Check: the browser tab, the rendered H1, and URL Inspection in Search Console.

Lesson 2: Elementor can leave broken CSS behind

Five stylesheet files in /wp-content/uploads/elementor/css/ returned a 404 with an HTML page instead of CSS. Visitors might not notice at first, but it causes layout shifts, wasted requests and inconsistent rendering.

Fix: in Elementor, regenerate files and data, then clear the WordPress and CDN caches. Only dig into CDN or origin rules if the errors survive. Check: each CSS URL should return 200 with text/css.

Lesson 3: WordPress makes small images, but themes still load the big ones

Nine images added up to about 23 MB. Two banners were 4.6 MB each. WordPress had already generated smaller versions, yet the pages requested the full-size originals.

Fix: resize to display size, use WebP or AVIF, make sure srcset is output, and keep PNG only for transparency. Add width, height and alt text. Check: re-run PageSpeed and compare total page weight.

Lesson 4: “Load more” can hide products from crawlers

The crawler flagged /produk/page/2/ as “Pagination URL Not in Anchor Tag”. The next page existed, but not as a normal link. Crawlers and AI agents that don't click buttons may never reach later products.

Fix: output real numbered or Previous/Next links from WooCommerce pagination, even if you keep a Load More button for visitors. Check: view source on page 2 and find page 3 inside an a href.

Lesson 5: product tags quietly duplicate your categories

Two product groups existed as both a category and a tag, with near-identical titles still ending in “Archives”. That splits signals and gives Google two pages to choose from.

Fix: keep categories as the main structure, set redundant tag archives to noindex, stop linking to them, and rename category titles properly.

Lesson 6: thin product pages don't answer buyers

More than 23 pages had fewer than 200 words, from 33 words on the category index to about 180 on a main product. Word count is not a ranking rule, but these pages skipped what buyers need: material, sole construction, sizes, fit, use case, certification, warranty, care and procurement details.

Fix: expand only the pages that matter for search or sales, using verified specifications. A useful product page answers:

• What is it made of, and what is the sole like?
• Which sizes exist, and how does it fit?
• Which work does it suit, and what certification applies to this product?
• What does the warranty cover, and how do I care for it?
• How do institutions or companies order in bulk?

Model names alone (“[Model] Doff”) don't help new buyers either. Add the category and a verified feature to each title.

Lesson 7: don't over-read the Agentic Browsing score

Lighthouse's experimental Agentic Browsing category scored 1/3. It checks things like accessible labels, layout stability and agent-friendly interfaces. It is not a Google ranking score and it does not predict whether ChatGPT or Perplexity will mention you. A missing llms.txt is optional.

Fix: read which checks failed and fix the ones that also help people: labels, stable layout, crawlable content and usable forms.

Lesson 8: GEO starts with access and verifiable facts

One automated request was blocked during the review, while Google-indexed pages stayed visible. That could be a firewall, a security plugin or a rate limit. For AI search, the order of work is simple: make sure verified crawlers can fetch the pages, describe the business and products accurately in schema, and back every claim (certification, founding year, warranty) with current evidence. Schema must match what visitors can see.

The 90-day plan in one table

Does your store have the same problems?

Most WooCommerce stores I review share at least three of these eight problems. Several of them never show up in the browser: they only appear in the page source, the crawl data or the server responses, which is why a store can look fine and still leak visibility. An SEO and GEO audit checks all of them on your store and puts the fixes in order of impact.

Frequently asked questions