Overall AI readiness score
A combined result across all audit signals.
Overall AI readiness score
A combined result across all audit signals.
Overall AI readiness assessment
Clerk was independently audited by llmsmap. clerk.com currently scores 70/100 for AI readiness. The result combines AI-specific files, crawler policy, sitemap discovery, structured homepage data, and—when available—the mobile Google Lighthouse technical profile.
llms.txt is accessible and contains 4,666 tokens. An expanded llms-full.txt is also available with 192 tokens, giving agents more direct context. No separate ai.txt policy was detected; it is optional, but can clarify training, retrieval, and attribution preferences.
robots.txt is available. 9 of 11 tracked AI bots are not blocked, while 2 receive a prohibition. Declared sitemaps: 1. No Schema.org type was detected on the homepage. 0 OpenGraph tags were found and markup completeness is 0%, leaving more entity interpretation to crawlers.
The mobile Lighthouse profile adds Performance 43/100, Accessibility 96/100, Best Practices 73/100, SEO 100/100, and experimental Agentic Browsing 100/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.
A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.
Performance
Accessibility
Best Practices
Technical SEO
Agentic Browsing
Mobile performance is 43/100, with the largest visible content block appearing in 13.5 s and the browser main thread blocked for 570 ms. Layout shift was 0. The main thread is where the browser runs JavaScript, calculates layout, and paints the page; long work there delays both user input and browser-agent actions.
Accessibility scored 96/100, Best Practices 73/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 100/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.
Split long JavaScript tasks, defer non-critical scripts and styles, and shorten blocking request chains. This helps the primary content appear sooner and makes controls usable earlier.
Remove unused CSS and JavaScript, load heavy widgets on demand, and limit third-party scripts. Less code means less parsing and background work on the device.
Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.
First content
Main content
Layout stability
Blocking time
Visual speed
Machine-readable files, crawler policy, discovery, and homepage markup.
ai.txt file was not found
1 sitemap found
Schema.org markup was not found on the homepage
OpenGraph tags were not found on the homepage
Based on robots.txt analysis
Declared discovery routes for crawlers and agents.
# Clerk > The most comprehensive User Management Platform. Clerk is a complete suite of embeddable UIs, flexible APIs, and admin dashboards to authenticate and manage your users. ## Index and content files - [All llms-full.txt files](https://clerk.com/llms-full.txt): Meta-index linking to every llms-full.txt on clerk.com - [Documentation index](https://clerk.com/docs/llms.txt): Curated index of Clerk documentation pages, maintained in clerk-docs - [Documentation (full content)](https://clerk.com/docs/llms-full.txt): Complete Clerk documentation in a single file - [Dashboard index](https://dashboard.clerk.com/llms.txt): Index of the Clerk Dashboard for LLMs and agents - [Articles index](https://clerk.com/articles/llms.txt): Index of every Clerk article - [Articles (detailed)](https://clerk.com/articles/llms-index.txt): Index of all Clerk articles with metadata and table of contents - [Articles (full content)](https://clerk.com/articles/llms-full.txt): Complete markdown body of every Clerk article, concatenated into a single file - [Blog index](https://clerk.com/blog/llms.txt): Index of every Clerk blog post - [Blog (detailed)](https://clerk.com/blog/llms-index.txt): Index of all Clerk blog posts with metadata and table of contents - [Blog (full content)](https://clerk.com/blog/llms-full.txt): Complete markdown body of every Clerk blog post, concatenated into a single file - [Changelog index](https://clerk.com/changelog/llms.txt): Index of every Clerk changelog entry - [Changelog (detailed)](https://clerk.com/changelog/llms-index.txt): Index of all Clerk changelog entries with metadata and table of contents - [Changelog (full content)](https://clerk.com/changelog/llms-full.txt): Complete markdown body of every Clerk changelog entry - [Glossary index](https://clerk.com/glossary/llms.txt): Index of every Clerk glossary entry - [Glossary (full content)](https://clerk.com/glossary/llms-full.txt): Complete markdown body of every Clerk glossary entry - [Homepage (markdown)](https://clerk.com/index.md): Full markdown version of the Clerk homepage ## Product - [User Authentication](https://clerk.com/user-authentication): Powerful options to securely authenticate and manage your users - [<SignIn /> component](https://clerk.com/components/sign-in): A production-ready sign-in component with secure authentication, social login, and OTP verification - [<SignUp /> component](https://clerk.com/components/sign-up): A production-ready sign-up component with secure authentication, social login, and OTP verification - [<UserButton /> component](https://clerk.com/components/user-button): A production-ready user button component with account management and multi-session support - [<UserProfile /> component](https://clerk.com/components/user-profile): A production-ready user profile component that centralizes profile, security, connected accounts, billing, and API keys. - [Waitlist](https://clerk.com/waitlist): Gather interest, invite early testers, and go live faster with Clerk's drop-in waitlist - [<Waitlist /> component](https://clerk.com/components/waitlist): A production-ready waitlist component for capturing early sign-ups and managing early access - [B2B Authentication](https://clerk.com/organizations): Add-on features built specifically for B2B applications - [<CreateOrganization /> component](https://clerk.com/components/create-organization): A production-ready component for creating new organizations with member invitations - [<OrganizationSwitcher /> component](https://clerk.com/components/organization-switcher): A production-ready component for switching between organizations and personal accounts - [Billing](https://clerk.com/billing): The easiest way to implement subscriptions for applications - [<PricingTable /> component](https://clerk.com/components/pricing-table): A production-ready component for flexible pricing and seat-based subscription billing in one drop-in - [<CheckoutButton /> component](https://clerk.com/components/checkout-button): A production-ready checkout button that opens a fully integrated, inline checkout drawer for payments and subscriptions - [Platform](https://clerk.com/platform): The user management layer for modern platforms — provision, manage, and customize authentication for your customers' apps - [Pricing](https://clerk.com/pricing): Plans, pricing, and feature comparison for Clerk - [Pricing (markdown)](https://clerk.com/pricing.md): Full markdown version - [Clerk CLI](https://clerk.com/cli): Set up authentication, manage config, and support agent workflows from the command line - [Theme Editor](https://clerk.com/components/theme-editor): Customize Clerk component appearance with a visual theme editor ## Solutions - [React Authentication](https://clerk.com/react-authentication): Embeddable prebuilt UI components for quick and seamless integrations - [Next.js Authentication](https://clerk.com/nextjs-authentication): The fastest and most seamless authentication solution for Next.js - [Expo Authentication](https://clerk.com/expo-authentication): Implement cross-platform authentication the React way - [Authentication for AI](https://clerk.com/ai-authentication): Authentication and abuse protection tailored to AI applications ## Articles - [Build vs Buy Authentication: The Real Cost of Rolling Your Own Auth](https://clerk.com/articles/build-vs-buy-authentication-the-real-cost-of-rolling-your-own-auth.md): Part 1 of 2: the real cost of building your own authentication — build time, endless maintenance, breach liability, compliance, and 3-year TCO — versus buying Clerk. - [Build vs Buy Authentication: The Real Cost of Rolling Your Own Auth - Part 2](https://clerk.com/articles/build-vs-buy-authentication-the-real-cost-of-rolling-your-own-auth-2.md): Part 2 of 2: build vs. buy authentication compared feature by feature, when each makes sense, how to choose a provider, and where Clerk fits, with code to first login. - [Authentication + Billing: How Clerk and Stripe Work Together](https://clerk.com/articles/authentication-billing-how-clerk-and-stripe-work-together.md): Clerk Billing's native Stripe integration puts plan and feature entitlements on the session token you already verify. Part 1 covers the architecture and a B2C paywall setup. - [Authentication + Billing: How Clerk and Stripe Work Together - Part 2](https://clerk.com/articles/authentication-billing-how-clerk-and-stripe-work-together-2.md): Part 2 of Clerk's Stripe billing guide: B2B organization plans and roles, billing webhooks, current limitations, and the build-vs-buy math versus wiring up Stripe yourself. - [Clerk vs AWS Cognito: Developer Experience vs Scale Economics](https://clerk.com/articles/clerk-vs-aws-cognito-developer-experience-vs-scale-economics.md): Part 1 of 3: Clerk vs AWS Cognito on developer experience — drop-in components, Next.js 16 SSR, session management, and building a custom sign-in with MFA. - [Clerk vs AWS Cognito: Developer Experience vs Scale Economics - Part 2](https://clerk.com/articles/clerk-vs-aws-cognito-developer-experience-vs-scale-economics-2.md): Part 2 of 3: Clerk vs AWS Cognito on enterprise architecture — B2B multi-tenancy, per-tenant SSO, RBAC, and SCIM Directory Sync, and where Cognito gets hard. - [Clerk vs AWS Cognito: Developer Experience vs Scale Economics - Part 3](https://clerk.com/articles/clerk-vs-aws-cognito-developer-experience-vs-scale-economics-3.md): Part 3 of 3: Clerk vs AWS Cognito on scale economics — MAU vs MRU billing, the ~208K-user cost crossover, vendor lock-in, and migrating off Cognito cleanly. - [Can Clerk Handle Enterprise Requirements?](https://clerk.com/articles/can-clerk-handle-enterprise-requirements.md): Can Clerk handle enterprise requirements? Yes for the core checklist — SAML/OIDC SSO, SCIM, organizations, RBAC, SOC 2, HIPAA, and a 99.99% SLA — with honest caveats, versus Auth0, WorkOS, and Okta. - [Clerk Security: How We Protect Your Users](https://clerk.com/articles/clerk-security-how-we-protect-your-users.md): Is Clerk secure? Clerk is SOC 2 Type 2 and HIPAA certified, patches every disclosed vulnerability within days, and publishes its full CVE history, uptime record, and outage postmortems. - [How to Evaluate Authentication Providers: A Developer’s Checklist](https://clerk.com/articles/how-to-evaluate-authentication-providers-a-developer-s-checklist.md): Part 1 of 3: the methodology for scoring authentication providers on a weighted 1–10 checklist, plus dimensions 1–7 (auth methods, SSO, SCIM, security) — Clerk, Auth0, WorkOS, and more. - [How to Evaluate Authentication Providers: A Developer’s Checklist - Part 2](https://clerk.com/articles/how-to-evaluate-authentication-providers-a-developer-s-checklist-2.md): Part 2 of 3: dimensions 8–15 (developer experience, pricing, lock-in, AI-agent auth), the weighted checklist, and a scorecard rating Clerk, Auth0, WorkOS, Firebase, Supabase, and Cognito. - [How to Evaluate Authentication Providers: A Developer’s Checklist - Part 3](https://clerk.com/articles/how-to-evaluate-authentication-providers-a-developer-s-checklist-3.md): Part 3 of 3: in-depth provider profiles, red flags, migration and hash-export guidance, and a decision tree — with a worked example scoring Clerk against the 15-dimension checklist. - [Authentication for Serverless and Edge Deployments](https://clerk.com/articles/authentication-for-serverless-and-edge-deployments.md): Part 1 of 3: why ephemeral serverless and edge runtimes break traditional session auth, and the stateless JWT, JWKS, and architectural patterns behind edge-ready providers like Clerk. - [Authentication for Serverless and Edge Deployments - Part 2](https://clerk.com/articles/authentication-for-serverless-and-edge-deployments-2.md): Part 2 of 3: platform notes for Vercel, Cloudflare Workers, and AWS Lambda, managing auth across a monorepo, and a hands-on guide to implementing edge authentication with Clerk. - [Authentication for Serverless and Edge Deployments - Part 3](https://clerk.com/articles/authentication-for-serverless-and-edge-deployments-3.md): Part 3 of 3: a feature comparison of edge auth options — Clerk, Auth0, Cognito, Supabase, Firebase, and roll-your-own — plus security best practices and a production-readiness checklist. - [Clerk Compatibility in Expo 54 and 55](https://clerk.com/articles/clerk-compatibility-in-expo-54-and-55.md): Clerk's @clerk/expo v3.1.x supports Expo SDK 54 and 55. Part 1 of 2 covers version requirements, the New Architecture, Expo Go limits, and Google, Apple, SSO, passkey, and biometric sign-in. - [Clerk Compatibility in Expo 54 and 55 - Part 2](https://clerk.com/articles/clerk-compatibility-in-expo-54-and-55-2.md): Clerk's beta Native Components, secure token caching, organizations, ClerkProvider setup, and production deployment for Expo SDK 54 and 55 — Part 2 of this two-part compatibility reference. - [How to Add Authentication to a Python Backend](https://clerk.com/articles/how-to-add-authentication-to-a-python-backend.md): Part 1 of 3: how Python backend authentication actually works with Clerk — the verify-the-token model, token formats, your DIY-vs-managed options, and Clerk Python SDK setup. - [How to Add Authentication to a Python Backend - Part 2](https://clerk.com/articles/how-to-add-authentication-to-a-python-backend-2.md): Part 2 of 3: complete Clerk authentication for FastAPI, Flask, and Django/DRF — dependency and decorator patterns, endpoint protection, RBAC, error handling, and testing. - [How to Add Authentication to a Python Backend - Part 3](https://clerk.com/articles/how-to-add-authentication-to-a-python-backend-3.md): Part 3 of 3: wire a Clerk-secured Python API to a React frontend, then add webhooks, organizations, M2M tokens, production deployment, and a Clerk-vs-Auth0/Supabase/Cognito comparison. - [How to Add Face ID/Biometric Login to Your Expo+Clerk App](https://clerk.com/articles/how-to-add-face-id-biometric-login-to-your-expo-clerk-app.md): Part 1 of a two-part guide: set up an Expo project with Clerk email/password auth, check device biometric availability, and store credentials behind Face ID or fingerprint. - [How to Add Face ID/Biometric Login to Your Expo+Clerk App - Part 2](https://clerk.com/articles/how-to-add-face-id-biometric-login-to-your-expo-clerk-app-2.md): Part 2 of a two-part guide: build the biometric sign-in button for returning Clerk users, manage stored credentials, and add passkeys, cross-platform handling, and security best practices. - [How to use SwiftUI components in a React Expo and Clerk app](https://clerk.com/articles/how-to-use-swiftui-components-in-a-react-expo-and-clerk-app.md): Part 1 of a two-part guide to building a React Native Expo app with Clerk's native SwiftUI components: why native auth beats WebView OAuth, Expo setup, and Google Sign-In. - [How to use SwiftUI components in a React Expo and Clerk app - Part 2](https://clerk.com/articles/how-to-use-swiftui-components-in-a-react-expo-and-clerk-app-2.md): Part 2 of a two-part guide to building a React Native Expo app with Clerk's native SwiftUI components: Apple Sign-In, user profile management, and Expo Router route protection. - [How to Handle Session Expiry in a React Native App with Clerk](https://clerk.com/articles/how-to-handle-session-expiry-in-a-react-native-app-with-clerk.md): Part 1 of 2: Clerk's two-token architecture, session-lifetime config, and the hooks that detect expiry, with background and offline handling in a React Native Expo app. - [How to Handle Session Expiry in a React Native App with Clerk - Part 2](https://clerk.com/articles/how-to-handle-session-expiry-in-a-react-native-app-with-clerk-2.md): Part 2 of 2: build resilient session-expiry UX in a React Native Expo app with Clerk — redirect and pending-task flows, network-error recovery, native OAuth, and testing. - [How to Set Up Clerk Authentication with Expo Router: Protected Routes, MFA, and Social Login](https://clerk.com/articles/how-to-set-up-clerk-authentication-with-expo-router-protected-routes-mfa-and-soc.md): Set up the authentication foundation for a React Native app with Clerk and Expo Router — ClerkProvider, secure token caching, sign-in/sign-up screens, and protected routes. Part 1 of 2. - [How to Set Up Clerk Authentication with Expo Router: Protected Routes, MFA, and Social Login - Part 2](https://clerk.com/articles/how-to-set-up-clerk-authentication-with-expo-router-protected-routes-mfa-and-soc-2.md): Extend a Clerk-authenticated Expo Router app with user profiles, multi-factor authentication, native Google and Apple sign-in, and component customization. Part 2 of 2. - [The real cost of enterprise SSO: per-connection vs per-MAU pricing](https://clerk.com/articles/the-real-cost-of-enterprise-sso-per-connection-vs-per-mau-p.md): Part 1 of 4: per-connection vs per-MAU enterprise SSO pricing explained, why the real bill outruns the sticker, and how Clerk's MRU-based model fits B2B SaaS. - [The real cost of enterprise SSO: per-connection vs per-MAU pricing - Part 2](https://clerk.com/articles/the-real-cost-of-enterprise-sso-per-connection-vs-per-mau-p-2.md): Part 2 of 4: the hidden costs of enterprise SSO — the SSO tax, SCIM fees, and the six-figure price of building it in-house versus buying managed auth like Clerk. ## Blog - [Adding Clerk auth to your CLI](https://clerk.com/blog/adding-clerk-auth-to-your-cli.md): A practical OAuth 2.0 + PKCE localhost-callback pattern for authenticating CLI users with Clerk. - [Build a blog with tRPC, Drizzle, Next.js and Clerk](https://clerk.com/blog/build-a-blog-with-trpc-drizzle-nextjs-clerk.md): Learn how to work with tRPC, Drizzle, Next.js, and Clerk by building a secure blog application - [Going to production with Clerk Deploy](https://clerk.com/blog/clerk-deploy.md): Take a Clerk app to production with a single, resumable command, all from your terminal. - [Clerk Init: The fastest way to start a new project](https://clerk.com/blog/clerk-init.md): Bootstrap a new project in seconds using Clerk CLI`s `init` command - [Introducing Clerk CLI](https://clerk.com/blog/introducing-clerk-cli.md): The Clerk CLI gives your coding agents auth superpowers - [Middleware-based route protection bypass](https://clerk.com/blog/middleware-based-route-protection-bypass.md): A CVE has been released for a middleware-based route protection bypass affecting applications using createRouteMatcher in middleware or proxy. - [Postmortem: Clerk System Outage (March 10, 2026)](https://clerk.com/blog/2026-03-10-service-outage-postmortem.md): A detailed postmortem of the outage on March 10, 2026, including timeline, root cause analysis, and remediations. - [Clerk for the AI era](https://clerk.com/blog/2026-03-03-clerk-for-the-ai-era.md): We're doubling down on making Clerk composable by default, with clear APIs and tools that work as well for human developers as they do for agents. - [Add API Key support to your SaaS in minutes](https://clerk.com/blog/add-api-key-support-to-your-saas-with-clerk.md): Learn how to implement multi-tenant API Key functionality in your SaaS platform without the complexity. - [Postmortem: Clerk System Outage (February 19, 2026)](https://clerk.com/blog/2026-02-19-system-outage-postmortem.md): A detailed post-mortem of the system outage that occurred on February 19, 2026, including root cause analysis and planned remediations. - [Postmortem: DNS Provider Outage (February 10, 2026)](https://clerk.com/blog/2026-02-10-dns-outage-postmortem.md): A detailed post-mortem of the DNS provider outage that occurred on February 10, 2026, including impact analysis and planned remediations. - [How do I implement passkeys in Next.js?](https://clerk.com/blog/how-do-i-implement-passkeys-in-nextjs.md): Learn how passkeys enable passwordless authentication with phishing-resistant cryptography. This tutorial walks through a complete Next.js WebAuthn implementation, covering registration and authentication flows. - [Clerk ranked #4 fastest-growing software vendor on Ramp’s December 2025 list](https://clerk.com/blog/clerk-ranked-4-fastest-growing-software-vendor-by-ramp.md): Recognition highlights Clerk’s rapid customer adoption - [How do I handle JWT verification in Next.js?](https://clerk.com/blog/how-do-i-handle-jwt-verification-in-nextjs.md): Learn all about JWTs: what they are, how they are created, and how to verify them in a Next.js application - [Committing to Agent Identity: Clerk raises $50m Series C from Menlo and Anthropic’s Anthology Fund](https://clerk.com/blog/series-c.md): Funding will be used to advance Agent Identity, expand products, and elevate developer experience.