willaicite
generative engine optimization

Proof

This page is the audit trail of willaicite scoring its own site: the baseline report, the fixes it prescribed, and the reproducible result. The site you are reading was optimized by the tool it sells, and every number below comes from logged runs on July 17, 2026.

Where did the site start?

The first audit of the freshly built landing page logged at 15:37 UTC and scored 51/100. The verdict line read “Needs work: real gaps are limiting how AI engines retrieve and cite this site.” The page was technically clean and completely uncitable: readable by every crawler, with nothing an answer engine could attribute, date, or quote.

dimensionbaselineafter
AI crawler access 100 100
Renderability 100 100
Structured data 0 100
Answer-readiness 45 100
Evidence density 28 100
Freshness 30 100
Entity & E-E-A-T 20 100
Overall51100

What did the audit flag?

The fix-first list named each gap with its evidence. What followed was not a redesign; it was working through that list:

  • Structured data, 0 to 100. The report said, verbatim: “no JSON-LD blocks found on the audited pages”. Fixed with one schema graph: Organization, Person, WebSite, TechArticle with author and dates, FAQPage, BreadcrumbList.
  • Answer-readiness, 45 to 100. No definitional opening, one question-shaped heading, no FAQ. The page now opens with a sentence an engine can lift whole, and the FAQ renders from the same array as its FAQPage markup, so the two cannot disagree.
  • Evidence density, 28 to 100. The baseline had zero statistics and one outbound link; the fix-first list read, verbatim: “Add concrete statistics with units (%, $, counts) to the main content”. The GEO study found citing sources lifted generative visibility 24.9 percent, statistics 25.9 percent, and quotations 27.8 percent, so the page now carries all three, with every external link verified live before shipping.
  • Freshness, 30 to 100. No dates anywhere, and the audit rewards a machine-readable date signal from the last 90 days. Dates went into the schema, the meta tags, and the sitemap.
  • Entity & E-E-A-T, 20 to 100. No author, about page, contact route, favicon, or Open Graph metadata. All added, all real.

What does it score now?

The after column above is the re-run, and its fix-first list is empty. Independent measures agree: Lighthouse scores the page 100 for accessibility, best practices, SEO, and agentic browsing, and PageSpeed Insights measured first paint at 0.9 seconds with 0 ms of blocking time and zero layout shift (mobile, July 17, 2026).

Proof FAQ

Did you game your own tool?

Gaming it would show. Every point is tied to a page property anyone can inspect: the JSON-LD is in the source, the citations resolve, the dates are real, the FAQ you are reading renders from the same data as its schema markup. The audit is deterministic, so re-running it reproduces the same evidence lines, and a faked signal would show up as a contradiction between the report and the page. The dogfood also cut the other way: running the tool on ourselves exposed a real scoring bug (percent-sign statistics could never be counted), which we fixed and shipped the same day.

Can I reproduce these numbers?

Yes. Run the audit on willaicite.com and you get the same score from the same evidence; that is what deterministic means here. The independent measures are reproducible too: Lighthouse scores this page 100 in all four categories, and you can paste any page of this site into Google’s Rich Results Test or the Schema.org validator to check the structured data yourself.

Why does this matter for my site?

Because the loop that took this site from 51 to 100 is the product: audit, fix what the report flags in priority order, re-run until clean. The fix-first list is sorted by impact per effort, so the expensive-looking score usually falls to a handful of small, real changes.

Verify it yourself

Run the same audit on your site