Context

Use the Context queue to fix the information Supasaito works from, so everything it generates for you is about your actual business.

Context overview

Context is one of the three recommendation categories in the sidebar, alongside Technical and Content. The number next to it is how many items are still open.

Everything in this queue is a gap in what Supasaito knows — not a problem on your website. The brand description, your aliases, which competitors you track, how many prompts you’re measuring: these are the inputs. The app’s own description of the category says it plainly — “Improve the data quality inside Supasaito.”

It matters more than it sounds. The same inputs feed your prompts, your market map and your content briefs, so a thin description doesn’t produce a warning — it produces generic results everywhere, quietly.

What lands here

Items appear when something Supasaito relies on is missing, stale, or too thin to work from:

• Your brand’s own details — no description, no industry, no target audience, no domain.
• Naming — missing spelling variants or aliases, including kana variants, so mentions of you go uncounted.
• Things waiting for your review — cited domains that haven’t been categorized, competitor candidates nobody has confirmed or dismissed, alias suggestions, unreviewed demand.
• Coverage — too few prompts to measure anything reliably, or topics sliced so finely that each one carries almost no data.
• Movement worth reacting to — a competitor’s sudden rise in your prompts.

Good to know Context items are the cheapest ones in the product. Most are a text field or a single review decision, and several take under a minute — but because they’re inputs, they change every result downstream rather than one page.

How these are prioritized

Every card carries a priority of High, Medium or Low, plus an estimated impact and an effort label. Work from the top: the queue is already ordered.

Each card has a status — Open, In progress, Done, Skipped or Resolved. You set the first four yourself. Resolved is the app closing a card on its own, because the next scan no longer detects the problem.

An empty queue is a real result, not a missing feature. When there’s nothing here the screen says so: “Your brand context is in good shape — nothing to fix here.”

How to work through them

Open a card to see The problem, Why this matters and How to do it. Context cards finish with a link straight to the screen where the fix lives — Brand settings, Prompts, Sources, Competitors — so you rarely have to go looking.

• Most items land on Brand: description, industry, audience, aliases.
• Coverage items land on Prompts and topics.
• Review items land on Sources or Competitors.

For the queue mechanics — marking done, skipping, reopening, what happens to a card you ignore — see Recommendations.

What it does not mean

The count isn’t a score. Twelve open Context items doesn’t mean your brand is in worse shape than one with three. It means twelve pieces of information are missing or unreviewed — and a new account legitimately starts with a lot of them.

An empty queue doesn’t mean you’re visible. It means Supasaito has what it needs to measure you properly. Whether AI actually recommends you is what the scans, the Content queue and your competitors’ pages will tell you.

It isn’t about your website. Nothing in this queue is a change you deploy. If a card asks for a brand description, it wants it in Supasaito — your site’s own copy is a separate thing.

It isn’t optional groundwork. These are the inputs the prompts, the market map and the content briefs are all built from. Leaving them open doesn’t slow anything down visibly; it quietly makes everything downstream more generic.