Method

Every number, explained

Indexa owns its whole pipeline: the crawler, the link graph, the index and the scoring. Here is exactly how each figure is produced — and what we refuse to guess.

The crawler

Our crawler identifies itself as IndexaBot, reads robots.txt before fetching anything, and skips any path the site disallows. It follows internal links breadth-first up to the page limit and depth you choose, storing the title, meta description, first heading, word count, response code, response time and every link it finds.

Pages indexed

The number of distinct URLs of that site currently in our index. It reflects how much we have crawled, not how many pages the site has in total.

Referring domains and backlinks

Every link we record becomes an edge in our graph. Backlinks are external links pointing at the domain from pages we have crawled; referring domains are the distinct sources among them. Both grow as more of the web is crawled.

Authority score (0–100)

42 points from log-scaled referring domains, 22 from log-scaled backlink volume, 12 from the share of follow links, 16 from log-scaled indexed pages, and up to 8 from crawl response speed. It is a measure of the site's standing inside our graph — not a prediction of anyone else's rankings.

Keyword positions

Positions are measured inside the Indexa index. For a phrase we score every indexed page on term matches in title, heading, description and body text, rank them, and record where the tracked site's best page lands. Because it is our index and our scoring, you can always see why a page won.

Real visits

Visit counts exist only for sites that install the Indexa snippet, which records page views first-hand. We do not run a behavioural panel, so we never publish estimated traffic, bounce rate, session duration or audience demographics.

Known limits

Our index starts small and grows crawl by crawl, so a site with real backlinks may show few until the linking pages are crawled. Very large sites are sampled, not exhausted. JavaScript-only content is not executed, so pages that render entirely client-side may show little text.