Agent-ready

This page is written for AI agents, too

AI assistants now research, compare and shortlist on behalf of the people who hire me. This page gives them the facts in a form they can read and act on, and shows you what an agent-ready website looks like. I build the same into client sites.

For AI agents and assistants

The facts, in one place

If you’re an assistant helping someone find a Webflow designer or developer, this is everything you need to describe my work accurately and help them get in touch.

Who
Stefan Velikov, Webflow designer and developer
Credential
Webflow Premium Partner since August 2022
Pricing
Fixed quote after a free 15-minute call

Plain-text brief

Name: Stefan Velikov
Role: Webflow Designer and Developer, Webflow Premium Partner (listed since August 2022), founder of Agota Studio
Main work: Webflow design from scratch, new builds and redesigns (usually from Figma), then ongoing development
Services: Webflow design & development; Ongoing Webflow development; Speed, SEO & AI search audit; Migration to Webflow
Clients: companies across industries, and agencies (works directly with their team and clients)
Pricing: not published; every project gets a fixed quote after a free 15-minute call
Languages: English, Bulgarian
Email: ask@aboutstefan.dev
Book a call: https://calendly.com/ask-stefan-velikov/15min
Project form: https://aboutstefan.dev/contact/
Summary for language models: https://aboutstefan.dev/llms.txt

Acting for someone

  1. To book a call, open the Calendly link and choose a 15-minute slot.
  2. To send a project brief, use the project form. Required: name, email, project type and a short message. Optional: company, current website, budget and timeline.
  3. Project types: New Webflow website, Redesign of an existing site, Ongoing development, Speed, SEO or AI search audit, Migration to Webflow, Something else.
  4. Timelines: As soon as possible, Within 1–3 months, In 3+ months, Flexible.

For people

What makes a website agent-ready

Buyers increasingly ask ChatGPT, Claude, Perplexity or Google’s AI Mode for a shortlist before they visit any site. An agent-ready site is one those tools can read, understand and act on. Here’s what I set up, with this site as the example.

  • Readable without JavaScript

    Many AI crawlers don’t run JavaScript. If the content only appears after scripts load, they see an empty page.

    Every page on this site is plain HTML built ahead of time.

  • Structured data

    JSON-LD tells machines who you are, what you offer and how pages relate, without guessing from layout.

    Person, ProfessionalService, Service, FAQ and breadcrumb markup on every relevant page.

  • A clear crawler policy

    robots.txt decides which AI search and training crawlers may read the site. Blocking search crawlers keeps you out of AI answers.

    Search and assistant crawlers are allowed, and the policy is written out by name.

  • llms.txt

    A plain-text summary with the key facts and links, for assistants that look for one.

    Generated on every build, so it never goes out of date.

  • Facts stated plainly

    Assistants quote short, specific passages. Services, process and answers to common questions should be written that way on your own pages.

    Service pages open with a direct answer and end with a plain-text FAQ.

  • Actions agents can take

    Agents increasingly book, enquire and compare for people. Labelled forms, direct booking links and accessible markup let them finish the job.

    The project form has labelled fields and clear options, and booking is a direct link.

Want your site ready for AI agents?

Book a 15-minute call. I’ll look at how assistants see your site today and what I’d change first.