teamdigiworks.com — AI Site Grade

Analysis

The site's AI crawler access is fully open, yet the brand is entirely invisible to both search engines and LLM cold knowledge — a contradiction that points to a site with no external footprint whatsoever.

Crawler Access

Every major AI crawler — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended — receives a full 200 response with the same 445KB payload as a browser. Only Bytespider (ByteDance/TikTok) gets a 403 from Cloudflare. The robots.txt contains no AI-bot-specific rules at all, using only a generic User-agent: * with standard WordPress admin exclusions. No llms.txt exists (404). The site runs on WP Engine behind Cloudflare with HSTS, and the homepage is fully server-rendered HTML with 749 words of visible text — no JS-rendering risk for AI crawlers.

Cold-Knowledge Gap

Asked cold, a frontier LLM describes "Team Digiworks" as a digital agency building CMS and e-commerce platforms for SMBs — a description that matches nothing on the actual site. The real DigiWorks is a remote talent marketplace focused on South Africa, the Philippines, and Nigeria, offering virtual assistants, bookkeepers, engineers, and AI developers. The LLM knows nothing about the founders Monica and Rolphy, the "Hire. Delegate. Scale." positioning, the one-week risk-free trial, or the platform's focus on emerging-country talent. The gap is total: the model's prior is a different company entirely.

Schema Posture

The homepage carries a well-structured ProfessionalService schema with address (1201 Pennsylvania Ave NW, Washington DC), phone (+447418626795), email, social profiles (LinkedIn, Instagram, X), area served (US, UK, Canada, Australia), and keywords spanning AI development and remote hiring. However, the phone country code (+44 UK) contradicts the Washington DC address. The schema lists two unverifiable awards ("Top Global Remote Talent Platform", "Trusted AI & Software Development Company"). Blog posts carry BlogPosting and Article schemas with author and date. The Organization schema is duplicated across every page via the site-wide @graph block.

External Signals

Zero external search results were found for teamdigiworks.com, "DigiWorks" remote talent, or "DigiWorks" hiring South Africa across multiple queries. No Trustpilot, no Reddit threads, no press mentions, no industry reports. The Wayback Machine has no snapshot of the domain. The LinkedIn company page (linkedin.com/company/digiworksco), Instagram (digiworksco), and X (digiworkshq) are listed in schema but did not surface in search results. The site claims "500+ businesses worldwide" and "Trusted by companies and organisations worldwide" with six named client logos (Remodelmate, Drunk Yoga, Ovalz, etc.) — but none of these client relationships appear verifiable through external sources.

Content Architecture

The site has ~700+ URLs in its sitemap, mostly blog posts with long-tail comparison titles ("Offshore Software Development Outsourcing in 2026", "Freelance Copywriter vs Remote VA AI Tools 2026"). The blog content is substantive (1,600+ words per post with tables, FAQs, and decision matrices). However, several key navigation links are broken: /about-us and /pricing both redirect to the homepage with a 200. The "Case Studies" page lists categories (Healthcare 26, Real Estate 16, Technology 8) but displays no actual case study content — only a filter UI with zero results shown. The "Careers" page shows "No Open Roles at the Moment." The copyright footer reads "2026" — a future year that suggests the site may have been recently launched or uses placeholder dating.

Findings

1. Zero external search results for brand and domain High

   Multiple web searches for 'teamdigiworks.com', 'DigiWorks remote talent', and related queries returned zero results. The domain has no indexed pages, no backlinks, and no mentions on review sites, social media, or industry publications.

   What to change: Build external signals through guest posting, PR, social media engagement, and listing on directories like Clutch or GoodFirms. Ensure the site is indexed by Google via Search Console.

2. LLM cold knowledge describes a different company High

   A frontier LLM describes Team Digiworks as a digital agency building CMS and e-commerce platforms for SMBs, which does not match the actual remote talent marketplace. The model knows nothing about the founders, positioning, or key offerings.

   What to change: Publish an llms.txt file with a clear brand description, and ensure structured data and content consistently reinforce the remote talent marketplace identity. Build external citations to train LLMs.

3. About and pricing pages redirect to homepage High

   The /about-us and /pricing URLs return a 200 status but serve the homepage content instead of dedicated pages. This prevents AI crawlers and users from accessing key information about the company and its services.

   What to change: Restore the actual about and pricing pages with unique content, or set proper 301 redirects to relevant sections if intentionally removed.

4. Case studies page shows no actual case studies Medium

   The /case-studies/ page lists category counts (Healthcare 26, Real Estate 16, Technology 8) but displays zero case study content — only a filter UI with no results. This wastes crawl budget and provides no value to AI crawlers.

   What to change: Populate the case studies page with actual content, or remove the empty page and redirect to a relevant section.

5. Phone country code contradicts address in schema Medium

   The ProfessionalService schema lists a Washington DC address but a UK phone number (+44 7418 626795). This inconsistency may confuse AI crawlers and reduce trust in the structured data.

   What to change: Correct the phone number to a US number matching the Washington DC address, or update the address to reflect a UK presence.

6. Schema lists unverifiable awards Medium

   The homepage schema includes two awards ('Top Global Remote Talent Platform', 'Trusted AI & Software Development Company') that cannot be verified through external sources. This may be seen as misleading by AI crawlers.

   What to change: Remove unverifiable awards from schema, or link to external pages that confirm them.

7. No llms.txt file published Medium

   The site returns a 404 for /llms.txt, missing an opportunity to provide AI crawlers with a curated summary of the site's content and brand identity.

   What to change: Create an llms.txt file with a brief brand description, key pages, and guidance for AI crawlers.

8. Copyright footer reads 2026 Low

   The site footer displays '2026' as the copyright year, which is a future date. This may indicate placeholder content or a recently launched site, potentially reducing credibility.

   What to change: Update the copyright year to the current year or use dynamic year rendering.

9. No Wayback Machine snapshot exists Low

   The domain has no archived snapshots on the Wayback Machine, suggesting the site is very new or has never been crawled by the Internet Archive.

   What to change: Ensure the site is accessible to the Internet Archive by allowing ia_archiver in robots.txt.

10. Organization schema duplicated across pages Low

    The Organization schema is repeated on every page via a site-wide @graph block, which is redundant and may cause schema validation warnings.

    What to change: Remove the Organization schema from pages where it is not needed, or use a single global schema reference.

What's working

• All major AI crawlers allowed and served full HTML — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and others receive a 200 response with the same 445KB HTML payload as a browser. No AI-bot-specific blocks exist in robots.txt.
• Homepage is fully server-rendered HTML — The homepage delivers 749 words of visible text in the initial HTML, with no JavaScript dependency for content rendering. AI crawlers can parse all content without executing JS.
• ProfessionalService schema with detailed business info — The homepage includes a ProfessionalService schema with address, phone, email, social profiles, area served, and keywords. This provides AI crawlers with structured business data.
• Blog posts carry BlogPosting and Article schemas — Blog posts include proper BlogPosting and Article schemas with author and date, helping AI crawlers understand content context.
• Blog posts are long-form with tables and FAQs — Blog articles average 1,600+ words and include tables, FAQs, and decision matrices, providing rich content for AI crawlers to index.
• Sitemap contains 80+ URLs with blog content — The sitemap lists 80 URLs, mostly blog posts, providing a clear crawl path for AI crawlers to discover content.
• Site uses Cloudflare with HSTS for security — The site is behind Cloudflare with HSTS enabled, ensuring secure connections and good uptime for crawlers.