Trust & Proof: Ausbury – Signal Evidence & AI Readability

Ausbury

(https://ausbury.co.uk) 📸 Data Snapshot: June 21, 2026
Trust & Proof — The Lens

Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.

Trust & Proof Verifiable evidence vs. Trust Theatre.
2 Impact Weight: 20 / 100
10% Reputation

The site displays a review_count of 108 across all pages, yet the proof_links_count is 0, suggesting these reviews are static text or internal data with no third-party verification. Trust flags like ‘Secure Payments’ and ’30-day guarantee’ are used as H3 headings but lack links to actual policy documents or merchant verification certificates. The claim of being built ‘5 years ago’ is a common template temporal anchor that lacks any external business registration evidence or press mentions to support its longevity.

The ratio of verifiable proof to marketing fluff is nearly zero; while prices and Royal Mail shipping are mentioned, there is no evidence of the ‘5-year’ promise history or the ‘artisanal’ selection process. Out of over 600 products, not one includes a link to a material certification (like GOTS or OEKO-TEX) which would be standard for a brand claiming ‘Quality Elevates Every Moment.’ The site relies entirely on 108 unverified reviews as its sole proof mechanism.

Trust & Proof is read by weighing trust language against real verification. Below is the page-by-page tally of review mentions and external proof links, then the schema markup that may (or may not) declare verifiable ratings and identity proof.

🛡️ Trust Signals — reviews, proof links, trust-theatre check
432Review mentions (all pages)
0External proof links (all pages)
PageReviewsProof links
/ (home) 108 0
/search/ 108 0
/collections/all/ 108 0
/collections/lingerie/ 108 0
🔗 Identity & Technical Layer — schema JSON-LD: declared ratings, reviews & identity proof
Homepage — no schema detected (entity gap)
/search/ — no schema detected (entity gap)
/collections/all/
{
    "@context": "http://schema.org",
    "@type": "CollectionPage",
    "name": "Products"
}
/collections/lingerie/
{
    "@context": "http://schema.org",
    "@type": "CollectionPage",
    "name": "Lingerie"
}