← The AI Hype Audit — all 645 verdicts
PARTLY
Partly true: this vibe-coding SEO checklist is mostly sound and matches Google's docs, but the 60 and 160 character limits are not Google rules, and FAQ rich results were retired in May 2026
The claim'If you're vibe coding a site, ask your AI for these so Google and AI search can find it: pre-rendered HTML (not a blank JS page); server-rendered FAQ answers (in the code, not just on click); unique titles and descriptions (under 60 and 160 chars); schema markup (link your site, GBP, LinkedIn); noindex tags (hide test/draft pages); WebP images and alt text; sitemap and robots.txt (submit in Search Console).' A reply adds that FAQ answers in code are the biggest win because AI answers lift them.
This is one of the better short checklists for AI-built sites, and most of it lines up with Google's own documentation. Google's JavaScript SEO guide says server-side or pre-rendering 'is still a great idea' because not all bots run JavaScript, and that content missing from the rendered HTML cannot be indexed. That is exactly the blank-JS-page problem many vibe-coded sites have. Unique titles and descriptions, schema that links your site to your Google Business Profile and LinkedIn, noindex on test pages, compressed images with alt text, and a sitemap submitted in Search Console are all standard, correct advice. Two items are overstated. The 60 and 160 character limits are not Google rules: Google's title-link documentation says there is no limit on title length and that results are truncated to fit the device, so these numbers are display rules of thumb. And the reply's 'biggest win' framing for FAQ answers needs an update: Google stopped showing FAQ rich results in Search on May 7, 2026 and removed that documentation in June 2026. Putting real question-and-answer text in the HTML is still good for readers and AI answers, but there is no FAQ rich result to win anymore. Nothing is sold in the captured text.
What holds up
- Threads post and top reply text captured from the logged-in browser.
- Google JavaScript SEO basics read: server-side or pre-rendering recommended; unrendered content cannot be indexed.
- Google title-link documentation read: no limit on title length; truncated to fit the device.
- Google Search Central documentation updates read: FAQ rich results not shown from May 7, 2026; FAQ docs removed June 2026.
- x-ref #314 (20-item vibe-coded SEO mega-prompt).
What doesn’t
- 60 and 160 characters are display rules of thumb, not Google limits.
- FAQ rich results are gone as of May 2026; the reply's 'biggest win' is dated.
- An AI will happily claim it did all seven; you still have to verify each one.
The catch
Asking your AI for these is the easy part. Checking that it actually did them, by viewing the page source and using Search Console's URL Inspection, is the step most vibe coders skip.
How to actually do it
- After the AI builds the site, open View Source on a key page and confirm the main text and FAQ answers are in the raw HTML.
- Run the page through Search Console URL Inspection to confirm Google sees the content, and validate your schema.
- Submit the sitemap in Search Console and confirm test or draft pages carry noindex.
A solid checklist with two dated or overstated details. The real value is verifying each item, not just asking for it.
- Confidence
- High
- Posted by
- a vibe-coding creator on Threads (about 10,200 views); post sent to Buddy Sun Nov 15, 2026, 7:49 AM
We test hype for free. We build the real thing for a living.
Thirty minutes, no pitch — and you'll leave with something useful either way.
Book a call with Todd or start with the free Business Checkup →The Verdict Weekly
Three verdicts every Friday. Free forever, unsubscribe anytime, no spam — that would be ironic.
© Schreier Group · schreiergroup.com · See a wild AI claim? Drop it here and we'll test it.