SEO Basics for Your App: How to Get Found on Google

You've launched. Now you'd like people to find you when they search for what your app does. That's SEO — search engine optimisation. It has a reputation for being mysterious, but for a small app or product site, most of what matters is a handful of basics done properly.

This guide covers those basics — and one technical issue that quietly hides many AI-built sites from search engines.

How search engines work, in one paragraph

Search engines send automated programs called crawlers to visit web pages, read their content, and follow their links to find more pages. They store what they find in an index. When someone searches, the engine picks the most relevant, useful pages from its index. So SEO comes down to three things: can crawlers reach your pages, can they understand them, and are your pages the best answer to what someone searched?

1. Make sure search engines can read your pages

The single-page-app problem

Many AI builders create single-page apps (SPAs) — typically React apps built with Vite. When a visitor loads the page, the server sends an almost empty HTML file, and JavaScript then builds the content in the browser.

Humans never notice. But crawlers that don't run JavaScript (or don't wait for it) see an empty page. Google can run JavaScript, though with delays and limits; many other crawlers — including some that feed AI search tools — don't.

How to check: right-click your page and choose View Page Source (not Inspect). If you can't find your page's actual text in there — just an empty <div id="root"></div> — search engines may be seeing very little.

How to fix it: for the pages you want found (homepage, features, pricing, blog), use server-side rendering or static generation, where the server sends the full content. Frameworks like Next.js, Astro, Nuxt, and SvelteKit do this well. A common pattern: a server-rendered marketing site, with the logged-in app itself as an SPA (which doesn't need to be indexed anyway).

Don't block crawlers by accident

A file called robots.txt at your site's root tells crawlers what they may visit. Check it isn't blocking everything (Disallow: /).
Check your pages don't include <meta name="robots" content="noindex"> — some tools add it to preview sites, and it sometimes leaks into production.

2. Give every page a clear title and description

In each page's HTML <head>:

<title>Invoice Tracker for Freelance Photographers | Snapbill</title>
<meta name="description" content="See which clients owe you money at a glance. Track invoices, due dates, and payments in one simple dashboard.">

The title is the blue headline in search results. Make it describe the page, with the words people actually search for, under about 60 characters. Every page should have a different title.
The description often appears under the title. It doesn't directly affect ranking, but a good one gets more clicks. Around 150 characters.

A classic AI-built-app mistake: every page has the same title — often the default from a template, like "Vite + React." Check yours.

3. Structure pages clearly

One <h1> heading per page, saying what the page is about.
Subheadings (<h2>, <h3>) for sections.
Descriptive link text — "see pricing" rather than "click here."
Alt text on images — a short description of each image, for screen readers and search engines.
Clean URLs — /pricing and /blog/how-to-track-invoices, not /page?id=7.

4. Add a sitemap and tell Google about it

A sitemap (/sitemap.xml) lists all the pages you want indexed. Most frameworks can generate one automatically.

Then set up Google Search Console (free). Verify your domain, submit your sitemap, and you'll see which searches you appear for, which pages are indexed, and any problems Google found. It's the single most useful SEO tool, and it's free. Bing Webmaster Tools is the equivalent for Bing, which also feeds some AI search products.

5. Make it fast

Slow sites rank worse and lose visitors. The usual culprits in AI-built apps:

Huge images — resize them, and use modern formats like WebP.
Too much JavaScript — large bundles delay everything.
Slow hosting or no caching — a CDN helps (What Is a CDN?).

Google's free PageSpeed Insights tool measures your page and lists what to fix.

6. Set up link previews

When someone shares your link in a chat app or on social media, a preview card appears with a title, description, and image. That's controlled by Open Graph tags:

<meta property="og:title" content="Snapbill — Invoice tracking for photographers">
<meta property="og:description" content="See who owes you at a glance.">
<meta property="og:image" content="https://snapbill.app/og-image.png">

Not strictly SEO, but it makes every shared link look professional.

7. Write things worth finding

Technical SEO lets search engines read your pages. Content is what makes them rank. For a small product:

A clear homepage that says who it's for and what it does, in the words your customers use.
A page for each main use case or feature.
Genuinely helpful articles answering questions your potential customers search for.

Write for people first. Pages that answer a question well tend to do well.

A quick SEO checklist

Page content visible in View Page Source (not just after JavaScript)
robots.txt not blocking the site; no stray noindex
Unique title and description on every page
One h1 per page; clear headings
Alt text on images; clean URLs
Sitemap submitted in Google Search Console
Reasonable PageSpeed score
Open Graph tags for link previews
HTTPS on your own domain

EasySpawn runs server-rendered frameworks like Next.js as real servers — so search engines get full pages — with HTTPS on your own domain. See how it works for AI-built apps or join the waitlist.