SEO basics for makers who would rather build

SEO basics for a small app means making sure that when someone searches for the problem you solve, a clear page of yours shows up and makes sense. In practice that is five things: a unique title, an honest description, plain headings, one focused page per topic, and pages that load fast and a crawler can read. That is most of it.

What does SEO actually do for a small app?

SEO gets your page in front of someone at the exact moment they are looking for what you built. That is the whole job. You spent weeks on the product. Then it sits at a URL nobody types and a search nobody connects to it. SEO closes that gap so the person already typing your problem into Google lands on you instead of bouncing off a competitor or a Reddit thread.

Here is the part that stings if you skip it: this is happening right now, every day, whether or not you have done anything. People are searching for what you do. Today those searches are going to other results. The cost of ignoring SEO is not a future risk, it is current traffic you are not getting. You do not have to win every search. You have to be findable for the few that describe your app precisely.

What are the few SEO basics that matter most?

For a small app, five basics carry almost all the weight. Get these right and you are ahead of most indie projects, which ship with a default title like "Vite App" and no description at all.

1. 1.Give every page a unique, specific title tag. This is the clickable headline in Google. "Invoice generator for freelancers" beats "Home". One sentence, says what the page is.
2. 2.Write an honest meta description for each page. It does not change ranking much, but it is the snippet under your title, and a clear one earns the click.
3. 3.Use real headings (H1, then H2s) that match how people ask. One H1 per page. Headings are how both readers and crawlers skim what a page covers.
4. 4.Keep one page per topic. Your pricing lives on one page. Your main use case lives on one page. Do not scatter the same idea across five half-pages.
5. 5.Make sure the page is crawlable. The text should be in the HTML, not locked behind a click or a login, so a search engine can actually read it.

Why is one clear page better than ten thin ones?

One clear, deep page beats ten thin ones because search engines and AI tools both reward the page that fully answers a question, and they get confused when several of your pages compete for the same one. Ten shallow pages on near-identical topics split your effort and split whatever authority you have. They also leave every visitor with a half-answer.

Think about it from the searcher's side. Someone asks "how do I add Stripe to my app". The page that walks through it start to finish, with the gotchas, is the one they stay on and link to. A thin page that restates the question and trails off is the one they leave. Depth is not padding. It is answering the follow-up questions before the reader has to go ask them somewhere else.

This is also the hardest thing to judge about your own writing, because you already know the answer. You wrote three sentences and your brain filled in the rest. A first-time reader cannot. If you want a second opinion on whether your pages actually land for someone who has never seen your app, that blind spot is exactly what an outside review is for.

How does technical health affect being found?

Technical health decides whether your good content ever gets a fair shot. A page that loads slowly, breaks on a phone, or hides its text from crawlers can have perfect copy and still lose. Search engines treat speed and mobile usability as ranking signals, and they cannot rank text they cannot read.

• ▸Speed: a page that takes several seconds to show anything loses visitors before they read a word, and search engines notice the bounce. Compress images and avoid loading huge scripts on the first paint.
• ▸Mobile: most searches happen on phones. If your layout overflows, buttons are tiny, or text needs pinching to read, you are quietly losing the majority of traffic.
• ▸Indexable pages: if your content only appears after JavaScript runs or after a login, a crawler may see a blank page. Make sure the words a searcher needs are in the HTML that loads.
• ▸One canonical URL: pick whether you live at example.com or www.example.com and redirect the other, so you are not splitting credit between two addresses.

How does SEO connect to being found by AI tools?

The same clarity that helps Google is what gets you quoted by ChatGPT, Claude, and Perplexity. AI tools read the open web to answer questions, and they favor pages that state things plainly, answer the question directly, and structure the page so a passage can be lifted out and trusted. Good SEO and good AI visibility are not two projects. They are mostly the same project.

The overlap is large: clear titles, direct answers near the top, real headings, and pages that load as readable HTML. There are a few AI-specific moves on top of that, like a plain-English file that tells assistants what you do. We cover the dedicated steps in how to get your app recommended by ChatGPT and Claude and the specific file in what is llms.txt and does my app need one. If you only do the SEO basics here, you are already most of the way to being AI-readable too.

One more lever sits at the intersection: independent mentions. When a third party writes about your app in clear language, that content can be found and cited by both search engines and AI tools, and it carries a trust your own marketing page cannot. That is part of why reviews help AI find and recommend you, especially when you are new and have no track record to point to yet.

What is a realistic first SEO checklist?

A realistic first checklist is short enough to finish in an afternoon. Do these in order, ship, and move on. You can always come back when you have real traffic to learn from.

1. 1.Give your homepage and top three pages unique, specific titles and honest descriptions.
2. 2.Make sure each page has one clear H1 and a few H2s that match how people would ask about it.
3. 3.Run your site on your phone and on a slow connection. Fix anything that overflows, breaks, or stalls.
4. 4.Check that your content is in the HTML. Search "site:yourdomain.com" on Google and see if your pages show up.
5. 5.Add a sitemap.xml and a robots.txt that lets crawlers in. Most frameworks and hosts can generate these for you.
6. 6.Write one genuinely useful page for the main thing people search before they would ever search your brand name.

What SEO advice can a small maker safely ignore?

Most of the advanced playbook is safe to ignore until you have traffic worth optimizing. A lot of SEO content is written for large sites with teams, and applying it to a brand-new app is wasted effort. You can skip these for now.

• ▸Obsessing over keyword density or stuffing phrases. Modern search and AI tools penalize this. Write for a human and name things plainly.
• ▸Buying backlinks or running link schemes. At best a waste of money, at worst a way to get your site demoted.
• ▸Chasing dozens of low-volume keyword pages before you have a single strong page. Depth first.
• ▸Daily rank tracking and elaborate dashboards. You have no traffic to interpret yet. Check in monthly at most.
• ▸Technical micro-optimizations like shaving a few milliseconds when your real problem is a blank crawl or a missing title.
• ▸Long, AI-generated articles padded for word count. They read thin, and both Google and AI tools increasingly recognize that.

The honest summary: nail the five basics, write one deep page that actually helps, make sure a crawler can read it, and ignore the rest until you have numbers to act on. SEO for a small app is less about clever tactics and more about not being invisible by accident. If you want a second set of eyes on whether your pages are clear to a stranger and findable in the first place, that is the kind of thing an outside review catches fast.