PRESTASHOP SEO AUDIT · PRODUCT SCHEMA · FRIENDLY URLs · AI VISIBILITY
Free PrestaShop SEO Audit
PrestaShop SEO requires correct friendly URL configuration, Product schema with aggregateRating, canonical management for product combinations, category page content, and Core Web Vitals from real field data. DeepSEOAnalysis audits your live PrestaShop store — no admin access, module install, or API key needed — with PrestaShop-specific module and theme template fix guidance for every finding.
WHAT WE CHECK
6 PrestaShop-specific SEO checks
PrestaShop SEO covers friendly URL rewriting, Product schema completeness in server-rendered HTML, combination and layered navigation duplicate URL management, category editorial content, Core Web Vitals from real CrUX data, and AI visibility — with PrestaShop module configuration and Smarty template fixes for each finding.
Friendly URL configuration and rewrite quality
PrestaShop\'s URL rewriting system converts dynamic PHP URLs (`/index.php?id_product=42&controller=product`) into clean SEF URLs (`/mens-running-shoes.html`) when the Friendly URL option is enabled. The audit checks whether friendly URLs are active across the crawled page set — an ID-based URL pattern indicates the rewrite isn\'t functioning. Beyond activation, URL quality matters: PrestaShop generates slugs from the product/category name, which can produce suboptimal patterns (special characters, excessive length, non-keyword terms from default naming). The audit checks: slug character composition (no raw accented characters or special characters that survive urlencode but rank poorly), URL length (PrestaShop slugs can be very long for products with long names — keep under 75 characters), and URL uniqueness (two products with identical names but different IDs can generate duplicate slugs — PrestaShop appends IDs to resolve, but the resulting URLs are less readable). Also checks: `.htaccess` rewrite rules are in place, `mod_rewrite` is functioning (a 404 on a product SEF URL indicates a missing/broken `.htaccess`), and the `Sitemap` directive in `robots.txt` points to the correct SEF sitemap URL.
Product schema and aggregateRating
PrestaShop doesn\'t output Product JSON-LD by default — the base installation has no structured data for product pages. This means PrestaShop stores miss Google Shopping Rich Results eligibility and Review star display in organic search until schema is added via a module or theme customisation. The audit checks for Product JSON-LD in the server-rendered HTML of each crawled product page: presence of the schema block, required property completeness (`name`, `description`, `image`, `sku`, `offers` with `price`, `priceCurrency`, `availability` as `https://schema.org/InStock`), and `aggregateRating` with `ratingValue` and `reviewCount` for review-enabled products. PrestaShop has native customer review functionality — if reviews are enabled on products, a correctly configured SEO module should read the average rating and review count and output them in `aggregateRating`. Common gaps: the module outputs schema but uses the shorthand `InStock` instead of the required `https://schema.org/InStock` URI; the `image` property points to a thumbnail URL rather than the full-size product image; `price` doesn\'t match the visible page price (a Rich Results disqualifier). The audit flags all of these with the exact module configuration or PHP template fix.
Combination and attribute duplicate content
PrestaShop\'s combination system (product attributes like size, colour, material) can generate multiple URLs for what is essentially the same product in different variants. When combinations have landing pages enabled (`/product-name-red-large.html`, `/product-name-blue-small.html`), each variant is a separate indexable URL with nearly identical content — different only in the selected attribute value. This creates a duplicate content cluster that wastes crawl budget and dilutes the link equity that should concentrate on the main product URL. The audit detects combination-URL patterns in the crawled page set and checks their canonical tag implementation: combination pages should carry `link rel="canonical" href="/product-name.html"` pointing to the base product. Most PrestaShop SEO modules (SEO Expert, SEO Manager) handle this automatically when correctly configured. The audit also checks product attribute filter URLs in category pages — PrestaShop\'s layered navigation generates filter parameter URLs (`/category?id_feature=3&id_feature_val=7`) that require either canonical management or robots.txt disallow to prevent duplicate indexation. PrestaShop\'s "Indexed URL in Google for attribute" setting in the layered navigation module controls this.
Category page content and hierarchy
PrestaShop\'s category pages (`/category-name/`) are the primary commercial ranking pages for broad product queries. Common SEO gaps: no editorial description on category pages (add via Catalog → Categories → Description field — PrestaShop\'s TinyMCE editor allows rich HTML descriptions that appear above or below the product grid depending on theme placement); shallow category page authority from limited internal links (top-level navigation often only links the main menu to category pages, without cross-category contextual links); deep sub-category nesting at 4+ clicks from the homepage (flatten with breadcrumb navigation and a mega-menu that links directly to key sub-categories). The audit checks category page content length (thin descriptions under 100 words are flagged), canonical tag self-reference at each hierarchy level (parent category at `/shoes/` canonicalising to `/shoes/mens/` incorrectly), breadcrumb navigation presence and BreadcrumbList JSON-LD (PrestaShop\'s native breadcrumb is HTML only — schema requires a separate JSON-LD block), crawl depth from the homepage to each category level, and internal link count per category page (categories with few inbound links are under-powered for their commercial query targets).
Core Web Vitals for PrestaShop
PrestaShop storefronts are PHP-rendered and served from the web server — there\'s no JavaScript rendering gap in the sense of a headless CMS or React SPA. However, PrestaShop themes and installed modules contribute to Core Web Vitals performance. **LCP** — the first product image or category hero image is almost always the LCP element. Ensure it uses `fetchpriority="high"` in the theme template (edit `product.tpl` or `category.tpl` in your theme). Enable image compression and WebP conversion via a PrestaShop module (WebP module, Image Optimizer) or at the server level (nginx `image_filter`, Imagick). **INP** — PrestaShop\'s JavaScript for cart, quickview, and wishlist; and third-party modules that inject storefront JavaScript (live chat, loyalty, popups). Defer non-critical module JS using PrestaShop\'s resource management settings or a performance module (PrestaShop Page Speed, Cache Cleaner). **CLS** — product images without explicit width and height in the theme template; web font FOUT; module-injected banners after initial paint. The audit uses real CrUX field data from actual Chrome users — mobile and desktop separately — to score LCP, INP, and CLS against Google\'s Good/Needs Improvement/Poor thresholds with PrestaShop-specific template and module fix guidance.
AI visibility for PrestaShop stores
Add `llms.txt` at the PrestaShop store root — create the file via FTP/SFTP at `/public_html/llms.txt` (or the PrestaShop root directory). The file lists your key content sections and their purposes in plain text format. Verify AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Amazonbot) are not blocked in `robots.txt` — PrestaShop\'s default `robots.txt` (generated via Tools → Generate → Robots File) typically allows all crawlers for the storefront but should be checked after any manual modifications. For FAQPage JSON-LD on product and category pages: add via a PrestaShop SEO module that supports FAQPage schema, or add directly to the theme template (`product.tpl`) using a PHP-generated JSON-LD block that reads from product description fields or a dedicated FAQ custom field. For category pages: structure the HTML description field with question-format `<h2>` headings ("What to look for in [category]?") to contribute to the question-heading ratio signal. The audit checks all five AI visibility signals — llms.txt, AI crawler access, FAQPage/HowTo schema in server-rendered HTML, question-heading ratio (≥20%), and content chunkability (≤400w avg section) — with PrestaShop module and template fix guidance.
HOW IT WORKS
Audit your PrestaShop store in 60 seconds
- Enter your PrestaShop store URL. No admin access, module installation, or FTP credentials needed — the audit crawls the public HTTP output as Googlebot would. Works with all PrestaShop versions (1.6, 1.7, 8.x) and any installed theme.
- We crawl and analyse. The engine checks friendly URL patterns across all crawled pages, validates Product schema in the raw server HTTP response (detecting module schema injection gaps), identifies combination URL duplicate patterns, checks layered navigation filter URL canonicals, measures CrUX Core Web Vitals from real Chrome field data, and evaluates all five AI visibility signals.
- You get a prioritised report. PrestaShop-specific issues first — friendly URL configuration, Product schema without aggregateRating, combination canonical gaps, category thin content — then general SEO, each with PrestaShop module settings paths, Shop Parameters configuration, and Smarty template code for the fix.
FAQ
Questions about the PrestaShop SEO audit
Does PrestaShop have good SEO out of the box?
PrestaShop\'s SEO capabilities out of the box are functional but require configuration. What works by default: it generates title tags and meta descriptions from product/category names (though template-based, not hand-crafted), it produces a sitemap via the Google Sitemap module, and the URL rewriting system (when mod_rewrite is enabled) generates clean SEF (Search Engine Friendly) URLs. What requires configuration: the "Friendly URL" option in Shop Parameters → SEO & URLs must be explicitly enabled (it\'s sometimes off by default on fresh installs); the default title tag format "{name} - {my-shop}" may not be keyword-optimal; PrestaShop\'s combination and attribute pages (size/colour variants) generate separate URLs that need canonical management; and Product schema isn\'t output by default — requiring a module or theme customisation. PrestaShop has a rich ecosystem of SEO modules (SEO Expert, SEO Manager, Prestashop SEO) that add features like per-page meta overrides, Product JSON-LD, and automated redirects.
How do I handle PrestaShop product combinations for SEO?
PrestaShop\'s product combinations (e.g., a shoe available in sizes S/M/L and colours red/blue/black) can create multiple product variant URLs if combinations have their own landing pages enabled. The SEO approach: (1) Ensure the main product page is canonical — all combination variant URLs should carry a canonical tag pointing to the base product URL (`/product-name.html`). Most PrestaShop SEO modules handle this automatically. (2) Disable combination-specific URLs in the SEO & URLs settings if they don\'t serve distinct ranking purposes — most size/colour variants don\'t have separate search demand and indexing them creates duplicate content. (3) If certain high-volume combinations have their own search demand (e.g., "red running shoes" has meaningful search volume separate from "running shoes"), consider dedicated product pages rather than URL parameters. (4) Verify in Google Search Console that combination URLs don\'t appear in the Coverage report as separately indexed pages — they should show as "Duplicate, Google chose different canonical."
What are the most common PrestaShop SEO problems?
The five most common PrestaShop SEO issues: (1) **Friendly URLs not enabled** — PrestaShop defaults to ID-based URLs (`/index.php?id_product=42&controller=product`) rather than SEF URLs (`/product-name.html`). Enable in Shop Parameters → SEO & URLs → Friendly URL. Requires mod_rewrite enabled on the server and an `.htaccess` file in the PrestaShop root. (2) **Duplicate content from combinations** — product combination URLs indexed without canonical tags. (3) **Missing Product schema** — no `aggregateRating` or incomplete `offers` properties, limiting Rich Results eligibility. (4) **Thin category pages** — category pages with no description content beyond the product grid. Add descriptions via the category editor in Catalog → Categories. (5) **Admin panel crawlability** — PrestaShop\'s `/admin*/` directory should be blocked in robots.txt; the admin URL is randomised by default but should still be disallowed.
Is the PrestaShop SEO audit free?
Yes. The complete audit is free with no signup and no email gate. Paid plans add saved history, scheduled monitoring, larger crawls (up to 1,000 pages), and agency workflows.