---
lastModified: 2026-10-15
title: Troubleshoot data and publication
description: Resolve empty Analytics, publication gates, unreachable SEO targets, partial provider data, and stale reports.
---

Use this page to identify whether a missing result comes from store state, date range, plan access, feature access, or an external data source.

## Entry paths

- Store project → **Measure** → **Analytics** for store-event data.
- Store project → **Grow** → **SEO** for public search and AI-visibility data.

[![English annotations: This publication requirement explains why a new store has no SEO report. Sample data is not a completed analysis.](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgGWQf4eTjKSvqNCku6G2oLnTm47agxUZ0wt1A)](https://ixft9x6szo.ufs.sh/f/Cc8uxBgAYTzgGWQf4eTjKSvqNCku6G2oLnTm47agxUZ0wt1A)

English callouts highlight the controls. Select the image to enlarge it.

This publication requirement explains why a new store has no SEO report. Sample data is not a completed analysis.

## Before you start

- Note the exact page, store, selected period, and visible message.
- Check whether the issue affects one section or the whole page.
- For SEO, open the public storefront directly before starting another analysis.
- For Analytics, confirm the selected period could contain the event you expect.

## Controls and click results

| Control | What happens after you select it |
| --- | --- |
| Analytics time range | Refreshes the report for the selected period; it does not create missing traffic or order events. |
| **Analyze** | Starts the available SEO or AI-visibility analysis for the current public target. |
| **Analyze again** | Requests a new snapshot after a meaningful public-site change. |
| **Retry** | Repeats the failed section or request when offered; it does not fix publication, access, or provider prerequisites. |

## Troubleshooting

| What you see | Likely meaning | Next step |
| --- | --- | --- |
| Upgrade or plan screen | The current plan does not include the page. | Review plan access; repeated reloads will not unlock it. |
| Navigation entry is missing | The feature is not enabled for this workspace. | Treat it as conditional and ask a workspace owner or support. |
| **Get your store found by Google and AI.** | SEO has no eligible public target. | Complete publication, open the live URL, then return to SEO. |
| Analytics dash, zero, or empty chart | No matching events exist for the selected period. | Try a longer window and verify the store has visits or orders. |
| **No store yet.** | The project has no store build yet, so there are no visits to count. | Select **Start building** and describe your store. After you publish it, visits appear here. |
| **Your store isn't published yet.** | The store is built but not published. | Select **View store** and publish it. Shoppers can visit only after that. |
| **Sample data · not your store** | The page shows example numbers, not your results. | Your plan does not include these reports, so the samples stay until you upgrade. Select **Upgrade to Pro** to see your own numbers. |
| **Coming soon** on a panel | That panel has no data source yet. | Use the other panels; this is not a store or tracking problem. |
| **This panel did not load.** | One request failed. | Select **Try again** when it is shown, or reload the page. The other panels still show your data. |
| Target unreachable | The analyzer could not load the public page. | Open the exact URL directly and resolve publication, domain, or access problems. |
| Not enough data | The provider cannot return a useful estimate yet. | Keep the site public and retry after more public activity or discovery. |
| Partial sections | Some providers completed and others failed. | Use completed results; retry only the missing section later. |
| **Out of date** label | The saved snapshot may no longer reflect the public site. | Select **Analyze again** after meaningful changes. |

## Check Analytics data

1. Open **Analytics** and note the selected period.
2. Choose **Last 30 days**, then clear optional filters to rule out a narrow query.
3. Confirm the live store has received real sessions.
4. Confirm orders or refunds exist before expecting sales or refund metrics.
5. Compare funnel stages to see which events are present.
6. Reload once. If the whole page still fails, record the store and time range for support.

## Check SEO publication and analysis

1. Open the public storefront in a separate tab.
2. Confirm it loads without a private preview or sign-in requirement.
3. Return to **SEO** and confirm the intended domain or target.
4. Select **Analyze** or **Analyze again** once.
5. Wait for a terminal result instead of starting repeated jobs.
6. If one section fails, preserve the successful sections and retry later.

## What a successful setup does not prove

- Publication does not guarantee search indexing.
- Search indexing does not guarantee traffic or a top position.
- AI-visibility setup does not guarantee a mention.
- A successful prompt run does not predict every future model answer.
- An Analytics event does not explain why a shopper acted.

## Separate report access from collection

Expand **Measure** or **Grow** before treating an entry as missing. A plan preview is not a live report. In the **All reports** layout, the **Setup** reports hold tracking and settings tools; opening them does not create shopper events. Confirm the store, period, filters, and actual activity before changing collection settings.

**Checkpoint:** Identify whether access is blocked, the query is empty, or a named request failed. An empty report alone cannot distinguish no activity from missing collection.

## Related guides

- [Analytics overview](./analytics-overview)
- [SEO overview](./seo-overview)
- [AI visibility](./ai-visibility)
- [Runner documentation](../product-guide)
