New Kitbase MCP is live — talk to your analytics in plain English
Kitbase Kitbase
Start free
Meta tags & schema

AI Citation Preview

Paste a URL to preview how it appears as a Google result, a social card and an AI answer citation. We check the title, description, canonical, Open Graph tags, JSON-LD schema, dates and headings, and score what to fix so ChatGPT and Perplexity cite you.

How it works

1

Paste a URL

Any public page — a blog post, a docs page, a landing page. A bare domain works too; we default to https.

2

We fetch it like a crawler

We request the HTML the way a search or AI crawler does — no JavaScript — and read the title, meta tags, Open Graph, JSON-LD, headings, dates and author.

3

See how it renders, and what to fix

A Google result, a social card and an AI answer citation side by side, plus a scored checklist of what is missing or malformed.

What AI answer engines look at

Nobody publishes the algorithm. What we do have are citation studies — which pages ChatGPT, Perplexity and Claude cite, and what those pages have in common — and the crawler behaviour we see in Kitbase's own bot analytics. These are correlations, not rules, but they are consistent enough to act on. The tool checks each of them.

  1. 1

    A title and first paragraph that answer the question

    Answer engines lift the opening of a page far more often than a paragraph buried halfway down. If your first paragraph states the answer plainly, that is the sentence they quote — and it is what this tool shows in the citation card.

  2. 2

    A visible, machine-readable date and an author

    Recency and accountability are two of the strongest correlates of being cited. Put datePublished / dateModified in JSON-LD or article:published_time / article:modified_time meta tags, and name an author. A page with no date reads as stale.

  3. 3

    Structured data that names what the page is

    Article or BlogPosting for editorial content, Organization for who publishes it, BreadcrumbList for where it sits, FAQPage when the page genuinely holds question-and-answer pairs. Valid JSON-LD is what turns a wall of HTML into something an engine can classify.

  4. 4

    Canonical and indexable

    A self-referencing canonical and no noindex. Most AI engines lean on a search index somewhere in the pipeline; if the page cannot be indexed, it is very unlikely to be cited.

  5. 5

    Fast, server-rendered HTML

    The content, meta tags and schema should be in the HTML the server sends. Tags injected by JavaScript are invisible to almost every crawler — including this tool, on purpose.

For the engine-by-engine detail behind these, read how Perplexity chooses its citations and how Claude picks its web sources.

How the score works

Every page starts at 100. Each distinct issue we find deducts a fixed amount by severity, and the score never goes below zero. It is a checklist score — a measure of how complete and well-formed the page's markup is — not a prediction of where the page will rank or how often it will be cited.

Severity Deduction Examples
Error −20 noindex, missing title, invalid JSON-LD, page not reachable
Warning −8 no meta description, title over 60 characters, no canonical, no date signal, no og:image, thin content
Info −2 multiple h1, no twitter:card, no author, redirected, slow response

Fix the errors first: they are the things that stop a page being indexed or parsed at all. Warnings are the tags an engine expects to find and will hold against you when they are missing. Infos are polish.

Frequently asked questions

Does the tool render JavaScript?

No. We read the HTML your server sends, which is exactly what most crawlers see — Googlebot renders JavaScript eventually, but GPTBot, ClaudeBot, PerplexityBot and their peers largely do not. If your title, meta description or Open Graph tags are injected on the client, they are invisible here and invisible to those crawlers. Server-render them.

Why is my og:image missing here when it shows up in Slack?

Usually one of three things: the tag is added by JavaScript after load, the URL you pasted redirects to a page that carries different tags, or the image URL is relative and the unfurler you tested with resolves it while others do not. Open the Open Graph & Twitter panel to see the exact tags we found on the final URL.

How long should a title and a meta description be?

Keep titles under about 60 characters and descriptions under about 160. Google actually truncates by pixel width, so those are safe ceilings rather than exact limits. AI engines do not truncate the same way, but they do read the title and description as the page's own summary of itself — so make them literal, not clever.

Do I need FAQ schema?

Only if the page really contains question-and-answer pairs. Google dropped most FAQ rich results in 2023, but well-structured Q&A still helps answer engines lift a direct answer, and the tool flags a missing FAQPage only when it sees several question-shaped headings. Never add FAQ markup for content that is not on the page.

Do you store the page?

Not the page. We fetch it, analyze it in memory and return the result; the result is cached for five minutes so repeated checks of the same URL do not hammer your server, then discarded. What we do keep is a usage log — the URL you checked and its headline score — so we can see how the tool is used and improve it.

Why does it say the page blocked our request?

Your CDN or firewall answered with a challenge page or a refusal — a Cloudflare "Just a moment" interstitial, a 403, a 429. Most AI crawlers get the same treatment, which is worth knowing. Run your domain through the AI Crawler Access Checker to see exactly which crawlers your origin turns away.

Can I check a page behind a login or on a staging server?

No. Only publicly reachable pages work, and requests to private or internal network addresses are refused outright. Publish the page (or a preview URL) first, then check it.

Is the score a ranking prediction?

No. It is a checklist score: 100 minus a fixed deduction for every issue found. A high score means the page is well-formed and gives crawlers everything they look for; it says nothing about how good the content is or where it will rank.

Stop checking by hand. Kitbase watches this for you.

AI Visibility runs continuously on your real traffic and your real pages — with alerts when something changes, not when you remember to look.