dennemeyer.com — AI Site Grade

Analysis

Dennemeyer.com: AI-Visibility Audit

The site has no structured data beyond breadcrumb schemas and no llms.txt, yet every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider — receives a full 200 with identical HTML content as a browser, meaning the technical gate is wide open but the semantic gate is locked.

Crawler Access

All 11 tested bots (including GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended, Bytespider, Perplexity-User, and a browser baseline) return 200 with identical byte size (108,620) from the homepage. The robots.txt contains a single User-agent: * block with TYPO3-internal disallows and zero AI-bot-specific rules. No bot is blocked, rate-limited, or served a thin JS shell. The site runs on Apache with HSTS and a permissive CSP (default-src 'self' 'unsafe-inline' 'unsafe-eval' * blob: data:). The llms.txt returns a 404 — the site has no AI-friendly content map.

Cold-Knowledge Gap

The LLM prior knows Dennemeyer as a Luxembourg-founded (1962) global IP firm with 1,000+ employees, 20+ offices, handling 3M+ IP rights, with products including DIAMS and Octimine. The site confirms all of this. However, the model's prior mentions an "IP Management Suite" (a name the site does not use — the product is called DIAMS iQ and now DIAMS Infinity) and omits the Simple IP free tier entirely. The site heavily promotes Simple IP as a freemium entry point for startups and SMEs, but the cold model has zero awareness of it. The model also does not know about the DIAMS Infinity launch (May 2026) or the explicit anti-private-equity positioning on the About page.

Schema Posture

Every page checked carries only a BreadcrumbList schema. There is no Organization schema, no Product or SoftwareApplication schema for DIAMS iQ, DIAMS Infinity, Simple IP, or Octimine, no FAQPage schema despite FAQ content on /ip-software/ and /ip-software/simpleip/, and no Article schema on blog posts. The homepage has zero JSON-LD of any type. This is the single largest structural gap: AI engines crawling the site get rich text but zero entity markup to ground their understanding of the brand, its products, or its service hierarchy.

External Signals

Web searches for reviews, Reddit threads, and recent press return no results — the brand has minimal independent third-party discussion in discoverable channels. The site itself carries customer testimonials (Red Bull, Accelleron, Varta AG, Springer Nature, Swiss Federal Institute of Intellectual Property) but none are marked up with schema. The blog is active and publishes multiple times per month with articles dated into May 2026, but blog posts lack Article schema and are not surfaced in an llms.txt.

Surprising Details

The About page contains a notable anti-private-equity manifesto: "Dennemeyer refuses to be influenced by external parties and remains an independent, trusted partner... the lack of private equity capital." This is a distinctive brand-positioning signal that no AI model would surface without live retrieval, since it is not reflected in any schema or external press. The sitemap is a TYPO3-generated index with only three sub-sitemaps (pages, blog posts, blog tags) and a modest URL count — suggesting many service pages may not be indexed. The homepage uses a carousel with JS-dependent content, but the underlying HTML is rich enough that crawlers see the full text regardless.

Findings

1. Missing Organization schema on homepage and all pages High

   No Organization JSON-LD exists anywhere on the site, so AI engines cannot reliably extract brand name, logo, description, or social profiles.

   What to change: Add Organization schema with name, url, logo, description, and sameAs links to the homepage and About page.

2. Missing SoftwareApplication schema for all IP products High

   DIAMS iQ, DIAMS Infinity, Simple IP, and Octimine product pages lack SoftwareApplication or Product schema, preventing AI from understanding features, pricing, or categories.

   What to change: Add SoftwareApplication schema to each product page with name, description, applicationCategory, offers, and operatingSystem.

3. FAQ content on product pages lacks FAQPage schema Medium

   Pages like /ip-software/ and /ip-software/simpleip/ contain FAQ sections but no FAQPage markup, so AI cannot extract Q&A pairs for rich results.

   What to change: Add FAQPage schema with mainEntity array of Question/Answer pairs to pages with FAQ content.

4. Blog posts lack Article schema Medium

   The IP blog publishes multiple times per month but posts have no Article or BlogPosting schema, reducing their chance of appearing in AI-generated summaries or Google News.

   What to change: Add Article schema to each blog post with headline, datePublished, author, and image.

5. llms.txt returns 404, no AI content map High

   The site has no llms.txt file, so AI crawlers have no curated summary of key pages, product descriptions, or brand information to efficiently ground their knowledge.

   What to change: Create an llms.txt file listing core pages (homepage, product pages, About, blog) with brief descriptions.

6. Simple IP free tier unknown to AI models Medium

   The cold LLM prior has no awareness of Simple IP, a freemium product heavily promoted on the site, meaning AI-generated summaries will omit a key offering.

   What to change: Add SoftwareApplication schema for Simple IP and include it in llms.txt to improve AI grounding.

7. DIAMS Infinity launch missing from AI knowledge Medium

   The cold model does not know about DIAMS Infinity (launched May 2026), a major product update, reducing the site's ability to attract AI-driven leads.

   What to change: Add SoftwareApplication schema for DIAMS Infinity and publish a press release or blog post with schema markup.

8. Minimal independent third-party signals online Medium

   Web searches for reviews, Reddit discussions, and recent news return no results, limiting the site's external authority signals for AI ranking.

   What to change: Encourage customer reviews on third-party platforms and publish press releases with schema markup.

9. Customer testimonials lack schema markup Low

   Testimonials from brands like Red Bull and Springer Nature appear on the site but are not marked up with Review or Testimonial schema, missing an opportunity for rich snippets.

   What to change: Add Review schema to testimonial sections with itemReviewed, author, and reviewRating.

10. Sitemap contains only three sub-sitemaps, likely missing many pages Medium

    The TYPO3-generated sitemap index has only three sub-sitemaps (pages, blog posts, blog tags) and a modest URL count, suggesting service pages may not be indexed.

    What to change: Review and expand the sitemap to include all important service and product pages.

11. Distinctive anti-private-equity positioning not marked up Low

    The About page contains a strong independence statement, but no schema or external press references it, so AI models cannot surface this unique brand differentiator.

    What to change: Add Organization schema with description including the independence stance, or publish a press release with schema.

What's working

• All major AI crawlers receive full HTML content — Every tested bot (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, etc.) gets a 200 with identical byte-size HTML as a browser, ensuring no content is hidden from AI.
• Homepage and product pages contain rich, crawlable text — Despite JS carousels, the underlying HTML is rich enough that crawlers see full text, avoiding the empty-shell problem common in modern sites.
• Blog publishes multiple times per month with recent content — The IP blog is active with articles dated into May 2026, providing fresh content that AI crawlers can index for topical authority.
• BreadcrumbList schema present on all checked pages — Every page carries BreadcrumbList JSON-LD, helping AI understand site structure and page hierarchy.
• CSP allows AI crawlers to execute scripts if needed — The Content-Security-Policy includes 'unsafe-inline' and 'unsafe-eval', which, while not a security best practice, ensures AI crawlers that execute JS can still render the page.
• HSTS enforced for secure connections — The site uses HSTS, ensuring all connections are HTTPS, which is a positive trust signal for AI crawlers.