Help Getting started
Browser extension
Check any page while you’re looking at it, without leaving the tab.
Extension overview
The Chrome and Edge extension puts a panel next to whatever page you’re on. It does two different things depending on whether you’re signed in.
Signed out, it runs a set of checks on the page in front of you, entirely inside your browser. Nothing is sent anywhere.
Signed in, and on a domain you’ve allowed, it also shows what Suparanku already knows about that page — its real score, whether AI has cited it, its open issues, and the recommendations for it.
How to check a page without an account
Open the panel and click Check this page. It reads the page’s markup and reports what it finds — title, meta description, canonical, indexability, language, headings, structured data, author and freshness signals, social card, image alt coverage, and more.
Browser-internal pages and store pages can’t be checked; the panel says so.
Good to know This check runs entirely in your browser. The page is never sent to Suparanku, and you don’t need an account for it.
How to connect it to your account
- Click Sign in in the panel.
- Click Allow your brand domains and grant access to the domains you track.
From then on, opening a page on an allowed domain shows Suparanku’s own data for it straight away — no button to press. Open dashboard jumps to the app, and Open the full report goes to that page’s full audit.
Three messages tell you why data isn’t showing: the domain isn’t connected to any of your brands, the page hasn’t been crawled yet (run a site audit to include it), or you need to sign in.
Why the panel’s score differs from SRPS
The panel’s Quick page score is an estimate from that page’s HTML alone. SRPS is not.
SRPS also reads the rendered page, your robots.txt, your llms.txt, your sitemap, Core Web Vitals, and whether AI assistants actually cite you. The panel can’t see any of that from inside your browser, and it says so rather than pretending otherwise.
Use the panel for a fast look while you work. Use the page audit when the number matters — see Page audit.