HomeBlogTechnical website errors: what to fix first and what add-ons can help
Technical website errors: what to fix first and what add-ons can help
Website promotion doesn’t start with text or links—it starts with a technical audit. You can write great content all you want, but if your site has duplicate pages, empty meta tags, and no canonical on pagination, search engines literally can’t tell which page to show in the results, and they end up spreading your site’s ranking weight across multiple copies.
This article kicks off a series on Search and Generative Optimization by Hand. Over the coming weeks, we’ll break down CS-Cart e-commerce SEO one topic at a time. We’re starting with the fundamentals: technical errors. What to fix first, how it impacts organic traffic, and which issues you can resolve with a ready-made add-on versus handling manually through the admin panel.
Why a technical audit is the first step, not text or links?
Before you write a single piece of content or invest in a single link, you need to make sure search crawlers can actually crawl and understand your site properly. Without that, any content effort will just hit a technical wall.
Below is a list of common CS-Cart technical errors. For each one, we’ll cover what it affects, how to fix it manually, and which ready-made add-on can handle it for you.
Why does the same product show up under multiple URLs?
The problem: the same product or category is accessible through several different URLs—/category and /category/, with www and without. Search engines see these as separate pages with identical content.
What it affects: ranking weight gets split across duplicates, pages end up competing with themselves in search results, and you waste crawl budget.
How to fix it:
1. In the CS-Cart admin panel, set a single URL format (with or without a trailing slash) and set up 301 redirects from all variants to the canonical version. Doing this manually requires server-level configuration and careful handling to avoid breaking existing links.
or
2. The SEO Optimization add-on automatically cleans up extra slashes across all URLs and locks in the link format without any code changes.
Why do hundreds of product cards look identical to search engines?
The problem: dozens or hundreds of product cards all share the same Title—often just the product name, with no description, category, or attributes.
What it affects: search engines can’t tell the difference between pages, your snippet in search results is vague and unhelpful, and click-through rates suffer.
How to fix it:
1. Write unique Titles and Descriptions manually for every single page. This is only realistic if you have a very small catalog.
or
2. The SEO Templates add-on automatically fills in Titles, Descriptions, and human-readable URLs using a template based on product attributes. When you change the template, old URLs get a 301 redirect automatically.
Why separate Title and H1 if they're basically the same anyway?
The problem: the product page Title is identical to the H1 heading—meaning you’re missing a chance to add extra keywords to the Title (e.g., “buy,” city, synonyms).
What it affects: Title and H1 serve different jobs—H1 is for the user, Title is mainly for search engines and the snippet. When they’re the same, you lose some relevance for related queries.
How to fix it:
1. Add more variety to the Title template while keeping the H1 shorter and cleaner.
Why doesn't the search engine notice updates on the site?
The problem: your pages aren’t telling search engines when they were last updated.
What it affects: search engines re-crawl pages for freshness less frequently, which can delay re-indexing after changes—especially problematic for blogs and catalogs with frequently changing prices and stock levels.
How to fix it:
1. Enable proper Last-Modified header delivery at the server level—a job for a technical specialist.
The problem: deleted products, categories, broken internal links, and missing images are returning a 404 status.
What it affects: this is more serious than it looks. A large number of 404 errors signals to search engines that the site has poor technical quality overall. Beyond the ranking impact on the entire domain, users who land on a dead page simply leave—and your bounce rate goes up.
How to fix it: if a 404 is coming from a deleted product—set up a 301 redirect to the parent category or a similar replacement product, and avoid redirect chains since they slow down crawlers. If a 404 is just a broken link in your content or a missing image, track it down and replace it—don’t redirect it. Regularly check the 404 error logs in Google Search Console and clear them out in batches, rather than letting the list pile up for months. This is one of those issues where there’s no “set it and forget it” add-on—it requires ongoing manual review. You’ll need to dig into the reports and handle each case individually.
What happens to pages when you change the catalog structure?
The problem: when you delete a product, change a category URL, or migrate from another platform, old links aren’t redirected to new ones—users and search engines hit 404s.
What it affects: you lose accumulated page ranking weight, break external links, and drop in positions whenever the site structure changes.
How to fix it:
Keep a mapping table of old and new URLs and manually set up redirects every time you make a structural change—labor-intensive if your catalog changes often.
or
The Search Engine Optimization (SEO) module includes export and import of 301 redirects and a built-in editor for search-friendly names, which is especially handy for bulk structural changes.
Как решается:
1. Keep a mapping table of old and new URLs and manually set up redirects every time you make a structural change—labor-intensive if your catalog changes often.
или
2. The SEO Optimization add-on includes export and import of 301 redirects and a built-in editor for search-friendly names, which is especially handy for bulk structural changes.
Why do heavy images hold back your rankings?
The problem: products are loading original JPG or PNG files that are 1–3 MB each—especially painful for large catalogs.
What it affects: page load speed is both a ranking factor and a direct contributor to bounce rates, particularly on mobile.
How to fix it:
1. Compress images manually through external tools before uploading and convert them to WebP—effective but slow if you have hundreds of items.
or
2. The WebP Images add-on automatically converts all site graphics to WebP without any quality loss. If the user’s browser doesn’t support the format, it falls back to the original image.
Why aren't product images bringing in traffic from image search?
The problem: images without the alt attribute are invisible to image search and less accessible to screen readers.
What it affects: you miss out on traffic from Google Images, and your site becomes harder to use for people with visual impairments.
How to fix it:
1. Write alt text manually for each image—completely impractical for a catalog with thousands of products.
or
2. The SEO for Images add-on automatically generates alt and title attributes based on a template using the product or category name, and renames image files according to a template as well.
Why can a sitemap actually hurt indexing instead of helping it?
The problem: the sitemap doesn’t update automatically, includes pages that no longer exist, exceeds size limits, or leaves out important sections—like the blog, brands, or tags.
What it affects: slower and incomplete indexing, which is especially problematic for catalogs with frequently changing inventory.
How to fix it: manually keeping the sitemap up to date is unrealistic for a dynamic catalog. The Extended SitemapXML add-on generates the sitemap on a schedule, splits it into parts when limits are exceeded, excludes empty categories and products with no stock or price, and creates a separate image sitemap.
Why do catalog pages with pagination compete against each other?
The problem: catalogs with a lot of products are split across multiple pages, and without a canonical tag, search engines treat them as duplicates.
What it affects: relevance gets diluted across listing pages, and products on the second page and beyond risk dropping out of the index.
Important nuance: search engines handle this differently. Yandex recommends pointing the canonical for all pagination pages to the first page of the section. Google, on the other hand, expects each pagination page to have its own self-referencing canonical—for Google, pagination pages are independent content, not duplicates. If your store is targeting both Yandex and Google, you’ll need to pick a primary search engine or implement different rules for different crawlers.
How to fix it:
1. Set up the canonical generation rule through template code—a task for a developer.
or
2. The SEO Optimization add-on manages page canonicalization, including separate pagination settings, with no code changes required.
Why isn't the price and rating showing up next to my site link in search results?
The problem: product pages, categories, reviews, and blog posts aren’t passing structured data to search engines—just plain text and raw HTML with no markup.
What it affects: without microdata, search engines see your page “flat”—they can’t tell where the price, rating, availability, or brand is. That means you lose out on rich results in search—prices, star ratings, stock status right in the snippet—which significantly boost click-through rates compared to a standard blue link. Most of the top 10 results in any search engine use microdata. So not having it puts you at a competitive disadvantage.
How to fix it:
1. Manually mark up pages according to Schema.org documentation, embedding JSON-LD into the template for each page type. This requires a developer and validation through Google’s testing tool.
or
2. The JSON-LD Markup add-on automatically marks up products, reviews, blog posts, and company information. CS-Cart comes with basic product page microdata out of the box, but everything else stays unmarked without the add-on.
Why do catalog filters sometimes do more harm than good for SEO?
The problem: filter combinations (brand, color, size) generate thousands of technical parameter URLs that end up getting indexed as thin, low-quality content.
What it affects: index bloat from irrelevant pages, wasted crawl budget, and the risk of ranking penalties for “junk” content.
How to fix it:
1. Block parameter-based URLs from indexing via robots.txt or meta robots. This requires regular monitoring to make sure you don’t accidentally block important pages.
or
2. The SEO for Filters add-on turns selected filter combinations into dedicated landing pages with clean, human-readable URLs, while all other combinations get search-friendly names without bloating the index.
How do you prioritize when you can't fix everything at once?
If you’re working with limited resources, a sensible order would be:
Duplicate pages—this is the foundation; without it, nothing else matters.
404 errors and redirects directly affect how search engines assess your site’s technical quality.
Canonical on pagination and filters saves crawl budget.
Meta tags, alt attributes, and microdata directly impact click-through rates and visibility in search results.
XML sitemap is critical if your catalog changes frequently.
WebP image conversion gives you a measurable speed boost.
Most CS-Cart technical errors can be fixed with ready-made add-ons without touching a single line of code. That’s faster and safer than custom development. However, if your site has special changes—a non-standard theme or custom work done by third-party developers—an off-the-shelf solution might need some adaptation.
If you’d rather skip the manual data digging and log analysis, just order a technical audit. You’ll get a prioritized list of issues without having to check everything yourself.
In the next article in this series, we’ll dive into landing pages for low-volume queries—how to turn so-called “junk” filters and subcategories into a reliable source of traffic.
Q&A
How can I tell if my CS-Cart site has technical issues that are hurting its rankings?
The first warning sign is a polished-looking site that isn’t gaining traction in rankings and gets almost no organic traffic, even when you update content regularly. Check Yandex.Webmaster and Google Search Console for indexed page counts, crawl errors, and duplicate content warnings. A quick DIY check: open a product page and a category page, view the source, and look for an empty Title or a missing canonical. If you spot a few of these, it’s more efficient to get a technical audit than to keep guessing.
Do I need to sign up for a monthly SEO retainer just to fix technical errors?
No—these are separate things. Fixing technical errors is a one-off job: you identify them, prioritize them, and resolve them with add-ons or small fixes, not ongoing work. Monthly SEO comes later, once the foundation is solid, to build link equity, create content, and expand your keyword footprint. Many clients handle the technical side as a one-time project and only then decide whether to move into ongoing SEO.
How much does it cost to fix technical errors on a CS-Cart site?
It depends on the catalog size, how many issues are found, and which ones can be solved with a ready-made add-ons versus which require custom work. Some issues (duplicate pages, missing canonical, microdata) can be fixed by buying and configuring an existing add-on, which is cheaper than custom development. You’ll get a much clearer cost estimate after a technical audit, once you have a concrete list of problems.
How soon will I see results after fixing technical errors?
Technical fixes alone won’t push your site to the top of the results. They remove barriers that were keeping search engines from properly evaluating your site. You’ll usually start seeing changes in indexing and crawl behavior within a few weeks after pages are re-crawled. Meaningful gains in rankings and traffic generally require additional content and link work on top of a solid technical base.
What if I don’t have the budget for a technical audit right now—where should I start?
Start with the free reports in Yandex.Webmaster and Google Search Console. They’ll already show you duplicates, 404s, and indexing issues at no cost. Then work through the issues based on the priority order in this article, starting with duplicate pages and 404s. Some problems—WebP, microdata, meta tags—can be fixed by buying a single ready-made add-on without involving a developer. When the list of issues gets too big to handle manually, that’s the time to invest in a full audit.
Conclusion
Technical errors aren’t minor issues you can push aside for later. They’re the foundation, and without them in order, any investment in content and links is only half as effective. Most of them on CS-Cart can be fixed with ready-made solutions and no developer involvement. It’s faster and cheaper than it seems at the start. If you’d rather start with a concrete action plan than with guesswork, order a technical audit. You’ll know exactly what to fix first.
Technical website errors: what to fix first and what add-ons can help
Website promotion doesn’t start with text or links—it starts with a technical audit. You can write great content all you want, but if your site has duplicate pages, empty meta tags, and no canonical on pagination, search engines literally can’t tell which page to show in the results, and they end up spreading your site’s ranking weight across multiple copies.
This article kicks off a series on Search and Generative Optimization by Hand. Over the coming weeks, we’ll break down CS-Cart e-commerce SEO one topic at a time. We’re starting with the fundamentals: technical errors. What to fix first, how it impacts organic traffic, and which issues you can resolve with a ready-made add-on versus handling manually through the admin panel.
Why a technical audit is the first step, not text or links?
Before you write a single piece of content or invest in a single link, you need to make sure search crawlers can actually crawl and understand your site properly. Without that, any content effort will just hit a technical wall.
Below is a list of common CS-Cart technical errors. For each one, we’ll cover what it affects, how to fix it manually, and which ready-made add-on can handle it for you.
Why does the same product show up under multiple URLs?
The problem: the same product or category is accessible through several different URLs—/category and /category/, with www and without. Search engines see these as separate pages with identical content.
What it affects: ranking weight gets split across duplicates, pages end up competing with themselves in search results, and you waste crawl budget.
How to fix it:
1. In the CS-Cart admin panel, set a single URL format (with or without a trailing slash) and set up 301 redirects from all variants to the canonical version. Doing this manually requires server-level configuration and careful handling to avoid breaking existing links.
or
2. The SEO Optimization add-on automatically cleans up extra slashes across all URLs and locks in the link format without any code changes.
Why do hundreds of product cards look identical to search engines?
The problem: dozens or hundreds of product cards all share the same Title—often just the product name, with no description, category, or attributes.
What it affects: search engines can’t tell the difference between pages, your snippet in search results is vague and unhelpful, and click-through rates suffer.
How to fix it:
1. Write unique Titles and Descriptions manually for every single page. This is only realistic if you have a very small catalog.
or
2. The SEO Templates add-on automatically fills in Titles, Descriptions, and human-readable URLs using a template based on product attributes. When you change the template, old URLs get a 301 redirect automatically.
Why separate Title and H1 if they're basically the same anyway?
The problem: the product page Title is identical to the H1 heading—meaning you’re missing a chance to add extra keywords to the Title (e.g., “buy,” city, synonyms).
What it affects: Title and H1 serve different jobs—H1 is for the user, Title is mainly for search engines and the snippet. When they’re the same, you lose some relevance for related queries.
How to fix it:
1. Add more variety to the Title template while keeping the H1 shorter and cleaner.
or
2. The SEO Templates add-on lets you set separate formulas for Title and H1.
Why doesn't the search engine notice updates on the site?
The problem: your pages aren’t telling search engines when they were last updated.
What it affects: search engines re-crawl pages for freshness less frequently, which can delay re-indexing after changes—especially problematic for blogs and catalogs with frequently changing prices and stock levels.
How to fix it:
1. Enable proper Last-Modified header delivery at the server level—a job for a technical specialist.
or
2. The SEO Optimization add-on manages this header without needing any server access.
Why are 404 error pages dangerous?
The problem: deleted products, categories, broken internal links, and missing images are returning a 404 status.
What it affects: this is more serious than it looks. A large number of 404 errors signals to search engines that the site has poor technical quality overall. Beyond the ranking impact on the entire domain, users who land on a dead page simply leave—and your bounce rate goes up.
How to fix it: if a 404 is coming from a deleted product—set up a 301 redirect to the parent category or a similar replacement product, and avoid redirect chains since they slow down crawlers. If a 404 is just a broken link in your content or a missing image, track it down and replace it—don’t redirect it. Regularly check the 404 error logs in Google Search Console and clear them out in batches, rather than letting the list pile up for months. This is one of those issues where there’s no “set it and forget it” add-on—it requires ongoing manual review. You’ll need to dig into the reports and handle each case individually.
What happens to pages when you change the catalog structure?
The problem: when you delete a product, change a category URL, or migrate from another platform, old links aren’t redirected to new ones—users and search engines hit 404s.
What it affects: you lose accumulated page ranking weight, break external links, and drop in positions whenever the site structure changes.
How to fix it:
Keep a mapping table of old and new URLs and manually set up redirects every time you make a structural change—labor-intensive if your catalog changes often.
or
The Search Engine Optimization (SEO) module includes export and import of 301 redirects and a built-in editor for search-friendly names, which is especially handy for bulk structural changes.
Как решается:
1. Keep a mapping table of old and new URLs and manually set up redirects every time you make a structural change—labor-intensive if your catalog changes often.
или
2. The SEO Optimization add-on includes export and import of 301 redirects and a built-in editor for search-friendly names, which is especially handy for bulk structural changes.
Why do heavy images hold back your rankings?
The problem: products are loading original JPG or PNG files that are 1–3 MB each—especially painful for large catalogs.
What it affects: page load speed is both a ranking factor and a direct contributor to bounce rates, particularly on mobile.
How to fix it:
1. Compress images manually through external tools before uploading and convert them to WebP—effective but slow if you have hundreds of items.
or
2. The WebP Images add-on automatically converts all site graphics to WebP without any quality loss. If the user’s browser doesn’t support the format, it falls back to the original image.
Why aren't product images bringing in traffic from image search?
The problem: images without the alt attribute are invisible to image search and less accessible to screen readers.
What it affects: you miss out on traffic from Google Images, and your site becomes harder to use for people with visual impairments.
How to fix it:
1. Write alt text manually for each image—completely impractical for a catalog with thousands of products.
or
2. The SEO for Images add-on automatically generates alt and title attributes based on a template using the product or category name, and renames image files according to a template as well.
Why can a sitemap actually hurt indexing instead of helping it?
The problem: the sitemap doesn’t update automatically, includes pages that no longer exist, exceeds size limits, or leaves out important sections—like the blog, brands, or tags.
What it affects: slower and incomplete indexing, which is especially problematic for catalogs with frequently changing inventory.
How to fix it: manually keeping the sitemap up to date is unrealistic for a dynamic catalog. The Extended SitemapXML add-on generates the sitemap on a schedule, splits it into parts when limits are exceeded, excludes empty categories and products with no stock or price, and creates a separate image sitemap.
Why do catalog pages with pagination compete against each other?
The problem: catalogs with a lot of products are split across multiple pages, and without a canonical tag, search engines treat them as duplicates.
What it affects: relevance gets diluted across listing pages, and products on the second page and beyond risk dropping out of the index.
Important nuance: search engines handle this differently. Yandex recommends pointing the canonical for all pagination pages to the first page of the section. Google, on the other hand, expects each pagination page to have its own self-referencing canonical—for Google, pagination pages are independent content, not duplicates. If your store is targeting both Yandex and Google, you’ll need to pick a primary search engine or implement different rules for different crawlers.
How to fix it:
1. Set up the canonical generation rule through template code—a task for a developer.
or
2. The SEO Optimization add-on manages page canonicalization, including separate pagination settings, with no code changes required.
Why isn't the price and rating showing up next to my site link in search results?
The problem: product pages, categories, reviews, and blog posts aren’t passing structured data to search engines—just plain text and raw HTML with no markup.
What it affects: without microdata, search engines see your page “flat”—they can’t tell where the price, rating, availability, or brand is. That means you lose out on rich results in search—prices, star ratings, stock status right in the snippet—which significantly boost click-through rates compared to a standard blue link. Most of the top 10 results in any search engine use microdata. So not having it puts you at a competitive disadvantage.
How to fix it:
1. Manually mark up pages according to Schema.org documentation, embedding JSON-LD into the template for each page type. This requires a developer and validation through Google’s testing tool.
or
2. The JSON-LD Markup add-on automatically marks up products, reviews, blog posts, and company information. CS-Cart comes with basic product page microdata out of the box, but everything else stays unmarked without the add-on.
Why do catalog filters sometimes do more harm than good for SEO?
The problem: filter combinations (brand, color, size) generate thousands of technical parameter URLs that end up getting indexed as thin, low-quality content.
What it affects: index bloat from irrelevant pages, wasted crawl budget, and the risk of ranking penalties for “junk” content.
How to fix it:
1. Block parameter-based URLs from indexing via robots.txt or meta robots. This requires regular monitoring to make sure you don’t accidentally block important pages.
or
2. The SEO for Filters add-on turns selected filter combinations into dedicated landing pages with clean, human-readable URLs, while all other combinations get search-friendly names without bloating the index.
How do you prioritize when you can't fix everything at once?
If you’re working with limited resources, a sensible order would be:
Duplicate pages—this is the foundation; without it, nothing else matters.
404 errors and redirects directly affect how search engines assess your site’s technical quality.
Canonical on pagination and filters saves crawl budget.
Meta tags, alt attributes, and microdata directly impact click-through rates and visibility in search results.
XML sitemap is critical if your catalog changes frequently.
WebP image conversion gives you a measurable speed boost.
Most CS-Cart technical errors can be fixed with ready-made add-ons without touching a single line of code. That’s faster and safer than custom development. However, if your site has special changes—a non-standard theme or custom work done by third-party developers—an off-the-shelf solution might need some adaptation.
If you’d rather skip the manual data digging and log analysis, just order a technical audit. You’ll get a prioritized list of issues without having to check everything yourself.
In the next article in this series, we’ll dive into landing pages for low-volume queries—how to turn so-called “junk” filters and subcategories into a reliable source of traffic.
Q&A
How can I tell if my CS-Cart site has technical issues that are hurting its rankings?
The first warning sign is a polished-looking site that isn’t gaining traction in rankings and gets almost no organic traffic, even when you update content regularly. Check Yandex.Webmaster and Google Search Console for indexed page counts, crawl errors, and duplicate content warnings. A quick DIY check: open a product page and a category page, view the source, and look for an empty Title or a missing canonical. If you spot a few of these, it’s more efficient to get a technical audit than to keep guessing.
Do I need to sign up for a monthly SEO retainer just to fix technical errors?
No—these are separate things. Fixing technical errors is a one-off job: you identify them, prioritize them, and resolve them with add-ons or small fixes, not ongoing work. Monthly SEO comes later, once the foundation is solid, to build link equity, create content, and expand your keyword footprint. Many clients handle the technical side as a one-time project and only then decide whether to move into ongoing SEO.
How much does it cost to fix technical errors on a CS-Cart site?
It depends on the catalog size, how many issues are found, and which ones can be solved with a ready-made add-ons versus which require custom work. Some issues (duplicate pages, missing canonical, microdata) can be fixed by buying and configuring an existing add-on, which is cheaper than custom development. You’ll get a much clearer cost estimate after a technical audit, once you have a concrete list of problems.
How soon will I see results after fixing technical errors?
Technical fixes alone won’t push your site to the top of the results. They remove barriers that were keeping search engines from properly evaluating your site. You’ll usually start seeing changes in indexing and crawl behavior within a few weeks after pages are re-crawled. Meaningful gains in rankings and traffic generally require additional content and link work on top of a solid technical base.
What if I don’t have the budget for a technical audit right now—where should I start?
Start with the free reports in Yandex.Webmaster and Google Search Console. They’ll already show you duplicates, 404s, and indexing issues at no cost. Then work through the issues based on the priority order in this article, starting with duplicate pages and 404s. Some problems—WebP, microdata, meta tags—can be fixed by buying a single ready-made add-on without involving a developer. When the list of issues gets too big to handle manually, that’s the time to invest in a full audit.
Conclusion
Technical errors aren’t minor issues you can push aside for later. They’re the foundation, and without them in order, any investment in content and links is only half as effective. Most of them on CS-Cart can be fixed with ready-made solutions and no developer involvement. It’s faster and cheaper than it seems at the start. If you’d rather start with a concrete action plan than with guesswork, order a technical audit. You’ll know exactly what to fix first.
Related Services and Add-ons
Subscribe to stay up-to-date!
I want to be notified about ecommerce events.
Subscribe to stay up-to-date!
I want to be notified about ecommerce events.
More articles from this category