Getting started
Glimana turns the data you already have — Search Console, Analytics, your own pages — into a short, ranked list of things to do, then measures whether doing them changed anything. It does not estimate traffic or buy third-party numbers: every figure in the panel is measured on your site or comes straight from Google.
What Glimana is built around
Measured, not estimated. Clicks and impressions come from Search Console, visits from GA4, speed from Chrome's real-user data (CrUX), and everything about your pages from our own crawler. If a number cannot be measured, the panel says "—" rather than guessing.
Tasks, not reports. A crawl finds issues; the rules engine turns the ones worth doing into tasks and ranks them by the organic clicks of the pages they touch. A task about a page nobody visits sits at the bottom, however "technical" it is.
Verified results. When you mark a technical task done, the affected pages are re-crawled within hours and the task is only closed if the problem is gone. Content tasks are measured 31 days later against a control group of similar pages that you did not touch, so a site-wide rise does not get counted as your win.
The panel at a glance
The left sidebar is site-scoped: everything under To do, Content and Data refers to the site shown in the switcher at the top of the sidebar. Account-wide things — team, billing, connections, API and MCP — live under your avatar in the top-right corner.
| Area | What you find there |
|---|---|
| Dashboard | Score, KPIs, 90-day chart, health by category, sections, position distribution, "Do this week". |
| Tasks / Issues / Impact reports | The to-do list, the raw crawl findings behind it, and what your finished work measurably changed. |
| Articles | The article writer: opportunities from Search Console, brand voice, drafts, publishing. |
| Traffic · Keywords · Pages · SEO map · Speed · AI access · Competitors · Crawls | The data screens. Each one is explained on its own help page. |
| Site settings | URL, target country, language, brand names, competitor domains, crawl limits, AI visibility preference. |
| Avatar menu | Account settings, Team, Connections, Plan & billing, API & MCP, Help & support, language, sign out. |
Ten-minute setup
- Add your site. Open the switcher → + Add site and enter the canonical root, for example
https://www.example.com. Glimana checks the www/https preference on the first request and corrects it if needed. - Connect Google. Avatar → Connections → Connect with Google (GSC + GA4). Only read scopes are requested. Then, in Property mappings, pick the Search Console property for the site (a
sc-domain:property if you have one) and, optionally, the GA4 property. Mapping Search Console marks the site as verified and starts a 16-month history import in the background. - Let the first crawl finish. A full crawl starts automatically. On a 3,000-page site at the default 4 requests/second it takes 15–20 minutes; the sidebar shows "last crawl · x min ago" when it is done. You can watch it under Crawls.
- Read the dashboard. The SEO score card names the single task that would gain the most points. Health by category shows where the open issues sit.
- Work the task list. Open Tasks. The first three or four rows are usually enough for a week. Each task tells you why it exists, what to do, where the guidance comes from and how it will be verified.
- Mark tasks done — honestly. "Mark as done" triggers a verification crawl for technical tasks and starts the 28-day measurement window for content tasks. Marking something done that you did not do only produces a failed verification.
Add the site before the connection
Property mappings are per site, so the site has to exist before Glimana can offer you its Search Console property. If you connect Google first, nothing is lost — come back to Connections after adding the site.
What happens every night
Each night Glimana runs an incremental crawl (changed and new pages only; a full crawl runs on a schedule and when the sitemap changes), fetches the latest Search Console and GA4 days, re-evaluates all 102 rules, re-ranks the task list, looks for traffic anomalies and decay, and closes tasks whose issue is no longer seen. The dashboard subtitle shows when each source was last fetched.
Search Console data arrives two to three days late — that is Google's publishing delay, not a fault, and Glimana never treats it as one. The only thing the panel alarms on is a fetch that stops running.
Where to go next
- Sites and site settings — adding sites, crawl limits, brand names, AI visibility.
- Connections — Google, Bing Webmaster, IndexNow, publishing.
- Tasks — how the priority formula works and what each status means.
- Issue guides — every rule explained, with the fix.