If none of the above matches what you are seeing, it is worth separating two different kinds of problem before you go looking for help, because they have different routes. If the question is how to use something, open Get Help at the bottom of the sidebar. It carries Guided Tours that walk through the screens step by step, which is usually faster than describing a workflow in writing and waiting on a reply. If something looks wrong rather than unfamiliar, get in touch through seerly.app/contact, or write to hello@seerly.app if you would rather use email. Either reaches the same place. Whichever you use, a handful of details will save a round trip. Include: - The domain and project you are looking at, since many accounts have several and the answer frequently depends on which one. - The exact screen, written as the path you took to reach it, for example Sidebar → Insights → Visibility. Several screens show similar-looking numbers, and knowing which one you were on removes most of the ambiguity. - What you expected against what you saw. This sounds obvious and is the single most useful thing you can write, because a number that looks wrong is often a number being read against a different definition than the one it uses. - When you noticed it, roughly, and whether it has been consistent since. A problem that appeared once and cleared is a different investigation from one that has persisted for a week. - How wide it goes: one topic, one engine, or everything. That single detail usually determines where the answer lies, because a problem confined to one engine points somewhere quite different from one affecting the whole account. - A screenshot if the issue is visual, cropped to the panel in question. If your question is about billing, plans or what your subscription includes, say so up front and skip the rest, since none of the diagnostic detail applies and it will only slow the reply down.

Troubleshooting

Common symptoms in Seerly, what usually causes them, and the first thing to check in each case.

HelpUpdated 25th August 20265 min read

Overview#

These are the symptoms people report most often, along with what usually turns out to be behind them and where to look first. Almost everything on this page resolves to one of three causes: the topics are wrong, the run has not happened yet, or crawlers cannot read the site.

"The numbers haven't moved"#

Nine times out of ten the analysis simply has not re-run. Numbers here change when a run completes rather than continuously, and how often that happens depends on your plan, with the cadence shown in Settings.

Check when the last run completed on InsightsVisibility. If it finished within your normal cadence, what you are seeing is expected and there is nothing to fix.

If runs are definitely completing and the numbers still look static, you are most likely reading a window too short to show movement. Switch to weekly trends across several weeks and the picture usually resolves itself.

"The tracked topics don't match what we sell"#

This is normally one of two things: the topic set was approved without anyone looking at it closely, or the target country is wrong.

Check the country first, because it scopes the entire picture and a wrong one will give you a confident, coherent description of a market you have never sold into. Once that is right, review the topics themselves on ActionsPromptsManage. It is worth doing this before anything else on your list, since every other number in the product is measured against those topics, and an off-target set means the whole dashboard is describing somebody else's business.

"We're invisible on one engine but fine on another"#

This is usually not a brand problem at all. Engines draw on different sources, so being missing from one of them means that particular engine leans on sources which do not mention you.

Go to InsightsGap Analysis, filter to the engine in question, and read what it cites in your place. More often than not it is a review site, a directory or a comparison page you are simply not present on, and getting yourself listed there is considerably faster than publishing your way in.

"We publish constantly but nothing gets cited"#

There are two things to check, and the order matters.

Start with whether crawlers can read your pages at all, on ActionsSmart Audit. A site can be in excellent health as far as Google is concerned and still serve almost nothing to AI crawlers, which happens particularly often when pages are assembled in the browser. The readiness check covers this, and until it passes, everything else you do is moot.

If that is clear, the question becomes whether your pages are specific enough to quote. Engines lift concrete claims out of pages. Something that surveys a topic broadly without committing to anything definite gives them nothing to work with.

Allow some time as well. Publishing, discovery, indexing and citation span several cycles between them, so recent work will not show up immediately.

"Sentiment mentions something we fixed long ago"#

This is almost always a stale source. Engines describe you from what has been written and indexed, and that can lag reality by a very long way.

Open InsightsSentimentAspects to find the theme, then follow its citation back to the page that caused it. The offending source is usually easy enough to identify, and third-party pages can often be corrected simply by asking.

"The competitors listed aren't our competitors"#

Two possibilities here. Either your topics are off-target and Seerly is looking at an adjacent market, or these genuinely are the brands AI engines name in your category, which is itself worth knowing even when it is unwelcome.

Check your topics first. If they turn out to be right, treat the list as information rather than an error, and manage which competitors are tracked on InsightsCompetitors.

"An audit says 'in progress' and the numbers look wrong"#

Only read audit results once the run has actually finished. Mid-run figures are incomplete rather than encouraging, and a partially populated audit has an unfortunate habit of looking like a clean bill of health.

"Content generation is unavailable"#

Usually the monthly credit allowance has been used up. It resets at the start of your billing cycle, and neither existing drafts nor published content are affected in the meantime. See seerly.app/pricing.

Still stuck?#

If none of the above matches what you are seeing, it is worth separating two different kinds of problem before you go looking for help, because they have different routes.

If the question is how to use something, open Get Help at the bottom of the sidebar. It carries Guided Tours that walk through the screens step by step, which is usually faster than describing a workflow in writing and waiting on a reply.

If something looks wrong rather than unfamiliar, get in touch through seerly.app/contact, or write to [email protected] if you would rather use email. Either reaches the same place.

Whichever you use, a handful of details will save a round trip. Include:

The domain and project you are looking at, since many accounts have several and the answer frequently depends on which one.
The exact screen, written as the path you took to reach it, for example InsightsVisibility. Several screens show similar-looking numbers, and knowing which one you were on removes most of the ambiguity.
What you expected against what you saw. This sounds obvious and is the single most useful thing you can write, because a number that looks wrong is often a number being read against a different definition than the one it uses.
When you noticed it, roughly, and whether it has been consistent since. A problem that appeared once and cleared is a different investigation from one that has persisted for a week.
How wide it goes: one topic, one engine, or everything. That single detail usually determines where the answer lies, because a problem confined to one engine points somewhere quite different from one affecting the whole account.
A screenshot if the issue is visual, cropped to the panel in question.

If your question is about billing, plans or what your subscription includes, say so up front and skip the rest, since none of the diagnostic detail applies and it will only slow the reply down.