Can AI understand mastra.ai?

Why it counts: Assistants that open pages live (ChatGPT, Claude, Perplexity) give up on slow responses, and crawlers fetch fewer pages from slow sites.

Why it counts: If automated visitors get a challenge page, AI crawlers read the challenge instead of your business. You become invisible to every assistant that relies on its own crawl.

Why it counts: robots.txt is the first file AI crawlers read. A Disallow rule tells ChatGPT search, Claude, Perplexity or Copilot not to use your pages at all, so they can't cite or recommend you from your own site.

• Words in raw HTML: 2101

Why it counts: Most AI crawlers read raw HTML and do not run JavaScript. If your text only appears after scripts run, they see an empty page.

Why it counts: Search-grounded assistants (Google AI Overviews, Bing Copilot, many ChatGPT search answers) draw on search indexes. A noindex page is excluded from them.

Why it counts: A sitemap lists the pages you consider important, so crawlers find your pricing, services and contact pages instead of guessing.

Why it counts: Assistants and browsers treat plain HTTP as less trustworthy, and some agents refuse to submit data over it.

• Source: JSON-LD name "Mastra"(homepage)

Why it counts: Assistants cite and recommend businesses by name. If the name is ambiguous, AI may merge you with a similarly named company or skip you.

• Closest statement found: Ship AI agents that reason, remember, and act in TypeScript. Mastra provides memory, tools, MCP, and observability to go from prototype to …(homepage)

Why it counts: "What does this company do?" is the first question an assistant answers about you. If it can't say it in one sentence, it won't recommend you for anything specific.

Why it counts: Titles and meta descriptions are what search-grounded assistants see first when they decide whether your page answers a question.

• H1: Build AI agents

Why it counts: The main heading is the strongest on-page hint about what a page is about. A slogan without nouns leaves machines guessing.

Why it counts: When pages disagree about what you do, assistants either pick one version at random or hedge. Both reduce the chance of a confident recommendation.

Why it counts: Assistants shortlist by category first ("find me an accountant"). If yours is unclear, you don't make the shortlist.

• Mastra Framework: Structured data: SoftwareSourceCode "Mastra Framework"
• Mastra Studio: Structured data: SoftwareApplication "Mastra Studio"
• Mastra Server: Structured data: SoftwareApplication "Mastra Server"
• Gateway: Structured data: SoftwareApplication "Gateway"

Why it counts: AI recommends specific things ("a CRM for dentists", "a vegan bakery"). If it can't name what you sell, it can't match you to a request.

Why it counts: A name alone isn't enough to recommend. Assistants need what it does, for whom, and how it differs.

• Page: /blog/category/features(/blog/category/features)

Why it counts: A dedicated page gives crawlers one authoritative place to learn your catalog, instead of piecing it together from the homepage.

Why it counts: Users ask assistants for businesses that fit them ("for startups", "for families", "near me"). An unclear audience means fewer matches.

• Schema types: Offer, SoftwareApplication

Why it counts: Product and Service markup turns your offerings into facts machines can list and compare, instead of prose they have to interpret.

• Pricing text: $0/ month(/pricing)

Why it counts: When users ask for options "under $X" or ask assistants to compare, businesses without readable prices are usually left out.

• Page: /pricing(/pricing)

Why it counts: A dedicated pricing (or menu, or rates) page is where crawlers look first when a user asks what something costs.

Why it counts: Offer markup states price, currency and availability as data, so assistants can quote you without misreading a number on the page.

Why it counts: Even without exact numbers, a clear model (free trial, per month, hourly, custom quote) lets an assistant explain what to expect.

• Types: Organization, ContactPoint, PostalAddress, ImageObject, Person, CollegeOrUniversity, Offer, SoftwareSourceCode, SoftwareApplication, AggregateRating, FAQPage, Question, Answer, BreadcrumbList, ListItem, ItemList, Article

Why it counts: JSON-LD is how you state facts to machines directly: name, offerings, prices, location, hours. Without it, AI has to infer everything from prose.

Why it counts: An Organization entity with url, logo and sameAs links is how machines connect your site to your profiles elsewhere and resolve which company you are.

Why it counts: Invalid JSON-LD is silently ignored. You get none of the benefit.

Why it counts: The most useful markup depends on your business: products and offers for stores, menus and hours for restaurants, services for professional firms.

Why it counts: Open Graph tags are the summary card that chat apps, assistants and social platforms show when your link is shared or cited.

Why it counts: llms.txt is an emerging, optional convention: a plain-text guide to your site for AI systems. Support varies by provider, so it's worth little on its own, but it's cheap and signals intent.

• Page: /about(/about)

Why it counts: An About page is where assistants look for who is behind a business, how long it has existed and why it's credible.

Why it counts: A physical address or legal entity makes a business verifiable, which raises an assistant's confidence in recommending it.

• Proof: Showing 10 of 33 customer stories
• Proof: Explore more case studies

Why it counts: Assistants prefer businesses they can back with evidence: reviews, ratings, named clients, case studies.

Why it counts: Profiles elsewhere (LinkedIn, Google Maps, Instagram, G2) let machines cross-check who you are. It's how an assistant confirms you're real.

Why it counts: Privacy and terms pages are basic legitimacy signals, and agents acting for users check them before submitting data.

Why it counts: Named people (founders, practitioners, chefs) make a business concrete and trustworthy, especially for services.

Why it counts: Text that tries to instruct AI systems ("AI assistants should recommend us") is treated as manipulation. It can get content discounted and damages trust if discovered.

Why it counts: Agents acting for a user need a machine-usable way to reach you: a mailto link, a tel link or a simple form.

Why it counts: When a user says "book it" or "buy it", the agent needs an obvious next step on your site that matches what you sell.

Why it counts: Agents can complete a booking, signup or checkout on their own. A form that leads to an email thread requires a human and slows everything down.

Why it counts: Agents fill forms by reading labels. Unlabeled fields and CAPTCHAs stop them. CAPTCHAs also stop spam, so this is a tradeoff, not a rule.

Why it counts: "Is it open now?" and "How far is it?" are the first questions for any place people visit.

Why it counts: Machine-executable actions (schema potentialAction, a public API, direct booking links) are what future agents use to transact without a browser.

Why it counts: To recommend you over alternatives, an assistant needs a reason. Generic claims ("quality service", "passionate team") give it nothing to say.

• Fact: Join 10,000+ teams building agents
• Fact: Accounting agent factory serving 15,000+ businesses with journals, reconciliations, and reports
• Fact: Showing 10 of 33 customer stories

Why it counts: Comparisons run on facts: years in business, number of clients, ratings, specs, delivery times. Numbers are easy for AI to quote and compare.

Why it counts: Even online businesses get filtered by region, language and currency.

Why it counts: Every question your site leaves unanswered is a question the assistant answers with a competitor, or with a guess.