allbirds.com

JSON-LD is the machine-readable version of your page. With none, agents fall back to scraping text and lose the facts that drive citations and purchases.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Allbirds",
  "url": "https://www.allbirds.com"
}
</script>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Allbirds",
  "url": "https://www.allbirds.com",
  "logo": "https://www.allbirds.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/your-company",
    "https://x.com/your-handle"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@allbirds.com"
  }
}
</script>

Product and Offer schema hands agents your name, price, and availability directly. Missing it means shopping agents cannot confirm what you sell or for how much.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Allbirds product name",
  "description": "One-line description of the product.",
  "sku": "SKU-123",
  "image": "https://www.allbirds.com/product-image.jpg",
  "brand": {
    "@type": "Brand",
    "name": "Allbirds"
  },
  "offers": {
    "@type": "Offer",
    "price": "29.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "url": "https://www.allbirds.com/product-url"
  }
}
</script>

A complete Offer (price, currency, availability, url) is what an agent needs to trust and place an order. Gaps make it hold back.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Offer",
  "price": "29.00",
  "priceCurrency": "USD",
  "availability": "https://schema.org/InStock",
  "url": "https://www.allbirds.com",
  "seller": {
    "@type": "Organization",
    "name": "Allbirds"
  }
}
</script>

A clear contact point and entity identity tell an agent who it is dealing with. Sites an agent cannot verify are the ones it avoids transacting with.

<a href="/contact">Contact us</a>

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Allbirds",
  "url": "https://www.allbirds.com",
  "logo": "https://www.allbirds.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/your-company",
    "https://x.com/your-handle"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@allbirds.com"
  }
}
</script>

Return and shipping schema answers the questions a buying agent checks before committing. Without it, the agent cannot confirm terms and drops the cart.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Offer",
  "priceCurrency": "USD",
  "price": "29.00",
  "availability": "https://schema.org/InStock",
  "hasMerchantReturnPolicy": {
    "@type": "MerchantReturnPolicy",
    "applicableCountry": "US",
    "returnPolicyCategory": "https://schema.org/MerchantReturnFiniteReturnWindow",
    "merchantReturnDays": 30,
    "returnMethod": "https://schema.org/ReturnByMail",
    "returnFees": "https://schema.org/FreeReturn"
  },
  "shippingDetails": {
    "@type": "OfferShippingDetails",
    "shippingRate": {
      "@type": "MonetaryAmount",
      "value": "0",
      "currency": "USD"
    },
    "deliveryTime": {
      "@type": "ShippingDeliveryTime",
      "handlingTime": {
        "@type": "QuantitativeValue",
        "minValue": 0,
        "maxValue": 1,
        "unitCode": "DAY"
      },
      "transitTime": {
        "@type": "QuantitativeValue",
        "minValue": 1,
        "maxValue": 5,
        "unitCode": "DAY"
      }
    }
  }
}
</script>

FAQ and HowTo schema is the format assistants lift answers from. Publishing it turns your support content into answers that name you.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is Allbirds?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A short, factual answer describing what Allbirds offers."
      }
    }
  ]
}
</script>

If an agent cannot find the path to cart, checkout, or contact from your homepage, the transaction ends before it starts.

<a href="/cart">Cart</a>
<a href="/checkout">Checkout</a>

A CAPTCHA on every form is a wall agents cannot climb. Each one you place on a key path is a conversion an agent cannot complete.

A blanket Disallow shuts every agent out at once, including the ones sending buyers. One stray wildcard rule can erase your entire agent audience.

User-agent: GPTBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: CCBot
Allow: /

GPTBot fetches the pages ChatGPT cites and shops from. If robots.txt blocks it, you are invisible to the largest assistant audience and the referrals it sends.

Claude's crawlers (ClaudeBot, Claude-User, Claude-SearchBot) gather the content Claude quotes to buyers. A block here removes you from those answers.

PerplexityBot feeds an answer engine that cites its sources directly. Blocking it drops you from results that carry high-intent clicks.

Google-Extended controls whether Gemini and AI Overviews may use your content. Disallowing it keeps you out of Google's AI answers while allowing it costs you nothing.

CCBot builds the Common Crawl corpus that trains and grounds many models. Allowing it buys long-term presence in the datasets agents learn from.

Agents give a page one quick request. If the homepage does not return a clean 200 fast, they move on and never see your offer.

Bot challenges and interstitials are built for browsers, not agents. An agent that hits a checking-your-browser wall cannot read or buy anything behind it.

Some CDNs serve agents a blank or blocked page while humans see the real site. If your bot response differs from the human one, agents come away with nothing.

Most agents read raw HTML and do not run your JavaScript. If the page is empty until JS loads, agents see a blank page where your content should be.

Landmarks and a clean heading order tell an agent what each part of the page is. Without them, agents guess and often quote the wrong thing.

An llms.txt file is the emerging map agents read first. A good one points them straight at the pages you want cited and bought from.

A sitemap lists every URL worth crawling. Without one, agents only find what they stumble across from your homepage.

Canonical tags tell agents which URL is the real one. Missing or cross-domain canonicals split your authority and confuse which page gets cited.

The title and meta description are the first summary an agent reads. Vague or missing ones make your page easy to skip in an answer.

Agents that cannot find a price in text or schema cannot compare or buy. Prices locked in images or JavaScript are invisible to them.

Account walls stop most shopping agents cold. A checkout that demands sign-up first loses the sale to a competitor that allows guests.

Platforms like Shopify expose agent-ready endpoints when configured. Turning them on lets agents read your catalog and cart the supported way instead of scraping.

Feeds, plugin manifests, and agent endpoints are how the newest agents connect directly. Exposing any of them puts you ahead of sites they have to scrape.