What BuiltToWinWeb Does Beyond Building Websites

A website can work perfectly for people and still be hard for automated agents to interpret. Its pages may be rendered in ways a crawler cannot use, or it may offer no structured path for an agent to discover its content. That is the problem BuiltToWinWeb is trying to address, though the name covers more than one kind of product.

BuiltToWinWeb combines a custom website development service with WebAgentScan, a hosted tool for examining how sites present themselves to AI agents. Alongside the scanner, it sells an AI Indexing Pack intended to add files and endpoints that those agents can read. These are related offers, but they do different jobs.

A site audit, not an AI visibility promise

WebAgentScan takes a domain and returns a score out of 100 across seven graded areas, according to the developer. The categories cover discovery files such as llms.txt and agents.txt, machine-readable content, crawler access, MCP quality and security, and Domain Rating data. The report also includes a fix list ordered by the value assigned to each fix.

That makes the product an audit tool: it is meant to show a site owner where agent-facing access may be weak. The Domain Rating component draws on licensed data from SEO services, rather than being a measure of whether an AI assistant will cite a site. A score can organise technical checks, but it cannot establish that a site is useful, trustworthy or likely to appear in an answer.

The distinction matters. A high readiness score is not the same as traffic, rankings or mentions in AI-generated responses. WebAgentScan can identify technical conditions the developer considers important; it cannot make a third-party assistant crawl a page or choose to cite it. Treat the score as a diagnostic and the fix list as a set of leads to investigate, not as a visibility guarantee.

The pack changes the site; the scanner checks it

The AI Indexing Pack is a separate product. The developer describes it as a set of files and endpoints for site owners to install, including agent discovery files, Markdown output for agents and an MCP server. Unlike the hosted scanner, it is meant to publish changes on a site. The developer also offers a WordPress edition, described as a plugin that generates its output from the site’s content.

The distinction is practical: the pack supplies implementation, while WebAgentScan scores and re-checks a domain as it changes. Neither replaces the other, and the pack is not presented as a requirement for using the scanner. The file-based version expects the owner to install and configure the supplied materials. That is a real bit of work, and a poor fit for someone who cannot edit or deploy files on their site. The WordPress edition may reduce that work for WordPress owners, but still assumes they can install a plugin.

There is also a limit to what these additions can do. Publishing files that an agent may look for does not ensure that any particular service will index the site, use its content or quote it. The pack can address discoverability and machine-readable access, not the editorial decisions or crawling policies of external AI systems.

A wider business behind the software

BuiltToWinWeb also offers hand-coded PHP business sites, stores and web applications for a one-time fee, with source ownership handed to the customer. That is a development service, not another function inside WebAgentScan. Someone hiring the company for a site project is buying custom work; someone using the scanner is evaluating an existing domain.

The service and software sit under the same brand, but the landing page does not make them one workflow. The scanner is a hosted web product, with web and API listed as its platforms. The available description does not explain the API’s authentication, response format or how it fits into an existing development pipeline. Developers considering automation should treat that as an unanswered integration question rather than assume the API is ready for a particular use.

WebAgentScan is paid, and the Indexing Pack is a separate one-time purchase. That makes the scanner a considered choice for an owner or developer who expects to run audits, rather than a casual free check. The services are aimed at businesses and site operators who want to improve how their content is exposed to crawlers, while the custom development side is for those who need a site built.

Who should consider it

WebAgentScan makes most sense for a developer, agency or technically involved site owner who wants a structured checklist for AI-agent readiness, MCP security and SEO-related signals. The pack is for someone prepared to install site changes and who understands that better machine-readable access is not a promise of AI citations. The PHP service is for a business that wants commissioned development and ownership of the resulting code.

It is not a fit for someone expecting an automatic route to AI search visibility, or for a site owner who wants a score to substitute for technical review. BuiltToWinWeb’s clearest use is as a way to inspect and improve a site’s agent-facing plumbing. The rest still depends on the site, its content and the systems that decide whether to use it.