What Is Indexability? How to Check Indexability in PrestaShop

Indexability describes whether a web page is eligible to be included in a search engine's index and potentially appear in search results.

For a PrestaShop store, indexability matters because not every URL should be treated the same way. Important product pages and category pages usually need to be available for indexing, while URLs such as cart pages, customer account pages, internal search results, or unnecessary URL variations generally do not need organic search visibility.

The goal is therefore not to make every URL indexable. It is to make sure the right pages can be indexed while unnecessary pages are kept under control.

What Is Indexability?

When a search engine discovers and crawls a page, it analyzes the page and determines whether it may be added to its index.

A page that is indexable is technically eligible to be included in that index.

However, three concepts should not be confused:

• Crawlable: Search engines can discover and access the page.
• Indexable: The page is eligible to be indexed.
• Indexed: The search engine has actually included the page in its index.

This means a page can be crawlable and indexable but still not be indexed by Google.

For example, Google may crawl a product page successfully and find no noindex directive, but still decide not to index it because it is very similar to another page or provides little unique search value.

Crawlability and indexability are closely related, but they address different parts of how search engines process your website.

Learn more about crawlability vs. indexability ->

Why Is Indexability Important for PrestaShop SEO?

Search engines can only show pages in organic search results if those pages are available and suitable for indexing.

For an ecommerce store, this makes indexability particularly important for pages such as:

• Product pages that customers may search for.
• Category pages targeting broader product searches.
• CMS pages containing useful information.
• Manufacturer or brand pages that provide useful search landing pages.
• Other content created specifically to attract organic traffic.

If an important product or category page is accidentally set to noindex, the page may work perfectly for visitors navigating your store but be prevented from appearing in search results.

However, the opposite problem can also occur.

PrestaShop stores can generate many URLs through filters, sorting options, search functions, parameters, product combinations, and other ecommerce functionality. Allowing every URL to be indexable can create large numbers of low-value or duplicate pages.

Therefore, good indexability management is not about maximizing the number of indexed URLs.

The goal is to make sure the pages that provide meaningful search value can be indexed while unnecessary URLs are kept out of the index where appropriate.

What Can Prevent a PrestaShop Page from Being Indexed?

Several factors can prevent an important page from being indexed or cause search engines to choose another URL instead.

The Page Has a Noindex Directive

A noindex directive tells search engines that a page should not be included in their search index.

It can commonly appear in a page's HTML as:

<meta name="robots" content="noindex">

Using noindex intentionally can be useful for pages that should not appear in search results.

The problem occurs when it is applied to an important page by mistake.

For example, after changing SEO settings, installing a module, modifying a theme, or migrating a store, important products or categories could unintentionally become noindex.

To perform a quick check:

1. Open the page.
2. View the page source.
3. Search for robots.
4. Check whether a noindex directive is present.

If an important page unexpectedly contains noindex, investigate which PrestaShop, theme, or module setting is generating the directive before changing it.

Search Engines Cannot Properly Crawl the Page

Indexability and crawlability are different, but they are closely connected.

Before a search engine can properly process a page for indexing, it generally needs to be able to discover and access that page.

Crawlability problems may be caused by factors such as:

• txt restrictions.
• Poor internal linking.
• Inaccessible navigation.
• Server errors.
• Security or firewall restrictions.
• Excessive or problematic URL variations.

Because crawlability involves its own set of technical checks, it should be investigated separately when search engines have difficulty reaching important pages.

Learn how to check crawlability in PrestaShop ->

Google Selects Another URL as Canonical

Several URLs can sometimes lead to identical or very similar content.

Search engines may therefore select one URL as the representative, or canonical, version.

For example, URL variations created by parameters, filters, combinations, or different navigation paths may represent substantially similar content.

A page can contain a canonical declaration such as:

<link rel="canonical" href="https://example.com/preferred-url">

You can perform a quick check by viewing the page source, searching for canonical, and looking at the URL specified in the tag.

If the canonical points to another URL, the current URL is indicating that another version should generally be treated as the preferred version.

Canonicalization can become complex when multiple versions of products or categories exist, so choosing and configuring canonical URLs should be handled as a separate topic.

Duplicate or Very Similar Pages Exist

Ecommerce stores naturally generate similar pages.

In PrestaShop, this can happen through:

• Sorting options.
• URL parameters.
• Product combinations.
• Similar category structures.
• Multiple URLs leading to substantially similar content.

Search engines do not necessarily need every variation to appear independently in search results.

If several URLs contain identical or highly similar content, Google may choose one representative URL and exclude other versions from its index.

Managing these situations can involve several different SEO mechanisms, including URL structure, canonicalization, crawl controls, and indexing directives.

Because the correct solution depends on how the URLs are generated and what purpose they serve, duplicate URL management should be evaluated separately rather than applying the same rule to every URL variation.

Google May Choose Not to Index Low-Value Pages

Removing technical barriers does not guarantee that a page will be indexed.

A page might:

• Return 200 OK.
• Be crawlable.
• Have no noindex directive.
• Use an appropriate canonical URL.

and still not appear in Google's index.

Search engines ultimately decide which pages they consider useful enough to include.

Pages that may provide limited independent search value include:

• Empty category pages.
• Pages with very little unique content.
• Near-duplicate pages.
• Automatically generated URLs.
• Pages that provide almost the same information as another URL.

This distinction is important when diagnosing indexing problems.

If a page is technically indexable but Google does not index it, repeatedly changing technical indexing settings may not solve the underlying problem. The page itself, its uniqueness, its relationship to other pages, and its value to search users may also need to be evaluated.

Making a page technically indexable does not guarantee that Google will index it.

The Page Redirects, Returns an Error, or Is Unavailable

The HTTP response of a URL also matters.

Common responses include:

• 200: The page is available normally.
• 3xx: The URL redirects to another location.
• 404: The requested page cannot be found.
• 5xx: The server encountered an error while serving the request.

If you expect a specific product, category, or content page to be indexed, first make sure that its intended URL actually returns a normal 200 response.

For example, if an old product URL redirects to a new product URL, search engines will normally treat the destination as the page that matters rather than indexing both URLs independently.

Redirects, 404 errors, and other HTTP responses have different purposes and should be investigated separately when they become a significant issue.

Which PrestaShop Pages Should Usually Be Indexable?

Not every URL in a PrestaShop store needs organic search visibility.

A useful starting point is to classify URLs according to their purpose and whether they provide independent value to search users.

These are general guidelines, not absolute rules.

For example, a manufacturer page containing useful information, products, and content that matches real search demand may be valuable as an organic landing page. A nearly empty manufacturer page may not provide the same value.

Filter URLs require particular care. Some filtered combinations may represent useful landing pages with genuine search demand, while thousands of automatically generated filter combinations may provide little independent value.

The decision should therefore be based on whether a page:

• Serves a meaningful search intent.
• Provides useful and sufficiently distinct content.
• Represents a page you actually want users to discover through search.
• Has a clear role within the store's SEO structure.

The objective is not to follow a universal rule such as "index all categories" or "noindex all filters." It is to determine which URLs deserve to function as search landing pages for your particular store.

How to Check Indexability in PrestaShop

You do not need to perform a complete technical audit every time you want to check one URL.

Start with a few fundamental signals.

Check the Meta Robots Directive

Open the page source and search for:

<meta name="robots"

Then check whether the directive contains noindex.

If an important page unexpectedly has noindex, determine where that directive is being generated.

Do not simply remove noindex from every page. Some pages may intentionally be excluded from search.

Check the Page's HTTP Status

Confirm that the URL you want indexed returns a normal 200 OK response.

If the URL redirects, returns a 404, or produces a server error, investigate why before looking for more complicated indexing problems.

This is particularly useful after:

• Changing URLs.
• Removing products.
• Restructuring categories.
• Migrating a store.
• Changing redirect rules.

Check the Canonical URL

View the page source and search for:

rel="canonical"

Check which URL is specified.

If you expect the current page to be the preferred version but its canonical points elsewhere, investigate the canonical configuration.

Do not automatically change the canonical to point to itself. The existing configuration may be intentional, especially when duplicate or variant URLs are involved.

Check the URL in Google Search Console

Google Search Console's URL Inspection tool can show how Google currently understands a particular URL.

Enter the URL and review information such as:

• Whether the URL is indexed.
• Whether Google can access the page.
• The reported indexing status.
• The user-declared canonical.
• The canonical selected by Google, where available.

Pay particular attention when the canonical you declared and the canonical Google selected are different.

Google Search Console can report several different reasons why a URL is not indexed. Understanding those statuses may require further investigation because different statuses can indicate very different situations.

Review Different Types of Important Pages

Do not assume that checking one product tells you the indexing condition of your entire store.

Review representative URLs from different page types, such as:

• Product page.
• Category page.
• CMS page.
• Manufacturer page, if important to your SEO strategy.

If one individual product has a problem, the issue may be page-specific.

If many products or all category pages show the same unexpected behavior, the problem may come from a shared template, module setting, or store-wide SEO configuration.

A Simple PrestaShop Indexability Checklist

For an important page that you expect to appear in search, check:

• Does the page return 200 OK?
• Is it free from an unintended noindex directive?
• Can search engines crawl the page?
• Does the canonical point to the intended URL?
• Does the page provide unique and useful search value?
• Is the page internally linked where appropriate?
• Is the preferred URL included in the XML sitemap where appropriate?
• Does Google Search Console show the expected indexing status?
• Is Google selecting the expected canonical URL?
• Are unnecessary URL variations being kept out of the index where appropriate?

If a page passes the basic technical checks but remains unindexed, do not assume there must be another hidden indexing setting. Evaluate the page's content, uniqueness, search value, and relationship with similar URLs as well.

Manage Indexability with PrestaHero SEO Audit

Checking SEO signals manually across hundreds or thousands of PrestaShop pages can quickly become time-consuming.

PrestaHero SEO Audit brings important technical SEO tools together in your PrestaShop back office, helping you analyze and manage elements such as URLs, canonical settings, XML sitemaps, robots.txt, redirects, and other SEO factors across your store.

This makes it easier to identify technical issues and keep important SEO signals organized as your catalog grows.

Check your store with PrestaHero SEO Audit

Make the Right Pages Available for Search

Good indexability does not mean putting every URL in Google's index.

For a PrestaShop store, the objective is to make valuable products, categories, and content available for indexing while keeping duplicate, utility, and low-value URLs under control.

Start with the fundamental signals: HTTP status, indexing directives, crawlability, canonical URLs, and Google Search Console. When those signals are correct but an important page still does not appear in the index, look beyond technical eligibility and evaluate whether the page provides enough unique value to deserve independent search visibility.

Ultimately, a healthy indexing strategy is less about how many pages Google indexes and more about whether Google can index the pages that matter to your store.