What happens if a site is protected by Cloudflare or a similar anti-bot system?

Seyka switches from the fast loader to the headless browser automatically, which clears the challenge screen like a normal visitor and returns the same page data.

Does the speed measurement count analytics trackers on the page?

Not by default — trackers are blocked so the score reflects the page itself, with an option to include them for PageSpeed Insights-comparable numbers.

How many IP addresses can one geolocation request check?

Up to 100 in a single batch request, useful for auditing a whole pool of servers or CDN nodes at once.

Seyka AI

All integrations

UnoAPI.ru

Available

Web-access primitives via UnoAPI.ru: a fast page parser, a real headless browser, page screenshots, Lighthouse measurements and IP geolocation.

Overview

UnoAPI.ru provides the low-level web-access primitives Seyka relies on in almost every audit: fetching and parsing pages, rendering JavaScript-heavy sites in a real browser, capturing screenshots, measuring loading performance and geolocating server IPs. The assistant picks the right path itself — the fast parser first, escalating to the headless browser when a site needs JavaScript or hides behind anti-bot protection.

Access

No authentication required — core checks work right away.

Tools

Page loader
Server-side page fetch with extraction via CSS selectors: title, meta tags, headings, links, images and Schema.org markup — or raw HTML when the actual markup matters. Tracks the redirect chain and distinguishes the requested URL from the one that finally served content. Does not execute JavaScript, which is what keeps it fast.
Headless browser
A real desktop browser controllable via API: it executes JavaScript and lets challenge interstitials clear naturally — Cloudflare, DDoS-Guard, Variti and similar anti-bot screens. The fallback for single-page applications and protected sites: same result shape as the fast parser, several times slower, used only when needed.
Lighthouse performance
Lighthouse-scored Core Web Vitals — FCP, Speed Index, LCP, TBT and CLS — each rated against Google thresholds, plus the overall performance score. Desktop and mobile profiles; analytics trackers are blocked by default so the score reflects the page itself, with an option to include them for PSI-comparable numbers.
IP geolocation
The ipinfo service: resolves any IP address to its country, city and network organization, with single and batch lookups of up to 100 addresses at once. This is the data behind the GeoIP enrichment in domain analysis — every resolved DNS record and every redirect hop arrives with the location and owner of the server behind it.
Page screenshots
Captures how a page actually renders in the headless browser — full-page or a chosen viewport, with wait conditions for late-loading content and caching of repeat shots. A visual complement to the parsers: what a real visitor sees, rather than what the markup claims.

Links

UnoAPI.ru — ready-made APIs for you and your AI

Before an assistant can analyze a page, it has to fetch it first — and that's not always trivial: some sites render content client-side, some sit behind anti-bot screens, and some just need to be seen visually to understand what's really happening.

UnoAPI.ru covers this base layer: the web-access primitives nearly every Seyka audit is built on top of.

What it is

Five low-level tools from UnoAPI.ru: a fast server-side page loader, a real headless browser for JavaScript and anti-bot challenges, Lighthouse-based speed measurement, IP geolocation, and page screenshots. This is infrastructure, not finished SEO reports — Seyka builds its reports on top of this data.

What you get

By default Seyka takes the fast path: a server-side fetch that parses title, meta tags, headings, links, images and Schema.org markup without executing JavaScript. When a page is built on a JS framework and returns empty HTML without rendering, or hits a challenge screen like Cloudflare or DDoS-Guard, Seyka escalates to the headless browser automatically — same result shape, full JavaScript execution, natural pass-through of anti-bot screens. IP geolocation resolves country, city and hosting organization, singly or in batches of up to 100 — the same data behind the GeoIP context in domain analysis. Lighthouse scoring covers Core Web Vitals (FCP, Speed Index, LCP, TBT, CLS) against Google's own thresholds, with separate desktop and mobile profiles, and screenshots capture how a page actually renders rather than what its markup claims.

FAQ

What happens if a site is protected by Cloudflare or a similar anti-bot system?: Seyka switches from the fast loader to the headless browser automatically, which clears the challenge screen like a normal visitor and returns the same page data.
Does the speed measurement count analytics trackers on the page?: Not by default — trackers are blocked so the score reflects the page itself, with an option to include them for PageSpeed Insights-comparable numbers.
How many IP addresses can one geolocation request check?: Up to 100 in a single batch request, useful for auditing a whole pool of servers or CDN nodes at once.