empowerpharmacy.com — AI Site Grade

Analysis

Empower Pharmacy: Full AI Crawler Access, No AI Content Map

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receives a 200 with full HTML content identical to browser delivery. The site runs on nginx behind AWS CloudFront with strong security headers (HSTS, X-Frame-Options DENY, CSP), but no bot is blocked, throttled, or served a JS shell. This is the cleanest crawler-access posture observed across any compounding pharmacy domain.

Crawler Access

The robots.txt is a bare Yoast default: User-agent: * Disallow: with no AI-bot-specific rules whatsoever. The llms.txt returns a 404 (WordPress 404 page). The sitemap lives at /sitemap_index.xml (three sub-sitemaps: 114 posts, 113 pages, 200+ products), but the canonical /sitemap.xml path also 404s. DNS records confirm the site has both openai-domain-verification and anthropic-domain-verification TXT records — the brand proactively registered with both AI vendors — yet provides no structured AI content map for them to consume.

Cold-Knowledge Gap

The LLM prior knows Empower as a "Houston-based 503A compounding pharmacy" focused on BHRT, pain management, and dermatology, serving functional medicine and anti-aging clinics. The actual site positions itself far more broadly: a dual 503A/503B operation with $55M+ purpose-built facilities, PCAB accreditation, LegitScript certification, nationwide shipping including Puerto Rico, and a heavy emphasis on GLP-1 agonists (semaglutide, tirzepatide) as trending products. The cold knowledge entirely misses the 503B outsourcing facility, the GLP-1 weight management focus, the GHK-Cu peptide push, and the uniformed-services discount program. The site's scale narrative ("North America's largest compounding facility") is absent from the model's prior.

Schema Posture

JSON-LD is present and well-structured via Yoast: Organization, WebSite, WebPage, BreadcrumbList, Article on blog posts, and Product on individual drug pages. The Product schema on drug pages is thin — it includes name, description, brand, and url but lacks sku, offers (price), manufacturer, or identifier fields. The FAQ page has no FAQPage schema despite containing 6,000+ words of Q&A content. The homepage has no LocalBusiness or Pharmacy schema, which is a missed signal for local and healthcare-specific search.

External Signals

The brand has a Google review solicitation link embedded site-wide, an API documentation portal at api-docs.empowerpharmacy.com, and a careers subdomain. Web search returned zero indexed external press or Reddit mentions for the brand — a striking vacuum that means AI engines have almost no third-party citation mass to draw from when describing Empower. The site's own knowledge center (114 articles) and press mentions (CEO awards, industry features) are the only narrative fuel available.

Findings

1. No llms.txt file for AI content discovery Medium

   The site returns a 404 for /llms.txt, providing no structured content map for AI crawlers despite having registered domain verification with OpenAI and Anthropic.

   What to change: Create an llms.txt file listing key pages (compounding pharmacy, GLP-1 medications, about, knowledge center) to guide AI crawlers to the most important content.

2. Cold knowledge misses 503B facility and GLP-1 focus High

   LLM prior knowledge only knows Empower as a 503A compounding pharmacy for BHRT and pain management, but the site is a dual 503A/503B operation with a major GLP-1 weight management program, PCAB accreditation, and nationwide shipping. This gap means AI answers will underrepresent the brand's full scope.

   What to change: Publish authoritative content (press releases, industry articles, schema markup) that explicitly states the 503B outsourcing facility, GLP-1 offerings, and facility scale to update the LLM knowledge base.

3. Product schema lacks key fields like SKU and offers Medium

   Drug pages have Product schema but omit sku, offers (price), manufacturer, and identifier fields, reducing the richness of structured data for AI crawlers and search engines.

   What to change: Add sku, offers (with price), manufacturer, and identifier (e.g., NDC) to Product schema on all drug pages.

4. FAQ page lacks FAQPage schema Medium

   The FAQ page contains over 6,000 words of Q&A content but has no FAQPage structured data, missing an opportunity for rich results and direct AI extraction.

   What to change: Add FAQPage schema markup to the FAQ page, wrapping each question-answer pair in a Question/Answer node.

5. Homepage missing LocalBusiness or Pharmacy schema Low

   The homepage has Organization schema but no LocalBusiness or Pharmacy subtype, which would help local and healthcare-specific search visibility.

   What to change: Add LocalBusiness schema with Pharmacy subtype on the homepage, including address, phone, and opening hours.

6. No indexed external press or Reddit mentions High

   Web searches for the brand returned zero results from external press, reviews, or Reddit, meaning AI engines have almost no third-party citation mass to draw from when describing Empower.

   What to change: Proactively build external citations through press releases, industry awards, guest posts, and Reddit engagement to create a third-party signal footprint.

7. Robots.txt has no AI-bot-specific rules Low

   The robots.txt is a bare Yoast default with no rules for AI crawlers like GPTBot or ClaudeBot, leaving them unrestricted but also unguided.

   What to change: Add specific directives for AI crawlers to prioritize key pages (e.g., Allow: /compounding-pharmacy/, Allow: /about/).

8. Canonical sitemap path returns 404 Low

   The sitemap is available at /sitemap_index.xml but the canonical /sitemap.xml path returns a 404, which may confuse some crawlers.

   What to change: Redirect /sitemap.xml to /sitemap_index.xml or serve the sitemap at the canonical path.

What's working

• All major AI crawlers receive full HTML content — Every tested AI bot (GPTBot, ClaudeBot, PerplexityBot, etc.) gets a 200 with complete HTML, identical to browser delivery. No bot is blocked, throttled, or served a JS shell.
• Domain verification TXT records for OpenAI and Anthropic — DNS records include openai-domain-verification and anthropic-domain-verification TXT records, indicating proactive registration with both AI vendors.
• Well-organized sitemap with three sub-sitemaps — The sitemap index at /sitemap_index.xml contains three sub-sitemaps (posts, pages, products) covering 300+ URLs, providing good crawl coverage.
• JSON-LD schema implemented via Yoast — The site uses Yoast to output JSON-LD for Organization, WebSite, WebPage, BreadcrumbList, Article, and Product, providing a solid structured data foundation.
• Knowledge center with 114 articles — The site has a knowledge center with 114 articles covering compounding pharmacy topics, providing substantial content for AI crawlers to index.
• Strong security headers (HSTS, CSP, X-Frame-Options) — The site returns HSTS, Content-Security-Policy, and X-Frame-Options DENY headers, indicating good security posture without blocking crawlers.