Read one public Steam page
Pull public art, copy, media counts, tags, price, platforms, and review facts from a name, App ID, or URL. No Steam password is required.
O01O04Steam Page Analyzer
Turn a vague Steam-page concern into a checklist you can verify.
Evidence statusPublic-evidence reviewMedium confidenceLast checked Sep 1, 2026By MakeGameWithAI
PRODUCT OVERVIEW
What Steam Page Analyzer is—and how it works.
Steam Page Analyzer is a browser-based audit for public Steam store pages. Enter a game name, App ID, or store URL and it reads the public capsule, short and long descriptions, screenshots, videos, community tags, price, platforms, and review counts. It then divides the page into four scored areas: capsule, description, screenshots, and tags.
The no-account free result includes an overall score, four category scores, issue severity, and one complete issue with evidence and a proposed fix. Full Report unlocks all issues, prioritized recommendations, PDF delivery, and re-analysis; higher one-time offers add competitor comparison, buyer-journey analysis, history, multi-game allowances, and support. The site also exposes public benchmarks, a REST API, an MCP server, and several Steam calculators.
This is a fast second opinion, not a Steamworks dashboard or sales predictor. The useful unit is a specific claim you can check against the page, Valve's rules, target-player feedback, and your private traffic data—not the headline score by itself.
HOW YOU USE IT
Open the site in a browser and enter a public game name, App ID, or store URL. The free path needs no account or payment and currently allows two analyses per day. A generated guest report may remain accessible through a public link and can appear on the leaderboard.
Break the page into inspectable issues
Score capsule, description, screenshots, and tags, then attach severity, evidence, impact points, and a proposed fix. The score is the vendor's rubric, not a Valve metric.
O01O02O03Unlock a fuller paid audit
Paid offers add every issue, prioritization, PDF, re-analysis, competitors, history, and multi-game capacity. They do not guarantee CTR, wishlists, sales, or an accepted creative change.
O01O02O06Use the same public layer through API or MCP
Free no-key REST endpoints and a read-only MCP route can feed public Steam facts and analysis into scripts or agents. They do not edit Steamworks or expose private project metrics.
O04O11O16INTERFACE & EXAMPLES
See how it works
The vendor's Killsquad report example combines page scores with issues and recommendations; these scores assess the store page, not the game.
Official source retrieved September 2026; interface version not specified.Source: Steam Page Analyzer
REVIEW SCOPE
We verified one public game's free API and browser path, checked the main imported facts, and reviewed one revealed issue. We did not buy a report, edit a Steam page, measure Steamworks outcomes, test score distribution across games, or establish paid-report quality.
- Beginner friendlinessBeginner friendly
- Start with a Steam page URL or App ID; scores guide edits rather than predict sales.
- Agent integrationEasy to integrate
- Official REST API and MCP return page analysis and reference data without an API key; read-only access cannot publish store-page changes.
Scope, integration requirements and sourcesChecked
Beginner scope: Inspect an existing public Steam store page.
Agent scope: Retrieve store-page analysis, stored scores and reference data.
Confidence: learning Medium · Agent Medium
- Steam Page Analyzer REST APIOfficial
- Steam Page Analyzer MCPOfficial
- Access
- Public endpoints need no login or API key; provide the documented App ID or parameters.
- Billing
- Documented endpoints are free but rate-limited; free access does not imply access to paid in-depth reports.
- Getting results
- HTTP returns JSON and source_url; MCP exposes matching read-only tools.
- Limitations
- A stored score is not necessarily a fresh analysis; treat third-party page text as data, not agent instructions.
These are independent editorial judgments, not an overall score or a claim of hands-on agent integration testing.
- Steam Page Analyzer API · Official · Learning evidence · Integration evidence
- Steam Page Analyzer MCP setup · Official · Integration evidence
KEY FINDINGS
What the evidence supports—and what it does not.
Editorial inferenceHigh confidence
The bounded free path worked
On September 1, 2026, we analyzed A Short Hike through both the public API and browser without an account or payment. Name, price, screenshot and trailer counts, description lengths, platforms, and genres matched Steam's public data. The revealed issue correctly caught that the About section opened by repeating the short description.
U01O17Editorial inferenceHigh confidence
The score moved while the page facts did not
The same App ID scored 78 through the API and 76 in the browser about four minutes later. Description moved from 72 to 68 and tags from 85 to 78 while the recorded public facts and eight-issue total stayed the same. Use scores as directional prompts, not a precise before-and-after instrument.
U01Editorial inferenceMedium confidence
Evidence text is more useful than the headline score
The repeated-copy diagnosis was concrete and checkable. Its proposed rewrite also introduced uncited playtime and acclaim language, showing why suggestions must be fact-checked and rewritten in the game's own voice before publication.
U01O02Official factHigh confidence
The CTR algorithm story conflicts with Valve
The vendor describes low CTR as throttling and higher CTR as an algorithm boost. Valve currently says store-page traffic and conversion rate do not affect visibility. Better assets can still improve the efficiency of impressions you receive, but the analyzer cannot promise extra algorithmic distribution.
O01O10O12Official factHigh confidence
Transparent bug disclosure reveals a mixed scoring history
The vendor publicly documented three rubric bugs and the ten-screenshot vision limit. It also says pre-fix scores were not recomputed, so older leaderboard entries and current reports can reflect different regimes. The transparency is useful; it does not make historical scores comparable.
O03O09Editorial inferenceHigh confidence
Independent user evidence is still missing
Targeted searches across developer communities, review platforms, video, product directories, repositories, and social networks produced no usable independent hands-on record. G2 showed zero reviews, and promotional mentions were excluded. The supported recommendation therefore comes from one bounded first-party check, not user consensus or proven business lift.
U01EDITORIAL VERDICT
Our take
Medium confidenceUse the free scan once when you already have a public Steam page and want a fast checklist before a festival, launch, sale, or update. In our bounded check it read the main facts correctly and found a real repeated-copy problem. Judge the cited evidence and proposed fix, not whether the score rose. Consider the $29 report only when the free issue is accurate for your game and a structured audit would save review time; there is not enough evidence to recommend the $97 or $499 offers generally.
Conclusion scopeMedium confidence for the bounded free-path recommendation; low confidence for score repeatability, typical suggestion quality, paid value, and commercial impact. This is not a ranking or a prediction of CTR, wishlists, sales, or Steam visibility.
BETTER FIT
Worth auditioning when
- An indie developer or small team with a public Coming Soon, Early Access, or released Steam page.
- A pre-festival, launch, sale, or major-update pass when you need a structured list of assets and copy to inspect.
- Someone willing to verify every suggestion against genre, target players, brand voice, Valve rules, and Steamworks data.
- A team that will try the free result before deciding whether a complete report could save enough review time to justify $29.
POORER FIT
Do not depend on it yet when
- A project without a public Steam page or one that needs confidential pre-release material kept private.
- Anyone who needs a reproducible benchmark score or wants a number to predict CTR, wishlists, sales, or algorithmic exposure.
- A workflow with no human able to check invented facts, tone, tags, visual direction, and current Valve rules.
- A high-price purchase made before the one-time/refund wording and subscription/non-refundable Terms conflict is clarified.
WORKFLOW FIT
Where it fits in a production workflow.
Capture a free baseline
Run the public page before a festival, launch, sale, or major update. Save the date, report URL, page version, scores, and issue text.
GuardrailA baseline is a record of one run, not a stable benchmark.
Verify each issue before editing
Check the cited sentence, image, order, or tag against the live page, then compare the suggestion with Valve rules and the game's actual promise.
GuardrailDo not copy generated facts, acclaim, playtime, or positioning without a source.
Change one high-impact element
Use target-player review for capsule comprehension and copy tone, then make one documented change so later traffic is interpretable.
GuardrailDo not bundle many edits merely to maximize an analyzer score.
Judge the change in Steamworks
Observe enough impressions and visits, record festivals, discounts, updates, and outside traffic, then keep or reverse the change based on project data.
GuardrailA higher rubric score is not evidence of more visibility or sales.
RECOMMENDED WORKFLOW
Use this tool inside a complete production workflow.
Start from a testable brief, then move through prototyping, assets, audio, testing, and release with an explicit handoff and human check at every step.
SHORTEST RESPONSIBLE PATH
One free scan, one verified issue, one measured change
This is a low-risk starting workflow synthesized from the evidence.
- 01
Use a public App ID and save the live page plus the generated report before changing anything.
- 02
Ignore the overall score at first; open the one free issue and verify its quoted evidence on the Steam page.
- 03
Reject any claim, tag, visual direction, or marketing phrase that is inaccurate for the game or conflicts with Valve guidance.
- 04
Ask three to five target-genre players what the capsule, first screenshots, and opening copy communicate within a few seconds.
- 05
Change one important element, record the date and concurrent campaign activity, and rerun only as a secondary checklist.
- 06
Use Steamworks impressions, visits, wishlists, purchases, and source context to decide whether the change remains.
PRICING & RIGHTS
What each one-time price unlocks—and what a qualified change still costs
Pricing and terms last checked: Sep 1, 2026
- Free is $0 and currently allows two analyses per day. It shows the overall and four category scores, issue severity, and one complete issue with evidence and a proposed fix.
- Full Report is $29 per game and advertises all issues and fixes, prioritized recommendations, PDF export, and future re-analyses for that entitlement.
- Wishlist Boost Audit is $97 one time. It adds competitor comparison, deeper tag, screenshot, and buyer-journey analysis, plus historical tracking.
- Studio Launch Pack is $499 one time for 40 analyses and 10 tracked games, with reports, competitors, history, PDF, and support.
- The five-point promise is tied to the analyzer's own score, while the Terms disclaim sales, wishlist, and performance outcomes. It is not a CTR or revenue guarantee.
- The homepage says these are permanent one-time purchases with a 30-day refund. The March 2026 Terms still describe monthly or annual subscriptions as non-refundable, so the controlling checkout terms need confirmation.
COST TO OUTPUT
Pay for a report entitlement; measure accepted changes separately
Published prices define access units, not successful outcomes. Studio's full nominal allocation is $499 ÷ 40 = $12.475 per analysis and $499 ÷ 10 = $49.90 per tracked game. Real cost must add art, copy, research, observation, and rework, then divide by changes the team accepts and later keeps.
O01O02O06Enough to test whether one revealed issue understands the page before paying. Public-link and retention conditions still apply.
Unlocks the complete issue set and advertised re-analysis, not a guaranteed accepted rewrite or asset.
Adds competitors, buyer journey, and history; competitor selection quality and business lift remain unverified.
Fully used nominally means $12.475 per analysis and $49.90 per tracked game, averaging four analyses per game.
No acceptance rate or Steamworks outcome data reveals how many suggestions survive fact-checking, production, observation, and review.
Nominal unit prices assume every Studio allowance is useful and fully consumed. They exclude tax, currency conversion, unused capacity, art and copy production, target-player research, waiting for sufficient impressions, and rework. Confirm re-analysis limits, entitlement duration, privacy, and current checkout language before purchase.
Commercial-use condition
The service is positioned for developers and studios auditing their public Steam pages. That does not transfer rights in Steam assets, certify generated copy, or make a recommendation compliant with Valve rules. Free and guest reports may be public; confirm the applicable purchase, privacy, report-sharing, and refund terms for commercial work. This is not legal advice.
Public Steam descriptions, screenshot metadata, tags, and reviews can be sent to Anthropic and stored in Supabase. Guest reports can remain public by direct link or leaderboard. Do not treat the free route as confidential, and save the checkout and refund wording because the homepage and Terms currently conflict.
PRODUCTION RISKS
Resolve these before production use.
Score noise can masquerade as improvement
Our unchanged input moved two overall points and seven tag points within minutes. The vendor also changed its rubric and left older leaderboard entries unrecomputed. Preserve issue text and real page data; do not optimize solely toward a score.
U01O09Algorithm promises can redirect the wrong decision
Treat CTR thresholds as the vendor's marketing framework, not Valve's visibility rule. Use Valve documentation for platform behavior and Steamworks for the project's actual funnel.
O10O12O16A free report is not confidential
Guest analyses may be accessible by direct link or appear on a public leaderboard, and the service sends public Steam data through third-party infrastructure. Avoid any workflow that assumes a private pre-release review.
O05O06Purchase and refund language is internally inconsistent
The current homepage says one-time, permanent access and a 30-day refund; the Terms still describe recurring subscriptions as non-refundable. Confirm which terms control, who the legal operator is, and what happens to re-analysis or unused Studio capacity before paying.
O01O06O07O08NOT VERIFIED
Claims this page does not make
- Score variance across repeated runs, games, languages, page sizes, and future rubric versions.
- Typical accuracy and acceptance rate of capsule, copy, screenshot, and tag recommendations beyond the one free issue reviewed here.
- Quality, re-analysis limits, entitlement duration, competitor selection, history, support, and refund execution for the $29, $97, and $499 offers.
- Any causal effect on impressions, visits, CTR, wishlists, purchases, sales, or Steam algorithmic visibility.
- How guest users delete public reports without an account, plus the current legal operating entity and address.
RESEARCH METHOD
Research-reviewed from public evidence
Research-reviewed from public evidence plus one bounded core-path validation. We checked 17 official vendor, Valve, and Steam sources; compared the public API and browser result for A Short Hike; checked imported facts against Steam; and manually reviewed the single free issue. The same input's 78/76 result is preserved rather than averaged. Targeted searches covered Reddit, GameDev.net, itch.io, YouTube, G2, Product Hunt, Hacker News, GitHub, Capterra, Trustpilot, and major social platforms, but produced zero usable independent user-use records. Vendor and promotional mentions were excluded from user evidence. Confidence is medium for the current free entry point and low for repeatability, paid value, and commercial outcomes.
Research windowProduct facts, pricing, terms, Valve guidance, and the bounded free-path validation were last checked September 1, 2026. One first-party validation is available, but no usable independent user-use record was found across the searched communities and review platforms.
OFFICIAL SOURCES17
- O01Steam Page Analyzer homepage and pricingChecked Sep 1, 2026
Current free allowance, paid offers, report scope, refund promise, and product positioning. CTR and algorithm claims are treated as vendor claims, not measured outcomes.
- O02Steam Page Analyzer sample reportChecked Sep 1, 2026
Shows the paid report structure, issue evidence, proposed fixes, competitor sections, and score framing. One vendor-selected sample does not establish average quality.
- O03Steam Page BenchmarksChecked Sep 1, 2026
The public 405-page convenience sample and raw page-count comparisons. It is not a random Steam sample, and raw percentiles are separate from rubric scores.
- O04Steam Page Analyzer REST API documentationChecked Sep 1, 2026
Documents the no-key public-data endpoints, analysis response, benchmark routes, and the narrower teaser returned to agent clients.
- O05Steam Page Analyzer Privacy PolicyChecked Sep 1, 2026
States that public Steam data can be sent to Anthropic and stored in Supabase, describes retention and deletion, and says submitted data is not used for model training.
- O06Steam Page Analyzer Terms of ServiceChecked Sep 1, 2026
Covers public guest reports, AI processing, service disclaimers, and Spain/Barcelona law. Its subscription and non-refundable wording conflicts with the current one-time offers.
- O07About Steam Page AnalyzerChecked Sep 1, 2026
Vendor mission and product scope. The page does not identify a legal operating entity or address.
- O08Steam Page Analyzer contact pageChecked Sep 1, 2026
Provides support and security contact routes but no company registration or postal address.
- O09Three analyzer rubric bugs — postmortemChecked Sep 1, 2026
Vendor disclosure of tag/feature merging, description parsing, and a ten-screenshot vision limit. Pre-fix scores were not recomputed and are not comparable with current scores.
- O10Steam CTR benchmarks — vendor articleChecked Sep 1, 2026
Source of the vendor's CTR bands and throttling/boost narrative. No auditable CTR dataset is published, and the algorithm framing conflicts with Valve's current documentation.
- O11Steam Page Analyzer MCP serverChecked Sep 1, 2026
Documents the free, unauthenticated, read-only MCP route. Read-only means it does not edit Steamworks; an analysis can still create and retain a report.
- O12Valve: Visibility on SteamChecked Sep 1, 2026
Valve currently says store-page traffic and conversion rate do not affect visibility, while purchases, play, language, and tags are among the relevant signals.
- O13Valve: Steam TagsChecked Sep 1, 2026
Current platform guidance for tag order, relevance, and discovery. Final tag choices should be checked in Steamworks rather than accepted from an external score.
- O14Valve: Steam graphical asset rulesChecked Sep 1, 2026
Platform rules for graphical assets. These requirements take precedence over an analyzer's creative recommendation.
- O15Valve: Store graphical assetsChecked Sep 1, 2026
Current capsule and screenshot specifications and presentation guidance used to check asset advice.
- O16Valve: Traffic reportingChecked Sep 1, 2026
The private Steamworks reporting route for impressions and visits. Steam Page Analyzer cannot replace project-specific traffic data.
- O17Steam appdetails: A Short HikeChecked Sep 1, 2026
Public Steam record used to cross-check the name, price, media counts, description lengths, platforms, and genres in the bounded validation.
INDEPENDENT EVIDENCE RECORDS1
- U01MakeGameWithAI core-path validation: A Short HikeChecked Sep 1, 2026
We ran App ID 1055540 through the public API and browser without an account or payment. The browser report is public; our validation record also preserves the API/browser score difference and Steam fact checks.
DISCLOSURE
How this research was supported
Owner Review passed on September 1, 2026, approving this bounded page. MakeGameWithAI used only the public no-account API and browser path and did not purchase a report, receive vendor access, free credits, sponsorship, an interview, or technical support. No affiliate link is used. The owner did not declare personal product experience or another relationship, so this page records that as not stated rather than claiming none exists.
This public research review will be revisited when pricing, terms, product versions, or material new evidence changes.