inmar.com — AI Site Grade

Analysis

I have enough data to write the audit. Let me compile the findings.

Inmar Intelligence — AI-Visibility Audit

The site's dedicated AI page (/about/inmar-artificial-intelligence) returns a 404, yet the homepage prominently links to it and the brand markets itself as an AI-powered data platform — meaning any AI crawler following that link hits a dead end instead of structured content about Inmar's AI capabilities.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Applebot-Extended, Bytespider, anthropic-ai — receive a full 200 response with identical byte size (130,120 bytes) to a browser baseline. No UA-based blocking exists. The robots.txt uses a single User-agent: * catch-all with no AI-specific directives; GPTBot, ClaudeBot, and others are not mentioned. The llms.txt returns a 404 (an HTML error page, not even a plain-text 404). The sitemap at /sitemap.xml contains 401 URLs and is well-formed. The site runs on nginx behind Varnish cache, hosted on Pantheon, built on Drupal 9 — a standard CMS stack with no JS-rendering barrier for crawlers.

Cold-Knowledge Gap

The LLM prior describes Inmar as a "supply chain optimization, returns management, and promotional efficiency" company founded in 1980, headquartered in Winston-Salem, processing billions of transactions. The actual site positions itself as an "applied data platform" powering martech (incentives, loyalty, retail media, e-commerce settlement) and healthcare (supply chain, revenue cycle management, patient safety, pharmaceutical returns). The cold knowledge misses the healthcare division entirely — no mention of DSCSA compliance, prescription returns, or revenue cycle management, which are major site pillars. The cold knowledge also omits the martech media/retail media offering and the AI-first messaging ("AI-enhanced, data-driven decision-making") that dominates the homepage.

Schema Posture

Zero JSON-LD schema exists on any page examined — homepage, martech, healthcare, case studies, newsroom, FAQ, and press releases all return empty "types": [] and "jsonld": []. This is a critical gap for a company that wants AI engines to understand its entity structure, solution categories, case study results, and industry verticals. The FAQ page has rich Q&A content but no FAQPage schema. Case studies have structured result metrics (e.g., "24K+ unique shoppers", "$99 ROAS") but no Article or CaseStudy schema.

Content & Structure

The homepage has a single H1 ("We make businesses smarter to improve consumers' lives.") followed by H2 sections for Martech and Healthcare. The navigation is deep and well-organized across ~60 internal pages. The blog/insights page returns very thin content (57 words extracted) — likely a JS-rendered listing that crawlers see as near-empty. The footer copyright reads "© 2026 Inmar Inc." — two years ahead of the actual date, a stale-content signal. The press release announcing the CEO (Spencer Baird) is dated October 2022, over two years old with no newer leadership updates visible.

External Signals

External mentions are sparse in search results. The newsroom links to coverage in Progressive Grocer, C-Store Dive, Packaging Digest, and HR Magazine — legitimate trade press but limited volume. No Reddit threads, Glassdoor reviews, or analyst coverage surfaced. The DNS TXT records reveal integrations with OpenAI (openai-domain-verification), Anthropic (anthropic-domain-verification), Atlassian, Box, Cisco, Twilio, Zoho, Monday.com, Miro, Pardot — a broad SaaS stack suggesting active API/partnership usage, but none of this is surfaced on the site itself.

Findings

1. Dedicated AI page returns 404 High

   The page at /about/inmar-artificial-intelligence, which is linked from the homepage and describes Inmar's AI capabilities, returns a 404 error. AI crawlers following that link encounter a dead end instead of structured content about Inmar's AI platform.

   What to change: Restore the AI page with current content about Inmar's AI-enhanced data platform, or redirect it to a relevant section.

2. Zero JSON-LD schema on any page High

   No JSON-LD structured data exists on the homepage, martech, healthcare, case studies, newsroom, FAQ, or press release pages. This prevents AI engines from understanding entity relationships, solution categories, case study results, and industry verticals.

   What to change: Add Organization, WebSite, Solution, Article, FAQPage, and CaseStudy JSON-LD schemas to relevant pages.

3. llms.txt returns 404 Medium

   The llms.txt file at /llms.txt returns a 404 HTML error page instead of a plain-text file. This is a missed opportunity to provide AI crawlers with a curated summary of the site's content.

   What to change: Create a valid llms.txt file with a summary of key pages and resources.

4. Blog insights page has thin content Medium

   The blog/insights page returns only 57 words of extracted text, likely due to JavaScript-rendered listings. Crawlers see a near-empty page, limiting discovery of blog content.

   What to change: Ensure the blog listing page includes server-rendered content or a static fallback for crawlers.

5. Footer copyright shows year 2026 Low

   The footer displays '© 2026 Inmar Inc.', which is two years ahead of the actual date. This signals stale content to crawlers and users.

   What to change: Update the footer copyright to the current year or use dynamic year rendering.

6. Cold knowledge misses healthcare division Medium

   LLM prior knowledge describes Inmar as a supply chain and returns company but omits the healthcare division (DSCSA compliance, prescription returns, revenue cycle management) and martech media/retail media offerings, which are major site pillars.

   What to change: Publish structured data and dedicated content for healthcare and martech solutions to improve AI understanding.

7. FAQ page lacks FAQPage schema Medium

   The FAQ page contains rich Q&A content but no FAQPage structured data, reducing the chance of appearing in AI-generated answer snippets.

   What to change: Add FAQPage JSON-LD schema to the FAQ page.

8. Case studies lack Article or CaseStudy schema Medium

   Case study pages contain structured result metrics (e.g., '24K+ unique shoppers', '$99 ROAS') but no Article or CaseStudy schema, limiting their visibility in AI-generated summaries.

   What to change: Add Article or CaseStudy JSON-LD schema to case study pages, including key metrics.

9. CEO press release is over two years old Low

   The most recent press release announcing CEO Spencer Baird is dated October 2022, with no newer leadership updates. This may give an impression of outdated content.

   What to change: Publish more recent press releases or leadership updates to keep the newsroom current.

10. Limited external mentions and search results Medium

    Web searches for Inmar Intelligence return very few results, and no Reddit threads, Glassdoor reviews, or analyst coverage were found. This limits external signals that AI models use to validate the brand.

    What to change: Encourage customer and partner testimonials, case studies, and thought leadership content to increase external mentions.

What's working

• All major AI crawlers allowed and served full content — All tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive a 200 response with identical content to a browser, with no UA-based blocking.
• Sitemap is well-formed with 401 URLs — The sitemap at /sitemap.xml contains 401 URLs and is properly structured, aiding crawler discovery.
• Standard CMS stack with no JS-rendering barrier — The site runs on Drupal 9 with nginx and Varnish cache, serving server-rendered HTML that crawlers can easily parse.
• OpenAI and Anthropic domain verification records present — DNS TXT records include openai-domain-verification and anthropic-domain-verification, indicating active integration with major AI platforms.
• Well-organized navigation across ~60 internal pages — The site has a deep navigation structure covering martech, healthcare, case studies, newsroom, and FAQ, providing comprehensive content for crawlers.
• Homepage has a clear H1 tag — The homepage uses a single H1 tag ('We make businesses smarter to improve consumers' lives.'), which is good for semantic structure.