joinblvd.com — AI Site Grade

Analysis

I have all the data I need. Here's the audit.

Boulevard (joinblvd.com) — AI-Visibility Audit

The cold LLM has zero knowledge of Boulevard — it cannot confirm the brand's existence, products, or reputation — despite the company having raised $150M in venture funding, powering 40,000+ professionals, and processing nearly $5B in annual payments.

Crawler Access

All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended, anthropic-ai) receive a 200 status with identical byte payloads to browser traffic on the homepage. No UA-based blocking exists. However, the robots.txt is a single-line catch-all (User-agent: * Disallow: /api/) with no AI-bot-specific rules — no GPTBot, no ClaudeBot, no PerplexityBot directives at all. The site runs on Next.js behind AWS CloudFront (no WAF detected, no security headers like HSTS or CSP). The llms.txt exists and is well-structured, containing company description, mission, positioning, contributor bios, testimonials, integration lists, and review links — a strong signal for AI consumption.

Content & Schema

The homepage has a single Organization JSON-LD schema with brand name, address, social profiles, and contact info — but no SoftwareApplication schema, no Product schema, no FAQPage schema, and no BreadcrumbList. The pricing page, which contains a detailed FAQ section with 10+ questions, has zero schema markup — no FAQPage markup despite clear Q&A content. Several key pages (/about, /features/boulevard-ai, /features/scheduling, /why-boulevard) return fewer than 50 words of visible text from a plain GET, indicating heavy client-side rendering. The blog page lists article titles but the actual article URLs (e.g., the "Great Hair, Bad Vibes" post) return 404, suggesting broken or restructured blog paths.

Cold-Knowledge Gap

The LLM knows nothing about Boulevard cold. The site presents itself as "the fastest-growing client experience platform" for self-care businesses, with $80M Series D (July 2025), 40,000+ professionals, 5,000+ businesses, and 2M+ monthly bookings. The newsroom contains press releases about Deloitte Fast 500, Inc. 5000, and FinTech Breakthrough Awards. None of this institutional credibility surfaces in the model's prior. The gap is total: the model cannot even confirm the brand exists.

External Signals

External review platforms (Capterra, G2, Software Advice) are linked from the homepage footer and llms.txt, but a web search for "Boulevard joinblvd salon software reviews" returned zero results — the brand has minimal organic search footprint outside its own domain. The llms.txt links to third-party comparison pages (Vagaro vs Boulevard, Mangomint vs Boulevard, Mindbody vs Boulevard) on thedigitalmerchant.com, which is a useful external citation source for AI engines. DNS records show Google Workspace (MX), Pardot (marketing automation), and Mailgun (transactional email) — a standard SaaS stack.

Surprising Findings

The blog article URLs listed on /blog resolve to 404 pages — the site displays article titles and excerpts but the actual content paths are broken. The /about page contains only 4 words of visible text ("Meet Boulevard watch video") — a JS-rendered shell with no substantive content for crawlers. The canonical on the 404 page points to a bizarre URL (/b/safelysunningsakredsalon/widget#/visit-type), suggesting a misconfigured fallback. Boulevard has a well-maintained llms.txt but the actual site content that AI crawlers would use to answer questions about the brand is thin or broken on most subpages.

Findings

1. Cold LLM has zero knowledge of Boulevard despite $150M funding High

   The LLM cannot confirm Boulevard's existence, products, or reputation. The brand has raised $150M, powers 40,000+ professionals, and processes nearly $5B in annual payments, yet none of this surfaces in the model's prior.

   What to change: Increase off-site citations on high-authority domains (e.g., Crunchbase, Wikipedia, major tech publications) and ensure structured data (SoftwareApplication, Product) is present on all relevant pages.

2. Key subpages render as thin JS shells with minimal visible text High

   Pages like /about (4 words), /features/boulevard-ai (32 words), /features/scheduling (44 words), and /why-boulevard (28 words) return very little visible text from a plain GET, indicating heavy client-side rendering that may not be fully indexed by AI crawlers.

   What to change: Add server-side rendered content or static HTML fallbacks for key subpages to ensure AI crawlers can extract meaningful text.

3. Blog article URLs listed on /blog return 404 errors High

   The blog page lists article titles and excerpts, but the actual content URLs (e.g., /blog/online-booking/great-hair-bad-vibes-why-71-of-clients-say-technical-skill-isnt-enough) return 404 pages, indicating broken or restructured blog paths.

   What to change: Fix broken blog URLs by restoring content or implementing proper redirects to the correct paths.

4. Pricing page FAQ section lacks FAQPage schema markup Medium

   The pricing page contains a detailed FAQ section with 10+ questions, but no FAQPage schema is present, missing an opportunity for rich results in AI and search engines.

   What to change: Add FAQPage structured data to the FAQ section on the pricing page.

5. No SoftwareApplication or Product schema on the site Medium

   The homepage has only Organization schema. There is no SoftwareApplication schema (which would help AI understand the product) and no Product schema for the software offering.

   What to change: Add SoftwareApplication schema to the homepage and product pages, and consider Product schema for pricing tiers.

6. robots.txt has no AI-bot-specific directives Low

   The robots.txt is a single catch-all rule (Disallow: /api/) with no explicit rules for GPTBot, ClaudeBot, PerplexityBot, or other AI crawlers. While not blocking them, the lack of explicit allowance may cause some crawlers to be cautious.

   What to change: Add explicit Allow directives for AI crawlers (e.g., User-agent: GPTBot Allow: /) to ensure they crawl the site without hesitation.

7. Minimal organic search footprint outside own domain Medium

   A web search for 'Boulevard joinblvd salon software reviews' returned zero results, indicating the brand has very little presence on third-party review sites or forums that AI crawlers might index.

   What to change: Encourage customers to leave reviews on high-authority platforms (Capterra, G2) and engage in industry forums to build external citations.

8. 404 page has misconfigured canonical URL Low

   The 404 page's canonical URL points to a bizarre path (/b/safelysunningsakredsalon/widget#/visit-type), suggesting a misconfigured fallback that could confuse crawlers.

   What to change: Fix the 404 page to either omit the canonical tag or point it to the homepage.

What's working

• Well-maintained llms.txt with company info and external links — The llms.txt is 7283 bytes and contains company description, mission, positioning, contributor bios, testimonials, integration lists, and review links, providing a strong signal for AI consumption.
• All major AI crawlers receive 200 status with full content — All 11 tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive a 200 status with identical byte payloads to browser traffic on the homepage, with no UA-based blocking.
• Homepage has valid Organization JSON-LD schema — The homepage includes a single Organization schema with brand name, address, social profiles, and contact info, providing basic entity recognition for AI.
• Newsroom contains detailed press releases about funding and awards — The newsroom has press releases about $80M Series D, $70M Series C, Deloitte Fast 500, Inc. 5000, and FinTech Breakthrough Awards, providing authoritative content for AI to cite.
• llms.txt links to third-party comparison pages — The llms.txt includes links to comparison pages (Vagaro vs Boulevard, etc.) on thedigitalmerchant.com, providing external citations that AI can use to validate the brand.
• Standard SaaS infrastructure with Google Workspace and Pardot — DNS records show Google Workspace, Pardot, and Mailgun, indicating a professional email and marketing automation setup that supports credibility.