Where does the report data come from?
Not every metric comes from the same source. Our crawler, official Google services and configurable third-party providers serve different purposes.
Which data powers each feature?
Some sources are optional depending on service availability and connected accounts.
Our server-side analyzer checks the submitted URL's HTML, HTTP headers, meta tags, links, images and other technical signals.
First-party measurementOur crawler examines accessible pages, links, status codes, canonical tags, titles and content signals.
First-party crawlingPerformance tools may use Google PageSpeed Insights and Lighthouse data, subject to provider availability and quotas.
Google PageSpeed InsightsWhen a user connects their Google account, the Search Console API may provide clicks, impressions, CTR and position data for authorized properties.
Google Search Console APISERP features use a configured provider layer, such as Serper or an administrator-managed worker.
Configurable SERP providerBacklink Checker visits submitted source URLs to verify links to the target domain. Some discovery workflows may also use Common Crawl data.
Live URL checks / Common CrawlRobots rules, HTML, schema, entities and answer-readiness signals are evaluated from the target URL; results do not guarantee rankings or AI visibility.
First-party analysisHow are connected accounts handled?
Account connections, including Search Console, are user-initiated and can be disconnected by the user. Sensitive credentials are not displayed publicly.
Why aren't these Google scores?
The overall SEOANALIZIN score is a weighted result of platform-defined checks, not a score issued by Google. We explain category weights and check contributions on the Scoring Methodology page.
Why can results differ?
Differences can arise from crawl timing, location, device, caching, personalization, providers and changing search results.