AgentBIAgent with Business Intelligence for DTC sites

Knowledge base

Sections and entries for this domain, shown from the carrier view of this page.

Optimise

What to change and how. Six sections organised by which layer a change lands in and who ships it; entries are remediation actions, each closing the loop from a scan reading, through the change, to a re-scan.

OPT-1 Config layer3 item(s)

Config files only, no code changes — lowest cost

Carrier on this page:Knowledge base — file specs and common misconfigurations.

Open-source tools:Lighthousellmstxt-generatorNuxt RobotsVaporScan

Skills:Config-layer fix: robots / sitemap / llms.txt / .well-known

  • Review robots.txt and the sitemap agent by agent

    OPT-1-1

    A shopping or search agent reads robots.txt first. Putting /products/ or /collections/ in Disallow makes products invisible; a stale sitemap delays discovery of new listings.

    • Check Disallow rules per user agent (GPTBot, PerplexityBot, Google-Extended …) and block only private paths such as checkout, account and internal search
    • Declare an absolute Sitemap URL in robots.txt, then re-crawl the homepage and key product pages with JavaScript disabled

    View detail

  • Declare llms.txt and .well-known/ucp entry points

    OPT-1-2

    Besides robots.txt, agents look for site-provided declaration files. Without them, the site capabilities can only be inferred from crawled pages and are easily misread. These are the owner own config files in a public format — no external data feed is involved.

    • Place llms.txt at the root: a short Markdown file listing the site purpose, crawlable sections and preferred entry points, without dumping the whole catalogue
    • If UCP is supported, declare the capability endpoint at .well-known/ucp per the current public spec; fetch it with JS disabled to confirm a parseable response, not an HTML error page

    View detail

  • Clean up CDN cache headers and redirect chains

    OPT-1-3

    An agent sees the CDN edge response. Long-caching HTML that contains prices, or a chain of 301/302 before the landing page, makes it read stale content or give up.

    • Give product/price responses a short TTL or revalidate them under no-cache; never long-cache HTML that contains prices
    • Reduce key landing pages to a single hop and re-crawl with JS disabled to confirm the final status and canonical agree

    View detail

18 more items not shownSign up free

OPT-2 Template layer3 item(s)

Front-end templates — requires a deploy

Carrier on this page:Knowledge base — per-template fixes and regression checklists.

Open-source tools:Schema.org vocabularyschema-dtsmetascraper

Skills:Template-layer fix: server rendering, JSON-LD and canonical

  • Server-render the core product facts

    OPT-2-1

    Many external agents do not execute JavaScript, or only part of it. If name, price and availability are filled in only by hydration, the agent sees an empty shell.

    • Put name, price, availability and JSON-LD into server-rendered HTML; fetch once with JS disabled to confirm the price is readable
    • Validate every template with the Rich Results Test, not just one hand-written sample page

    View detail

  • Complete JSON-LD and canonical / hreflang per template

    OPT-2-2

    Structured data that exists only on a few hand-written pages disappears with the next template change; on multilingual sites, missing hreflang makes agents treat same-named products across markets as duplicates or mix up prices.

    • Make Product / BreadcrumbList / Organization JSON-LD template variables, with price and availability sourced from the same fields as the server-rendered HTML
    • Emit a self-referencing canonical on every indexable page; cross-link hreflang with x-default on localised pages, and spot-check each template with the Rich Results Test

    View detail

  • Template output for image srcset / alt and critical CSS

    OPT-2-3

    When the main image is JS-lazy-loaded and alt is empty, an agent has no citable image data; if critical CSS blocks first paint, the main content never appears in a JS-disabled fetch.

    • Emit real alt text and srcset for the main image in the template, with a no-script src fallback
    • Inline critical CSS and load the rest async; confirm name and price are visible in a JS-disabled fetch

    View detail

18 more items not shownSign up free

OPT-3 Data layer3 item(s)

Product master data and feeds — cross-system

Carrier on this page:Knowledge base — master-data governance SOP.

Open-source tools:MedusaSaleor

Skills:Data-layer fix: feed and master-data consistency

  • Keep feed and landing-page price / availability consistent

    OPT-3-1

    When the readings disagree, an agent discards the whole record. A feed that is not refreshed after a bulk price change is the most common hidden loss.

    • Make product master data the single source of truth for detail page, cart, checkout and feed
    • Force a feed refresh after every bulk price change and auto-compare the three amounts plus availability

    View detail

  • Unify SKU↔id mapping and unit / size conversions

    OPT-3-2

    When the same product carries different ids in ERP, storefront and feed, an agent reads it as two items; unit and size conversions buried in prose rarely line up across markets.

    • Fix one stable product id as the primary key, map SKU / variant / channel ids onto it, and version the mapping alongside product master data
    • Express weight, dimensions and size conversions as structured fields and lookup tables; never leave approximately-equals only in the description text

    View detail

  • Put currency, decimals and tax wording into master data

    OPT-3-3

    Guessing currency from the URL, two decimals on JPY, or no tax wording next to the price makes agents misread amounts across markets.

    • Attach an ISO currency code and decimal rule to every price (0 for JPY/KRW) and make tax-inclusive/exclusive a separate field
    • Render detail page, cart, checkout and feed from that same field set instead of formatting separately in each template

    View detail

18 more items not shownSign up free

OPT-4 Flow layer3 item(s)

Business flows — highest cost, often needs a sandbox

Carrier on this page:Knowledge base — step-by-step SOP.

Skills:Flow-layer fix: sandbox checkout regression

  • Sandbox the checkout flow and regression-test currencies

    OPT-4-1

    Any break between add-to-cart and order confirmation makes an agent treat the site as unusable; 3DS and currency rules differ by market.

    • Run a sandbox order per market (add to cart → address → shipping → payment → success) and log failure-code distribution
    • Use 0 decimals for JPY/KRW, label tax-inclusive vs exclusive, and keep amounts identical across detail page, cart, checkout and feed

    View detail

  • Make 3DS, chargebacks and the returns path explicit in checkout

    OPT-4-2

    If payment verification and after-sales paths hide behind modals or scripts, an agent cannot tell whether the transaction can complete. These flow changes need a human or a sandbox; tools only mark the boundary and do not promise automation.

    • Document 3DS trigger conditions, retry and fallback payment paths as crawlable steps in checkout, noting which markets enable them
    • Put the returns / refund entry point and its deadlines into order confirmation and the help centre; run one human sandbox pass per market, log failure codes per step, and do not treat these as auto-verifiable

    View detail

  • Show shipping and duties before checkout

    OPT-4-3

    Shipping and duties that appear only at the payment step are the most common cause of cart abandonment, and an agent reads the same signal as a trust issue.

    • State shipping estimates, duty responsibility and delivery time on the product/cart pages and keep checkout consistent
    • Verify shipping math per market in a sandbox; label landed price separately from item price rather than blending them

    View detail

18 more items not shownSign up free

OPT-5 Content layer3 item(s)

Human-written content, continuously expanded

Carrier on this page:Knowledge base — style guide and per-category fact sheets.

Open-source tools:claude-seoweb-quality-skills

Skills:Content-layer fix: category pages and multilingual copy

  • Make category pages and size guides agent-readable

    OPT-5-1

    A size chart as an image, or specs scattered through free text, leaves an agent unable to compare products — so it cites a competitor instead.

    • Use an HTML table for the size chart, state how to measure, and put key conversions into structured data
    • Write a citable fact sheet per category (material, origin, use case) and keep first-screen content off hover / JS

    View detail

  • Keep multilingual product copy and the help centre consistent

    OPT-5-2

    When each market writes its own copy, material, warranty and delivery claims diverge and an agent ends up quoting contradictory answers. The help centre is the most-cited yet least-updated place.

    • Maintain one shared fact sheet per product (material, origin, warranty, delivery); generate localised copy from it and update every language when the facts change
    • Include returns / duties / delivery help pages in the review checklist for every price or policy change, keeping help pages and checkout consistent

    View detail

  • Structure per-product specs and material facts

    OPT-5-3

    Specs buried in long descriptions cannot be extracted into comparable fields, and inconsistent material names across pages produce contradictory citations.

    • Move material / dimensions / weight / origin into a spec table or structured fields, with names fixed in one shared fact sheet
    • Attach units and measurement method to each spec; let the description explain rather than carry the only copy of a fact

    View detail

18 more items not shownSign up free

OPT-6 Policy layer3 item(s)

Legal and compliance — review-gated

Carrier on this page:Knowledge base — compliance wording and review process.

Open-source tools:axe-corePa11y

Skills:Policy-layer fix: compliance labels and a review gate

  • Compliance labelling and accessibility basics

    OPT-6-1

    Terms hidden behind JS, forms with only placeholders, or fabricated review counts make agents distrust the site or trigger Rich Result errors.

    • Complete returns / tax / privacy policies per market, keep policy pages directly crawlable, and give form controls real labels
    • Check contrast and keyboard reachability against WCAG AA with axe / Lighthouse; only ever publish real review counts

    View detail

  • A review-gated process for review authenticity and credentials / tax labels

    OPT-6-2

    Treating compliance as a one-off check lets it drift back fast: reviews, credentials and tax labels change with every new product and market. It needs a named reviewer and a release log, not a single fix.

    • Show only genuine reviews and real counts, complete credentials and tax labels per market, name a reviewer and keep a record of every approval
    • Make crawlable policy pages, real review counts and complete labels a fixed pre-listing gate, with periodic spot checks rather than a single launch-time check

    View detail

  • Review compliance fields in structured data

    OPT-6-3

    aggregateRating, offer and return-policy fields that disagree with visible page content trigger Rich Result errors and make agents distrust the site.

    • Keep review counts, prices and return policy in structured data sourced from the visible page; omit a field rather than inventing it
    • Spot-check structured data per template and route the errors into the pre-listing review gate

    View detail

18 more items not shownSign up free