UCP status report
de.dawanda.com
de.dawanda.com responded, but its profile did not pass schema validation.
HTTP 200
Release none
Checked 17 Oct, 09:01 UTC
To fix first
Problem
Serve profile as application/json
The profile URL did not return parseable JSON. How to fix →
Also worth fixing
To fix
Publish Organization schema (JSON-LD) on the homepage
No Organization-typed JSON-LD detected on your homepage. How to fix →
To fix
Publish a /llms.txt brand brief
No /llms.txt file detected at the root of your domain. How to fix →
To fix
Publish a sitemap.xml
No sitemap.xml detected at the root of your domain. How to fix →
To fix
Add Open Graph meta tags to the homepage
OG tags missing or incomplete on your homepage. How to fix →
To fix
Add a mobile viewport meta tag
No viewport meta tag detected on your homepage. How to fix →
Passed
4 OK
HTTPS, AI bot access, Public keys published, No validation warnings
Show all 4
- HTTPS: Profile URL uses https://
- AI bot access: robots.txt allows /.well-known/ucp
- Public keys published: Keys published at the top level
- No validation warnings: No outstanding validation issues
Check trace
How de.dawanda.com answered our check
The five ways an agent can reach this store, what each one met, and every request we made.
1 of 5 open
4 requests · 855 ms at the store · public requests only
4 requests · 855 ms at the store · public requests only
-
Finding the profileOpen
-
Acting for the buyerNot offered
-
In the buyer's browserNot offered
-
Calling its servicesNone
-
Sending the buyer to the websiteNot declared
UCP Checkerpublic requests
- 2 requestsFinding the profile/.well-known/ucp · 200
- read from profileActing for the buyernot declared
- read from profileIn the buyer's browsernot declared
- not calledCalling its servicesnone declared
- read from profileSending to the websitenot declared
- 2 requestsOutside UCPhomepage · /llms.txt
Open
01 · Finding the profile2 requests
Served at /.well-known/ucp with 200 OK, 1.1 KB. robots.txt allows /.well-known/ucp.
Not offered
02 · Acting for the buyerread from profile
The profile doesn't declare identity linking, so an agent can't act for a signed-in buyer.
Not offered
03 · In the buyer's browserread from profile
No Embedded service is declared.
None
04 · Calling its servicesnot called
No services are declared.
Not declared
05 · Sending the buyer to the websiteread from profile
No permalink declared. Whether error replies carry a continue_url shows only in an agent run.
- 01 PROFILEGET /.well-known/ucp → 200, 1.1 KB of JSON855 ms
- 01 PROFILEGET /robots.txt → allows /.well-known/ucp–
- 01 PROFILEProfile did not pass schema validation: Response is not a valid JSON objectlocal
- OUTSIDE UCPGET / → 403, no Organization schema found–
- OUTSIDE UCPGET /llms.txt → 200, not found–
UCP profile as served 1.1 KB · 42 lines
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<title>DaWanda sagt danke!</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" media="screen" href="/goodbye_assets/styles.css" />
</head>
<body>
<header>
<img src="/goodbye_assets/dawanda.png" alt="logo">
</header>
<main>
<div class="illustration-banner"></div>
<div class="thank-you-banner">
<h1>Wir sagen Danke für 12 Gemeinsame Jahre</h1>
<img src="/goodbye_assets/closed.png" alt="closed">
</div>
<div class="products-banner"></div>
<div class="etsy-banner">
<h2>Der DIY Trend geht weiter. DaWanda-Shops bei Etsy</h2>
<p>Etsy, der weltweite Marktplatz für Handgemachtes und Vintage, bietet
DaWanda-Verkäufern und -Käufern ein neues Zuhause.</p>
<a href="https://www.etsy.com">Jetzt zu <span>Etsy</span></a>
</div>
</main>
<footer>
<p>© DaWanda GmbH 2006 - 2019</p>
</footer>
</body>
</html>
Is de.dawanda.com your store?
Claim it with one DNS record.
Why is de.dawanda.com's profile invalid?
We found a UCP profile, but it failed schema validation against the official spec. The findings on this page list what failed — usually missing required fields, wrong data types, or version mismatches. Agents reject profiles that don't validate, so this needs fixing before de.dawanda.com is agent-ready.
How can de.dawanda.com fix this?
Run the profile through our UCP Validator — it shows line-by-line schema deviations and how to fix each one. Most invalid profiles are quick fixes: a missing field, a typo, or an outdated spec version.
Does this mean de.dawanda.com is broken for shoppers?
No — the regular website still works fine for human customers. Only AI agents that strictly validate the profile will refuse to use the UCP integration. The store just isn't agent-ready until the validation issues are resolved.
How was this UCP report for de.dawanda.com generated?
Our crawler fetches
de.dawanda.com/.well-known/ucp directly, parses the profile against the official UCP JSON schema, checks robots.txt for its rules for AI crawlers, and runs payment-handler validation. No manual review, no opinions — just what the profile actually says. The check ran 2 days ago.How do I get a newer result for de.dawanda.com?
This page shows the stored result of our last check and when it was observed. To run a new check, use Check again on this page.
Why does this status matter?
Universal Commerce Protocol is an open standard that lets a UCP agent find out what a store sells, build a cart and check out through a published contract instead of reading web pages. A valid UCP profile is how a store declares that support.
