---
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 → **Analytics** for store-event data.
- Store project → **SEO** for public search and AI-visibility data.

## 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. |
| **Publish your storefront to start analyzing** | 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. |
| 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. |
| Stale 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. Change to **Last 30 days** to rule out an overly narrow range.
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.

## Related guides

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