Nikola Arsić
DisciplineTechnical SEO, implementedAlso servesSEO agencies, white-labelEngagementDirect, no agency layer

PrestaShop SEO from the person who can actually change the template.

Most PrestaShop SEO is delivered as a PDF: an audit that lists duplicate content, thin categories, missing schema and slow pages, and then waits for a developer. I am the developer. Technical SEO is half of what I do for two agencies on Shopify and BigCommerce, and on PrestaShop the fixes land in the code the same week they are found.

Where PrestaShop loses rankings by default

The platform has a handful of structural SEO problems that every store inherits. Filter navigation can expose every filter combination as a crawlable URL. Pagination, product combinations and the multi-category tree create several addresses for one page. The canonical redirect setting is often left off. Multistore and multilanguage setups emit hreflang that is nearly right, which for Google is the same as wrong. And category pages, the pages that should rank for the money terms, usually carry no copy at all.

None of these are fixed by a module. They are fixed by understanding how the routing, the theme and the modules interact, and then changing the right one.

  • Duplicate content: canonicals, combination handling, pagination, print and filter URLs
  • Filtered URLs: which filters may be indexed, which canonicalise back to the category, which are not followed, per category
  • URL structure and rewrites, with a redirect map for every change so nothing is lost
  • Product, breadcrumb and organisation structured data that matches what the page shows
  • Multilanguage and multistore hreflang that Google actually accepts
  • Core Web Vitals on product and category templates: images, scripts, caching, server response

How the work runs

It starts with your Search Console data and a crawl of the live store, cross-checked against the raw server access log so we know what Googlebot actually requests rather than what the sitemap claims. I keep a free access log viewer on this site for that exact job.

From there the findings are ranked by what they cost you, not by how alarming they look, and implemented in order: template changes, module configuration, routing and redirects, structured data, then content structure on the categories that should carry the revenue. Each change is measured against the position bands in Search Console over the following weeks, so you know which fix moved what.

For SEO agencies

If you are an agency with a PrestaShop client and no developer who knows the platform, this is the arrangement I already run for two agencies on other platforms: you own the client and the strategy, I implement inside the theme and modules, white-label. Your ticket, my commit, your report.

Read the guide first

The PrestaShop SEO guide on this site walks through the settings, the duplicate-content traps and the module decisions in detail, and it is free. Read it, apply what you can, and bring me what is left.

Questions people ask first

Do you do content and link building as well?
I do the technical and structural work, and the on-page structure of category and product templates. For editorial content and outreach I work alongside your agency or writer rather than replacing them.
Which SEO module should we install?
Usually none. Most of what the paid SEO modules do is either already in core since 1.7 or better done in the theme. The exceptions are specific, and the audit names them.
Can you work on a multistore with several languages?
That is the normal case for me. The estate I run is 26 storefronts in 22 markets on one codebase, so multistore hreflang and per-market URLs are daily work.
How do we know it worked?
Search Console, tracked per change. Impressions, position bands and clicks on the affected pages, before and after, with the change date marked. Not a rank tracker screenshot.