Wayli

Claude on Wayli

Claude's independent review of Wayli's crawlability, content, trust evidence and citation viability.

5 min

Review status

  • Published
  • Original prompt included
  • Original response included
  • Findings reviewed
  • Improvements documented where evidenced

Next scheduled review: January 2027

Reviewer
Claude
Review date
30 July 2026
Purpose
Independent external review
Source record
Prompt and response published
Editorial treatment
Formatting changes only
Status
Published and reviewed

Why we publish independent AI reviews

We use independent AI systems as external reviewers of Wayli.

Every review is published in full, including criticism. Where several independent reviewers identify the same issue, we treat that as evidence rather than opinion.

The objective is continuous improvement, not validation.

Consensus

Across the review series, multiple reviewers independently identified:

  • Strong transparency and information architecture
  • A distinctive preparation-first philosophy
  • Homepage and audience clarity as recurring opportunities
  • The need for growing external authority

Claude on Wayli

Verdict

Claude's review was commissioned to test whether Wayli's public pages could be acquired and understood after the site moved beyond a client-side React shell. Claude is distinctive here because the review combined direct retrieval with pasted crawler evidence and then separated technical acquisition from content and trust.

The review concluded that the JavaScript-shell problem had been resolved at an architectural level. It found semantic HTML, working internal links, canonical metadata, structured data, an open robots policy and a substantial sitemap. It then scored Wayli 76/100 against the platform's five assessment categories. Trust was the strongest category; audience clarity was the weakest.

Claude also drew an important boundary between technical crawlability and real-world citation. A site can be available to AI systems without yet having the external authority or search visibility required to be cited regularly.

AI Readiness

Ready to see how AI understands your own website?

Start with a free AI Readiness Assessment from Wayli and receive:

  • Overall AI Readiness score
  • Five evidence-based category scores
  • Your strongest area
  • Your biggest opportunity
  • Practical recommendations to improve AI understanding
→ Start Free Assessment

At a Glance

| | | |---|---| | Reviewer | Claude | | Overall Score | 76 / 100 | | Primary Focus | Crawlability, content and trust | | Strongest Area | Crawlability and trust evidence | | Biggest Opportunity | Audience clarity and external authority |

Highlights

  • Confirmed that meaningful semantic HTML was available without JavaScript execution.
  • Found consistent crawlability across multiple page templates.
  • Rated trust evidence as Wayli's strongest assessment area.
  • Identified the absence of an explicit audience statement as the clearest content gap.
  • Distinguished technical accessibility from search indexing and citation likelihood.
  • Noted that external references and authority signals would matter more than further technical polish.

What changed?

  • ✓ Prerendered semantic HTML retained in the production architecture.
  • ✓ Evidence acquisition separated from understanding and citation.
  • ✓ Audience wording reviewed across AI Readiness.
  • ✓ External authority retained as an area for further work.

Original Review

The original prompt and complete response are published below. Nothing has been selectively removed or rewritten; only Markdown formatting has changed for readability.

Wayli.uk — Independent Review

Conducted by Claude, via direct fetch and pasted curl evidence, across a multi-stage conversation. Reviewed July 30, 2026.

Part 1 — Crawlability Audit

Starting point

The site was initially served as a client-side rendered React app. Fetching the homepage returned only <head> metadata — no body content, no headings, no links. This is consistent with the "acknowledged but not crawled" status reported in Google Search Console at the time, and would have made the site invisible to non-JS-executing AI crawlers (ClaudeBot, Claude-User, Claude-SearchBot, GPTBot, PerplexityBot).

After the fix

Following a prerendering deploy, both pasted curl output (curl -A "ClaudeBot" ...) and Claude's own independent web_fetch calls confirmed:

  • Real, semantic HTML delivered without JavaScript execution — <header>, <nav>, <main>, <h1>, body copy, <footer>
  • Consistent structure across multiple templates (homepage, /ai-readiness product page, /explore, /about, /trust)
  • Correct, self-referencing canonical tags on every page checked
  • Valid JSON-LD structured data (Organization, WebSite, Person, SoftwareApplication, BreadcrumbList), varying appropriately by page type
  • A valid, well-formed robots.txt (User-agent: *, Allow: /, sitemap directive) with no blocks on relevant bots
  • A valid, well-formed sitemap.xml listing 89 URLs across a genuine content architecture (methodology pages, support pages, guides, Labs journal, topic taxonomy)
  • Real internal navigation via proper href attributes, not JS-only click handlers

Conclusion

The JS-shell problem is resolved. The fix appears applied at the architecture/build level rather than patched per-page, based on consistency across two structurally different templates. Nothing found would materially block Googlebot, Claude-User, ClaudeBot, Claude-SearchBot, GPTBot, or PerplexityBot from acquiring and understanding the site's public content.

Minor, non-blocking notes

  • No <lastmod> in sitemap.xml — optional, but would help crawlers prioritize re-crawls
  • Inconsistent URL encoding style between Labs slugs (raw apostrophes, e.g. isn&apos;t) and topic tags (%20-encoded spaces) — cosmetic only
  • "Decision Engines" exists only as a Labs topic tag (/labs/topics/decision%20engines), not as a dedicated landing page — worth a deliberate decision on whether it deserves parity treatment with AI Readiness (own header, nav, schema) as a category/hub page

Part 2 — Content & Trust Assessment

Scored against Wayli's own five-category framework (Who You Are / What You Offer / Who You Help / Why You're Trusted / Added Value), based on direct review of the homepage, /ai-readiness, /explore, /about, and /trust.

| Category | Score | Basis | | ------------------ | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Who You Are | 16/20 | Strong, distinctive founder narrative (journalist background, consistent framing). Missing: legal entity name, registration details, team beyond one named founder | | What You Offer | 15/20 | Three financial tools + AI Readiness clearly named and linked with plain-English descriptions. Actual tool output/example reports not independently verified | | Who You Help | 12/20 | No explicit audience statement found. UK-focused, finance-curious audience is inferable from topic choice but not stated outright — matches Wayli's own self-rated weak point | | Why You're Trusted | 17/20 | Strongest area. Thorough Trust Centre, dated review line, dedicated AI Transparency page distinguishing deterministic systems from AI-generated content. Missing: third-party validation (press, testimonials, usage numbers) | | Added Value | 16/20 | "Prepare Before You Prompt" framing and build-in-public Labs journal are genuine differentiators; free/no-signup positioning stated consistently |

Total: 76/100

Part 3 — Citation Viability

Technically: no reservations. Content is clean, crawlable, well-structured, and correctly marked up.

In practice: citation in a live AI answer depends on search index inclusion and ranking at query time, not just crawlability — these are separate problems. As a new domain with likely few inbound links, indexing and citation-worthy visibility will take real time (plausibly weeks) even with the technical fix in place. Backlinks and external signals will matter more than further technical polish from here.

Honest framing: the site itself describes AI Readiness as still developing and its assessment preview as "illustrative." That's accurate, appropriately transparent positioning for an early-stage project — not a weakness, but worth knowing that an AI reading the site today would characterize Wayli as early-stage rather than an established authority.

Original Prompt

I'd appreciate a second opinion about wayli.uk from a user and ai perspective, especially what it could do better, and in order of priority.

Outcome

Independent review is most useful when its evidence, assumptions and criticism remain available for scrutiny. No single reviewer defines Wayli. Preserving the complete record makes agreement, disagreement and change visible over time.