A “No” means the signal was not detected in the public HTML we received at that time. It may exist on another page, be added by browser-side JavaScript, or have been unavailable temporarily.
How to read “Yes”, “No” and “Pending”
Yes means our crawler detected the defined signal. No means it did not detect that signal in the observed homepage response. Pending means a reliable result is not available yet. These labels do not assess design quality, sales performance, trustworthiness or customer satisfaction.
These links are practical starting points, not endorsements. Using a listed product does not affect ECIndex inclusion, scoring or rank. Features and pricing can change; verify them with the provider.
HTTPS available
HTTPS encrypts information exchanged between a visitor’s browser and the website. We mark this “Yes” when the store’s public homepage is available through a secure HTTPS connection.
How to improve
- Install and renew a valid TLS certificate.
- Redirect HTTP traffic permanently to HTTPS.
- Remove mixed-content requests for images, scripts and styles.
- Check that both the root and
wwwdomain reach the intended secure website.
Check the certificate first, then correct certificate, redirect and mixed-content problems at the host or edge.
Inspect public storefront security and configuration signals before changing production settings.
Diagnose · FreeSSL Labs Server Test ↗Test the public TLS certificate, protocol support and server configuration.
Implement · Provider documentationCloudflare SSL/TLS ↗Configure edge certificates, encryption mode and HTTPS redirects when using Cloudflare.
Homepage reachable
This means our crawler received a successful public response within its bounded timeout. A temporary outage, DNS error, slow server, access block or repeated server error can produce “No”.
How to improve
- Monitor availability and origin errors continuously.
- Use caching and a content delivery network where appropriate.
- Keep DNS records and certificate configuration current.
- Allow clearly identified, non-abusive public measurement bots where your security policy permits.
Monitor from outside your own network, diagnose slow delivery, then correct DNS, origin or caching failures.
Monitor public availability and receive alerts when the homepage stops responding.
Diagnose · Related productSpeedAudit ↗Find performance bottlenecks that can make a reachable storefront slow or unreliable for visitors.
Implement · Provider documentationCloudflare Cache ↗Learn how edge caching can reduce repeated origin work and improve delivery resilience.
Meta description
A meta description is a short summary placed in the page’s HTML metadata. Search engines may use it when presenting a page, although they can choose different text.
How to improve
Add one accurate, useful description to the homepage. Explain what the store sells and which market it serves. Avoid keyword repetition, unsupported claims and identical descriptions across every page.
<meta name="description" content="Shop …">
Edit the description in your platform or theme, then confirm the published HTML and request re-indexing where appropriate.
Inspect an indexed URL, monitor search appearance and ask Google to revisit a corrected page.
Implement · Official guidanceGoogle snippet guidance ↗Review current guidance for useful, page-specific descriptions and understand when search engines may choose other text.
Implement · WordPressYoast SEO ↗Edit homepage and product-page metadata from WordPress when the store uses that platform.
Commerce schema
Structured data is machine-readable information, usually expressed as JSON-LD using Schema.org vocabulary. Technical methodology v0.1 checks the homepage HTML for Product, Offer or ItemList types.
Product markup normally belongs on individual product pages. Therefore, “No” on an ECIndex profile does not prove the website lacks Product schema elsewhere. Homepage ItemList markup should only be used when it accurately describes a visible list of products; markup must reflect content users can actually see.
How to improve responsibly
- Add Product and Offer information to eligible product pages.
- Include accurate name, image, price, currency, availability and canonical URL data where applicable.
- Keep structured prices and availability synchronized with visible content.
- Validate syntax and monitor search-engine enhancement reports.
- Do not add misleading markup solely to obtain an ECIndex signal.
Implement accurate Product and Offer data on eligible pages, validate both syntax and search eligibility, then monitor errors.
Test a URL or code sample for structured-data errors relevant to Google rich results.
Validate · FreeSchema.org Validator ↗Inspect JSON-LD, Microdata and RDFa and identify Schema.org syntax problems.
Implement · Official guidanceGoogle Product data guide ↗Choose suitable Product, Offer and merchant-listing properties for real, visible product information.
Desktop storefront capture
A desktop capture is a dated visual record of the public storefront view returned during an ECIndex observation. It helps merchants and researchers reproduce visible changes over time, but it is not proof that every interactive element completed loading.
How to improve or validate
- Open the homepage in a clean desktop browser session.
- Wait for primary images, fonts and above-the-fold content to finish loading.
- Resolve blocked assets, cookie walls, challenge loops and persistent error overlays.
- Request a fresh ECIndex observation after the corrected page is publicly available.
Reproduce the public page, inspect loading failures, and compare the result with the dated ECIndex capture.
Identify page resources and performance problems that can leave a capture incomplete.
Validate · FreePageSpeed Insights ↗Review lab and available field signals for the public URL.
Understand · ECIndexObservation methodologyReview what a capture represents and the limits of public observation.
Mobile storefront capture
A mobile capture records the storefront at a phone-sized viewport. It helps reveal responsive layout, navigation and above-the-fold content. It does not by itself test checkout completion, touch accuracy or every device.
How to improve or validate
- Test the homepage and product journey at common phone widths.
- Confirm that navigation, search, product cards and primary actions remain usable.
- Prevent intrusive banners and pop-ups from covering essential content.
- Use responsive images and reserve dimensions to reduce layout movement.
Combine a visual check with mobile performance and accessibility testing.
Reproduce responsive layouts and common mobile viewport sizes.
Validate · FreePageSpeed Insights ↗Run a mobile-oriented Lighthouse analysis of the public page.
Diagnose · Related productSpeedAudit ↗Turn performance findings into a focused remediation list.
Technology signals
Technology signals are publicly observable patterns associated with storefront platforms, analytics, advertising, hosting, payments, communications and other services. Detection is evidence-based but probabilistic: a technology may be hidden, removed, proxied or misidentified.
How to interpret and improve
- Treat detected technologies as observations, not vendor-certified declarations.
- Open each technology entry to review the evidence and detection date.
- Remove unused scripts and duplicate services where they add cost, risk or page weight.
- Request a fresh StackCheck after a material platform or integration change.
Compare a fresh scan with the store profile and report corrections when public evidence has changed.
Run a current public technology observation and update supported store signals.
Research · Related productStackRegister ↗Explore technology categories and public detections across websites.
Understand · ECIndexDetection methodologyReview evidence, limitations and how observations affect the index.
Practical improvement checklist
Reproduce the current response and identify whether the issue is persistent.
Update the platform, theme, server or integration responsible for the signal.
Check rendered pages, source HTML and relevant standards after publishing.
Ask ECIndex to observe the public homepage again after a material change.
This guide is educational and does not guarantee search visibility, ranking improvement or commercial results. Read the complete ranking methodology for weights, limitations and governance.