JPKCom DB

SEO & GEO Analyzer

What the SEO & GEO Analyzer does, who it's for, and how its 20 tabs work together — your starting point for the manual, examples, and tips.

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 — as an HTML report to hand over, if you like. 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 20 tabs, which the sidebar sorts into eight groups:

  • Overview — a dashboard with status, both scores, HTTP version, page size, TTFB, redirect count, the key on-page values, cards for the SSL and indexing status, and a list of the issues and warnings found — click any entry to jump straight to the tab where you can dig in. Alongside it sit the two score tabs, SEO Score and GEO Score, with every individual check.
  • Technical — HTTP Headers (response headers, raw view included), SSL / Security (certificate, issuer, validity, days left, SANs, certificate chain with signature verification, TLS version and cipher, graded security headers, mixed content), Redirects (the redirect chain hop by hop), and Performance (timing, render-blocking resources, resource hints, scripts and styles, every resource in one table).
  • On-page SEO — Meta Tags (title, description, canonical, robots, viewport, charset, language, OG, Twitter, validated hreflang, headings, pagination, double-encoded entities), Links (internal and external links, filterable and sortable), Images (src, alt, dimensions, modern formats, preview), Structured Data (JSON-LD blocks as a tree or raw text), Content Analysis (word, paragraph, and sentence counts, language-aware readability, Gunning Fog index, transition words, top keywords, duplicate-content signals), and Semantic HTML (landmarks and document structure).
  • Social — Social Preview with a Google search-result preview plus rendered preview cards for Facebook/LinkedIn and Twitter/X.
  • Accessibility — Accessibility covering landmarks, skip links, empty links and buttons, form fields without labels, ARIA attributes and tabindex, image and table accessibility.
  • Crawling — Robots Analysis: X-Robots-Tag, meta robots, and robots.txt working together, an access table for 40 well-known bots (search engines, social, archives, AI, SEO tools), the user-agent groups, and the declared sitemaps.
  • More — Source Code (the HTML source, formatted in an editor, with a jump to the W3C validator), an SEO Guide and a GEO Guide as in-depth reference content, and Export / Import to save an analysis as JSON or as an HTML report, load it back in, or open 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 according to version 2 of the llms.txt specification — using the same rules as the llms.txt Generator.
  • AI-crawler check: robots.txt is tested against 16 named AI bots — training crawlers such as GPTBot, ClaudeBot, Google-Extended, or CCBot, search crawlers such as OAI-SearchBot, Claude-SearchBot, and PerplexityBot, and user-triggered fetchers such as ChatGPT-User or Claude-User.
  • Content-Signal from robots.txt or an HTTP header gets its own card (purely informational, path-scoped rules included) 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. Pages up to 5 MB are analyzed in full; for anything larger, the tool tells you that only the first part was evaluated. If you run your own local proxy, you can also switch on the optional Expert Mode — no rate limits, plus batch checks for links, sitemaps, and structured data across several pages. How the proxy works and which limits apply (time budget, maximum size, rate limits) 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.
  • DNS, SSL, Redirect & URL — when the SSL / Security or Redirects tab flags something odd, that's where you dig into DNS, the certificate chain, and redirects in detail.

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.