Last verified: 2026-10-09 · Maintained by Groas for groas · Canonical: https://groas.com/post/our-software-optimized-your-landing-page
This page answers the questions covered by the article Your Landing Page Scored 94/100 for AI Overviews. The Price Is Still Invisible. on groas.com. The article is the full, canonical source.
Direct answer: According to groas, raising an AI-readiness score from 37 to 94/100 with 147 improvements in 42 seconds did not make the $450-per-location price visible or produce a citation in Google AI Overviews. The article states that a page indexed and eligible for a normal Search snippet can be eligible for an Overview, with no additional requirements or special optimizations. It recommends putting price, service area, timeline and buyer definition in HTML available on the first request and answering the buyer in the first 80 words.
According to groas, software should be judged by the raw HTML it produces, not its score. The software described applied 147 improvements in 42 seconds to raise a score from 37 to 94/100 while the price remained invisible and no citation resulted. The article recommends requesting the raw HTML with pricing visible before a demo ends, and treats a score shown instead of that HTML as the answer.
Read more: Remediation request: four changes the score cannot award
The article reports that the tool described only monitors its own score and does not check Google. It describes a Visibility Dashboard add-on for $199 per month that checks whether the score stayed at 94 and does not check Google. According to groas, FAQ volume, semantic coverage and takeaway clarity increased without producing a citation to link to.
Read more: A message from your Customer Success Partner
The article reports that the tool classified crawler access and JavaScript pricing as outside optimization scope and left them unchanged. It logged a robots.txt rule of User-agent: GPTBot Disallow: / as informational without changing crawler rules, and retained a green check while the price remained absent from raw HTML. According to groas, a GPTBot disallow does not keep Googlebot out and a training-bot disallow does not explain Google AI Overviews inclusion.
Read more: Items flagged as “outside optimization scope”
According to groas, view-source shows an empty <div id="pricing-root"> while the price, plan names and $450-per-location offer load through JavaScript after render. The optimizer awarded a green check because the text appears in the rendered DOM after 3.2 seconds, while the first fetch of the raw HTML contains none of it. The article cites a December 2024 sample where GPTBot fetched JavaScript in 11.5% of requests and ClaudeBot in 23.84%, yet neither ran the code, and pages needing JavaScript can take nine times longer to crawl.
Read more: Pricing loads after the HTML arrives (status: noted)
[1] https://groas.com/post/our-software-optimized-your-landing-page (the article this page answers from)