Few ecommerce problems are more frustrating than discovering that a product has disappeared, an important page has slowed down, or part of your catalog is no longer eligible to appear through Google Merchant Center.
These symptoms can have several causes, and the visible problem is not always where the underlying issue began. A missing product may originate in the ERP, an integration, the ecommerce database, a visibility rule, or the search index. A slow page may be affected by frontend code, database activity, hosting capacity, or a third-party service.
The goal is not to guess at a quick fix. It is to trace the issue through the relevant systems, confirm where the expected behavior changes, and address the underlying cause.
Here are three common ecommerce problems, a practical way to investigate them, and steps that can reduce the likelihood that they happen again.
1. Products Aren’t Appearing Where Expected
A product may exist in one system without being visible in search results, category pages, or the storefront. When that happens, work through the systems in the order the information moves.
Check the source data
Start with the system that owns the product information, such as an ERP, PIM, or supplier-data platform. Confirm that the record contains every field required by the ecommerce integration.
Depending on the business, required information may include:
- A product or variant identifier
- A name
- A category
- A price
- A unit of measure
- A status
- An availability value
- Attributes required for search or filtering
- A relationship between the main product and its variants
A product may look complete to the person reviewing it while still missing a value the integration requires. In one case, a list-price field was no longer being maintained after responsibilities changed internally. Because the integration required that value, affected products were never transferred to the ecommerce platform.
The fix involved more than correcting the records. The team also clarified who would maintain the required field going forward.
Check the integration
Next, confirm whether the source record was transferred successfully. Review integration logs, rejected-record reports, validation messages, and the timing of the most recent update.
A bulk import may create part of a product record without creating every required relationship. For example, the main product may exist without a valid variant, category assignment, price, or inventory record. The import can appear partly successful while the storefront still has nothing it can display.
Useful questions include:
- Was the record included in the latest transfer?
- Did a required-field rule reject it?
- Did the process create both the product and its variants?
- Were relationships and identifiers preserved?
- Did the import finish successfully, or were some records skipped?
- Can the same record be transferred again without creating a duplicate?
Check the ecommerce record
If the product reached the ecommerce platform, review the destination record itself. Confirm that the product and variant information is complete and connected properly.
Look for missing or invalid values in areas such as:
- Category assignments
- Product and variant relationships
- Pricing
- Descriptions and specifications
- Language or market settings
- Inventory
- URLs
- Product type
- Required merchandising attributes
The storefront may apply filters that prevent incomplete records from appearing. A product can exist in the database while remaining unavailable to customers because it does not meet the rules required for display.
Check visibility and publishing rules
Confirm that the product is active and available to the intended audience. Review both the main product and its variants.
Depending on the platform, visibility may be affected by:
- Published or unpublished status
- Start and end dates
- Archived or deleted status
- Default-language requirements
- Market or regional settings
- Customer or account groups
- Catalog permissions
- Page permissions
- Product eligibility rules
Do not automatically broaden the product to all users. B2B sites may intentionally restrict products by customer, contract, account, market, role, or region. Confirm that the rules match the intended audience.
Check inventory and commercial rules
Availability thresholds and commercial requirements can also hide products. A storefront may suppress products when inventory falls below a certain level, when a price is missing, or when the item is not eligible for the customer’s account.
Review:
- Out-of-stock display settings
- Minimum inventory thresholds
- Backorder rules
- Customer-specific eligibility
- Price-list assignments
- Market availability
- Discontinued-product handling
A product may be behaving exactly as configured even when the configuration no longer matches the business need.
Check search indexes and caches
If the product appears through a direct URL but not through search or category navigation, the remaining issue may be an outdated search index or cached data.
Confirm:
- Whether the product is included in the index
- When the index was last updated
- Whether indexing errors occurred
- Whether category and filter values were included
- Whether the storefront is serving an older cached result
- Whether the relevant job or scheduled process is running
Reduce the chance of recurrence
Missing products are easier to manage when the system detects incomplete or rejected records before a customer or employee notices them.
Helpful controls may include:
- Required-field validation in the source system
- Import and integration error reports
- Alerts for rejected records
- Automated checks for products without variants, prices, or categories
- Clear ownership of required product fields
- Search-index monitoring
- A report comparing source and destination record counts
- Post-import storefront checks
2. The Site Is Slower Than Expected
Site performance can affect how easily customers browse, evaluate products, and complete an order. But speed is only one part of the experience, and there is rarely one universal fix.
Start by measuring what users experience, then identify whether the delay comes from the browser, network, server, database, integrations, or third-party services. Google’s Core Web Vitals focus on real-world loading performance, responsiveness, and visual stability.
Measure before making changes
Test representative pages and workflows rather than looking only at the homepage. A category page with many filters, a technical product page, an account dashboard, and checkout may have very different performance characteristics.
Review both laboratory tests and real-user information where available. PageSpeed Insights can help identify opportunities, while browser monitoring, application logs, and infrastructure metrics can help the technical team trace the source of a delay.
Ask:
- Which pages or workflows are slow?
- Is the issue affecting most users or a particular device, region, or account type?
- Did it begin after a release or configuration change?
- Is the delay in loading, responding to interaction, or keeping the page visually stable?
- Does it occur consistently or only during peak traffic?
- Which resource, query, or service is consuming the most time?
Review frontend weight and execution
Large images, oversized code bundles, inefficient JavaScript, and unnecessary resources can delay the page or make it less responsive.
Common areas to review include:
- Image dimensions and compression
- Modern image formats
- Lazy loading
- JavaScript execution
- Unused CSS or code
- Font loading
- Layout shifts
- Resources that block rendering
- Duplicate libraries
The goal is not to remove everything that adds weight. It is to understand which resources support an important business or customer need and whether they are being delivered efficiently.
Review third-party services
Analytics, personalization, chat, advertising, reviews, consent tools, and other third-party services can provide real value. Each service also adds code, requests, and another dependency to the page.
Review them regularly and ask:
- Is the tool still being used?
- Which customer or business need does it support?
- How much does it affect page loading or responsiveness?
- Can it load later without affecting the task?
- Are several tools performing overlapping functions?
- Does the value justify the performance cost?
This should be a cross-functional decision. Marketing, ecommerce, analytics, privacy, and technical teams may all have relevant context.
Review the application and database
Database configuration, indexing, repeated queries, and inefficient custom code can slow down pages even when the frontend is relatively light.
The technical team may need to review:
- Slow-query logs
- Database indexes
- Repeated or unnecessary calls
- Large or poorly filtered result sets
- Custom code paths
- Application caching
- Search-service performance
- Integration calls made during page requests
Caching can reduce repeated processing when it is applied to suitable data and workflows. The effect will depend on the existing architecture and the actual source of the delay, so measure the result rather than assuming a particular improvement.
Review infrastructure and network capacity
Hosting resources that once supported the site may no longer match current traffic, catalog size, integrations, or processing needs.
Review:
- CPU and memory use
- Server response time
- Traffic patterns
- Network latency
- Storage and database capacity
- Autoscaling or load-balancing configuration
- Content-delivery network usage
- Performance during scheduled jobs
- Peak-period behavior
Additional capacity may help when the system is resource-constrained, but it will not correct inefficient code, a slow external dependency, or an unnecessary database query.
Prioritize based on customer and business impact
A performance improvement should be connected to the workflows that matter. A small change to a high-traffic product page may create more value than a large improvement to a page few customers use.
Consider:
- How many users are affected
- Whether the page supports an important task
- How severe the delay is
- Whether the issue affects conversion or adoption
- How difficult the improvement is
- Whether the change introduces other risks
- How the result will be measured after release
Performance requires ongoing attention because sites change. New content, integrations, campaigns, scripts, and platform updates can introduce new bottlenecks over time.
3. Products Aren’t Appearing Through Google Merchant Center
Google Merchant Center issues may involve the submitted product data, the visible landing page, structured data, images, variants, or the checkout experience. The first step is to review the exact diagnostic message and determine which products are affected.
Google notes that incorrect, missing, or conflicting product information can lead to disapprovals, limited eligibility, or inaccurate product displays. Availability should remain consistent across the submitted data, landing page, checkout, and applicable structured data.
Start with the Merchant Center diagnostics
Review the products listed under “Needs attention” and record:
- The reported issue
- The affected product IDs
- Whether the issue applies to individual products or the broader account
- When Google last reviewed the data
- Whether the issue concerns the feed, page, image, identifier, or policy
- Which source is providing the product information
Use the diagnostic message as a starting point, not a complete explanation. The underlying issue may exist in the feed-generation logic, product page, inventory source, variant configuration, or another connected system.
Compare the submitted data with the visible page
For each affected product, compare important values across the Merchant Center data and product page:
- Product ID
- Title
- Price
- Currency
- Availability
- Condition
- Brand
- Product identifiers
- Variant attributes
- Image
- Landing-page URL
The customer should be able to see information that is consistent with the product data submitted to Google. If the feed says a product is in stock while the page or checkout says it is unavailable, the item may be disapproved for an availability mismatch.
Validate Product and Offer structured data
Structured data gives Google machine-readable information about the product and its offer. Use the Rich Results Test and URL Inspection tools to confirm that Google can access and interpret the markup. Product and Offer structured data can communicate details such as price and availability for merchant-listing experiences.
Confirm that:
- The markup is valid
- The product and offer values match the visible page
- The correct price and currency are included
- Availability is represented accurately
- Each relevant variant has appropriate product and offer information
- The page is accessible to Google
- The markup updates when product information changes
JSON-LD is one supported format for structured data. The important point is not the format alone; the values need to be valid, accessible, and consistent with what the customer sees.
Review product variants
Variants need distinct identifiers and clear relationships. Google Merchant Center uses the “item_group_id” attribute to group related variants, while each variant should retain its own unique product ID and relevant distinguishing attributes.
Review whether:
- Each variant has a unique ID
- Related variants share the correct item-group ID
- Variant attributes such as size, color, or another distinguishing value are complete
- Price and availability are accurate for each variant
- The product page exposes the selected variant clearly
- The structured data represents the variant relationships correctly
Google’s current Search guidance also supports ProductGroup and Product structured data to help describe product variations.
Review product images
Product images should provide an unobstructed view of the item. Promotional text, watermarks, overlays, or logos that cover the product can lead to image-related disapproval.
Confirm that:
- The image URL is valid and accessible
- The image represents the submitted product or variant
- Promotional text and obstructing overlays have been removed
- The image is clear enough to evaluate the product
- Variant images match their corresponding products
- Updated images are being served from the submitted URLs
A practical case example
One customer discovered that its products were no longer eligible to appear through Google Merchant Center. The reported issues included inconsistent availability data and product images containing text or watermarks.
The customer corrected the image issues but continued to see availability errors. We reviewed the Merchant Center product data, visible product pages, structured data, inventory rules, and variant configuration.
The remaining work included:
- Correcting how availability was reported when inventory was zero or below
- Replacing product structured data that Google could not interpret reliably
- Associating each distinct variant with its own offer information
- Adding the appropriate grouping information for related variants
- Confirming that the submitted data and visible product information agreed
After the information was corrected and made consistent, the products could be reviewed again through Merchant Center.
Reduce the Likelihood of Future Issues
The best troubleshooting process also identifies controls that can catch problems earlier.
Useful preventive measures may include:
- Required-field validation before products are published
- Integration and import error reports
- Automated checks for incomplete product relationships
- Search-index monitoring
- Post-release storefront checks
- Real-user performance monitoring
- Regular review of third-party scripts
- Merchant Center diagnostic alerts
- Feed-to-page price and availability checks
- Structured-data validation on representative products
- Automated smoke tests for important workflows
- Clear ownership of product, inventory, pricing, and account data
Know When to Involve Technical Support
Some checks may be available to ecommerce administrators, including publishing dates, product status, inventory thresholds, permissions, and Merchant Center diagnostics.
Changes to database queries, integrations, caching, infrastructure, search indexes, or structured-data generation should be reviewed by someone familiar with the platform and its dependencies. A change that corrects one symptom can create a different issue when the surrounding systems and business rules are not considered.
When requesting technical help, provide:
- The affected product, page, or account
- What you expected to happen
- What happened instead
- When the issue began
- Whether it affects all users or a particular group
- Recent releases, imports, or configuration changes
- Relevant screenshots, IDs, logs, or diagnostic messages
- Steps that consistently reproduce the issue
That context helps the team narrow the investigation and avoid spending time on unrelated parts of the system.
A Practical Troubleshooting Checklist
When an ecommerce problem appears, work through these questions:
- What is the exact symptom?
- Who or what is affected?
- When did the behavior change?
- Which system owns the relevant information?
- Did the information move successfully between systems?
- Does the destination record contain the required values and relationships?
- Are visibility, audience, inventory, or commercial rules affecting the result?
- Are search indexes and caches current?
- Can the issue be reproduced consistently?
- What changed immediately before the problem appeared?
- Which logs, metrics, or diagnostics confirm the cause?
- What control could detect the same issue earlier next time?
A Practical Next Step
Start by documenting the exact symptom and tracing the relevant information from its source to the customer-facing experience. Check each layer in order rather than changing several settings at once.
That approach makes it easier to identify the underlying cause, confirm that the correction worked, and avoid introducing a second problem while addressing the first.
Dealing With a Product-Visibility, Performance, or Merchant Center Issue?
We can help you trace the problem across the data, integrations, platform configuration, and customer experience—and identify a practical next step.
Contact us to talk through what you are seeing.
