SEO & GEO Analyzer

One tool for SEO, GEO, and a technical check

The SEO & GEO Analyzer inspects a single URL and answers three questions at once: How well is the page optimized for classic search engines (SEO)? How ready is it for AI systems and generative search (GEO/AI readiness)? And is the underlying tech sound — from HTTPS through the HTTP headers to performance?

You paste an address, click Analyze, and get back a multi-part report: two scores plus detailed per-area breakdowns. Exactly one page is analyzed per run — no whole-domain crawl, just a sharp look at one specific URL.

The tool is built for everyone who works on websites: developers who need a quick technical and header check; SEO and content people who want to judge titles, meta data, heading structure, and structured data; and agencies that need to show a client, in a meeting, exactly where a page stands. Everything runs in the browser — no account, no installation.

Two scores: SEO and GEO

The analyzer computes two independent ratings, both normalized to a 0–100 scale and each shown as a circular gauge:

SEO score — classic on-page and technical optimization: HTTPS and SSL, status code and redirects, title and meta description, heading hierarchy, canonical, indexability, Open Graph and Twitter/X data, performance, and a handful of accessibility and content signals.
GEO score — AI readiness: how well the page can be picked up and cited by generative systems through structured data, llms.txt, AI-crawler rules, a clean heading structure, and machine-readable markup.

Both scores work the same way: a set of weighted individual checks is summed up and reported as a percentage. Each check carries a status of pass, partial, or fail (the GEO score adds purely informational info notes that don't affect the result). For quick orientation there are rating bands: the gauge turns green at 80 points, yellow at 50, and red below that, plus a letter grade from A to F. Exactly how much each check counts is covered in the manual — here it's enough to know there are two numbers and two perspectives.

What the analyzer checks — at a glance

The report is organized into tabs. All told, it covers around 20 checks, which group thematically like this:

Overview — a dashboard with status, both scores, HTTP version, page size, TTFB, redirect count, the key on-page values, and a list of the issues and warnings found.
Technical — HTTP Headers (response headers), SSL / Security (certificate, issuer, validity, days left, SANs, chain, algorithm), Redirects (the redirect chain hop by hop), and Performance (timing, render-blocking resources, resource hints, scripts, and styles).
On-page SEO — Meta Tags (title, description, canonical, robots, viewport, charset, language, OG, Twitter, hreflang, headings), Links (every <a> flagged external/nofollow), Images (src, alt, dimensions), Structured Data (JSON-LD blocks), Content Analysis (word, paragraph, and sentence counts, Flesch readability, lists, tables), and Semantic HTML (semantic landmarks).
Social — Social Preview with rendered preview cards for Open Graph and Twitter/X.
Accessibility — Accessibility covering landmarks, skip links, empty anchors and buttons, form fields and missing labels, ARIA roles and tabindex, tables with captions and <th>.
Crawling — Robots Analysis: the contents of robots.txt, allow/disallow rules, sitemaps, and AI-crawler rules.
More — Source Code (the raw HTML in an editor), an SEO Guide and a GEO Guide as in-depth reference content, and Export / Import to save an analysis as JSON, re-import it, or load one of the three demo datasets.

The GEO part: AI readiness

What sets the analyzer apart from a plain SEO checker is its dedicated GEO evaluation. It looks specifically at the signals that matter for generative search and AI citability:

llms.txt is fetched and checked not just for presence but for a valid structure.
AI-crawler check: robots.txt is tested against nine named bots — including GPTBot, ChatGPT-User, OAI-SearchBot, Google-Extended, Claude-Web, ClaudeBot, anthropic-ai, PerplexityBot, and CCBot.
Content-Signal from robots.txt or an HTTP header is evaluated (purely informational) and flags a conflict when the signals welcome AI but the robots rules block AI crawlers.
Markdown alternates: a <link rel="alternate" type="text/markdown"> is rewarded as an AI-friendly extraction affordance.
Schema signals: the variety of JSON-LD types, FAQ schema, and author/organization schema feed into the GEO score as E-E-A-T and citability signals.

The GEO Guide puts all of this in context — including what Google's AI search actually needs, and why llms.txt and schema still pay off for other engines such as Perplexity, ChatGPT, or Claude.

Server-side fetch, in-browser analysis

Architecturally the analyzer is a hybrid, by design: the target page is fetched server-side via the JPKCom proxy (a direct fetch from your browser would otherwise fail on CORS). The actual analysis then happens locally in your browser — the HTML is parsed with DOMParser, evaluated, and scored. So the analyzed page sees a request from the JPKCom server, not from you; internal and private addresses are blocked server-side. How the proxy works and what limits apply (timeouts, maximum size) is covered in the manual.

Try it now

→ Open the SEO & GEO Analyzer — paste a URL, click Analyze, read the report. No account, free, right in the browser. If you'd like to see what it looks like first, the three demo datasets (perfect, broken, empty) in the Export/Import tab load ready-made example analyses.

The analyzer finds gaps — these tools help you close them:

Meta Tags Generator — produce clean titles, descriptions, and Open Graph/Twitter data that the analyzer will then pass with flying colors.
robots.txt & Sitemap — build crawling rules and sitemap entries that get checked in the Robots Analysis tab.
llms.txt Generator — create a structurally valid llms.txt that feeds straight into the GEO score.

There's more on the subpages: the manual with the full feature reference and every score weight, hands-on examples, and a collection of tips & tricks.