Skip to content

Haide · free tool

Signal Check

Six signals of AI-search readiness, for any URL. Paste a landing page, a blog post, or a homepage — we return pass/warn/fail verdicts with evidence and a specific fix.

  • Scope: the page you enter, plus site-wide robots.txt and sitemap.xml.
  • Thirty seconds, no email, no account.
  • Free, forever. Use it on your pages or anyone else's.

Enter any URL — a homepage, a landing page, a blog post. Just a bare domain works too; we scan the homepage in that case.

We store the URL and results for 30 days. No email.

What the scan checks

Six signals that actually move AI citations.

Six checks with a direct causal line to whether ChatGPT, Claude, and Perplexity mention you in their answers — the ones that actually move citations, rather than a bloated checklist.

Signal 01

AI Crawler Access

What: Your robots.txt plus a live request with GPTBot's user-agent to confirm your server actually lets the bot through.

Why: Cloudflare blocks AI crawlers by default since July 2025. Plenty of sites are invisible to ChatGPT and don't know it.

Signal 02

Entity Clarity

What: Organization schema with a sameAs array linking to Wikipedia, LinkedIn, or similar authoritative profiles. If the scanned page does not have it, we also check the homepage (where it usually lives).

Why: LLMs disambiguate your brand by cross-referencing sameAs links. Without them, you are one of many companies with your name.

Signal 03

Answer Capsule

What: The page's H1 length, hero paragraph length, brand presence, boilerplate patterns, and — via TextRazor — entity density and subjectivity.

Why: LLMs quote the first 40–60 words of a page more than any other section. This signal checks whether those words earn the quote.

Signal 04

Structured Data Coverage

What: Every JSON-LD @type on the scanned page. We flag whether you have the citation-driving types (FAQPage, Article, Product, HowTo).

Why: FAQPage markup alone lifts citation rates measurably. Baseline Organization schema is not enough on its own.

Signal 05

Technical Integrity

What: HTTPS, Strict-Transport-Security header, canonical tag, meta robots (checking for accidental noindex), and whether sitemap.xml exists at the site root.

Why: One accidental noindex or a cross-domain canonical silently kills discoverability. These are the "check the basics before debugging anything fancy" signals.

Signal 06

Core Web Vitals

What: LCP, INP, and CLS for the scanned URL on mobile, pulled from Google's CrUX field data via PageSpeed Insights (real users, not synthetic lab tests).

Why: Slow pages get fewer citations. Google's threshold is not marketing — AI Overviews filter by it.

How it works

Three steps. No configuration.

Signal Check runs server-side where it can, client-side where it must, and degrades gracefully when any piece is missing. You get a complete report or a clear reason why a specific signal is inconclusive.

015 seconds

Enter a URL

A landing page, a blog post, a homepage — any URL works. A bare domain is fine too; we scan the homepage in that case. No ownership check.

023 seconds

We fetch and parse

The page, plus robots.txt and sitemap.xml for site-wide rules. We send one request with GPTBot's user-agent to see what LLM crawlers actually get back. The hero text goes to TextRazor for entity analysis.

03under 30 seconds total

You get six verdicts

Pass, Warn, or Fail per signal. Each one ships with its evidence (what we saw) and a specific fix (what to do about it). Core Web Vitals loads last from your browser in the background.

Why we built this

The first thirty seconds of every SEO engagement.

Before any conversation about content or strategy, we check six things on a page: whether LLMs can read it, whether the brand entity is clear in the schema, whether the opening paragraph earns a quote, which structured data types are present, whether the technical foundation is clean, and whether the page loads fast enough to cite. If those six answers are not good, the rest of the work has nothing to build on.

Signal Check is that diagnostic, automated. We built it for ourselves, to stop asking the same six questions by hand on every prospect call. We made it public because seeing it run on your own URL is more useful than any pitch deck we could write.

Use it on your homepage. Use it on the landing page you just shipped. Use it on a competitor's article that keeps showing up in ChatGPT. The six signals are the ones that decide whether a page enters the AI-answer conversation in 2026 — and each one has a specific, fixable answer.

Frequently asked questions