Name: OnPage.dev
Author: dev.onpage

Tools observed via MCP handshake

scan_page — Scan one public web page for SEO and AI visibility. Returns a 0-100 score, the issues to fix first with why and how, AI readiness, and the key facts (title, des
check_ai_visibility — Check whether ChatGPT, Claude, Perplexity, Gemini and other AI crawlers may read a page (robots.txt per bot), whether llms.txt exists, how ready and citable the
check_focus_keyword — Check how well a page targets one search term: title, meta description, H1, URL, first 100 words, subheadings, image alt texts and keyword density (flags stuffi
get_fix_pack — Use after a scan to get the fixes as code. Set platform to how the user ships: html (default), wordpress, git for a pull request, or cloudflare for an edge Work
check_web_vitals — Get Core Web Vitals from real Chrome users (the Chrome UX Report, the field data Google uses for ranking): LCP, INP, CLS, FCP and TTFB at the 75th percentile, o
analyze_logs — Analyse server access log lines to see what Googlebot, Bingbot and AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Appl
submit_indexnow — Submit changed URLs to IndexNow, so Bing, Yandex, Naver, Seznam and Yep recrawl them within minutes instead of days. Call it after a fix is live. The first time
check_accessibility — Check a page against WCAG 2.1 level AA, the standard behind the European Accessibility Act (EN 301 549): page language, text alternatives, form labels, link and
check_answer_format — For a question people search (a featured snippet or a People Also Ask question), find the section that answers it on the pages that rank and on your page, and c
check_consent — Quick check of the cookie banner setup from the HTML. To see what GA4 really sends before and after accepting, use check_ga4_tracking. Check a page's cookie con
check_product_page — Check an ecommerce product page for Google: Product structured data with name, image, price, currency and availability, identifiers (SKU, GTIN, MPN, brand), shi
map_topics — Group a site's search queries into topic clusters and map them to pages: which page owns each topic, where several pages compete for the same topic, which topic
check_question_coverage — Check how well a page covers a topic the way AI search reads it. AI Mode and AI Overviews split a search into many sub-questions (a query fan-out) and pick a so
check_hreflang — Check the hreflang setup of a multilingual page: valid language and region codes, x-default, the self-reference and duplicates, then each language version: does
check_trust_signals — Check the trust signals Google and AI models look for across a site, not only on one page: an About page with real content, contact details (email, phone, addre
check_local_seo — Check a local business site for Google Maps and local search: LocalBusiness markup (most specific type, address, phone, opening hours, geo coordinates), whether
map_link_equity — Map how link authority flows through a site from a finished site audit: internal PageRank per page, click depth from the home page, links in and out. Finds page
check_ga4_tracking — Use when GA4 numbers look wrong or consent may not reach GA4. For a quick check of the banner setup from the HTML, use check_consent. Debug Google Analytics 4 o
log_fix — Record SEO fixes after they ship, so OnPage.dev keeps them honest: it checks about every 6 hours that each fix is still live (title, description, canonical, rob
get_fix_log — Show a fix log: per fix whether it is still live, undone or changed since it shipped, with the restore code for every undone fix, the measured impact when measu
explain_index_status — Use when pages are missing from Google: turns Search Console URL Inspection results (or rows from the Pages report: URL plus reason) into causes, fixes and the
build_edge_rules — Use when the same SEO problem repeats across a section of a site (all product pages, all blog posts) and the CMS or templates are hard to change: from a finishe
get_prerender_worker — Use when a site is built in the browser (React, Vue, Angular) and AI crawlers such as GPTBot, ClaudeBot and PerplexityBot, which do not run JavaScript, see an e
diagnose_traffic_drop — Use when organic traffic dropped: fetch two periods of equal length from the user's Search Console (before and after the drop), per page or per page and query,
find_ctr_gaps — Use to find quick wins without ranking changes: from the user's Search Console rows (page, or page and query, with impressions, clicks or CTR and position), fin
find_striking_distance — Use to find the fastest ranking wins: from the user's Search Console rows by query and page, finds queries ranking at positions 8 to 20 with real impressions, g
check_vitals_trend — Use to see whether speed changed for real users and since when, for example after a performance fix: Core Web Vitals (LCP, INP, CLS, FCP, TTFB) at the 75th perc
measure_ai_citations — Use to prove AI visibility gains: pass how often AI assistants cited each page before and after the fixes (from Ahrefs Brand Radar or another AI-visibility tool
check_sitemap — Use to check a site's XML sitemap the way Google reads it: finds it through robots.txt or the usual locations, follows a sitemap index, and checks the format, t
extract_from_pages — Use to check a template change or a data point across many pages at once, like custom extraction in a crawler: give up to 20 URLs and one of a CSS selector (wit
find_duplicate_content — Use to find pages that say almost the same thing, which compete with each other and make Google pick one: groups the pages of a finished site audit by text simi
check_url_parameters — Use when a site has filter, sort, tracking or search URLs that waste crawl budget or create duplicates: classifies every query parameter found in a site audit's
create_dashboard_feed — Use when the user wants an SEO dashboard or client report that stays up to date: OnPage.dev then checks the site's key pages every day and keeps the history (sc
get_dashboard_data — Use to fill an SEO dashboard or report from a feed made with create_dashboard_feed: returns one dataset as a clean table with a date column (YYYY-MM-DD) and ful
build_seo_dashboard — Use when the user wants a live SEO dashboard in Claude (Claude Dashboards or an artifact): returns a complete blueprint that combines a realtime block from the
scan_html — Scan raw HTML that is not published yet, for example a local build, a template or a draft from your editor. Returns the same score, fixes and AI readiness as sc
rescan_and_compare — Scan a live page again and compare it with the previous scan of that page: score change, issues fixed, new issues and AI readiness change. Use this after deploy
check_snippet — Estimate how a title and meta description show in Google: pixel width against the cut-off on desktop and mobile, and the truncated text a searcher would see. No
generate_schema — Writes validated JSON-LD for Article, Product, FAQPage, Organization or BreadcrumbList. For LocalBusiness use check_local_seo; to check JSON-LD you wrote yourse
find_answer_passages — Find the passages on a page that best answer a given question, the way AI answer engines pick text to quote. Returns the top passages with their heading, word c
generate_llms_txt — Build a ready-to-upload llms.txt for a site from its sitemap and home page: site name, summary and the main pages grouped by section. Upload the result to the r
ai_crawler_policy — Write robots.txt rules for AI crawlers based on a policy, and merge them into the site's current robots.txt. Policies: allow_all, search_only (allow AI search a
deep_audit — One page, every measurement by section: use it when scan_page is not detailed enough. For a whole site use start_site_audit. Everything OnPage.dev measures on a
check_urls — Check up to 20 URLs at once: final status code, the full redirect chain and where each one ends up. Built for site migrations, broken link sweeps and launch che
test_robots — Test a URL against the site's live robots.txt for one or more crawlers, using Google's matching rules (most specific user-agent group, longest matching rule, Al
validate_schema — Validate JSON-LD you wrote before you publish it: JSON syntax, @context and @type, absolute URLs, ISO dates, and Google's required and recommended fields per ri
compare_html — Compare two versions of a page's HTML, for example before and after a code change, and report what got better or worse for SEO: score, issues fixed and introduc
start_site_audit — Start an SEO audit of a whole site (up to 25 pages from the sitemap, or from the home page links when there is no sitemap). Returns an audit_id and the first pr
get_site_audit — Continue a site audit started with start_site_audit: each call scans the next pages and reports progress. Keep calling until status is complete, then you get th
suggest_internal_links — Suggest which existing pages should link to a target page, with anchor text, based on a completed site audit. The target can be a page from the audit or a new p
compare_pages — Compare a page with up to 3 competitor pages that rank for the same search: score, AI readiness, words, headings, rich results, speed and more side by side, plu
prioritize_fixes — Use when Search Console, GA4, Ahrefs or Semrush data is available, also to explain a traffic drop (pass clicks_previous): ranks the fixes by the traffic or reve
check_entity_graph — Check how a page's structured data describes who and what it is about, the way AI knowledge graphs read it: which entities there are (Organization, Person, Arti
validate_llms_txt — Validate a site's llms.txt against the llmstxt.org format: served as text (not an HTML page), one H1 with the site name, a > summary, ## sections with [name](ur
compare_ai_citations — Compare the pages AI assistants cite with the ones they skip, using citation counts from the user's connected tools. Before calling, check your available tools:
watch_page — Start watching a page. OnPage.dev rescans it about once a day and records what changed for search and AI: the page going down or redirecting, a new noindex, AI
get_watch — Read a watch created with watch_page: the latest snapshot, when it was last checked and every change found so far, newest first.
unwatch — Stop a watch created with watch_page and delete its history.
create_content_brief — Build a writing brief for a search term from the pages that rank for it. Get the competitor URLs from your own search tool, Ahrefs, Semrush or the user (1 to 3)
plan_redirects — Match old URLs to new ones for a site migration or restructure and write the redirect rules. Give the old URLs (a list, or the old site's address while it is st
share_result — Scan a page again and publish a shareable proof page on onpage.dev with the score before and after, the issues fixed and the ones still open. Useful after fixin
render_page — Use to see what visitors and crawlers without JavaScript (GPTBot, ClaudeBot, PerplexityBot) get on the first screen. Load a page in a real browser on a phone (3
get_layout_probe — Get a small JavaScript measurement script to run in your own browser tool (Claude in Chrome, Playwright, Puppeteer or similar). Run it on the page at each viewp
analyze_layout — Analyse the results of the get_layout_probe script, measured in your own browser: the same checks as render_page (H1 and call to action position, pop-ups, tap t
screen_reader_view — Show a page the way a screen reader announces it, from the browser's accessibility tree: landmarks, the heading outline, and the reading order of links, buttons
export_findings — Turn a page scan or a finished site audit into an action plan the team can work from. Returns: rows for a spreadsheet plus a private CSV link that loads straigh
measure_impact — Use to answer "did our fixes win traffic?" with before and after numbers. For the score change of one page use rescan_and_compare. Show whether SEO fixes paid o
match_intent — Check whether a page matches what searchers want for a keyword, based on what actually ranks. Fetch the top organic results for the keyword with the user's conn
check_readability — Check how easy a page is to read, against the right target. A product page should read differently from documentation, so the target depends on the page type (g
check_og_tags — Check how a page looks when it is shared on Facebook, LinkedIn, X, WhatsApp, Slack or iMessage: every Open Graph and Twitter Card tag, and the share image itsel

when	check	result	http	latency	detail
1 h ago	mcp initialize	ok	200	15 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 70 tools
8 h ago	mcp initialize	ok	200	36 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 70 tools
14 h ago	mcp initialize	ok	200	14 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 55 tools
21 h ago	mcp initialize	ok	200	16 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 50 tools
27 h ago	mcp initialize	ok	200	25 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 50 tools
34 h ago	mcp initialize	ok	200	77 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 50 tools
2 d ago	mcp initialize	ok	200	47 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 50 tools
2 d ago	mcp initialize	ok	200	13 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 50 tools
2 d ago	mcp initialize	ok	200	65 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 42 tools
3 d ago	mcp initialize	ok	200	59 ms	server onpage-dev 1.4.0 · protocol 2025-06-18 · 39 tools

OnPage.dev

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from