Agent-readiness report
Is Lovebrands agent-ready?
Agents can call it as a tool, but cannot read it.
lovebrands.at, last scanned yesterday, on 29.09.2026
Agent classes working
1/3
Score history
±05 scans since 19.09.2026
- 2
- Blocking agents
- 8
- Weak spots
- 16/26
- Checks passed
What costs Lovebrands the most
1 of 3 agent classes work
- ✕Answer engines & research agents
- ✓MCP tool-callers
- !Summarisers & knowledge agents
- ✕
robots.txt turns AI crawlers away
ChatGPT and Perplexity are told not to read the site, so it cannot appear in their answers.
Blocker - ✕
The site does not say who it is
A model cannot tell that this domain is the brand it was asked about.
Blocker - ✕
No stated policy for automated access
Cautious platforms will not act on the site without an explicit permission signal.
Improvement - !
Title, description and canonical URL
Answer engines have no reliable label for the page, so they invent one or skip it.
Improvement - !
Sitemap is discoverable and structured
Agents have to find pages by luck instead of reading a list.
Improvement
✓16 checks passed · 5 more to fix+−
Free dashboard
Track lovebrands.at and watch it climb.
Weekly re-scans, the fix for every gap above, and the rank moves of your rivals.
- 10 optimization suggestions, ready today
- Weekly re-scan with alerts on every change
- Rank and rival moves in one view
Your dashboard
We email you a sign-in link and add lovebrands.at to your dashboard.
- Re-scan weekly
- Fixes listed
- Rivals tracked
Check a rival
5 domains free, unlimited with a plan.
Machine interfaces
Lovebrands exposes 5 of 8 interfaces agents look for: Bot user-agent handling, llms.txt, MCP server, API or feed, Machine-readable contact.
Locked
All 8 interfaces and 26 checks for lovebrands.at
See which interface is missing, what each check looked for, and what to change to pass it. Free account, no card.
View detailed signalsE-commerce & product feeds
Measured separately, not part of the public score or rank
Add-on score
21/100
- 6
- Blocking agents
- 3
- Weak spots
- 3/12
- Checks passed
- ✕
Product pages are closed to crawlers
The homepage is readable but the products are not, so agents never see prices or stock.
- ✕
Products have no structured data
Agents cannot tell what is for sale, so the catalogue is invisible to them.
- ✕
Price and stock are not machine-readable
Comparison agents quote a stale price or leave the shop out of the comparison.
- ✕
Not on Qomvia Market
Agents using Qomvia cannot get an agent price or a payable order from this shop.
- ✕Autonomous shopping agents
- ✕Feed & API integrators
- ✕Price-comparison & monitoring bots
- ✓Agent payment protocols
- ✕Catalogue access0%
- ✕Product data legibility13%
- !Agent-commerce protocols60%
- ✕Checkout traversability0%
The seal
Agent-Readable
Agents can read the site, but acting on it still breaks. Paste this line where you want the seal: it is drawn at runtime, so it upgrades itself when you improve and removes itself if a deploy closes the site to agents.
<script src="https://qomvia.com/badge.js" data-slug="lovebrands-at" async></script>There is no image URL and no static version. The seal exists only as markup we serve per request, which is what makes it worth displaying.
- Agent-Ready Champion90+
- Agent-Ready75+
- Agent-Readable60+
- In Progress40+, dashboard only
Lovebrands and AI agents: common questions
Is Lovebrands readable by AI agents?+−
Lovebrands (lovebrands.at) scores 66 out of 100 for agent readiness, grade C, measured yesterday, on 29.09.2026. 1 of 3 agent classes we test can use the site, and 2 checks currently block agents outright.
What stops agents from using lovebrands.at?+−
The heaviest problems are: robots.txt turns AI crawlers away; The site does not say who it is; No stated policy for automated access; Title, description and canonical URL; Sitemap is discoverable and structured. Each one is scored from a public HTTP response, and the fix for each is listed in the signed-in report.
How is the Lovebrands agent-readiness score calculated?+−
Qomvia fetches public pages of lovebrands.at as an AI agent would and runs the core checks every site gets across 6 groups: Machine access, Content legibility, Discovery surface, Identity & policy, Agent-facing performance, Agent protocols. Checks are weighted by how much an agent loses when they fail, and the score is expressed out of 100. E-commerce & product feeds checks are scored separately (21/100) and do not affect the public score or rank.
How often is this score updated?+−
Public scores are re-checked when the site is re-scanned; tracked domains are re-scanned weekly and their owners are alerted when a check regresses. This page shows the scan from yesterday, on 29.09.2026.
Compare and keep reading
Scores are computed from public HTTP responses only. We never submit forms, never attempt a purchase and never bypass a bot challenge. Disagree with a result? Request a correction or opt this domain out.