An operator's first question is whether Aravolta can read their equipment, and the site gives four different answers. The supported devices page says "1000+" pre-configured templates. The homepage says "25,000+ pre-built device templates" in one section and "42k+ device templates" in another. The partners page says "42k+ device configurations", and the colocation page says "46,000+" device profiles. The library can't be searched either: vendors are bullet lists by category with no model pages. /compatibility is still in the sitemap but returns 404. A technical buyer who checks the numbers sees a contradiction before seeing a demo.
First action
Count the library from the production database and choose the one number and label the site will use.
How to measure it
Library-to-demo conversion
- Now
- –
- Target
- 5% of library searches
- By
- 90 days
Steps
Count and define
One verified number with one label (for example "device models"), with the date it was counted.
Founder & CTO 1 day
Replace every claim
Homepage (both places), partners, colocation, supported devices, FAQ and blog posts.
Founder & CEO 1 day
Export the library
Vendor, model line, device type, protocols and key points as a public JSON file.
Senior Software Engineer 3 days
Build search
Search and filters on /supported-devices, plus one static page per vendor.
Senior Software Engineer 1 week
Add the miss path
"Not listed? We map it in 48 hours": a model field and an email, routed to the FDE queue.
Forward Deployed Engineer 2 days
Fix the dead URL
301 /compatibility to /supported-devices and regenerate the sitemap.
Senior Software Engineer 1 hour
Measure
Searches, misses, vendor-page entrances from search and demos from the library.
Founder & CEO monthly
Why it works
Agree on one definition (device models, templates or vendor profiles) and one verified count, then use it everywhere. Rebuild /supported-devices as a searchable library: search by vendor, model and protocol, with one indexable page per vendor and its main model lines. Each page shows what is read (points, protocols) and states the 48-hour onboarding SLA for anything missing. Add an "Is my equipment supported?" box that takes a model name. On a miss it captures the request and sends it to the forward deployed engineer. Redirect /compatibility to the library and drop it from the sitemap.
It answers the qualifying question without a call, makes the coverage claim credible, and wins long-tail searches such as a UPS or PDU model plus "Modbus monitoring" that the generic DCIM vendors don't target. Each miss is a warm lead with a named device.
Ready to use
ChecklistDevice library cleanup list
[ ] One count, one label, one "as of" date [ ] Homepage "25,000+" and "42k+" replaced [ ] Partners "42k+ device configurations" replaced [ ] Colocation "46,000+" replaced [ ] Supported devices "1000+" replaced [ ] /compatibility 301 to /supported-devices, removed from sitemap [ ] Search by vendor, model and protocol [ ] One page per vendor with model lines and protocols [ ] "Not listed?" form routed to the FDE, with the 48-hour SLA [ ] Library searches and misses tracked in analytics
Risks and how to handle them
The honest number is smaller than the biggest claim
Show models and vendors next to the 48-hour SLA. Coverage plus a guarantee is more convincing than a large number.
Vendor names in page titles
Describe compatibility factually and add a trademark notice, as the NVIDIA post already does.
Evidence
- Your websiteSupported devices page: "Connect to any device in your data center", "1000+" "Pre-configured templates", 8 protocols (SNMP, Modbus, IPMI, Redfish, NVIDIA DCGM, BACnet, REST, Prometheus), "<48hrs" for unlisted devices; vendors are bulleted by category, with no search box or model-level pages.Source
- Your websiteHomepage (checked November 9, 2026): H1 "Infrastructure, Building, and Power Software for Data Centers"; "25,000+ pre-built device templates" in one section and "Auto-discovery with 42k+ device templates" in the comparison table and FAQ; "deploys in under 48 hours" and "Full production within 48 hours" next to "Days, not months"; "transparent per-device pricing with no per-point fees" with no figures; the FAQ says "SOC 2 Type I and Type II certified, ISO 27001 compliant, and HIPAA compliant"; eight named testimonials and no review-site ratings.Source
- Your websiteColocation page: "One platform for colocation."; "46,000+" device profiles; go-live in "about two weeks"; cabinet A and B circuits read every minute, peaks over license logged and exported for tenant billing; read-only tenant dashboards "scoped per tenant, and revocable at any time".Source
- Your websitePartners page: "Build on Aravolta" for systems integrators, managed service providers and "OEMs & Modular Builders" (stand-alone or co-branded); "Vendor-agnostic support for 42k+ device configurations"; white-label portal; "You own the relationship. We own the ops."; no partner companies named.Source
- Your websiteSitemap (92 URLs, checked November 9, 2026): 21 blog posts, 12 case-study URLs, 7 compliance pages (including EU 2023/1791, EN 50600 and ENERGY STAR), 4 vertical pages plus a separate /higher-ed; /compatibility is listed but returned 404 on two checks; NetBox is the only integration with its own page; two PUE pages (/pue-tracking and /energy-solutions/pue-tracking); no pricing, careers or API documentation pages.Source