Every number and every piece of text in the app comes from one of the sources below. We list them, how fresh they are, and what they cannot tell you — including what BeOnTop does not have.
| What you see | Where it comes from | How it is read, and its limit | How fresh |
|---|---|---|---|
| Page checks: titles, headings, links, images, structured data, llms.txt | BeOnTop itself | It reads your pages over an ordinary web visit, the same way any visitor or search engine does, as plain HTML. It does not see what a script adds afterwards (except in the on-request JavaScript check). | Every check; scheduled sites on their chosen schedule |
| Speed in the laboratory (load time, Lighthouse scores) | Google PageSpeed Insights | One Lighthouse run on a Google machine over a simulated connection. A laboratory number, not what your visitors felt. | Every check |
| Speed as real visitors felt it | Chrome UX Report (Google) | What real Chrome users experienced over the last 28 days. Small sites usually have no record at all, and then we say “not enough visitors” rather than guess. | Every check, when Google has a record |
| “How big is this site” bracket | Chrome UX Report dataset (Google BigQuery) | Only a bracket (among the top 1,000, 10,000 … origins). It is never a visitor count; nobody can count another site’s visitors from outside. | Once a month per site, only when Google has a record |
| Security and trust rows (certificate, headers, e-mail records, versions shown, consent banner) | BeOnTop itself, public DNS | Passive only: what any visit and public DNS hand to everybody. We do not probe for hidden files, logins or weaknesses. Shown, but never part of the score. | Every check |
| Known weaknesses in WordPress plugins | Wordfence Intelligence vulnerability feed | A public database of known plugin weaknesses, matched against the plugins your site shows. A match means “this version has a known problem”, not “you were hacked”. | Feed read once a day |
| Uptime and speed monitor | BeOnTop itself, from Google Cloud in Europe (Belgium) | A request to your home page at the interval you pick per site. A failure is confirmed by a second try a few seconds later before anyone is alerted. | Every few minutes, as chosen per site |
| Your search words, clicks, tracked keywords, links export | Google Search Console, with your permission | Only your own sites that you connected. Google’s numbers are delayed by a few days and group rare searches away. | Read when you open the report or the scheduled job runs |
| Suggestions, the assistant, rewrites of titles and descriptions | Anthropic Claude | Drafts of text written from your own check results. They are suggestions for you to approve, never numbers, and never written to your site without your click. | On request |
| Are you named in AI answers? | Perplexity and Gemini | A few questions put to the two engines, once a month per site. AI answers vary from one asking to the next, so read the result as a sample, not a measurement. ChatGPT, Copilot and Google AI Overviews are not covered. | Once a month per site |
| “How do you compare with sites like yours” | Anonymous scores of BeOnTop members’ own sites | Numbers about whole groups only, shown from a minimum group size so nobody’s own score can be read out of it. No site, name or address is in them. | Once a week |
| Comparison with competitors | The rival’s public pages, read like a visitor | The same checks as for your site. It shows only what their own website shows: no rankings, no traffic, no backlinks. | When you compare |
| WordPress fixes (alt texts, SEO title and description) | Your own site’s WordPress, with the Application Password you saved | Only your own site, only when you press the button, and every change is written in a short log. | On request |
These need paid data providers or data that Google does not share. We would rather say so than fill the gap with guesses.
Your own tools can read your sites and scores through a read-only API with keys (Settings → API keys).