Independent technical audit

builtwith.com

Overall AI readiness score

A combined result across all audit signals.

Excellent

AI readiness audit: 7/21/2026Public technical data

Overall AI readiness assessment

How ready builtwith.com is for AI systems

86/100

BuiltWith was independently audited by llmsmap. builtwith.com currently scores 86/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.

Audit context

llms.txt is accessible and contains 790 tokens. An expanded llms-full.txt is also available with 1,928 tokens, giving agents more direct context. A separate ai.txt policy is published.

robots.txt is available. 11 of 11 tracked AI bots are not blocked. Declared sitemaps: 1. No Schema.org type was detected on the homepage. 7 OpenGraph tags were found and markup completeness is 60%, leaving more entity interpretation to crawlers.

The mobile Lighthouse profile adds Performance 86/100, Accessibility 95/100, Best Practices 96/100, SEO 100/100, and experimental Agentic Browsing 32/100. These signals have a limited weight: they complement rather than replace llms.txt, robots.txt, and structured-data checks.

Confirmed strengths

Accessible llms.txt
Expanded llms-full.txt
Published AI policy
1 sitemap declaration

Priority improvements

1Add JSON-LD for the organisation, website, and core entities.
2Complete OpenGraph and canonical homepage metadata.
3Reduce mobile rendering delay and main-thread work.

llms.txt tokens790

llms-full.txt tokens1,928

ai.txt

sitemap.xml

Google Lighthouse technical profile

A mobile Lighthouse measurement. Google’s experimental Agentic Browsing category is explained separately and does not replace the broader llmsmap AI-readiness score.

Mobile · Lighthouse

Performance

Accessibility

Best Practices

100

Technical SEO

Agentic Browsing

What these results mean

Mobile performance is 86/100, with the largest visible content block appearing in 3.4 s and the browser main thread blocked for 0 ms. Layout shift was 0.063. 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 95/100, Best Practices 96/100, and technical SEO 100/100. The experimental Agentic Browsing category scored 32/100. It measures signals Google currently tests for software agents and is shown separately from the llmsmap AI-readiness score.

Free the main thread and accelerate the first view

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.

Reduce code that loads without helping the page

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.

Optimise images and their loading order

Serve correctly sized modern formats, prioritise the primary visual, and lazy-load content below the first viewport.

Make controls unambiguous

Give buttons and links accessible names, associate labels with fields, and use ordered headings and semantic regions. The same structure helps screen readers and software agents understand actions.

FCP2.7 s

First content

LCP3.4 s

Main content

CLS0.063

Layout stability

TBT0 ms

Blocking time

SI3.2 s

Visual speed

Metric glossary

FCP · First content: When the first text or image appeared on screen.
LCP · Main content: When the largest visible element in the first viewport rendered.
CLS · Layout stability: How much content shifted unexpectedly while loading; lower is better.
TBT · Blocking time: How long the browser main thread could not respond quickly to input.
SI · Visual speed: How quickly the visible viewport filled with content.

7/21/2026Lighthouse 13.4.0Mobile profile

AI readiness checks

Machine-readable files, crawler policy, discovery, and homepage markup.

llms.txt

File found and accessible

https://builtwith.com/llms.txt

llms-full.txt

Full version is available

https://builtwith.com/llms-full.txt

ai.txt

AI rules are defined

https://builtwith.com/ai.txt

robots.txt

File found

https://builtwith.com/robots.txt

Sitemap in robots.txt1

1 sitemap found

Schema.org (JSON-LD)

Schema.org markup was not found on the homepage

OpenGraph60%

7 OG tags found

AI bot access

Based on robots.txt analysis

GPTBotNot mentioned

OAI-SearchBotNot mentioned

ChatGPT-UserNot mentioned

Google-ExtendedNot mentioned

ClaudeBotNot mentioned

Claude-SearchBotNot mentioned

Claude-UserNot mentioned

BytespiderNot mentioned

CCBotNot mentioned

PerplexityBotNot mentioned

Perplexity-UserNot mentioned

Sitemaps

Declared discovery routes for crawlers and agents.

https://builtwith.com/sitemap.xml

OpenGraph tags

Social preview metadata found on the homepage.

Markup completeness: 60%

og:titleBuiltWith

og:descriptionFind out what websites are BuiltWith

og:imagehttps://builtwith.com/img/logo/logoSquare.png

og:urlhttps://builtwith.com/

og:site_nameBuiltWith

og:typewebsite

og:langen-US

# BuiltWith

> Find out what websites are built with.

BuiltWith detects the technologies used on any website including CMS, ecommerce platforms, analytics,
frameworks, hosting providers, and more.

## Start Here (For LLMs and AI Agents)

Use the API-focused LLM guide first:
- https://api.builtwith.com/llms.txt

This file is a high-level product map. The API LLM guide above contains detailed endpoint usage.
A full version of this product map is at https://builtwith.com/llms-full.txt and the full API
reference is at https://api.builtwith.com/llms-full.txt.

## Core BuiltWith Links

- Website lookup: `https://builtwith.com/[domain]`
  - Example: https://builtwith.com/example.org
- Natural language Ask tool: https://builtwith.com/ask
- Technology trends and market movement: https://trends.builtwith.com
- MCP endpoint for AI integration: https://api.builtwith.com/mcp
- API LLM guide (primary): https://api.builtwith.com/llms.txt

## Discovery Endpoints

BuiltWith publishes the following `.well-known` resources for agents, API clients, and integration discovery:

- Agent Skills Discovery index: https://builtwith.com/.well-known/agent-skills/index.json
- BuiltWith API agent skill: https://builtwith.com/.well-known/agent-skills/builtwith-api/SKILL.md
- MCP discovery manifest: https://builtwith.com/.well-known/mcp.json
- Agent card: https://builtwith.com/.well-known/agent-card.json
- API catalog: https://builtwith.com/.well-known/api-catalog
- OAuth authorization server metadata: https://builtwith.com/.well-known/oauth-authorization-server
- OAuth protected resource metadata: https://builtwith.com/.well-known/oauth-protected-resource
- OpenAI plugin/app manifest: https://builtwith.com/.well-known/openai.json
- HTTP message signatures directory: https://builtwith.com/.well-known/http-message-signatures-directory
- Security contact policy: https://builtwith.com/.well-known/security.txt

## Billing And Credit Endpoints

BuiltWith exposes MPPX credit and spending-limit endpoints on the API host. The same paths are discoverable from `builtwith.com` as redirects to `api.builtwith.com`.

- Credit balance: `GET https://api.builtwith.com/mppx/api-discovery`
- Spending limits: `GET https://api.builtwith.com/mppx/api-configuration`
- Credit purchase: `POST https://api.builtwith.com/mppx/api-purchase`
- Local OpenAPI discovery: `GET https://api.builtwith.com/mppx/openapi.json`
- BuiltWith.com aliases:
  - `GET https://builtwith.com/mppx/api-discovery`
  - `GET https://builtwith.com/mppx/api-configuration`
  - `POST https://builtwith.com/mppx/api-purchase`
  - `GET https://builtwith.com/mppx/openapi.json`

## Programmatic Access

For direct API requests, use the official API docs and endpoint details:
- https://api.builtwith.com

Popular API families include:
- Domain technology lookup
- Technology and company lists
- Relationships / related sites
- Trust and risk signals
- Redirect and keyword data
- API-based trends data

## Notes

- Bots/AI agents may be blocked on interactive website pages.
- For reliable automated access, use the API and MCP routes.

Share or continue the analysis

Share this audit

Discuss with AI

Added 7/19/2026