Site SEO & AI Crawler Audit

Shows whether robots.txt allows or blocks 14 published AI crawlers Shows the rule that decided each crawler, the sitemaps and any noindex or noai directives Reads a page's title, description, canonical link, language and icons Reads Open Graph and Twitter share tags and lists the common ones that are missing Follows the redirect chain with each status code and shows the final address and headers Checks one product page's title, description, h1, canonical link and Product structured data (price, GTIN, availability) Checks a domain for llms.txt, agents.md, the Shopify UCP file, a sitemap and AI crawler rules in robots.txt Checks a page for five AI citation signals: summary, author credentials, Q&A format, headings, structured data Checks up to 40 sitemap addresses for broken pages and redirect chains, skipping pages robots.txt disallows Checks a landing page's h1, call to action, form fields, trust signals, pricing, viewport and contact path Tests up to five call-to-action links of a page and gives each finding with evidence and a fix Checks the exposed surface of a domain its owner proves: leaked files, dangling subdomains, default pages Finds API keys in the JavaScript an owned app ships, public source maps and open admin paths, keys masked Flags 6 legal signals on an owned app (COPPA, fonts, session replay, CAN-SPAM, renewals, DMCA) with sources Refuses private, local and internal addresses and redirects into them

Site SEO and AI Crawler Audit checks public web pages and reports what they publish right now: SEO tags, redirects, AI crawler rules, AI citation signals, landing page conversion and, for a site you own, what leaks publicly. People also call it Site Check. The exposure check works only on a domain you prove you own: the first call gives a DNS TXT record or a file to publish, and the check runs once it is live. It never looks up a person, a user name or an email address. Page and crawler checks: which of 14 AI crawlers robots.txt allows on a page and the rule that decided it; the title, description, canonical, Open Graph and Twitter tags and which are missing; and the 301 redirect chain with status codes and headers. Store and AI checks: one product page's SEO and Product structured data (price, GTIN, availability); a domain's llms.txt, agents.md, UCP file, sitemap and AI crawler rules; five AI citation signals of one page, each with evidence and a fix; and a sample of up to 40 sitemap addresses for broken pages and redirects. Landing page check: twelve conversion items such as the h1, the call to action and whether its links work, form fields, trust signals, a price section, viewport and a contact path, each with evidence and a fix. It is a checklist, not a forecast. Exposure check: exposed or clean with the top 3 risks and fixes, from dangling subdomains, leaked files such as .env, admin paths and masked API keys in the page's scripts, plus six legal signals with official sources. No port scan, and not legal advice. What it does not do: no speed test, no rankings or traffic, no JavaScript, no sign-in, no page text returned, and no private, local or internal addresses. It does not request a page that robots.txt disallows for Agent Tools. robots.txt is a request, not access control, and a firewall can treat real crawlers differently. It stores nothing about you or the site. Answers are cached for five minutes, and the only lasting record is a daily count of calls per tool.