gomomentus.com — AI Site Grade

Analysis

The Cold-Knowledge Gap Is the Story

The LLM's cold knowledge describes Momentus as a performing-arts ticketing and fundraising platform (competing with Tessitura, PatronManager) — a description that matches the pre-2023 Ungerboeck-era product. The actual site sells a completely different company: an enterprise venue management platform for stadiums, convention centers, corporate campuses, and universities, with AI-powered operations, white-label ticketing, and risk/incident management.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended — receive a full 200 response with identical byte size (~196KB) to browser traffic. Only Bytespider gets a 403 block. The robots.txt contains no AI-bot-specific rules whatsoever: a single User-agent: * directive disallowing only tracking-parameter URLs (/*__hstc=, /*_page=). No llms.txt exists (404). The site is built on Webflow, served behind Cloudflare (cf-ray headers), with DNS pointing to Fastly (151.101.193.91). The homepage renders ~3,300 words of visible text on plain GET — no JS-shell risk.

Cold-Knowledge Gap

The LLM's prior knowledge is stale by approximately 3+ years. It describes Momentus as a ticketing/CRM/fundraising tool for performing arts centers, originally spun off from the University of Texas at Austin's Performing Arts Center. The actual site describes a company that rebranded from Ungerboeck in January 2023, following acquisitions of EventBooking, Priava, Showorks, and Risk Manager. The current product line is Momentus Enterprise (convention centers, corporate campuses, universities), Momentus Elite (stadiums, arenas, performing arts centers, conference centers), Momentus Ticketing (white-label), and Momentus WeTrack (risk/incident management). The site claims 4,000+ venues, 60,000 users, customers including SoFi Stadium, Google, ExCeL London, Apollo Theater, and Harvard — none of which appear in the LLM's cold knowledge. The LLM also mentions "mixed reviews on G2 and Capterra" — but DuckDuckGo returned zero search results for Momentus on any review platform, suggesting the domain has minimal external citation footprint.

Schema Posture

The homepage and about page carry rich JSON-LD with Organization, WebSite, and BreadcrumbList types. The Organization schema includes founding date (2025 on homepage, 1985 on about page — a contradiction), leadership team, customer references, product offers, and social profiles. The ticketing page adds Product and FAQPage schemas. However, the sameAs links point to linkedin.com/company/momentus and twitter.com/momentus — generic handles that may not resolve. The blog and content hub use CollectionPage and BlogPosting schemas. No Article or NewsArticle markup on individual blog posts was verified.

External Signals

DuckDuckGo returned zero results for searches including "gomomentus.com", "Momentus Technologies venue management", "Momentus venue management reviews", and "Ungerboeck rebrand Momentus". This is an extreme external-signal vacuum. The DNS TXT records reveal integrations with HubSpot, Zendesk, Qualtrics, Pendo, 1Password, Atlassian, DocuSign, Microsoft 365, and Anthropic (an anthropic-domain-verification TXT record is present). The site links to a trustcenter.gomomentus.com subdomain. The blog posts show dates like "June 22-24, 2025" as location markers — a templating artifact that suggests content may be using placeholder or syndicated date fields.

Findings

1. LLM cold knowledge describes pre-2023 product, not current platform High

   LLMs describe Momentus as a performing-arts ticketing and fundraising platform (pre-2023 Ungerboeck era), while the site sells an enterprise venue management platform for stadiums, convention centers, and universities with AI-powered operations. The rebrand from Ungerboeck in January 2023 and acquisitions are not reflected in AI knowledge.

   What to change: Publish an llms.txt file with a summary of the current product line, rebranding history, and key customer references. Submit updated business information to major AI knowledge bases and data aggregators.

2. Domain has zero external search citations High

   DuckDuckGo returned zero results for searches including 'gomomentus.com', 'Momentus Technologies venue management', and 'Momentus venue management reviews'. The domain has minimal external citation footprint, which limits AI model training signals and reduces visibility in AI-generated answers.

   What to change: Build a backlink strategy through PR, industry partnerships, and content syndication. Encourage customer reviews on G2, Capterra, and TrustRadius. Ensure the site is indexed by Google and Bing.

3. Organization schema has contradictory founding dates Medium

   The homepage Organization schema lists foundingDate as 2025, while the about page lists 1985. This contradiction can confuse AI parsers and reduce trust in structured data.

   What to change: Reconcile the founding date across all pages. Use the actual founding year of the original company (1985) or the rebrand date (2023) consistently.

4. No llms.txt file published Medium

   The site returns a 404 for /llms.txt. An llms.txt file would help AI crawlers understand the site's content and provide accurate summaries, especially given the cold-knowledge gap.

   What to change: Create an llms.txt file that describes the company, product lines, key pages, and rebranding history.

5. sameAs links use generic social media handles Low

   The Organization schema's sameAs links point to linkedin.com/company/momentus and twitter.com/momentus, which may not resolve to the correct company pages. This can reduce the credibility of the schema.

   What to change: Verify that the social media URLs in the schema resolve to the official Momentus pages. Update if necessary.

6. Blog posts show placeholder date formatting Low

   Blog posts display dates like 'June 22-24, 2025' as location markers, suggesting a templating artifact. This may confuse AI parsers and reduce content freshness signals.

   What to change: Ensure blog post dates are displayed as single dates and use proper date formatting in the visible text and schema markup.

What's working

• All major AI crawlers receive full 200 responses — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, and Applebot-Extended all receive the same content as browser traffic. No AI-bot-specific blocks in robots.txt.
• Homepage and about page carry rich JSON-LD schemas — Organization, WebSite, and BreadcrumbList schemas are present with detailed information including leadership, customer references, and product offers. Ticketing page adds Product and FAQPage schemas.
• Key pages have substantial visible text content — The homepage has ~3,300 words, about page ~2,200 words, pricing page ~5,500 words, and AI page ~2,300 words. This provides rich content for AI crawlers to index.
• Pages render fully on plain GET without JavaScript — All fetched pages return complete HTML content without requiring JavaScript execution. This ensures AI crawlers can index the content without rendering issues.
• Sitemap is accessible and contains 80 URLs — The sitemap returns 200 with 80 URLs, helping crawlers discover all pages. No index sitemap is present, but the single sitemap covers the site.
• Blog and content hub provide ongoing content — The site has a blog and a content hub with multiple articles, including a 'State of AI in Venue & Event Management' report. This supports freshness and topical authority.
• Customer stories page with named references — The customer stories page lists notable clients like SoFi Stadium, Google, ExCeL London, Apollo Theater, and Harvard, providing social proof that can be used in AI training data.