workaterie.com — AI Site Grade

Analysis

The careers site for Erie Home (workaterie.com) has full AI-crawler access and rich schema, but the LLM's cold knowledge of the parent brand is dominated by negative reputational signals — lawsuits, a D- BBB rating, and aggressive-sales complaints — that the careers site never acknowledges.

Crawler Access

All major AI bots — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai — receive a full 200 response with the same 216KB payload as a browser. Bytespider is the sole exception, returning a 403 from Cloudflare. The robots.txt contains no AI-bot-specific rules; it only disallows a single WP-Optimize plugin file. llms.txt returns a 404. The site runs on Cloudflare (CDN) with WP Engine hosting and nginx, behind a WordPress/Yoast SEO stack. No JS-rendering risk: the homepage delivers ~2,100 words of visible text on a plain GET.

Cold-Knowledge Gap

The LLM knows nothing about "workaterie" as a brand. Asked about Erie Home (the parent company), it describes a residential roofing/siding/windows company with "multiple lawsuits," "BBB D- rating," "aggressive sales tactics," "consumer alerts from state attorneys general," and "questioned warranty enforcement." The careers site presents Erie Home as a supportive, high-growth employer with "exceptional advancement and earning potential," "great work/life balance," and "one of the highest industry ratings on Glassdoor and Indeed." The site never mentions the parent company's consumer-facing reputation, lawsuits, or BBB standing — a gap that means any AI engine retrieving the careers site alongside general knowledge about Erie Home will surface a stark contradiction.

Schema Posture

The site uses WebPage, WebSite, Organization, and BreadcrumbList JSON-LD consistently across all pages. The Organization schema includes sameAs links to Facebook and LinkedIn but no JobPosting schema on the positions page — a notable omission for a careers site. The positions page (/positions/) contains only 15 words of visible text and a Paylocity external application link; actual job listings live on a JS-dependent Paylocity subdomain that returns a blank shell to plain HTTP fetches. The /areas-served/ page is a dead archive with "No Entries."

External Signals

The parent domain eriehome.com links to workaterie.com in its footer and carries richer schema (HomeAndConstructionBusiness, Place with GeoCoordinates, OpeningHours). The BBB link on eriehome.com points to a profile for "Erie Construction Mid-West, LLC." The careers site's Facebook and LinkedIn pages use different handles (eriehomecareers vs eriehome) than the parent company's social profiles, creating fragmented citation signals. The site has only 10 indexed URLs total — a tiny footprint for a company claiming 60+ locations across the US.

Findings

1. LLM cold knowledge of parent brand Erie Home is dominated by negative reputational signals High

   The LLM's prior knowledge about Erie Home includes multiple lawsuits, a D- BBB rating, aggressive sales tactics, consumer alerts, and questioned warranty enforcement. The careers site presents a positive employer image but never acknowledges these reputational issues, creating a stark contradiction for AI engines that retrieve both sources.

   What to change: Add a section on the careers site that addresses the parent company's reputation transparently, such as a 'Our Commitment to Customers' page that acknowledges past issues and outlines improvements.

2. No JobPosting schema on positions page Medium

   The /positions/ page lacks JobPosting structured data, which is a notable omission for a careers site. This reduces the likelihood of job listings appearing in AI-generated job search results.

   What to change: Add JobPosting JSON-LD schema to the /positions/ page for each job listing, including title, description, location, and application URL.

3. Job listings on Paylocity subdomain are JS-dependent and invisible to crawlers High

   Actual job listings are hosted on a Paylocity subdomain that returns a blank shell to plain HTTP fetches. AI crawlers that do not execute JavaScript cannot see job details, limiting visibility.

   What to change: Ensure job listings are server-side rendered or provide a static HTML fallback for crawlers. Alternatively, embed job details directly on workaterie.com with links to Paylocity for application.

4. llms.txt file returns 404 Low

   The site does not provide an llms.txt file, which is a recommended way to guide AI crawlers to key content. This is a missed opportunity to improve AI visibility.

   What to change: Create an llms.txt file that lists important pages like /positions/, /about/, /benefits/, and /contact/.

5. Areas served page is a dead archive with no entries Low

   The /areas-served/ page contains only 12 words and displays 'No Entries', providing no value to users or crawlers. This wastes crawl budget and may confuse AI agents.

   What to change: Remove the page or populate it with a list of locations served, including city and state names.

6. Only 10 URLs indexed, tiny footprint for a national company Medium

   The site has only 10 indexed URLs, which is very small for a company claiming 60+ locations. This limits the site's visibility in search and AI results.

   What to change: Create location-specific pages for each of the 60+ locations, each with unique content and local schema markup.

7. Social media profiles use different handles than parent company Low

   The careers site's Facebook and LinkedIn pages use handles like 'eriehomecareers' while the parent company uses 'eriehome', creating fragmented citation signals. This may dilute the brand's authority in AI knowledge graphs.

   What to change: Align social media handles across the careers site and parent company, or ensure consistent cross-linking in schema sameAs fields.

8. Bytespider bot is blocked by Cloudflare Low

   Bytespider (ByteDance's crawler) receives a 403 error, preventing it from indexing the site. This limits visibility on TikTok search and other ByteDance products.

   What to change: Allow Bytespider access by adjusting Cloudflare WAF rules or robots.txt.

What's working

• All major AI bots receive full 200 response with rich content — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, and anthropic-ai all get the same 216KB HTML payload as a browser, with no JS-rendering issues. The homepage delivers ~2,100 words of visible text.
• WebPage, WebSite, Organization, and BreadcrumbList JSON-LD present on all pages — The site uses consistent structured data across all pages, including Organization schema with sameAs links to Facebook and LinkedIn. This helps AI agents understand the site's structure and entity relationships.
• Parent domain eriehome.com links to workaterie.com in footer — The parent company's website includes a link to the careers site in its footer, providing a strong internal backlink and reinforcing the brand connection for crawlers.
• Parent domain eriehome.com has rich schema with HomeAndConstructionBusiness and Place — Eriehome.com uses HomeAndConstructionBusiness, Place with GeoCoordinates, and OpeningHours schema, which strengthens the overall brand entity in knowledge graphs.
• Robots.txt does not block any AI bots — The robots.txt file contains no AI-bot-specific disallow rules, ensuring all major crawlers can access the entire site.
• Sitemap is present and indexed with 10 URLs — The sitemap_index.xml is accessible and contains 10 URLs, helping crawlers discover all pages.