SteamVaults scores 79/100 for its concrete Steam trading tools, clear fee guidance, and broadly accessible public templates. Its most material weakness is a scattered documentation surface alongside two publicly linked tools marked noindex, which limits discovery and self-serve help.
Reviewed by SiteList Engine · 13 dimensions · published Reviewed on November 7, 2026
This review was refreshed on .
Is this your site?
Claim itSteamVaults is a tool-led marketplace site for Steam players and item traders.
| Fact | Value |
|---|---|
| Domain | steamvaults.org |
| Category | Steam Community Market tools and supported Steam-item trading |
| Pricing | Unknown; price range ?-? USD |
| Pages crawled | 40 |
| Crawl date | 2026-10-27 |
| Overall SiteList score | 79/100 |
SteamVaults earns 79/100 by making a focused Steam trading proposition understandable and useful across the sampled public pages. Its strongest evidence is the Accessibility dimension at 97/100, backed by a PSI accessibility score of 100 on the sampled calculator page and named form controls in the sampled tools and support pages. Writing quality is 84.3/100, with concrete copy around supported items, a 30-second quote window, 1,000-Gem units, holds of up to 15 days, and a separate $0.80 Polygon withdrawal fee.
Usability is 81.6/100, Performance is 81.5/100, and decision-support surfaces score 82/100. The /vs page combines a live quote, a caveated cross-service estimate, filters, and a ten-service checklist; its review-content integrity score is 88/100. The main drag is documentation: Docs & self-serve help scores 57.3/100 because the support material is scattered. Design execution is 64/100, and technical SEO is 77.3/100, with two publicly linked product tools marked noindex. The result is a capable, specific utility site whose next gains come from consolidation and discoverability.
SteamVaults is immediately legible as a utility-led route for Steam players who trade items or need to reason about Steam Wallet proceeds. The homepage promise, "Top up Steam Wallet or sell Steam Gems for USDT," names the audience, item, destination and settlement route. The site also gives visitors concrete safeguards: Steam OpenID, bot-account checks and a separate USDT balance. That operational detail is credible, but the supplied crawl contains no attributable customer outcomes and no comparison surface. The strongest next step is a page that explains when to use SteamVaults, the official Steam Community Market or manual selling, with the existing fee and settlement caveats kept visible.
SteamVaults answers most pre-transaction questions, but visitors must assemble the full cost model across several pages. The fee calculator explains Steam's 5% transaction fee and common game-specific fees, while the sell flow describes the site's quote economics and a separate $0.80 Polygon withdrawal fee. Those answers are individually concrete, yet they do not form one route comparison. A single cost-and-settlement explainer should separate official Steam Market fees, SteamVaults' quote spread and the withdrawal fee, then place hold, refund and Trade URL guidance in the same start-to-finish flow. The existing trust copy is appropriately specific about Steam OpenID, passwords and bot-account approval, but the supplied evidence contains no attributable testimonials or independent customer outcomes.
SteamVaults supports the core journeys, with the main repeatable friction concentrated in mobile navigation. The homepage makes the offer and desktop sign-in path clear, and the tools and support routes use recognizable labels. In the simulated walkthroughs, mobile sign-in took 2 steps rather than 1, while reaching blog help took 3 rather than 2, because the compact header added a menu decision. The same cookie card appeared across all four supplied desktop screenshots and the mobile homepage, covering nearby explanatory content. Keep "Sign in with Steam" and "Blog" persistently discoverable in the mobile header, move consent into a compact banner, and add a latest-guides or topic filter to the long blog index. These are completed paths with avoidable hesitation, not dead ends.
SteamVaults has a strong automated accessibility baseline across the sampled public templates. PageSpeed Insights reports an accessibility score of 100 for the market-fee calculator, and the tools and support samples show named controls with landmark structure. The login page has additional concrete issues: its rendered DOM facts report 5 images, including 2 with missing alt attributes, and its heading sequence starts at h2 with no h1 in the supplied sample. Resolve each image as informative or decorative, promote the primary login title to h1, then run an element-level keyboard and accessibility-tree pass. The CSS capture includes focus-visible and prefers-reduced-motion rules, but the supplied artifacts do not establish actual focus trapping or screen-reader announcements.
SteamVaults has a coherent dark interface and a clear desktop composition, but mobile control sizing is not yet suited to a tool-led flow. The 390px layout reports 23 small tap targets; examples include a 33×24px SteamVaults link, a 40×40px menu control and a 44×40px English control. Inputs compute to 15px and buttons to 11px, making calculator interactions harder to scan and increasing the risk of iOS auto-zoom. The same capture reports scrollWidth 390 with a width=device-width viewport, so the issue is control ergonomics rather than page-level overflow. Raise mobile hit areas to at least 44×44px, set inputs to 16px minimum, enlarge button labels, then consolidate only rendered design values after a computed-style inventory.
The available field signal is good, while controlled mobile loads expose a slower critical path. PageSpeed Insights reports mobile p75 LCP of 2,067 ms and CLS of 0 for the sampled origin; mobile TTFB is 977 ms, and INP was not returned. Lab LCP reaches 3,226.5 ms on the fee calculator, 3,682 ms on the remote-play article and 3,226 ms on /ko, with estimated render-blocking savings of 950–1,590 ms. Start with the mobile waterfalls: defer non-critical CSS and scripts, reserve image space, and re-test the same templates. The /play route also records 3,416 KB across 62 requests, including 967 KB from shared.akamai.steamstatic.com and 525 KB from cdn.akamai.steamstatic.com, so it needs a separate payload budget.
SteamVaults' strongest writing is direct about transaction boundaries and what the user should expect next. The sell and buy flows name the 30-second quote window, Steam confirmation, holds of up to 15 days and the separate $0.80 Polygon withdrawal fee; the copy also states that Steam Wallet funding is not a direct top-up. The homepage is denser than those transactional pages: rendered text averages 25.5 words per sentence, versus 15.7 on /buy and 16.9 on /sell. Split the homepage's longer explanations around bot receipt, site-balance credit and Polygon withdrawal while preserving its risk caveats. The crawler also records missing alt text across sampled routes, so descriptive alternatives should be part of the same editorial pass.
The /vs page is a substantive comparison surface, not a decorative feature grid. It gives visitors a live SteamVaults quote of $68.63, an explicitly caveated $54.88–$78.40 estimate for other cash-out services, filters and a ten-service checklist. The page explains that SteamVaults uses a live Sack of Gems bid while other services use a broad 70–80% cash-value assumption plus published fees, so the range is directional rather than like-for-like. It also states that SteamVaults is its own service and that inclusion is not a safety endorsement or paid ranking. Add short, overridable "best for" recommendations for item coverage, cash-out route, settlement and verification priorities, then summarize the decisive axes before the long mobile service list.
SteamVaults presents the /vs page as disclosed comparative synthesis, with a method visible enough for readers to understand its limits. The page says official sources were reviewed on 2026-08-19, covers 10 active or limited services plus closure records, and uses one consistent checklist. It also discloses the central conflict: SteamVaults is its own service, and inclusion is not a safety endorsement or paid ranking. The supplied evidence reports no affiliate-link sample, and no Review or AggregateRating markup is shown for /vs. The next improvement is provenance at service-row level: add a source URL and checked date, or an evidence panel, for each claim and a dated what-changed note when fees, coverage, settlement or verification rules change.
The current risk picture is actionable, but it is not a measured traffic-loss diagnosis because no traffic-drop symptom or GSC/analytics data was supplied. The crawl marks /tools/smart-orders and /tools/portfolio as noindex while public navigation links to them. It also records /items/753-sack-of-gems canonicalizing to /vi/items/753-sack-of-gems and /sell?quantity=100 canonicalizing to /vi/sell. Resolve whether the tools are acquisition pages or authenticated utilities, then align noindex, canonicals, sitemap and internal links accordingly. The crawl does not evidence sitewide suppression, a redirect loop, a mass 5xx problem or client-side-only rendering dependency. After recrawling, verify intended language URLs in GSC; the supplied evidence cannot estimate actual traffic impact.
The supplied sample reflects a competent editorial program with visible mechanical QA debt. The overlay guide opens with the concrete problem, "Game runs but Shift+Tab does nothing?", and distinguishes an editorial diagnostic approach from a measured fix rate. Transaction pages similarly preserve the 30-second quote window, bot confirmation and non-direct Wallet top-up boundary. The release checklist should catch missing alt text across the homepage, /buy, /blog, /how-it-works and the overlay guide. It should also resolve the sign-in shell's title "Sign In", missing meta description and missing h1, plus the buy-page title measured at 67 characters. The supplied evidence establishes no schema-content mismatch, so improvements should focus on these confirmed defects rather than speculative rewrites.
SteamVaults has a credible support entry point, but it is too thin to serve as a self-serve answer center for a transaction-heavy product. The support page lets users submit trade, security and privacy requests without signing in, check a public request and see when Steam verification is required; it has 27 inbound links. Yet it is the only discovered documentation root, contains 324 extracted words and reports no search box. Turn /support into a task-oriented help index covering selling, buying, trade holds, withdrawals, security and privacy, with reviewed dates and a clear escalation path. Keep llms.txt aligned with that canonical support index so both people and machine readers can find the same core answers.
SteamVaults is crawlable and server-rendered across the 40-page sample, with a sound technical foundation and two high-priority signal conflicts. Robots.txt allows normal crawling and declares a verified 984-URL sitemap; HTTPS redirects in one hop, while HSTS and nosniff are present. The main issue is that /tools/smart-orders and /tools/portfolio return 200, are linked from public navigation, sit outside the sitemap and carry noindex. Either make them intentional acquisition pages with aligned canonical and sitemap treatment, or remove them from crawl-oriented navigation. Separately, /items/753-sack-of-gems and /sell?quantity=100 point canonicals at Vietnamese URLs. Align canonical, hreflang, sitemap and internal-link targets, then retain the current rendering strengths while reducing mobile render-blocking work.
SteamVaults is a strong fit for Steam players and item traders who need fee, inventory, trade-link, or supported-item cashout decisions. The site earns trust through concrete boundaries: Steam OpenID sign-in, live quotes, public-inventory limits, and clear explanations of Steam Wallet proceeds.
Three fixes would make the experience more complete. First, consolidate the scattered support material into a clearer self-serve path; Docs & self-serve help is the lowest supplied score at 57.3/100. Second, resolve the discovery problem created by noindex on two publicly linked product tools, identified in the 77.3/100 technical SEO review. Third, reduce the gap between the good 2,067 ms mobile field LCP at p75 and the 3.2–3.7 s mobile lab LCP range. Those are concrete improvements to an already focused utility and marketplace surface.
This 13-dimension review uses the supplied 40-page crawl from 2026-10-27, current product facts gathered from JSON-LD and text, the public dimension score table, and the supplied DOM, PSI, field-performance, and lab-performance signals. The score table includes dimensions 01, 02, 03, 04, 05, 07, 09, 12, 13, 17, 19, 23, and 25. Other dimensions are excluded from this frame because no score or public summary was supplied; the inputs do not specify a further exclusion reason, so this article does not infer one.
Google Search Console is not connected and access is unavailable, so no GSC enrichment is included. Pricing is also recorded as unknown with a ?-? USD range. Product facts describe web tools, Steam OpenID sign-in, public-inventory limits, quote timing, and USDT site-balance settlement; this review does not extend those facts into guarantees. Read How SiteList scores for the full method.
Steam publishes a 5% transaction fee and lists common game-specific fees such as 10% for Team Fortress 2 and Counter-Strike 2. Minimum fees, rounding, currency increments, and taxes can affect the final result.
Steam calculates each fee from the seller amount, floors it to the smallest currency unit, and applies per-fee minimums. Reverse calculations and low-price listings therefore differ from a simple 15% subtraction.
No. Community Market proceeds enter Steam Wallet. Valve states that Wallet funds have no cash value and are not exchangeable for cash.
Paste your SteamID or Steam profile link, choose the quantity, lock a quote for 30 seconds, and accept the trade offer in your Steam Mobile app. After receipt and settlement succeed, USDT is credited to your site balance.
No. It reads only inventory information the profile exposes publicly. Change the Steam inventory privacy setting if you want a third-party tool to read it.