robots.txt
# ============================================================
# RSL - Really Simple Licensing 1.0
# Global directive (not scoped to any user-agent group). Crawlers must
# retrieve and comply with these terms before processing site content.
# Spec: https://rslstandard.org/rsl
# ============================================================
License: https://built2winweb.com/license.xml
# ============================================================
# CONTENT SIGNALS (Cloudflare Content Signals Policy)
# search = appear in a traditional search index (links + excerpts)
# ai-input = use content in real-time generative answers (RAG)
# ai-train = use content to train or fine-tune a model
#
# All three are YES. This site WANTS to be read, cited and surfaced by
# AI assistants - that is the entire point of the agent surface it
# publishes (MCP, A2A, NLWeb, llms.txt). Signals are declarative, not
# enforcement. The RSL License directive above carries the legal terms.
# ============================================================
User-agent: *
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /
# ------------------------------------------------------------
# LANGUAGE VARIANTS (?lang=xx) — NOT CRAWLED. Added 2026-09-13.
#
# WHY THIS IS HERE AND WHY IT IS NOT THE MISTAKE DOCUMENTED FURTHER DOWN
# Read the "Pruned URL families" note below before touching this. That note
# says, correctly, not to robots-block a URL that carries a meta tag Google has
# to FETCH in order to obey. The ?lang= variants are the opposite case, on
# every point that mattered there:
#
# - They carry no noindex. They serve <meta robots="index, follow"> and a
# rel=canonical pointing at the bare English URL. Nothing is being asked of
# Googlebot that a block would prevent it from hearing.
# - The consolidation has ALREADY happened. Search Console reports 6,583 of
# them as "Alternate page with proper canonical tag" -- Google has read the
# canonical, accepted it, and excluded them. There is no deindexing left to
# do that this block could defeat.
# - Their "follow" value is nil. The outgoing links on a ?lang= page are
# either the same ten header destinations every English page already links,
# or more ?lang= URLs. No link equity reaches anywhere it was not already
# going.
#
# WHAT IT COSTS AND WHAT IT BUYS
# The sitemap carries 28,779 URLs. Every one of them is reachable in eleven
# languages through the switcher, so the crawlable surface was about 316,000
# URLs, of which roughly 287,000 can never rank because they canonicalise away.
# Meanwhile Cloudflare rate limiting answers 429 after ~70 requests in ~10s per
# IP (measured 2026-09-13: the 71st sequential request tripped it, Retry-After
# 10). Googlebot cannot crawl a 316,000-URL site through a 70-per-10s gate, and
# Search Console shows the result -- 679 "Server error (5xx)", 36,953 "Crawled
# - currently not indexed", 14,125 "Discovered - currently not indexed", and
# breadcrumb-eligible items down from ~9,000 in June to 57.
#
# This is exactly the lever the pruned-families note names: "reduce the NUMBER
# of these variants". It reduces them to zero for crawlers while leaving every
# translation working for the people who click the switcher.
#
# WHY TWO PATTERNS, AND WHY NOT "&lang=".
# "/*?lang=" catches the ordinary case, where lang is the first parameter.
# The obvious companion, "/*&lang=", DOES NOT WORK -- verified against a
# Google-spec parser (protego), which allows /a/?utm=1&lang=es straight
# through it. "/*?*lang=" is the one that matches a lang parameter in any
# position, and it still requires a query string, so it cannot accidentally
# catch a path segment that happens to contain "lang=". Do not "simplify"
# this to a single "&" rule; it silently stops blocking anything with a
# tracking parameter in front of the language.
# Under RFC 9309 the longest match wins, and both are longer than "Allow: /".
#
# TO REVERT: delete the two Disallow lines, and drop rel="nofollow" from the
# switcher anchors in includes/site-header.php, index.php, web-design.php,
# web-design-city.php, article-layout.php and state-of-ai-agent-readiness.php.
# ------------------------------------------------------------
Disallow: /*?lang=
Disallow: /*?*lang=
# ------------------------------------------------------------
# Machine-readable discovery documents (added 2026-08-08)
# CRITICAL: these MUST out-rank the "Disallow: /*.json$" rule further
# down. Under RFC 9309 the longest matching pattern wins, and every
# path here is longer than the 8-character "/*.json$", so these win.
# Without them robots.txt was forbidding every manifest the site
# publishes - agents.json, openapi.json, server.json and the entire
# .well-known tree (agent-card, acp, mcp, agent-skills, permissions).
# A perfect manifest on a disallowed path is an invisible manifest.
# ------------------------------------------------------------
Allow: /.well-known/
Allow: /agents.json$
Allow: /agents.txt$
Allow: /openapi.json$
Allow: /server.json$
Allow: /license.xml$
Allow: /llms.txt$
Allow: /llms-full.txt$
Allow: /AGENTS.md$
Allow: /sitemap.md$
# Editing backups (*.bak-*). .htaccess already 403s these, so every fetch is a
# wasted round trip. The .well-known variant is spelled out in full because the
# blanket "Allow: /.well-known/" above is a longer match and would win otherwise.
Disallow: /*.bak*
Disallow: /.well-known/*.bak*
# Allow essential assets
Allow: /fa/css/
Allow: /fa/webfonts/
Allow: /js/
Allow: /*.webp$
Allow: /*.css$
Allow: /*.js$
# Allow IndexNow key file (must be publicly crawlable for verification)
Allow: /b2w9a4f3c7e1d8b6e5f2a0c3d7e9f1b4.txt
# Disallow cache — hundreds of JSON files waste crawl budget
Disallow: /cache/
# Disallow sensitive and non-content directories
Disallow: /state_blocks/
Disallow: /tmp/
Disallow: /logs/
Disallow: /admin/
Disallow: /PHPMailer/
Disallow: /PHPMailer-6.8.0/
Disallow: /stripe-php-14.10.0/
Disallow: /vendor/
Disallow: /composer/
# Disallow non-public utility scripts
Disallow: /generate_cities.py
Disallow: /generate_city_details.php
Disallow: /split-city-details.php
Disallow: /test_place_id.php
Disallow: /test_weather.php
Disallow: /debug.php
Disallow: /ctr-graph.php
Disallow: /InvoiceSystem.php
Disallow: /send_invoice.php
Disallow: /create_stripe_session.php
Disallow: /stripe_success.php
Disallow: /send_contact_email.php
Disallow: /notify-indexnow.php
# Disallow raw data files
Disallow: /*.csv$
Disallow: /*.json$
Disallow: /*.zip$
# ------------------------------------------------------------
# Decorative trust badges - crawl-budget sink (added 2026-08-01)
# Cloudflare AI Crawl Control showed Claude-SearchBot pulling these
# files ~1,350x / 3.7 MB in 24h, re-fetching despite
# Cache-Control: max-age=31536000, immutable. They already carry
# X-Robots-Tag: noindex,nofollow via .htaccess, so they have zero
# index value and nothing is lost by blocking the fetch.
# Longer path match beats the "Allow: /*.webp$" rule above.
# ------------------------------------------------------------
Disallow: /goodfirms.webp
Disallow: /yelp.webp
Disallow: /sitelock.webp
Disallow: /trustpilot.webp
Disallow: /norton.webp
Disallow: /bbb.webp
Disallow: /google.webp
Disallow: /upwork.webp
Disallow: /hostinger.webp
Disallow: /pcs.webp
Disallow: /blank.gif
# ------------------------------------------------------------
# Pruned URL families - state/city variants
#
# The 31 "Disallow: /<family>/*/" lines that used to sit here were REMOVED on
# 2026-09-06, deliberately. Please read this before putting them back.
#
# Those same 31 families are served <meta robots="noindex, follow"> by
# config/pruned-slugs.php. Blocking them here meant Googlebot never fetched
# them, and a page that is never fetched is a page whose meta tag is never
# read. The block defeated BOTH halves of that tag:
#
# noindex - never seen, so the URLs could still be indexed URL-only from any
# external link. The block did not reliably deindex anything.
# follow - never seen, so no link equity moved through these pages to the
# national page each one points at. That flow is the whole reason
# the tag says "follow", and it was silently doing nothing.
#
# The crawl-budget saving was real (Cloudflare AI Crawl Control measured 0
# referrals across 4,798 of these paths) and giving it up is the cost of this
# change. It buys reliable deindexing and restores internal authority to the
# national pages, which is where the rankings actually are.
#
# If crawl budget becomes the bigger problem again, the lever is to reduce the
# NUMBER of these variants, not to block URLs carrying a meta tag Google has to
# fetch in order to obey.
# ------------------------------------------------------------
# ============================================================
# AI / LLM CRAWLERS — explicitly welcomed so the full site can be
# read, cited, and surfaced by AI search engines and assistants.
# Same protections as the default group (sensitive dirs stay blocked).
# ============================================================
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: ClaudeBot
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: anthropic-ai
User-agent: Claude-Web
User-agent: PerplexityBot
User-agent: Perplexity-User
User-agent: Google-Extended
User-agent: Applebot-Extended
User-agent: Amazonbot
User-agent: Meta-ExternalAgent
User-agent: CCBot
User-agent: Bytespider
User-agent: cohere-ai
User-agent: YouBot
Content-Signal: search=yes, ai-input=yes, ai-train=no
Allow: /
# ------------------------------------------------------------
# LANGUAGE VARIANTS (?lang=xx) — NOT CRAWLED here too. Added 2026-09-13.
# Full reasoning is on the identical pair in the "User-agent: *" group above;
# it is not repeated here. The short version: every ?lang= URL canonicalises to
# the bare English URL, so an AI crawler that follows one is reading a duplicate
# of a page it can already reach, and eleven of them per page is what put the
# crawlable surface at ~316,000 URLs against a 429 gate. Blocking them costs no
# content coverage -- the same pages remain fully open in English.
# ------------------------------------------------------------
Disallow: /*?lang=
Disallow: /*?*lang=
# ------------------------------------------------------------
# Machine-readable discovery documents (added 2026-08-08)
# CRITICAL: these MUST out-rank the "Disallow: /*.json$" rule further
# down. Under RFC 9309 the longest matching pattern wins, and every
# path here is longer than the 8-character "/*.json$", so these win.
# Without them robots.txt was forbidding every manifest the site
# publishes - agents.json, openapi.json, server.json and the entire
# .well-known tree (agent-card, acp, mcp, agent-skills, permissions).
# A perfect manifest on a disallowed path is an invisible manifest.
# ------------------------------------------------------------
Allow: /.well-known/
Allow: /agents.json$
Allow: /agents.txt$
Allow: /openapi.json$
Allow: /server.json$
Allow: /license.xml$
Allow: /llms.txt$
Allow: /llms-full.txt$
Allow: /AGENTS.md$
Allow: /sitemap.md$
# Editing backups (*.bak-*). .htaccess already 403s these, so every fetch is a
# wasted round trip. The .well-known variant is spelled out in full because the
# blanket "Allow: /.well-known/" above is a longer match and would win otherwise.
Disallow: /*.bak*
Disallow: /.well-known/*.bak*
Disallow: /cache/
Disallow: /state_blocks/
Disallow: /tmp/
Disallow: /logs/
Disallow: /admin/
Disallow: /vendor/
Disallow: /composer/
Disallow: /PHPMailer/
Disallow: /PHPMailer-6.8.0/
Disallow: /stripe-php-14.10.0/
Disallow: /*.csv$
Disallow: /*.json$
Disallow: /*.zip$
Disallow: /goodfirms.webp
Disallow: /yelp.webp
Disallow: /sitelock.webp
Disallow: /trustpilot.webp
Disallow: /norton.webp
Disallow: /bbb.webp
Disallow: /google.webp
Disallow: /upwork.webp
Disallow: /hostinger.webp
Disallow: /pcs.webp
Disallow: /blank.gif
# ------------------------------------------------------------
# Pruned URL families - state/city variants
#
# The 31 "Disallow: /<family>/*/" lines that used to sit here were REMOVED on
# 2026-09-06, deliberately. Please read this before putting them back.
#
# Those same 31 families are served <meta robots="noindex, follow"> by
# config/pruned-slugs.php. Blocking them here meant Googlebot never fetched
# them, and a page that is never fetched is a page whose meta tag is never
# read. The block defeated BOTH halves of that tag:
#
# noindex - never seen, so the URLs could still be indexed URL-only from any
# external link. The block did not reliably deindex anything.
# follow - never seen, so no link equity moved through these pages to the
# national page each one points at. That flow is the whole reason
# the tag says "follow", and it was silently doing nothing.
#
# The crawl-budget saving was real (Cloudflare AI Crawl Control measured 0
# referrals across 4,798 of these paths) and giving it up is the cost of this
# change. It buys reliable deindexing and restores internal authority to the
# national pages, which is where the rankings actually are.
#
# If crawl budget becomes the bigger problem again, the lever is to reduce the
# NUMBER of these variants, not to block URLs carrying a meta tag Google has to
# fetch in order to obey.
# ------------------------------------------------------------
# AI guide files (for LLMs / AI assistants — not a robots directive, informational)
# LLM-Content: https://built2winweb.com/llms.txt
# LLM-Content: https://built2winweb.com/llms-full.txt
# Sitemap
# ARD (Agentic Resource Discovery): points agents and readiness scanners
# straight at the capability manifest instead of guessing the path.
Agentmap: https://built2winweb.com/.well-known/ai-catalog.json
Sitemap: https://built2winweb.com/sitemap.xml
Sitemap: https://built2winweb.com/news/sitemap.xml
# The AI website builder lives on its own host and carries its own sitemap.
# Cross-host Sitemap lines are allowed in robots.txt (sitemaps.org, "Sitemaps & Cross Submits").
Sitemap: https://aiwebbuilding.built2winweb.com/sitemap.xml
llms.txt
# BuiltToWinWeb
> Hand-coded custom PHP websites at a flat one-time fee: no monthly costs, Lighthouse 100 performance guaranteed, delivered in about one month, full code ownership. Serving US small businesses (restaurants, law firms, dentists, contractors, salons, ecommerce, SaaS) with local-SEO landing pages in 11 languages. BuiltToWinWeb also builds and sells its own AI software: [AIWebBuilding](https://aiwebbuilding.built2winweb.com/) (an AI website builder, released and generally available: one-time price, hosted sites with blog, shop, booking and an MCP server, and now SaaS apps), [WebAgentScan](https://webagentscan.built2winweb.com/) (paid SaaS scoring any site out of 100 for AI agent readiness, MCP server quality and security, and Domain Rating), the [AI Indexing Pack](https://built2winweb.com/ai-indexing-pack/) (one-time download, plus a [WordPress plugin edition](https://built2winweb.com/ai-indexing-pack-wordpress/)) and [FreeAIBoost](https://freeaiboost.built2winweb.com/) (free daily launch queue and badge exchange). This site itself exposes an MCP server, an A2A agent, NLWeb /ask and llms.txt.
Every HTML page on this site supports Markdown content negotiation: request it with `Accept: text/markdown` to receive a Markdown version (with an `x-markdown-tokens` header).
## Start here
- [Agent Ready](https://built2winweb.com/agent-ready/): every endpoint on this site, documented for humans, with live examples
- [AGENTS.md](https://built2winweb.com/AGENTS.md): how to interact with this site, what to do and what not to do. Read this first.
- [Markdown sitemap](https://built2winweb.com/sitemap.md): every canonical page, grouped, as Markdown
- [Full context](https://built2winweb.com/llms-full.txt): the whole site in one fetch
Do not crawl page by page. Ask a question instead — `/ask` or the MCP `search_site` tool both run BM25 over all 167 pages plus 348 FAQ entries.
## Products for sale
- **AI Indexing Pack — $39 one-time (regular $599)** ([buy](https://built2winweb.com/#pricingSection)): a downloadable pack that makes any site you own readable by AI agents. Contains a working MCP server (output schemas + annotations), Markdown content negotiation, llms.txt and agent discovery files, every `.well-known` document, OAuth protected-resource metadata, bot access control that blocks forged crawlers, and a step-by-step README with a full verification checklist. Installs in about 30 minutes on any Apache or LiteSpeed host with PHP 7.4+. No subscription; install on as many sites as you own. Delivered by email immediately after payment — no consultation required, Terms acceptance only. This site runs the same pack: it scores 100/100 on isitagentready.com and 98/100 on Smithery.
- **AI Indexing Pack, WordPress Edition — $49 one-time** ([buy](https://built2winweb.com/ai-indexing-pack-wordpress/)): the same product delivered as a WordPress plugin. Publishes an MCP server, llms.txt, llms-full.txt, a Markdown sitemap, agents.txt, the `.well-known` agent discovery documents, RSL content licensing, OAuth protected-resource metadata and Markdown content negotiation — every document generated from the site it is installed on, so there is nothing to find-and-replace and nothing that can go stale. Works on any self-hosted WordPress site regardless of host, theme or domain extension; needs WordPress 6.0+ and PHP 8.0+. Priced above the file pack because the plugin does the configuration the file pack leaves to the buyer. Delivered by email immediately after payment, Terms acceptance only.
- Custom build services (websites, ecommerce, SaaS, SEO, migrations) are quoted per project and require a consultation before payment — see the commerce profile below.
## Agent endpoints
- [MCP server (Streamable HTTP, no auth)](https://built2winweb.com/mcp): tools search_site, list_offerings, request_quote, get_services, get_pricing, get_products (AIWebBuilding, WebAgentScan, FreeAIBoost, AI Indexing Pack, with live prices), get_contact, get_page_markdown. Also serves MCP Apps / A2UI widget resources (`ui://widget/*`) for hosts that render inline UI.
- [MCP server card](https://built2winweb.com/.well-known/mcp.json): SEP-2127 canonical discovery card ([legacy SEP-1649 path](https://built2winweb.com/.well-known/mcp/server-card.json) also served)
- [NLWeb /ask](https://built2winweb.com/ask): POST or GET a natural-language `query`, get Schema.org-typed JSON. Modes list/summarize/generate. Retrieval only — no model runs on this origin, so summaries are quoted verbatim from the cited page.
- [A2A agent card](https://built2winweb.com/.well-known/agent-card.json): A2A v1.0 JSON-RPC, streaming, AP2 merchant extension declared; skill get-products answers questions about AIWebBuilding and the other products
- [Agent permissions](https://built2winweb.com/.well-known/agent-permissions.json): per-path read/write policy
- [Agent skills index](https://built2winweb.com/.well-known/agent-skills/index.json): downloadable SKILL.md
- [API catalog](https://built2winweb.com/.well-known/api-catalog): RFC 9727 linkset
- [OpenAPI spec](https://built2winweb.com/openapi.json): all agent endpoints
- [Agent auth guide](https://built2winweb.com/auth.md): OAuth is optional; everything is public read-only
- [Commerce profile](https://built2winweb.com/.well-known/ucp): full priced catalog. Custom build services require a consultation plus Terms acceptance before payment, enforced server-side. The AI Indexing Pack is exempt from the consultation and is fixed-price. In both cases payment happens at Stripe Checkout and needs a human, so agents cannot complete checkout for a buyer.
## Licensing
- [RSL 1.0 license](https://built2winweb.com/license.xml), referenced globally from robots.txt
- Permitted: search indexing, AI search input (RAG), and model training
- Required: attribution — a visible, working link back to the page you used
- robots.txt carries the matching `Content-Signal: search=yes, ai-input=yes, ai-train=yes`
## AI agent readiness by industry
- [AI Agent Readiness hub](https://built2winweb.com/ai-agent-readiness/): 94 pages, one per industry, on what an assistant is asked to do for that kind of business and what on the website stops it. Grouped by the shape of the agent's task rather than by trade, so a locksmith and a plumber share a page structure and a dentist and a nail salon do not.
## Guides: making a website readable by AI (October 2026)
- [The AI Agent-Readiness Checklist for Websites (2026)](https://built2winweb.com/blog/ai-agent-readiness-checklist/): Every layer that makes a website usable by AI assistants and agents, in order, with a pass/fail test for each: crawl access, indexing, structure, Markdown, discovery, MCP.
- [What Is llms.txt? A Complete Guide with Examples](https://built2winweb.com/blog/what-is-llms-txt/): The llms.txt format explained: where it came from, the exact structure, a working example, llms-full.txt, and an honest look at who reads it.
- [Markdown for AI Agents: Serve a Clean Version of Every Page](https://built2winweb.com/blog/markdown-for-ai-agents/): How to serve a Markdown version of every page with content negotiation and .md URLs, why agents prefer it, and how to avoid duplicate-content problems.
- [How to Add an MCP Server to Your Website](https://built2winweb.com/blog/add-mcp-server-to-website/): A practical guide to putting a public MCP server on a business website: which tools to expose, Streamable HTTP, annotations, output schemas, OAuth metadata and security.
- [Agent Discovery Files Explained: agents.txt, Agent Cards and .well-known](https://built2winweb.com/blog/agent-discovery-files/): Every machine-readable file an AI agent looks for, what each one is for, which are standards and which are proposals, and the order to add them.
- [IndexNow: The Complete Guide to Instant Indexing](https://built2winweb.com/blog/indexnow-guide/): How IndexNow works, which search engines use it, how to set it up on any site, the limits, and what our own 200,000+ submissions taught us.
- [Local Business Schema for AI Search: The Markup That Gets You Described Correctly](https://built2winweb.com/blog/local-business-schema-ai-search/): The LocalBusiness JSON-LD properties that matter for Google and AI assistants, a full example, review markup rules, breadcrumbs, and the mistakes that get ignored.
- [AI Indexing Pack vs Doing It Yourself: An Honest Breakdown](https://built2winweb.com/blog/ai-indexing-pack-vs-diy/): Every component of AI agent readiness, what it takes to build by hand, what the AI Indexing Pack includes, what it does not, and when DIY is the better choice.
- [How to Make a WordPress Site Readable by AI Assistants](https://built2winweb.com/blog/make-wordpress-readable-by-ai/): A practical WordPress guide to AI readiness: crawler access, llms.txt, Markdown versions of posts, schema, IndexNow and an MCP server, with plugin and manual options.
- [robots.txt for AI Crawlers: Which Bots to Allow, Which to Block](https://built2winweb.com/blog/robots-txt-ai-crawlers/): The AI crawlers that matter in 2026, the difference between training, search and user-triggered bots, copy-ready robots.txt rules, and how to verify a bot is real.
- [How to Get Cited by AI Assistants (ChatGPT, Claude, Perplexity, Google AI)](https://built2winweb.com/blog/get-cited-by-ai-assistants/): What actually decides whether an AI assistant names your business: indexes, answerable content, entity consistency, third-party mentions and freshness, plus how to measure it.
- [What WebAgentScan Checks: The AI Agent-Readiness Score Explained](https://built2winweb.com/blog/what-is-webagentscan/): How WebAgentScan builds its score out of 100: the six pillars, what each one tests, why missing data is excluded rather than zeroed, and how to act on the result.
- [FreeAIBoost Explained: Followed Links, Daily Launches and the 50-Day Streak](https://built2winweb.com/blog/freeaiboost-guide/): How the FreeAIBoost daily launch page works: the badge, the review instead of a domain-rating gate, the rotating free lane, and how a 50-day streak unlocks the AI Indexing Pack.
- [An AI-Ready Website Builder: What AIWebBuilding Switches On for Every Site](https://built2winweb.com/blog/ai-ready-website-builder/): What makes a website builder AI-ready, the layers most builders leave out, and exactly what AIWebBuilding generates for every published site.
- [MCP Server Security Checklist: 20 Checks for a Public Endpoint](https://built2winweb.com/blog/mcp-server-security-checklist/): Twenty concrete security checks for a public MCP server: transport, origin validation, auth and token handling, input validation, prompt injection, rate limits, errors and logging.
- [What Is NLWeb? Microsoft's Natural-Language Endpoint for Websites](https://built2winweb.com/blog/what-is-nlweb/): NLWeb explained: where it came from, the /ask endpoint, how it uses Schema.org, why every NLWeb instance is also an MCP server, and how we run one on this site.
- [MCP vs A2A: Which Agent Protocol Does Your Website Need?](https://built2winweb.com/blog/mcp-vs-a2a/): The Model Context Protocol and the Agent2Agent protocol compared: what each is for, how they fit together, and which one a business website should add first.
- [How to Find AI Crawlers in Your Server Logs (and What They Tell You)](https://built2winweb.com/blog/ai-crawlers-in-server-logs/): Find GPTBot, ClaudeBot, PerplexityBot and other AI agents in your access logs, separate real bots from fakes, and read what they fetch and what you send back.
- [Content Signals and RSL: Telling AI How It May Use Your Content](https://built2winweb.com/blog/content-signals-and-rsl/): robots.txt says who may crawl; Content Signals and RSL say what they may do with it. How search, ai-input and ai-train signals work, what RSL licensing adds, and their limits.
- [Agentic Commerce Protocols Explained: ACP, AP2 and What Your Shop Needs](https://built2winweb.com/blog/agentic-commerce-protocols/): How AI agents buy things: the Agentic Commerce Protocol, the Agent Payments Protocol, product feeds and structured data, and what a small online shop should do now.
- [llms.txt Examples: Ready-to-Adapt Files for Six Kinds of Business](https://built2winweb.com/blog/llms-txt-examples/): Six complete llms.txt examples, for a dentist, restaurant, SaaS product, law firm, plumber and online shop, with notes on what makes each one work.
- [Where to List Your MCP Server: The Official Registry and Directories](https://built2winweb.com/blog/list-your-mcp-server/): How to get a public MCP server discovered: the official MCP Registry, server.json and namespace verification, community directories, and what to prepare first.
- [AI Crawler User-Agent List 2026: Every Bot and What It Does](https://built2winweb.com/blog/ai-crawler-user-agents/): GPTBot, ClaudeBot, PerplexityBot, Google-Extended and 20+ more: what each AI bot is for, whether it obeys robots.txt, and how to verify it is genuine.
- [How AI Assistants Read a Web Page: Fetch, Render, Extract](https://built2winweb.com/blog/how-ai-assistants-read-pages/): Index or live fetch, whether JavaScript runs, what gets extracted and what blocks AI assistants, plus five tests to see your page the way ChatGPT or Claude does.
- [How to Measure Traffic From ChatGPT, Perplexity and AI Assistants](https://built2winweb.com/blog/measure-ai-search-traffic/): Track AI assistant visits with referrers, utm_source=chatgpt.com, GA4’s AI Assistant channel, a custom channel group regex, server logs and citation reports.
- [Multilingual Websites: hreflang, lang and Translation](https://built2winweb.com/blog/multilingual-websites-ai-search/): Give each language its own URL, link versions with hreflang, set lang and dir, and have translations reviewed so search engines and AI assistants serve the right page.
- [Google Translate Widget in 2026: Available? Good for SEO?](https://built2winweb.com/blog/google-translate-widget-seo/): Google closed the Website Translator widget to new sites in 2019 and ended support on October 1, 2026. It never helped SEO; here is what to use instead.
- [Accessibility Is Agent-Readiness for AI Agents](https://built2winweb.com/blog/accessibility-for-ai-agents/): Browser agents read pages via screenshots and the accessibility tree, so semantic HTML, labels and keyboard access help them too. Includes a pass/fail checklist.
- [Which Schema Still Matters in 2026: Rich Results That Survived](https://built2winweb.com/blog/schema-rich-results-2026/): FAQ and HowTo rich results are gone and Google retired eight more types by 2026. Here is the schema that still earns rich results, with working JSON-LD.
- [How to Show Up in Google AI Overviews and AI Mode](https://built2winweb.com/blog/ai-overviews-ai-mode/): Google says AI Overviews and AI Mode need no special optimization, only an indexed, snippet-eligible page. Its rules, controls and reports, kept apart from SEO opinion.
- [Entity SEO for Small Businesses: Make Search and AI Know You](https://built2winweb.com/blog/entity-seo-small-business/): One consistent identity, Organization schema with sameAs, verified Google, Bing and Apple listings, an honest look at Wikidata, and how to claim a knowledge panel.
- [Connect a Custom Domain: DNS Records, Verification and SSL](https://built2winweb.com/blog/custom-domain-dns-ssl/): How A, CNAME, ALIAS and TXT records connect a domain, why the apex can’t take a CNAME, how automatic SSL works, and how to fix the records that block it.
- [INP Explained: The Core Web Vital That Replaced FID](https://built2winweb.com/blog/inp-core-web-vitals/): INP replaced FID on March 12, 2024. What it measures, the 200 ms and 500 ms thresholds, how to find slow interactions, and code fixes that bring the score down.
- [WebMCP Explained: Let AI Agents Use Your Site’s Tools](https://built2winweb.com/blog/webmcp-explained/): WebMCP lets a page register tools that browser AI agents can call. The current 2026 API, Chrome’s origin trial, the security model, a working example and when it isn’t worth adding.
- [Does Google Penalize AI Content? What Its Policies Say](https://built2winweb.com/blog/ai-content-google-policy/): Google doesn’t penalize content for being AI-written. It acts on scaled, low-value pages. What its AI guidance, spam policies and rater guidelines actually say in 2026.
- [Cloudflare AI Bots: Crawl Control and Pay Per Crawl](https://built2winweb.com/blog/cloudflare-ai-crawl-control/): How Cloudflare handles AI crawlers in 2026: Search, Agent and Training policies, AI Crawl Control, managed robots.txt, Pay Per Crawl and the setting that can block Googlebot.
- [Canonical Tags Explained: Fix Duplicate Content for Google and AI](https://built2winweb.com/blog/canonical-tags-duplicate-content/): How rel=canonical works in HTML and HTTP headers, why Google treats it as a hint, where duplicate URLs come from, and the canonical mistakes that quietly cost rankings.
- [noindex vs robots.txt: Which to Use, and the Mistake to Avoid](https://built2winweb.com/blog/noindex-vs-robots-txt/): robots.txt Disallow stops crawling, noindex stops indexing, and using both keeps pages in Google. When to use each, with code, AI crawler notes and a decision table.
- [Image SEO in 2026: Alt Text, AVIF, Lazy Loading and AI Search](https://built2winweb.com/blog/image-seo-2026/): Image SEO that holds up in 2026: alt text, filenames, AVIF and WebP, srcset, width and height, lazy loading without hurting LCP, image sitemaps and licence metadata.
- [Product Schema for Small Shops: Shipping and Returns Markup](https://built2winweb.com/blog/product-schema-merchant-listings/): The Product, Offer, shipping and return policy markup Google requires for merchant listings, with working JSON-LD for a small shop, plus Merchant Center free listings and AI shopping.
- [Bing Webmaster Tools in 2026: Copilot, ChatGPT and AI Search](https://built2winweb.com/blog/bing-webmaster-tools-ai/): Copilot grounds its answers in Bing, and Bing Webmaster Tools now reports AI citations and citation share. Setup steps, IndexNow, sitemaps and what is really known about ChatGPT.
- [Security Headers for Small Business: CSP, HSTS, Copy-Paste Config](https://built2winweb.com/blog/security-headers-small-business/): Which HTTP security headers a small-business site needs, which deprecated ones to remove, and tested config for Apache, Nginx and Cloudflare, with a safe way to roll out CSP.
- [TTFB Explained: How Hosting Affects Speed and How to Fix It](https://built2winweb.com/blog/ttfb-hosting-speed/): What Time to First Byte measures, web.dev’s 0.8 s and 1.8 s thresholds, how to measure it with PageSpeed Insights, DevTools, curl and Server-Timing, and the fixes that cut it.
- [AI Search Myths: 10 Claims About ChatGPT and AI Overviews, Checked](https://built2winweb.com/blog/ai-seo-myths/): Ten popular claims about ranking in ChatGPT and Google AI Overviews, checked against Google, OpenAI, Anthropic and published studies. Six are false, three partly true, one unproven.
- [Website Maintenance: What It Covers and When to Hand It Off](https://built2winweb.com/blog/website-maintenance-guide/): What website maintenance really covers, what skipping it costs, a realistic DIY schedule, what to check in a maintenance plan, and a fair look at BugShield’s WordPress plans.
## AIWebBuilding — the AI website builder BuiltToWinWeb built
- [AIWebBuilding](https://aiwebbuilding.built2winweb.com/) is an AI website builder designed, written and run by Jacob Campbell of BuiltToWinWeb (also called Built2Win Builder). Describe a business in a sentence, or paste an existing site's address, and it produces a finished, hosted site from an original section library: pages, a blog, an online shop, appointment booking, a no-code MCP server and an AI video studio. No WordPress, no page builder, no third-party templates.
- Price (October 2026): build and preview free, pay only to publish. $62.99 one-time for a site written from your own answers, $73.99 with the copy
