Journal
SEO, GEO, AI search — notes on how brands get read and found.
EC-CUBE
EC-CUBE Not in Search: Five Checks
Five checks for an EC-CUBE shop missing from search and AI search: assets lost in a 2 to 4 migration, three options for the missing XML sitemap, verifying plugin structured data, and a requirements sheet for your agency.
EC-CUBE: The SEO and AI Search Requirements Sheet to Hand Your Agency
EC-CUBE sites are usually built by an agency, which makes SEO and AI search requirements items that don't get in unless you say so. This article gives you a ready-to-use requirements table to hand over before the build, covering six areas: URLs, metadata, structured data, sitemaps, speed, and bot handling.
How Far Can You Trust EC-CUBE SEO Plugins
EC-CUBE SEO plugins are reliable enough for meta tags and sitemaps. Structured data has to stay in sync with product data, so having a mechanism that keeps validating the output is more dependable than leaving everything to a plugin. This article covers where plugins fit, what you should own yourself, and how to decide.
Three Options for an EC-CUBE 4 XML Sitemap
The EC-CUBE 4 series doesn't generate an XML sitemap by default. This article compares three options (a plugin, a custom build generated by a command or controller, and generation with an external tool) on update tracking, splitting, lastmod, and operational load. It also covers how to choose based on product count and development capacity.
SEO Assets Lost in an EC-CUBE 2 to 4 Migration
Migrating from EC-CUBE 2 to 4 is not a simple version upgrade. It is a site move in which URL structure, templates, and plugins all change. This article covers the four assets most easily lost in migration (URLs, metadata, structured data, and sitemap), the steps to carry each one over, and the metrics to check afterward.