peterhahn.com — AI Site Grade

Analysis

Peter Hahn — AI-Visibility Audit

The corporate site (peterhahn.com) and the shop (peterhahn.de) are two separate domains with radically different AI-visibility postures, and the cold-knowledge model already knows more about the brand's controversies than the corporate site discloses.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive a 200 with full HTML content on both peterhahn.com and peterhahn.de. No UA-based blocking exists. However, the shop domain (peterhahn.de) hides its robots.txt behind a Cloudflare JavaScript challenge (403 with captcha), meaning crawlers that cannot execute JS cannot read the crawl directives. The corporate site's robots.txt is wide open (User-agent: * Disallow:) but contains zero AI-bot-specific rules — no GPTBot, no ClaudeBot, no Google-Extended directives at all. Neither domain serves an llms.txt (both return 404/403).

Domain Split and Schema Posture

The brand operates a two-domain architecture: peterhahn.com is a thin corporate brochure (company profile, press releases, sustainability), while peterhahn.de is the full e-commerce shop. The corporate site carries only WebPage, BreadcrumbList, and WebSite schema — no Organization schema with logo, social profiles, or founding date, despite having all that data in its text. The shop domain does include Organization schema with phone number and social links, plus ItemList and Product schema on category pages. However, individual product pages lack Product schema entirely — only BreadcrumbList is present, meaning AI engines cannot extract price, availability, or brand data from the most important pages.

Cold-Knowledge Gap

The LLM knows Peter Hahn as a German fashion retailer founded in 1962, part of the Otto Group, targeting women 40+, with size-inclusive offerings (34-54). The actual site contradicts several of these facts: the company was founded in 1964 (not 1962), and the chronology page explicitly states that Equistone Partners Europe acquired the company in 2015 and Wourth Group became the new investor in 2025 — the brand is no longer part of the Otto Group. The model also recalls a 2023 ageist advertising controversy that the corporate site does not mention anywhere, not in the philosophy page, the chronology, or any press release. This creates a significant reputational blind spot: AI engines retrieving the site will find no response to a known reputational incident.

Content and External Signals

The corporate site is a static WordPress installation (Cloudflare-hosted, no JS-rendering risk) with 235+ URLs, mostly press releases about local sponsorships and awards. The sustainability page is substantive (GOTS, OEKO-TEX, The Good Cashmere Standard, EcoVero, Grünkauf program) but carries zero schema markup — no Product sustainability labels, no Organization certification references. External signals are sparse: no Reddit threads or review aggregator results surfaced in search. The brand's social footprint (Facebook, Instagram, YouTube, Pinterest, LinkedIn) is linked but not structured in schema. The chronology page is the most valuable page for AI knowledge extraction — it contains the full 60-year history, investor changes, and sustainability milestones — yet it uses only WebPage schema with no Event or Organization timeline markup.

Findings

1. Corporate site lacks Organization schema High

   The corporate site (peterhahn.com) contains text about founding date, investor changes, and social profiles but uses only WebPage, BreadcrumbList, and WebSite schema. No Organization schema is present, preventing AI engines from extracting structured entity data.

   What to change: Add Organization schema to the corporate site with name, founding date, logo, social profile URLs, and description.

2. Cold knowledge contradicts site facts on founding year and ownership High

   The LLM knows Peter Hahn as founded in 1962 and part of the Otto Group, but the site states founding in 1964 and that Equistone Partners Europe acquired the company in 2015, with Wourth Group becoming investor in 2025. The site does not clarify the current ownership structure.

   What to change: Update the site to clearly state the current ownership and correct the founding year in both text and schema.

3. Corporate site ignores known ageist advertising controversy High

   The LLM recalls a 2023 ageist advertising controversy involving Peter Hahn, but the corporate site contains no mention of it on the philosophy page, chronology, or any press release. This creates a reputational blind spot for AI engines that retrieve the site.

   What to change: Add a statement or press release addressing the controversy to the corporate site to provide context for AI engines.

4. Shop domain robots.txt hidden behind JavaScript challenge High

   The shop domain (peterhahn.de) returns a 403 with a Cloudflare JavaScript challenge for robots.txt, meaning crawlers that cannot execute JS cannot read the crawl directives. This may cause some AI crawlers to treat the domain as blocked.

   What to change: Configure Cloudflare to allow access to robots.txt without a JavaScript challenge, or serve a static robots.txt file.

5. Product pages lack Product schema High

   Individual product pages on peterhahn.de contain only BreadcrumbList schema, missing Product schema with price, availability, and brand data. AI engines cannot extract structured product information from the most important pages.

   What to change: Add Product schema to all product pages, including price, availability, brand, and description.

6. No llms.txt file on either domain Medium

   Neither peterhahn.com nor peterhahn.de serves an llms.txt file (404/403). This file helps AI crawlers discover key content and understand site structure.

   What to change: Create and serve an llms.txt file on both domains listing key pages and a brief description.

7. Corporate robots.txt has no AI-bot-specific rules Low

   The corporate site's robots.txt allows all user agents but does not include any directives for AI crawlers like GPTBot, ClaudeBot, or Google-Extended. While not blocking, this misses an opportunity to guide crawler behavior.

   What to change: Add explicit directives for AI crawlers, such as allowing or disallowing specific paths.

8. Sustainability page lacks structured markup for certifications Medium

   The sustainability page lists certifications (GOTS, OEKO-TEX, etc.) but uses no schema markup to represent them. AI engines cannot extract structured certification data.

   What to change: Add Product or Organization schema referencing certifications, or use a dedicated schema for sustainability claims.

9. Chronology page lacks Event or timeline schema Medium

   The chronology page contains the full 60-year history with key milestones but uses only WebPage schema. Adding Event or timeline markup would help AI engines extract historical facts.

   What to change: Add Event schema for each milestone or use a structured timeline format with schema markup.

10. Limited external signals from reviews and social media Low

    Web searches for Peter Hahn reviews and Reddit discussions returned no results. The brand's social media presence is linked but not structured in schema, limiting external validation for AI engines.

    What to change: Encourage customer reviews on third-party platforms and link to them from the site. Add social profile URLs in Organization schema.

What's working

• All major AI crawlers receive full HTML content — Both peterhahn.com and peterhahn.de return 200 with full HTML for all tested AI crawlers (GPTBot, ClaudeBot, etc.), ensuring content is accessible.
• Shop domain includes Organization schema with contact info — The shop domain (peterhahn.de) includes Organization schema with phone number and social profile links, helping AI engines identify the business entity.
• Sustainability page provides detailed certification information — The sustainability page lists multiple certifications (GOTS, OEKO-TEX, etc.) and programs, providing rich content for AI engines to reference.
• Chronology page details 60-year company history — The chronology page contains a detailed timeline of the company's history, including founding, acquisitions, and sustainability milestones, providing valuable context for AI knowledge extraction.
• Corporate site is static WordPress with no JS rendering risk — The corporate site is a static WordPress installation hosted on Cloudflare, meaning all content is available in HTML without JavaScript execution, ensuring crawlers can parse it.
• BreadcrumbList schema present on corporate and shop pages — Both domains use BreadcrumbList schema on key pages, helping AI engines understand site structure and navigation paths.
• Sitemap available with 80 URLs — The corporate site has a sitemap listing 80 URLs, helping crawlers discover content efficiently.
• English version of corporate site available — The corporate site offers an English version at /en/, expanding reach to international audiences and AI engines.