OnPage.dev Use in Claude & ChatGPT

Analyse your site like search and AI do.

Free SEO and AI check for any page or whole site. Get a score and the first fix to make, in plain language.

What do you want to scan?
  • ChatGPT app icon: check if ChatGPT and GPTBot can read your site
  • Perplexity app icon: check if Perplexity and PerplexityBot can read your site
  • Claude app icon: check if Claude and ClaudeBot can read your site
  • Gemini app icon: check if Gemini and Google-Extended can read your site
Can AI assistants read your site?

This is what a report looks like

Three real examples of the same page at different scores.

Sample OnPage.dev report, weak score of 46: 2 errors, 1 warning and 6 tips

What you get

Score and explanation
Every point in plain language, in order of importance.
Google preview
Your title and description as a search result, on desktop and mobile.
Social preview
How a shared link looks on Facebook, LinkedIn and X.
Headings and keywords
All headings, keyword tables and a word cloud.
AI crawlers and llms.txt
Whether GPTBot and ClaudeBot may read your site, and your llms.txt.
AI readiness score
A second score for AI search: can assistants read, trust and quote your page?
Core Web Vitals
Real Chrome visitors on phone and desktop: pass or fail, and the share of visits that load fast.
JavaScript apps too
React, Angular and Vue pages are loaded in a real browser, and you see what AI crawlers miss.
Whole site
Up to 25 pages in one scan, with what changed since last time.
Share and keep
CSV, PDF, or straight to Sheets, Slack or your task board.

The whole SEO loop inside your AI agent:

  1. scan_pageFindwhat is wrong
  2. get_fix_packFixwith ready code
  3. scan_page · htmlCheckbefore you ship
  4. share · exportSendto Sheets, Slack or your task board
  5. watch · pageWatchfor anything that breaks
  6. measure · impactMeasurethe traffic it won

37 tools, 116 jobs, free, no key.

You ask in your AI tool

  • Claude
  • ChatGPT
  • Cursor
  • VS Code

It checks how AI search sees you

  • ChatGPT
  • Claude
  • Gemini
  • Perplexity

It ships the fix to your CMS

  • WordPress
  • Shopify
  • Webflow
  • Wix
  • Storyblok
  • Sanity
  • Contentful
  • Strapi
  • Ghost
  • Magento
  • GitHub pull request
  • and any CMS at the edge

WordPress plugin

Your agent proposes. You approve in one click.

Your agent sends the fixes to the OnPage.dev plugin in wp-admin. You see what changes, tick what you want, and it goes live.

  • Old and new, side by side. Fixes, new drafts and post updates. Nothing changes until you approve it.
  • Yoast SEO or Rank Math. Or the plugin writes the tags itself.
  • Undo any time. Every change keeps its old value.
  • No passwords shared. OnPage.dev never logs in to your site.

Get the WordPress pluginFree. Upload it under Plugins, Add New.

Site memory

Your agent forgets. OnPage.dev remembers.

AI assistants start every chat from zero. OnPage.dev keeps one memory per site, so the next chat starts where the last one stopped.

  • Across chats and clients. Start in Claude, carry on in Cursor with the same key.
  • Learns what works. Every result is tied to the fixes before it, across sites if you opt in.
  • Connects the dots. Alerts come with the fixes and deploys behind them.
  • Knows what is next. Open alerts and unmeasured fixes become the next steps.

Search Console, GA4 and Bing

Ask about your traffic. Stop exporting CSVs.

Your assistant already reads Search Console, GA4 and Bing through its connectors. OnPage.dev turns those rows into answers.

  • Finds the day it broke. Spikes and drops against the normal weekday pattern.
  • Names the Google update. Core and spam updates within 3 days, from Google’s status dashboard.
  • Shows the queries you lost. And the queries two of your pages split.
  • Sees what AI answers. Question-style searches per page, and Google against Bing.

Content autopilot

Your agent writes. In your site’s own voice.

OnPage.dev learns how your site writes, plans what to publish next and checks every draft before you see it. Your own Claude or ChatGPT does the writing.

  • Learns your voice. Sentence length, structure and tone, from your best articles.
  • Plans the calendar. Pages almost on page 1 and topics you miss, dated per week.
  • Checks every draft. Voice match, figures without a source and SEO, before you approve.
  • Learns what works. Formats that lifted traffic on your site shape the next plan.

Built for AI agents

Most SEO tools stop at a report. OnPage.dev gives your AI agent the whole loop, from the first scan to the traffic it won. 37 tools, 116 jobs, free.

Takes action

Ships the fix
To WordPress, Shopify, Webflow and 7 more CMS, as a pull request, or at the edge.
Wins back lost links
Broken and lost backlinks and 404 visits, turned into 301s and outreach emails ready to send.
Checks every deploy preview
Vercel, Netlify and Cloudflare previews against production before you merge, as a pull request comment.
Answers your reviews
A reply for every Google review, unhappy customers first, posted after you approve.
Guards every deploy
robots.txt, sitemap, noindex and canonical checked every 6 hours, with the fix in the alert.

Proves it

Tracks the rankings that matter
Pages you worked on, money keywords and near wins, picked for you, with what moved each run.
Proves the result
Clicks, AI citations and speed, before and after, against pages you did not touch.
Paid and organic together
Ad spend you can test cutting where you rank top 3, and the converting ad terms that need a page.
Shows your share of voice
Your share of the clicks against competitors, and the keywords where they take them.
Counts visits from AI
ChatGPT, Perplexity and Gemini visits from your GA4, and brand versus non-brand growth.

Sees more

Finds keyword cannibalization
Your pages side by side: which one wins the keyword, on which signal, and how to fix it.
Finds where AI skips you
Questions where ChatGPT or Perplexity name competitors and not you.
Remembers every site
One memory per site across chats: what was shipped, what worked, and what to do next.
Sees what bots really get
The page as Googlebot, GPTBot and ClaudeBot get it: firewall blocks, pay-per-crawl and cloaking.
Sees what competitors publish
New and updated pages from their sitemaps every week, flagged when they touch your topics.

Free, fair and private

Reads pages like a crawler and like a browser
The scan reads the HTML your server sends, the way Google and AI crawlers do. The first-screen and screen reader checks load the page in a real browser on phone, tablet and desktop.
Free for everyone, fast for everyone
Fair-use limits per minute keep it quick: 10 page scans and 2 site audits of up to 25 pages. Real-browser checks share a daily budget.
Private by design
No account, no cookies, no page content stored. Only scores and issue names are kept, for up to 30 days, to show what changed.

Frequently asked questions

Is OnPage.dev free?

Yes. Scanning a page or a whole site is free, here and in your AI agent, with no account and fair-use limits per minute. Agencies and teams that need higher limits and reports with their own logo can ask about a plan.

Do I need an account?

No. You enter a website address and start the scan. You do not have to sign up.

Does it check AI crawlers such as GPTBot and ClaudeBot?

Yes. The scan reads the robots.txt of your site and shows whether AI crawlers such as GPTBot and ClaudeBot are allowed or blocked. The rules are matched the way Google documents robots.txt, and OpenAI lists its crawlers in its crawler overview.

What is llms.txt?

An llms.txt is a text file in the root of your site. It gives AI systems a short explanation of your site and its most important pages. The format is a proposal described at llmstxt.org. The scan shows whether your site has one, and the free llms.txt generator and llms.txt validator help you make and check it.

How does OnPage.dev compare to Yoast, Screaming Frog or Ahrefs?

OnPage.dev covers on-page SEO in one free scan: the checks you know from Yoast, without a plugin, and a crawl of up to 25 pages like Screaming Frog. On top of that it shows what AI search sees, whether your page matches the search intent of what ranks, and whether it reads as easily as the pages that rank. It has no search volumes, rankings or backlinks of its own. If Search Console, GA4, Ahrefs or Semrush is connected to your AI assistant, OnPage.dev uses their numbers to rank every fix by the traffic it can win.

Can I use OnPage.dev inside Claude or ChatGPT?

Yes. OnPage.dev runs as a free MCP server, so Claude, ChatGPT, Cursor and other AI assistants can scan a page for you and answer with the fixes. Add the server URL https://onpage.dev/mcp as a connector. It has 37 tools that cover 116 SEO jobs, from scans and ready fixes to whole-site audits, search intent and readability checks against the pages that rank, redirect plans, an llms.txt generator and validator, a first-screen check on three devices, a screen reader view, daily watches, exports to Google Sheets, Slack and task boards, fixes your agent can ship to WordPress, and a before and after impact measurement. See the setup steps.

What makes OnPage.dev different from other SEO tools?

It runs the whole SEO loop inside your AI agent: find what is wrong, write the fix, check it before you deploy, ship it to WordPress or as a pull request after you approve, send the plan to your team, keep watching, and measure the traffic it won. It checks what AI search sees, not only Google. And it is free with no account. Data MCPs such as Ahrefs and Semrush bring the numbers; see how OnPage.dev compares.

Does it work for JavaScript sites too?

Yes, also pure client-side apps built with React, Angular or Vue. When the server sends an almost empty page, OnPage.dev loads it in a real browser and checks the rendered page, the way Google sees it. It also shows how many words the server sends, because AI crawlers such as GPTBot and ClaudeBot do not run JavaScript. A second check compares the page with and without JavaScript on a phone, tablet and desktop.

Does it check page speed and Core Web Vitals?

Yes. Every scan shows Core Web Vitals from real Chrome users, the field data Google uses for ranking: LCP, INP and CLS, plus FCP and time to first byte, on phone and desktop. You see whether the page passes, and what share of visits is good, needs work or poor. Pages with too little traffic fall back to the whole site.

Get insights now

Scan your page or site and see what to fix first. Free, no account needed.