adamsknight.com — AI Site Grade

Analysis

I have enough data now. Let me compile the audit.

The domain name is a person's name but the brand is an agency — and AI models know nothing about it

The domain adamsknight.com hosts Adams & Knight, an integrated marketing agency founded in 1988 in Connecticut, but a frontier LLM queried cold on "Adam Knight" returned zero recognition — no awareness of the agency, its founders, its awards, or its client work. This is the central gap: the brand is entirely invisible to AI knowledge bases despite having a live, content-rich site.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Applebot-Extended, Bytespider, ChatGPT-User — receive a 200 with full HTML content (55KB, identical to browser baseline). The sole exception is anthropic-ai (the training crawler), which gets a 403 blocked by AWS ELB. The robots.txt is a generic template with no AI-bot directives whatsoever — no GPTBot, no ClaudeBot, no PerplexityBot rules exist. The llms.txt returns a 404. The sitemap lives at a nonstandard path (/stmap.xml.php) and is referenced in robots.txt, but the standard /sitemap.xml 404s.

Cold-Knowledge Gap

The LLM queried on "Adam Knight" returned: *"I do not have specific, verifiable information about an individual named Adam Knight... no notable products, services, or companies are associated with a prominent 'Adam Knight' in my training data."* The site itself is a full-service agency with Jill Adams (Principal/CEO) and Bill Knight (Principal/CMO) — 17 named leaders, clients including Hartford HealthCare and Connecticut Children's, and awards from PRWeek, HSMAI Adrian Awards, Telly Awards, and Effie Awards. None of this exists in the model's prior. The domain name (a person's name) actively misdirects AI engines away from the actual brand entity.

Schema Posture

Every page carries only a single WebSite schema with SearchAction — no Organization, LocalBusiness, Person, Article, FAQPage, BreadcrumbList (except the /people page which adds one), or CreativeWork schema. The agency's founding year (1988), location (Connecticut), leadership, awards, and client portfolio are all absent from structured data. The /people page lists 17 leaders with names and titles but no Person schema markup.

Content & Technical Signals

The homepage has 713 words of visible text with a clear H1 ("sparking results") and H2s covering awards, capabilities, and news. The blog has 10 posts with named authors and recent content (AI in healthcare, programmatic media). However, the /about page redirects to the homepage — there is no dedicated about page. The /awards page is a thin 164-word shell with no actual award list. Multiple pages use http://www.adamsknight.com as canonical while the site serves on https://adamsknight.com, creating a mixed-protocol canonical mismatch. The site runs on Apache behind AWS CloudFront with a notably permissive CSP (default-src * 'unsafe-inline' 'unsafe-eval').

Findings

1. Zero LLM recognition for Adams & Knight agency High

   A frontier LLM queried on 'Adam Knight' returned no awareness of the agency, its founders, awards, or client work. The brand is entirely absent from AI knowledge bases despite a content-rich site.

   What to change: Publish an llms.txt file with a brand summary and key entity details. Submit the agency to authoritative directories (e.g., Wikipedia, Crunchbase) to seed AI training data.

2. No Organization or LocalBusiness schema on any page High

   Every page carries only a WebSite schema with SearchAction. The agency's founding year, location, leadership, awards, and client portfolio are absent from structured data.

   What to change: Add Organization schema with name, founding date, location, and sameAs URLs to the homepage. Add Person schema to each leader on the /people page.

3. Domain name misdirects AI from brand entity High

   The domain 'adamsknight.com' is a person's name, but the brand is an agency. AI models queried on 'Adam Knight' find no connection to the agency, and the domain does not signal the actual business entity.

   What to change: Add Organization schema with brand name 'Adams & Knight' and sameAs profiles. Consider a separate domain or subdomain for the agency name if feasible.

4. llms.txt returns 404 Medium

   The standard llms.txt file is missing, which is a recommended signal for AI crawlers to understand site content and entity relationships.

   What to change: Create an llms.txt file with a summary of the agency, key pages, and entity descriptions.

5. Sitemap at nonstandard path, standard sitemap 404s Medium

   The sitemap is at /stmap.xml.php, but the standard /sitemap.xml returns 404. This may confuse crawlers expecting the conventional location.

   What to change: Serve a sitemap at /sitemap.xml (or redirect /stmap.xml.php to it) and ensure it lists all important pages.

6. robots.txt lacks AI crawler directives Medium

   The robots.txt is a generic template with no rules for GPTBot, ClaudeBot, PerplexityBot, or other AI crawlers. While most AI bots are allowed by default, the absence of explicit directives leaves policy ambiguous.

   What to change: Add explicit Allow or Disallow rules for major AI crawlers (GPTBot, ClaudeBot, etc.) to clarify crawling intent.

7. Anthropic training crawler blocked by 403 Medium

   The anthropic-ai crawler receives a 403 error from AWS ELB, preventing Claude's training crawler from accessing the site.

   What to change: Allow anthropic-ai in robots.txt and ensure the server does not block its user-agent.

8. People page lacks Person schema for leaders Medium

   The /people page lists 17 leaders with names and titles but no Person schema markup, missing an opportunity to establish entity recognition.

   What to change: Add Person schema with name, jobTitle, and url for each leader on the /people page.

9. Canonical URLs use http while site serves https Medium

   Multiple pages specify http://www.adamsknight.com as canonical, but the site serves on https://adamsknight.com, creating a mixed-protocol mismatch that can confuse crawlers.

   What to change: Update canonical URLs to use https://adamsknight.com consistently.

10. About page redirects to homepage Medium

    The /about page redirects to the homepage, meaning there is no dedicated about page with agency history, mission, or team information.

    What to change: Create a standalone about page with agency history, leadership, and mission, and include Organization schema.

11. Awards page is thin with no award details Low

    The /awards page contains only 164 words and no actual list of awards, missing a chance to showcase credibility and earn citations.

    What to change: Expand the awards page with a list of awards, years, and linking organizations, and add CreativeWork schema.

12. Permissive Content Security Policy Low

    The CSP header uses default-src * 'unsafe-inline' 'unsafe-eval', which is overly permissive and could pose security risks, though it does not directly impact AI visibility.

    What to change: Restrict the CSP to specific sources and remove unsafe-inline and unsafe-eval where possible.

What's working

• All major AI crawlers receive 200 with full HTML — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others get full HTML content (55KB), ensuring the site's text is accessible to AI crawlers.
• Homepage has 713 words of visible text with clear H1 and H2s — The homepage provides substantial content about the agency's capabilities, awards, and news, which helps crawlers understand the site's focus.
• Blog has 10 posts with named authors and recent content — The marketing blog includes recent articles on AI in healthcare and programmatic media, demonstrating topical authority and fresh content.
• People page lists 17 leaders with names and titles — The /people page provides a clear list of leadership, which is useful for entity recognition even without Person schema.
• Healthcare case studies page exists with client work — The /healthcare-casestudies page showcases client work (e.g., Spark Health), providing evidence of expertise and real-world results.
• Integrated marketing services page with detailed offerings — The /integrated-marketing-services page describes the agency's service areas, helping crawlers understand the business scope.
• Agency culture page with team values — The /agency-culture page provides insight into the company's values and work environment, adding depth to the brand narrative.
• Sitemap exists at /stmap.xml.php with 357 words — Although nonstandard, a sitemap is present and contains content, aiding crawler discovery of pages.