3
2 Comments

built a free tool to generate your JSON-LD files and keep them automatically updated

LLMs web crawlers love JSON-LD files so we've built Lens AI -website's here- to help everyone index their website/content and generate all the files and more importantly then: keep them up-to-date every time you update your content.

Feel free to check it out, it's free for now - feedback/questions/comments much welcome.

on August 30, 2026
  1. 1

    Congrats on shipping. Disclosure up front: I do landing page critique, so read this as a peer note rather than a customer one.

    You asked for feedback, so here is the most expensive thing I found, and it is not on the page. It is the gap between this post and the page. This post says: a free tool that generates your JSON-LD files and keeps them updated. The page says: "One source of truth. Every AI tool that mentions you." The words JSON-LD, structured data and schema do not appear anywhere in the page's visible text. So someone who clicks through from here is looking for the thing you just described and finds a knowledge layer instead. Either the JSON-LD part belongs near the top of the page, or this post should pitch the knowledge layer. Right now they describe two different products.

    The page itself is structurally as clean as they come: one button repeated everywhere, public pricing with a real free tier, an FAQ that answers the training-data question with a flat no. Keep all of that. Three things a checklist cannot see:

    There is no proof anywhere. Not one customer name, quote or number on the whole page. The only numbers a visitor sees are the dashboard mock's own: "Welcome back, John", 20.8k queries. For a product that asks a company to make you the source of truth for everything AI says about them, that is the whole objection. One named pilot or one founder-signed line under the hero button beats another paragraph of positioning.

    The hero subhead is four sentences and 45 words, six lines on a phone, sitting between the headline and the button. Your four use-case cards further down are the most concrete writing on the page. Cut the subhead to two lines and let those four labels carry the specifics.

    Your chat pill sits on top of your own product screenshot, on desktop and on mobile. On desktop it covers the middle metric card, so "Average Time to First Token" has no value under it. That pill is your own widget, lens.js, which makes it the only live demo on the page. Do not delay or hide it. Move it, or the screenshot, so both are readable, and label it so people know the thing answering them is the thing you sell.

    One more: "No credit card required" and "in a few minutes" are both already on your page, in the closing band and in FAQ item six. Put them under the hero button, where the decision happens.

    I ran our full teardown on your page and published it, free, nothing owed: https://squint.page/sample-16/ The proof and subhead points are worked through with exact rewrites there.

  2. 1

    The auto-update part feels more valuable than the initial JSON-LD generation.

    Curious whether keeping structured data accurate over time is the problem users actually struggle with, or whether discovery/generation is still the bigger pain.