Skip to content
  • There are no suggestions because the search field is empty.

ECOM | Google Search Console | Why Pages Aren't Indexed 

Understand why Google Search Console excludes certain URLs from GSC, how BLAZE ECOM automatically filters out duplicate noise to protect your crawl budget, and how to identify whether a non-indexed page requires review.

 

📌 The status examples below illustrate common Search Console reporting patterns and standard BLAZE ECOM behaviors, but this list is not exhaustive. Search engine algorithms and reporting categories update frequently. Individual URL behavior may vary depending on custom store setups or third-party integrations.

Alternate page with proper canonical tag

When you see pages listed under "Alternate page with proper canonical tag" in Google Search Console, it means Google found a secondary or duplicate version of a page on your website and correctly followed your site's instructions not to index it.

Instead of indexing the duplicate, Google gave full search visibility and ranking credit to your primary (canonical) page.

Why this happens? 

BLAZE ECOM naturally generate multiple URLs for the exact same product or page. Common examples include:

  • Product Filter & Sort Links: URLs created when shoppers filter by price, color, or brand (e.g., ?sort=price).
  • Tracking & Analytics Links: URLs with tracking codes added to the end (e.g., ?cbreadcrumb=...).
  • Mobile or Variant Links: Alternate URLs created for different screen sizes or product variations.

Is This an Error?

No, this is completely normal and healthy.

Having pages in this category means Google Search Console is doing its job correctly. It prevents thousands of duplicate or parameter URLs from competing against each other in search results, ensuring Google focuses its crawl budget and ranking power entirely on your main product and category pages.

Page with redirect

When you see pages listed under "Page with redirect" in Google Search Console, it means Google crawled a specific URL on your domain and encountered a redirect instruction (such as a 301 or 302 redirect) sending users and search bots to a different destination URL.

Instead of indexing the original source URL, Google correctly excludes it and passes search visibility and ranking credit straight to the final destination page.

Why this happens?

BLAZE ECOM naturally generate or maintain secondary URLs that redirect to live pages. Common examples include:

  • URL Normalization: System rules that automatically route non-secure (http://), non-www, secondary homepage paths (like /home), or non-trailing-slash URLs directly to your primary HTTPS domain.

Is This an Error?

No, this is completely normal and healthy.

Having pages in this category confirms that your site's redirect rules and canonicalization are working as intended. It prevents outdated, non-secure, or duplicate URL variations from diluting your store's search performance, ensuring Google concentrates its crawl budget and ranking power entirely on your primary, active pages.

Soft 404

When you see pages listed under "Soft 404" in Google Search Console, it means Google crawled a URL and received a success code from your server, but the actual content on the page indicated to Google that the page is missing, empty, or unavailable.

Instead of indexing these empty pages, Google intentionally excludes them to prevent searchers from landing on dead ends or duplicate tracking variations.

Why this happens?

BLAZE ECOM naturally triggers Soft 404 classifications through two primary system behaviors:

  • Tracking & Recommendation Links: Internal recommendation modules (like "Frequently Bought Together") generate links with tracking parameters (e.g., ?cbreadcrumb=...). Google flags these parameter links as Soft 404s because they contain no unique content, while keeping the primary canonical product page fully indexed.
  • Unavailable or Discontinued Items: When a product is out of stock or removed, BLAZE displays an "item no longer available" banner on the storefront while serving a 200 OK page load. Google recognizes that the product cannot be purchased and drops the page from search results to protect user experience.

Is This an Error?

No, this is normal and expected search engine behavior. 

Having these pages in the Soft 404 bucket confirms that Google's algorithms are working correctly to protect your store's search quality. It prevents tracking parameter variations and out-of-stock product pages from diluting your overall search authority.

Duplicate without user-selected canonical

When you see pages listed under "Duplicate without user-selected canonical" in Google Search Console, it means Google found multiple versions of the same or very similar page, and made its own determination about which one to treat as the primary version. The URL sitting in this report is the version Google decided not to index.

Why this happens?

BLAZE ECOM can generate multiple URLs that point to the same or very similar content. Common examples include:

  • Duplicate Product Listings: The same product accessible through more than one URL path (e.g., listed under two different categories).
  • URL Formatting Variants: Versions of a page with and without a trailing slash, or served over HTTP vs. HTTPS.
  • Parameter or Filter Variants: URLs generated by sorting, filtering, or tracking parameters that closely resemble the main page.

Is This an Error?

No, this is normal and expected indexing behavior.

This status simply reflects that Google identified duplicate content and chose one version to index — which is exactly the outcome Google's indexing system is designed to produce. In most cases, Google selects the correct page, and that page is indexed and ranking normally.

Server error (5xx)

When you see pages listed under "Server error (5xx)" in Google Search Console, it means Googlebot attempted to access a URL on your site, but your server returned a 500-level HTTP error response code. As a result, Google was unable to fetch or load the page content and could not index the URL.

Why this happens?

BLAZE ECOM can generate malformed URL paths that cause backend server crashes when accessed by search crawlers. Common examples include:

  • Unrendered Dynamic Route Variables: URLs containing raw code placeholders (e.g., [shop] or [slug1]) generated by internal site navigation or recommendation widgets.
  • Serverless Function Crashes: Backend Netlify function errors triggered when Googlebot attempts to render malformed template URLs or parameters.
  • Transient Infrastructure Failures: Temporary server timeouts or endpoint crashes occurring during a crawl request.

Is This an Error?

Yes, for the specific malformed URL attempt, but no for your active store content. While Search Console flags these 5xx events, they are platform artifacts caused by broken template parameters rather than actual product pages. The primary, clean product and category URLs (e.g., /menu/products/...) remain unaffected, fully functional, and indexed by Google.

Excluded by ‘noindex’ tag

When you see pages listed under "Excluded by ‘noindex’ tag" in Google Search Console, it means Google discovered the URL and successfully fetched the page, but detected an explicit noindex directive (via a <meta name="robots" content="noindex"> HTML tag or HTTP header). Google strictly follows this rule and excludes the URL from search results.

Why this happens?

Website platforms or SEO plugins intentionally apply noindex directives to utility pages, administrative paths, or secondary archives to prevent duplicate or low-value content from indexing. Common examples include:

  • Author Archives: Pages listing articles by a specific author (e.g., /author/wildglow/) on single-author sites to prevent duplicating main blog feeds.
  • Internal Search & Filter Pages: Dynamic query paths generated when visitors search or filter products.
  • Administrative Pages: Account login, cart, and checkout paths where search indexing is inappropriate or undesirable.

Is This an Error?

No, this is normal and expected indexing behavior.

This status confirms that Google is correctly respecting site configuration rules by keeping non-essential administrative, archive, or duplicate pages out of search results, allowing search engines to focus entirely on ranking your primary content and product pages.

Not found (404)

When you see pages listed under "Not found (404)" in Google Search Console, it means Googlebot tried to visit a URL, but the server returned an explicit 404 response code indicating the page no longer exists. Google automatically removes 404 pages from its search index over time.

Why this happens?

URLs appear in this report when content is permanently removed, deleted, or relocated without a redirect. Common examples include:

  • Deleted Content: Legacy blog posts, retired products, or out-of-date informational pages removed during site updates.
  • Renamed URL Slugs: Changing a page's URL address without establishing a 301 redirect from the old path to the new one.
  • Broken External Links: External sites linking to a misspelled or non-existent URL path on your domain.

Is This an Error?

Not necessarily.

If the page was intentionally deleted and has no equivalent replacement, a 404 status is the correct HTTP signal to tell search engines the content is gone. However, if the page was accidentally removed or moved to a new URL, a 301 redirect should be implemented to preserve traffic and link equity.

Crawled - currently not indexed

When you see pages listed under "Crawled - currently not indexed" in Google Search Console, it means Googlebot successfully discovered and visited the URL, but chose not to add it to the search index during that specific crawl event.

Why this happens?

On BLAZE ECOM , high URL counts in this report are usually caused by:

  • Tracking Parameters & Dynamic Queries: Recommendation widgets, pagination, or filter query strings (e.g., ?cbreadcrumb=...) where Googlebot crawls the parameter variations but ignores them in favor of the clean base URL.
  • Reporting Latency & Recrawl Delays: Search Console table reports reflect static snapshots from historical crawl logs. Pages often remain listed here temporarily even after Google has recrawled and successfully indexed the live page.
  • Low Value or Duplicate Variants: Alternate navigation routes or thin parameter paths that offer no distinct search value compared to the primary canonical product page.

Is This an Error?

No, provided your primary product pages are indexed.

This report is an indexation management log rather than a technical error or site penalty. As long as live URL inspection confirms that your clean base product URLs (/menu/products/...) return "URL is on Google," your primary storefront inventory remains active and searchable.

Discovered - currently not indexed

When you see pages listed under "Discovered - currently not indexed" in Google Search Console, it means Google found the page on your website (typically via your XML sitemap or internal links) but has not yet crawled or rendered its content.

Instead of indexing or rejecting the page, Google has placed it in an initial queue to be crawled when search resources allow.

Why this happens?

BLAZE ECOM and E-commerce sites and content hubs frequently generate new URLs that take time for Googlebot to prioritize. Common examples include:

  • Reporting & Crawl Delays: Google's sitemap parser discovers the URL and updates the list, but Googlebot has not yet allocated crawl resources to fetch the HTML.
  • New Blog Posts & Categories: Newly published articles or categories that lack sufficient internal links or external authority signals sit in the discovery queue until an initial fetch occurs.
  • Crawl Priority Queueing: Search Console displays "No referring sitemaps detected" or Last crawl: N/A simply because Googlebot has not completed its first crawl cycle to bind the sitemap data in the user interface.

Is This an Error?

No, this is not a technical defect or site error.

Having pages in this category means Google is aware the URLs exist, but is experiencing a standard reporting and crawl queue delay. Live testing confirms these pages are fully accessible, crawlable, and indexable with valid self-referential canonical tags. Submitting a direct inspection request moves them into Google's priority crawl queue for immediate indexing.

Duplicate, Google chose different canonical than user

When you see pages listed under "Duplicate, Google chose different canonical than user" in Google Search Console, it means Google discovered a page on your site, read your specified canonical tag, but determined that a different URL serves as a better master copy for search results.

Instead of indexing the URL you specified, Google assigned search visibility and indexing credit to the version it selected as the primary source.

Why this happens?

E-commerce platforms naturally generate overlapping content across multiple paths or subdomains. Common examples include:

  • Internal Search & Filter Paths: Dynamic URLs created when shoppers search or sort items (such as /menu/search/) that mirror product listings available elsewhere.
  • Cross-Domain or Platform Mirrors: Embedded menu frames or third-party integrations (such as menu syndication platforms) that display identical product inventories across multiple retailer sites.
  • URL Parameter Variations: Alternate paths generated for tracking, session handling, or variant selections where page layout and text remain substantially identical to a main category or product page.

Is This an Error?

Not inherently. In many cases, Google is actively protecting your crawl budget by consolidating duplicate or dynamic parameter paths into a single authoritative URL.

However, if Google selects an external domain or an unintended internal path as the canonical version, it indicates that Google views the underlying content as identical boilerplate. Resolving this requires verifying site availability (ensuring tools like robots.txt are accessible) or adding noindex headers to non-canonical search pages.

How to Report a Potential Indexing Issue

If you have reviewed your pages that are not indexed and believe there is a platform issue that is a potential ECOM issue please email ECOM Support at ecomsupport@blaze.me. 

We will need the following: 

  • The Specific Page URL
  • Which GSC non-indexed page category this page is under
  • Reason for review

To help us evaluate and troubleshoot your request, granting our team access to your Google Search Console account via access@blaze.me is greatly appreciated

Once you send these details over our team can evaluate the URLs and work with you on the next steps.