New iSuggest.ai users tend to ask the same question in their first week: do I check my site's health on /dashboard, or on /account? The two pages aren't interchangeable, and once you know what each one actually does, you stop clicking the wrong one. Here's a plain, feature-by-feature tour of where things live in the workspace.
By the iSuggest.ai Team · Updated for 2026
Two Different Jobs, One Sidebar
Everything behind login — dashboard, your websites, audits, the AI directory, credits and API keys — sits inside one left-sidebar workspace. The sidebar groups things the way you'd expect: a "Workspace" section with Overview, Websites, Audits and AI Directory, and a separate "Account" section with Credits and API access. If you're an administrator, an Admin section appears too. The footer of the sidebar always shows your current credit balance as a link straight to the credits page, so you're never more than one click from your balance no matter where you are.
That split — workspace on one side, account on the other — is the whole story. /dashboard is about your sites. /account is about your billing and your keys.
What /dashboard Actually Shows
If your account has no websites added yet, the dashboard is an onboarding path: four steps (add a website, verify it, run a scan, publish a snapshot) with a progress meter, plus a small table of any audits you've already run before adding a site.
Once you have at least one website, the page becomes a real overview. You get five tiles at the top: your average GEO score across sites, how many websites you have verified out of the total you've added, a count of critical and high-severity issues, how many audits you've run this month, and your credit balance with a small meter. Below that sits a table of your websites — score, letter grade, a trend sparkline, issue counts, when each was last scanned, and quick actions to verify, scan or open a site.
Further down, a "Fix these first" section rolls up your top five issues by rule across all your verified sites, ranked by severity and how many pages each one touches — so you're not hunting through separate reports to see what matters most. A score-over-time chart lets you compare up to four sites across a 30, 90 or 180-day window, and a "credits spent per week" bar chart shows the last eight weeks of spend with a link into the full ledger. A recent-activity feed closes it out: audits, verifications, directory publishes and scan events, newest first.
In short: the dashboard is where you go to see how your sites are doing right now.
What /account Actually Shows
/account by itself doesn't have its own content — it simply redirects to /account/credits. That page shows your credit balance with a meter, a short explanation of what credits actually pay for (audits themselves are free; only publishing a snapshot to an AI directory or running a multi-page site scan spends credits), a note that credits are non-refundable, a "Buy credits" button that goes to a support contact form, a link to the pricing page, the same weekly-spend chart the dashboard shows, and — unique to this page — a full ledger table listing every credit event: date, reason, the +/− change, and your running balance, up to the last 100 entries.
/account/api is a different page entirely, for integration rather than billing. It has two cards: one to set, update or remove a Gemini API key you supply yourself for AI suggestions (shown masked once saved), and one to issue, reissue or revoke your own isk_… developer key, which lets you call the iSuggest.ai API as yourself, scoped only to your own data. A new key's full value is shown once, right after you generate it; after that, only its prefix is visible.
Where They Overlap, and Where They Don't
The one thing both pages show is your credit balance — the dashboard as a single tile plus a weekly chart, the credits page as the authoritative source with the complete ledger and the "buy credits" path. That's deliberate overlap, not duplication: the dashboard gives you a glance, the account page gives you the detail. Everything else is strictly separated. The dashboard never shows your API keys or Gemini key, and the account pages never show a website score, an issue list or a trend chart. If you're looking for site health, you're in the wrong place on /account; if you're looking for your ledger or a key, you're in the wrong place on /dashboard.
A Simple Rule of Thumb
Dashboard answers "how are my sites doing." Account answers "how do I pay for this, and how do I connect to it." Most day-to-day work — checking scores, fixing issues, verifying a new domain, publishing a snapshot — happens from the dashboard and the per-site pages it links to. You only need /account when it's time to top up credits, check the ledger, or generate an API key for something you're building yourself.
If you haven't seen either page yet, how it works walks through the audit-to-publish flow end to end, and your account page is exactly where this post says it is. For more on what credits are actually for, see how the credit system works, and for the full path from first audit to a live AI directory snapshot, see the audit-to-publish workflow walkthrough.