ecomcy.com — AI Site Grade

Analysis

Ecomcy has a sophisticated AI-readiness posture (llms.txt with MCP endpoint, all bots allowed) but suffers from a near-total cold-knowledge vacuum — frontier LLMs have zero awareness of the brand despite the site claiming 1,000+ brands served and $500M+ in managed revenue.

Crawler Access

All major AI crawlers — GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, Bytespider, Applebot-Extended — receive HTTP 200 with full HTML content from the homepage. No UA-based blocking exists. The robots.txt has a permissive Allow: / for * but names zero AI bots explicitly — no GPTBot, ClaudeBot, or PerplexityBot rules. The site runs on Wix (server Pepyaka, IP 185.230.63.107) with HSTS and X-Content-Type-Options: nosniff set. An llms.txt exists and is unusually advanced: it documents a Wix MCP endpoint (/_api/mcp) for agentic AI access, listing tools like SearchInSite, CallWixSiteAPI, and GenerateVisitorToken. This is rare and technically ahead of most agency sites.

Cold-Knowledge Gap

A frontier LLM queried cold about Ecomcy returned: "I do not have specific, verifiable information about an ecommerce agency named Ecomcy" — zero recall of the brand, its services, founder, or reputation. This is the single largest AI-visibility gap. The site claims $500M+ active revenue managed, $75M+ ad spend, 1,000+ brands served, 20+ industry awards, and a team of 75 people. None of these claims appear in any external search results, Reddit threads, press mentions, or review sites. The brand has no detectable off-domain footprint — no Clutch, G2, Trustpilot, or Google Business reviews surfaced, and no news coverage or forum discussions exist in search results.

Content & Schema Posture

The homepage carries LocalBusiness and WebSite JSON-LD schema with a London address and phone number. However, all subpages lack any schema markup — the about, services, blog, podcast, and contact pages return zero @type declarations. The /services/ppc-management-for-amazon page returns 0 words of visible text — a JS shell with no content for crawlers. The /our-services page contains placeholder copy ("This is the space to introduce the Services section") in multiple accordion panels. The blog has 12 posts with proper BlogPosting schema and substantive content (800+ words each), but the author field uses a username (josettechua) rather than a real name. No FAQ schema, comparison tables, or structured answer-format signals exist anywhere on the site.

External Signals

Web searches for "Ecomcy reviews", "Ecomcy agency", and "Ecomcy Vincenzo Toscano" return zero results across general search and Reddit. The only external links found are to Calendly booking pages, LinkedIn, Facebook, Instagram, and YouTube — all owned social profiles with no independent third-party validation. The DNS TXT records include Brevo email, Microsoft 365, and Google/LinkedIn site verification, confirming the brand operates but has not accumulated any public reputation signals that AI engines could surface.

Findings

1. Frontier LLMs have zero awareness of Ecomcy High

   A cold query to a frontier LLM returned no verifiable information about Ecomcy, despite the site claiming $500M+ revenue managed and 1,000+ brands served. The brand has no detectable off-domain footprint.

   What to change: Build external signals through press releases, guest posts, review profiles (Clutch, G2, Trustpilot), and active participation in industry forums to create a verifiable public footprint.

2. Zero external reviews, press mentions, or forum discussions High

   Web searches for 'Ecomcy reviews', 'Ecomcy agency', and 'Ecomcy Vincenzo Toscano' returned zero results. No Clutch, G2, Trustpilot, or Google Business reviews exist, and no Reddit or news coverage was found.

   What to change: Claim and populate profiles on review platforms, issue press releases for major milestones, and engage in industry discussions to generate third-party mentions.

3. Robots.txt does not explicitly name any AI crawlers Low

   The robots.txt has a permissive Allow: / for * but does not include explicit rules for GPTBot, ClaudeBot, PerplexityBot, or other AI crawlers. While not blocking, this misses an opportunity to signal AI-friendliness.

   What to change: Add explicit Allow rules for GPTBot, ClaudeBot, PerplexityBot, and other AI crawlers to reinforce AI-readiness.

4. PPC management page returns zero visible text High

   The /services/ppc-management-for-amazon page returns 0 words of visible HTML content, appearing as a JavaScript shell. Crawlers cannot extract any information from this page.

   What to change: Ensure all service pages render substantive HTML content server-side or use static generation so crawlers can index the text.

5. Our Services page contains placeholder copy in accordion panels Medium

   The /our-services page includes placeholder text like 'This is the space to introduce the Services section' in multiple accordion panels, indicating incomplete content.

   What to change: Replace all placeholder text with detailed, unique descriptions of each service.

6. All subpages lack structured data markup High

   Only the homepage has LocalBusiness and WebSite JSON-LD schema. About, services, blog, podcast, and contact pages have zero @type declarations, reducing their visibility in AI-generated answers.

   What to change: Add appropriate schema types (e.g., Service, BlogPosting, PodcastEpisode, ContactPoint) to all subpages.

7. Blog posts use username instead of real author name Low

   The blog posts have BlogPosting schema but the author field uses 'josettechua' rather than a real name, reducing credibility and discoverability.

   What to change: Update the author field to use a real name and link to an author profile page.

8. No FAQ, comparison, or structured answer schema on the site Medium

   The site does not use FAQPage, HowTo, or comparison schema anywhere, missing opportunities to appear in rich AI answers.

   What to change: Add FAQ schema to service pages and comparison schema for service differentiators.

9. No independent third-party backlinks or mentions High

   The only external links found are to owned social profiles (Calendly, LinkedIn, Facebook, Instagram, YouTube). No independent sites link to Ecomcy, limiting domain authority and AI citation sources.

   What to change: Develop a link-building strategy through guest blogging, partnerships, and industry awards to earn third-party backlinks.

10. No Google Business Profile or local listings found Medium

    Despite a London address in schema, no Google Business Profile or other local directory listings were detected, reducing local AI visibility.

    What to change: Create and verify a Google Business Profile and list the business on relevant local directories.

What's working

• Advanced llms.txt with Wix MCP endpoint for agentic AI — The site hosts an llms.txt file that documents a Wix MCP endpoint, listing tools like SearchInSite and CallWixSiteAPI. This is a rare and forward-looking AI-readiness signal.
• All major AI crawlers receive full HTML content — All 11 tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) receive HTTP 200 with full HTML from the homepage. No UA-based blocking exists.
• Homepage has correct LocalBusiness and WebSite schema — The homepage includes JSON-LD schema with LocalBusiness and WebSite types, including London address and phone number, providing clear entity information.
• Blog posts have BlogPosting schema and substantive content — The 12 blog posts use BlogPosting schema and contain 800+ words each, providing crawlable, structured content that can be used by AI for training and answers.
• Permissive robots.txt allows all crawlers — The robots.txt has a global Allow: / rule, ensuring no crawler is blocked from the site.
• HSTS and security headers are properly set — The site sets HSTS and X-Content-Type-Options: nosniff headers, indicating good security hygiene that can positively influence trust signals.