Blue SteelCo
A 28-year Wix-hosted manufacturer gets full Product + FAQ schema, a vocabulary bridge, and AEO content coverage. Result: +218% indexed pages in 90 days, GSC verified.
The Starting Point
Blue SteelCo has manufactured industrial safety products since 1997. Fire extinguisher storage racks, collapsible pit handrails, safety platforms for railroads and power plants. Twenty-eight years of quality manufacturing — and a website that search engines barely noticed.
The site had 11 indexed pages at engagement start. No schema markup. No structured data. Product descriptions written in manufacturer language, not buyer language. Zero AI visibility.
What We Did
Phase 1: Foundation (Weeks 1-4)
- Full technical analysis revealing 47 issues
- Schema markup implementation across all product pages (Product, Organization, FAQ)
- Vocabulary bridge: mapped manufacturer terms to buyer search terms
- Fixed crawlability issues (broken links, missing meta tags, orphaned pages)
Phase 2: Content (Weeks 5-8)
- Created 8 AEO-optimized content pages targeting voice search and AI platforms
- OSHA compliance guides (1910.157 for fire safety, 1910.28/29 for fall protection)
- Industry-specific landing pages for each vertical (railroad, power, warehouse)
- FAQ pages using actual customer search language
Phase 3: Layer 3 groundwork (Weeks 9-12, staged for platform migration)
Blue SteelCo runs on Wix, and Wix does not currently expose root-level /.well-known/ files or custom llms.txt. That rules out a live WebMCP manifest on the current platform. Rather than skip the work, we authored the full Layer 3 stack for migration day:
- Drafted the WebMCP manifest (tools:
product_search,request_quote,compliance_check) - Authored llms.txt and llms-full.txt ready to publish at the moment the site either migrates off Wix or we wire a Cloudflare Worker proxy in front of the domain
- Documented exactly which Wix Custom Code slots already carry the structured data we could inject (LocalBusiness + Product + FAQPage) so the Layer 2 wins held without needing root-file access
The manifest is not live. That is the honest version. The path to live is either a CF Worker at the edge or a platform migration — both estimated at the end of the Enforcement engagement.
The Results
The numbers tell one story. The positioning tells another.
As of 2026-04-21, Google Search Console shows 35 indexed pages on bluesteelco.com — up from 11 at engagement start. That’s a +218% lift in three months, with five remaining URLs in the active queue (three page-with-redirect, one 404, one discovered-not-indexed — all diagnosable, none the result of a penalty).
Blue SteelCo went from invisible to findable. Product + FAQ schema is live. The vocabulary bridge means a buyer searching “fire extinguisher rack supplier” now hits Blue SteelCo product pages that actually answer the question. The Layer 3 manifest (WebMCP + llms.txt) is authored and staged, pending a Cloudflare Worker deploy or platform migration — Wix is the reason for the pending, not the execution.
That’s the difference between Layer 1 and Layer 2, with Layer 3 on deck.
Want to see where your site stands? Get a free score in 30 seconds.