Browser-side tools
Text, metadata, and markup utilities run entirely in your browser using your own input. Nothing you paste is uploaded or stored — the calculation happens on your device.
Methodology
How our tools and scores actually work.
Every number on this site comes from a method we can explain in plain language. This page documents where the data comes from, how each score is calculated, and — just as importantly — what each result cannot tell you. No proprietary “secret sauce”, and no promises about rankings.
Live-fetch tools
URL and domain checks send only the public address you enter to our edge function, which fetches the page once and reads the response. They report the live state at request time, which can change.
Public data APIs
A few tools call free, public APIs — Open PageRank, Google PageSpeed Insights, and Google Autocomplete. We present that data as sourced, with its provider and date, not as our own measurement.
Data sources
Where the underlying numbers come from.
We do not run a private web-scale crawl. Where external data is used, here is the exact source.
Open PageRank (DomCop)
Domain-authority-style estimates come from the free Open PageRank API, which models link-based importance across a large web crawl. It is published on a 0–10 scale; we multiply by ten for a familiar 0–100 figure and also show the raw value, global rank, and the provider's last-updated date. It is not Moz Domain Authority or Ahrefs Domain Rating — those are different metrics built from different data.
Google PageSpeed Insights
Page-speed results come straight from Google's official PSI / Lighthouse API: a simulated lab run plus real-world Chrome User Experience Report field data when Google has enough of it. Scores vary between runs because Lighthouse simulates load conditions — that is expected, not an error.
Google Autocomplete
Keyword ideas come from Google's public Autocomplete suggestions, expanded across letters and question words. These are real queries people type, but they are ideas only — we do not invent search volume, difficulty, or CPC, because no free source provides reliable figures for those.
Public RDAP & the page itself
Domain age comes from the public RDAP registration record. On-page checks (titles, meta tags, headings, links, schema, robots, sitemaps) are read directly from the page's served HTML or its robots.txtand XML sitemaps — the same things a search crawler sees.
How scores are calculated
Transparent, weighted heuristics — never a black box.
Our own scores (SEO score, AdSense readiness, GEO/AI-citation readiness, mobile-friendliness) are deterministic: each adds up clearly-defined checks. The checklist always shows which checks passed and failed, so the number is explainable, not magic.
Weighted checks, shown to you
A score is the sum of individual checks, each with a fixed weight that reflects how much it matters. You see every check's pass/warn/fail status, so you can act on specifics rather than chase a single figure.
Heuristics, clearly labelled
Mobile-friendliness and content-readiness use documented heuristics, not Google's internal systems (Google's standalone mobile-friendly test was retired). Each tool states this on its own page.
Counts from real signals
The Indexability Checker counts the URLs a site actually declares in its sitemaps and allows in robots.txt — a footprint estimate, not a live count of what Google has indexed.
Honest limitations
What these results cannot tell you.
Read this before you act on any number here.
No ranking guarantees
No score here predicts rankings, traffic, or AdSense approval. Google uses no single “authority score”, and rankings depend on relevance, content quality, intent, and technical health far more than any one metric. Be skeptical of any tool that promises a position.
No private backlink index
The Backlink Audit Tool analyses the data you provide and the single page it fetches. It does not discover every link pointing at a domain the way a paid crawler with its own index does, so treat counts as a structured read of a known sample, not a complete census.
A live fetch is a snapshot
Live-fetch tools see only what a single request returns at that moment. Content injected by JavaScript, or behind a login or paywall, may not appear, and results change whenever the target site changes.
Estimates, not vendor figures
Authority, age, and indexability are estimates that lag reality and differ between vendors. If you need a specific provider's official number, check it in that provider's own product.
Questions or corrections
Spotted something inaccurate? Tell us.
We treat methodology and accuracy feedback as part of normal maintenance — corrections are welcome.
Last updated: June 2026