hinge.co — AI Site Grade

Analysis

Hinge's AI-visibility posture is technically excellent but structurally shallow — all bots get full access to a Next.js site on Vercel, yet the site offers AI crawlers almost nothing beyond a bare Organization schema and a missing llms.txt.

Crawler Access

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, anthropic-ai — receives a 200 with identical byte payload (94,479 bytes) as a browser visit. No UA-based blocking, no Cloudflare challenge, no JS shell. The site runs on Vercel with a strict CSP and HSTS preload. The robots.txt is minimal (51 bytes): it only disallows /api/ and /download/ for all UAs, with zero AI-bot-specific rules. The llms.txt returns a 404 — no AI-friendly content map exists.

Schema Posture

Every page on the site carries the same thin Organization schema: {"@type": "Organization", "url": "https://hinge.co"}. No WebSite, FAQPage, Article, BreadcrumbList, Product, or SoftwareApplication schema exists anywhere. The newsroom has 84+ press releases and blog articles with rich Q&A content (e.g., the AI Dating Guide uses a natural FAQ structure), but none are marked up as FAQPage or Article. The homepage mentions a "Nobel-Prize-winning algorithm" — a distinctive factual claim — but no schema surfaces it.

Cold-Knowledge Gap

The LLM prior on Hinge is surprisingly accurate and current: it knows the "designed to be deleted" tagline, the Match Group acquisition (2018/2019), the prompt-based profile system, and even recent criticism about subscription costs and algorithm transparency. The site itself, however, does not address the pricing criticism or algorithm-transparency concerns directly on any fetched page — the how-we-connect-daters page explains the recommendation system but does not mention subscription cost complaints. The cold model also knows about "Roses" (premium likes) and "We Met" feedback, but the site's content is entirely corporate/brand — it does not explain these features in a way an AI crawler could easily extract as structured data.

Canonical Bug

The /ai-principles page declares a broken canonical URL: https://hinge.coinciples (missing the slash between .co and inciples). This is a technical error that undermines the page's indexing authority for a page about a topic (AI principles) that AI engines are increasingly likely to cite.

Content Depth vs. Crawlability

The site has strong editorial content — the newsroom contains 80+ articles with substantive text (833 words on the NFAQ piece, 767 on the AI Dating Guide, 1,034 on how the recommendation system works). However, the /blog page renders as a thin JS shell (~11 words of visible text) with no server-rendered article list, meaning AI crawlers see almost nothing there. The actual articles are at /newsroom/* paths and are server-rendered with full text, but they lack any article-level schema markup. The site also has no sitemap entry for localized pages beyond the root — the 20+ locale variants (/fr-fr/, /de-de/, etc.) are in the sitemap but their content is identical to the English version, creating a large crawl surface with no unique value.

Findings

1. llms.txt returns 404, no AI-friendly content map Medium

   The site does not provide an llms.txt file, which AI crawlers use to discover key content. This limits the ability of AI models to efficiently find and cite Hinge's resources.

   What to change: Create an llms.txt file listing key pages such as the mission, AI principles, newsroom, and how-we-connect-daters.

2. All pages carry only a bare Organization schema High

   Every page on the site includes the same minimal Organization schema with just a URL. No WebSite, FAQPage, Article, BreadcrumbList, or other schema types are used, missing opportunities to provide rich context to AI crawlers.

   What to change: Add relevant schema types (e.g., FAQPage for Q&A content, Article for newsroom posts, WebSite for the homepage) to provide structured data that AI models can parse.

3. Broken canonical URL on /ai-principles page High

   The /ai-principles page declares a canonical URL of 'https://hinge.coinciples' (missing a slash), which is a technical error that undermines indexing authority for a page about AI principles.

   What to change: Correct the canonical URL to 'https://hinge.co/ai-principles'.

4. Blog page renders as thin JS shell for crawlers Medium

   The /blog page contains only 11 words of visible text and appears to be a JavaScript shell, meaning AI crawlers see almost no content there. Actual articles are at /newsroom/* paths but are not linked in a crawlable way from /blog.

   What to change: Server-render the blog listing or add static links to newsroom articles so crawlers can discover them.

5. Newsroom articles lack Article schema markup High

   The newsroom contains substantive articles (e.g., AI Dating Guide, NFAQ) but none have Article or FAQPage schema. This prevents AI crawlers from understanding the content structure and surfacing it in rich results.

   What to change: Add Article schema to newsroom posts and FAQPage schema to Q&A content like the AI Dating Guide.

6. FAQ-style content not marked up as FAQPage Medium

   The AI Dating Guide uses a natural FAQ structure (questions and answers) but lacks FAQPage schema, missing an opportunity to appear in AI-generated answers and rich snippets.

   What to change: Add FAQPage schema to the AI Dating Guide and similar Q&A pages.

7. No SoftwareApplication schema for the dating app Low

   The site does not use SoftwareApplication schema to describe the Hinge app, which could help AI models understand the product and its features.

   What to change: Add SoftwareApplication schema to the homepage or a dedicated product page.

8. Pricing criticism not addressed on site Medium

   The cold LLM prior knows about subscription cost complaints, but the site does not address pricing or algorithm transparency on any fetched page, missing a chance to control the narrative in AI-generated summaries.

   What to change: Add a page or section explaining pricing and subscription value, and link to it from relevant pages.

9. Localized pages have identical content to English Low

   The sitemap includes 20+ locale variants (e.g., /fr-fr/, /de-de/) but their content is identical to the English version, creating a large crawl surface with no unique value and potentially diluting indexing authority.

   What to change: Either localize the content properly or remove duplicate locale pages from the sitemap.

10. No BreadcrumbList schema on any page Low

    The site does not use BreadcrumbList schema, which helps AI crawlers understand site hierarchy and can improve search result display.

    What to change: Add BreadcrumbList schema to pages with clear navigation paths.

What's working

• All major AI crawlers receive full access with no blocking — Every tested AI crawler (GPTBot, ClaudeBot, etc.) receives a 200 response with the same content as a browser visit. No UA-based blocking, Cloudflare challenges, or JS shells are encountered.
• Robots.txt is minimal and does not block AI bots — The robots.txt file is only 51 bytes and only disallows /api/ and /download/ for all UAs, with no AI-bot-specific rules. This ensures AI crawlers can access all public content.
• Newsroom articles are server-rendered with full text — Articles at /newsroom/* paths are server-rendered with substantial text (e.g., 833 words on NFAQ, 767 on AI Dating Guide), making them fully crawlable by AI bots.
• Cold LLM knowledge about Hinge is accurate and current — The LLM prior correctly knows Hinge's tagline, Match Group acquisition, prompt-based profiles, and recent criticism, indicating strong brand recognition and consistent external signals.
• Dedicated AI Principles page with substantive content — The /ai-principles page contains 688 words explaining Hinge's approach to AI, which is valuable for AI crawlers seeking to understand the company's stance on AI ethics.
• Trust & Safety page with detailed policies — The /trustandsafety page contains 566 words covering safety policies, which helps AI models understand Hinge's commitment to user safety.
• Detailed explanation of recommendation system — The /how-we-connect-daters page provides 1,034 words explaining how the matching algorithm works, offering transparency that AI crawlers can use to answer user questions.
• Sitemap includes 80 URLs covering key pages — The sitemap lists 80 URLs, including important pages like /ai-principles, /newsroom, and /how-we-connect-daters, helping crawlers discover content.