Learn/SEO and AEO
Video article · SEO and AEO

Check your AI-built website with view source before Google skips it

Some AI-built sites are a small piece of JavaScript that crawlers can't read. Right-click, view source and see whether your real words are in the page.

Rob SatromPublished November 15, 2026 · 5 min read
Quick answer

Right-click your site and hit view source. If your words aren't in there, Google may see nothing. Some AI-built sites are just a small piece of JavaScript, and crawlers skip over them. Check yours, and if the page is empty, switch to server-side rendering.

0:31Watch the videoWhy Google Can Skip AI-Built Websites

We made a short video on this tip. This article explains what's happening, how to run the check and what to do about it.

What a crawler sees

When you open a website, your browser builds the page on your screen. You see headlines, photos and buttons. A search engine crawler has a harder job. It requests the page and reads what comes back.

If the page comes back with your words in it, great. If it comes back with a nearly empty shell and a bundle of JavaScript that builds the words later, the crawler may not wait or may not run the code. It sees a little piece of JavaScript and moves on.

Why AI-built sites are prone to this

Many quick website builders and vibe-coding tools publish what's called client-side rendering. The page is assembled in the visitor's browser. It looks fine to a person. To a crawler, it can look empty.

I've seen it with sites built by AI tools. The owner is proud of the design, but search engines skip over the site. And answer engines, the AI tools that quote sources, have the same problem. If they can't read it, they can't quote it.

The two-minute check

You don't need to be technical.

  1. Open your homepage in a browser.
  2. Right-click anywhere and choose view source.
  3. Look for your actual headline and a few sentences from your page.
  4. Use the search shortcut and type a phrase from the page.

If your words show up in the source, a crawler can read them. If you find mostly code, scripts and almost no text, you have a rendering problem.

Check a few pages, not just the homepage. Service pages and blog posts matter most.

The fix: server-side rendering

Server-side rendering means the server sends a complete page with your words already inside. A crawler gets everything on the first request. A visitor sees the same page, just as fast.

Ask your builder or your platform one question. Do you support server-side rendering or pre-rendering? Some platforms have added it. When yours does, standard search and answer-engine best practices start to work, like clear headings, titles and descriptions.

Other checks to run

View source is the first test. Three more help.

  • Search your own words in quotes. Take a unique sentence from your page and search it. If it's indexed, it may show up.
  • Check your title and description. They should be in the source too.
  • Look at Search Console. It can show whether pages are indexed and what Google found when it fetched them.

If pages aren't indexed after a few weeks, the rendering problem is a prime suspect.

A worked example

This one is made up. A contractor builds his site with an AI tool over a weekend. It looks great. Months later, he searches his own company name and barely shows up. He right-clicks, views source and finds one small block of code and no text. He asks his platform about rendering. They enable server-side rendering, and he republishes. Now view source shows his headline, his services and his towns. Over the following weeks, his pages start getting indexed.

Why this matters for AI answers too

People now ask AI tools for recommendations, and those tools read web pages to build answers. If your page is an empty shell to a crawler, the AI has nothing to quote. A plain, readable page with clear headings and direct answers is more likely to be understood and used.

So this isn't only about the old search results. Fixing rendering helps you show up in both places. Clear text in the source, real proof on the page and direct answers near the top all work together.

Questions to ask your builder

If view source looks empty, don't guess. Ask these.

  1. Does my site use client-side rendering, server-side rendering or pre-rendering?
  2. If it's client-side, can you switch it on for my pages?
  3. Can I see my page source with all the text in it after the change?
  4. Will titles, descriptions and headings show in the source?
  5. How do I republish, and how long until crawlers see the update?

A good builder answers in plain words. If you get a vague answer, ask again or get a second opinion. This is a basic fix, not a luxury.

The mistake to avoid

The mistake is judging a site by how it looks. A site can be beautiful and invisible. Always check what the crawler sees, not just what you see.

What to do if you built it yourself

Plenty of owners build their own site with an AI tool, and that's fine. Just don't treat publish as the finish line. Treat it as the point where you start checking.

Spend ten minutes after every major update. View source, search a sentence from the page and confirm the title shows. If you use a tool that publishes new pages often, repeat the check on new pages. A habit of checking beats a surprise three months later when you notice nobody finds you.

Your Monday-morning list

  • Right-click your homepage and view source.
  • Find a sentence from your page in the code.
  • Repeat on a service page and a blog post.
  • Ask your builder about server-side rendering.
  • Check Search Console for indexed pages.

Not sure what Google sees on yours?

Book the $99 audit call, and I'll check it and give you your top three fixes. Book here: https://www.feedbackwrench.com/book

Questions people ask

Why doesn't Google show my AI-built website?

Some AI-built sites are client-side rendered. The page is a small piece of JavaScript that builds the content in the browser, and a crawler may see almost nothing. If your real words aren't in the source, search engines and AI answer tools have little to read.

How do I check what Google can see?

Right-click your site and choose view source. If your headline, paragraphs and links are in there, a crawler can read them. If it's mostly empty code, you have a problem.

What is server-side rendering?

It means the server sends a full page with your words already in it, so crawlers get everything on the first request. It's the fix for sites that look empty in view source.

Do I need to rebuild my site?

Not always. Ask your builder or platform whether it supports server-side rendering or pre-rendering. Some platforms added it, and then standard search and AI optimization practices work.

Rob Satrom
Rob Satrom, owner of Feedbackwrench

Rob built Feedbackwrench and Nuance Financial Tax & Accounting. Since 2015, our team has helped transform 550+ small businesses with marketing, strategy and systems.

Your next step

Want a second set of eyes on your marketing?

Book the $99 Sales & Marketing Audit. It's one live call with a scored look at your marketing and your top three fixes, in order. If nothing's broken, we'll tell you that too.