SEO and GEO for No-Code Websites

There's a particular kind of quiet that follows launching something.

You've built the thing. It works. You've clicked through it a dozen times and it holds up. You put the link somewhere, and then… nothing much happens. A few visits from people you told directly, and after that, silence.

This is completely normal, and it's not a sign that anything is wrong with what you made. Being built and being found are two different jobs, and only one of them is finished.

The second job used to be genuinely technical — files to edit, tags to write, things you'd need a developer for. Most of that is now handled for you. Which is good news, but it comes with a catch: because it's invisible, most people don't know what's being taken care of, what's missing, or what's still sitting on their plate.

For most of the internet's life, getting found meant one thing: ranking on Google. Someone types a question, they get ten blue links, you want to be one of them. That's SEO — search engine optimisation.

That's still true, and still important. But there's now a second thing happening alongside it. People increasingly ask an AI assistant instead of a search engine. They don't get ten links — they get an answer, sometimes with a recommendation attached. Making sure your site is understood and mentioned in those answers has picked up its own name: GEO, generative engine optimisation.

The two overlap a great deal. Most of what makes a site legible to Google also makes it legible to an AI assistant. Search engines want to know what your page is about, so they can rank it against other pages. AI assistants want to know what your site does, so they can describe it to someone who asked. One is about matching a query. The other is about being able to explain you to a stranger.

If you built on a modern no-code platform and connected a proper domain, a lot of the technical groundwork is already done. You should still check — platforms vary, and some of this only kicks in on paid plans or custom domains — but this is the usual list.

Everything above is plumbing. Plumbing being sorted is necessary, but it isn't what gets you found. This next part is.

An automatically generated title tells a search engine your page exists. A written one gives someone a reason to click it.

Title: roughly 50–60 characters. Put the important words near the front. Say what the page is, not what it's called internally. Description: roughly 150–160 characters. This doesn't affect ranking directly, but it heavily affects whether anyone clicks. Write it like an invitation.

A useful test: read your title and description on their own, with no context. Would a stranger know what they'd get?

Headings aren't styling. They're structure, and both search engines and AI assistants lean on them to work out what a page is about.

One H1 per page — the main subject. H2s for main sections, H3s beneath them. Use them in order, don't skip levels. Write them descriptively: "How pricing works" beats "Details".

The temptation in a visual builder is to pick a heading because it's the right size. Pick it because it's the right level, then adjust the size separately.

This is where SEO and GEO converge hardest. Search engines rank pages that answer the question someone asked. AI assistants quote and recommend sources that state things clearly and specifically. Both reward the same thing: content that says something useful in plain language.

Answer the question directly, near the top, before the context and caveats. Use the words people actually use, not your internal vocabulary. Be specific: "We help businesses grow" is unquotable, while "We train non-technical teams to build their own internal tools" can be repeated by an assistant to someone who asked. Include the concrete details — where you operate, who it's for, what it costs, what it doesn't do.

That last point is underrated for GEO. An assistant can only recommend you accurately if the specifics exist somewhere in writing.

Give every image alt text. It describes the image for people using screen readers, and tells crawlers what the image shows. Describe it plainly, and skip "image of" — it's already implied.

Watch your own speed. Platforms optimise a lot, but they can't save you from a 4MB photo uploaded straight from a phone. Resize images before uploading; nothing on a web page needs to be 4000 pixels wide. Be sparing with heavy embeds — videos, maps, chat widgets — since each one costs loading time. Test on a phone on mobile data, not on your laptop on office wifi.

Check your navigation is really links. If you've customised it, make sure the menu items are genuine links to genuine addresses, not boxes that swap content on the same page. The tell: click a menu item and watch the address bar. If it doesn't change, that page effectively doesn't exist as far as search engines are concerned.

Not very much, for a while.

Search engines take weeks to properly discover and assess a new site, and longer to rank it for anything competitive. AI assistants work on their own timelines too. This is the part where most people conclude it isn't working and stop.

A more realistic picture: in weeks one and two, pages start getting indexed and Search Console will show you. Over months one to three, you'll appear for very specific searches — your own name, unusual phrases, narrow questions. From month three, broader terms become possible, mostly on the strength of how much genuinely useful content you've published.

The uncomfortable truth is that the checklist above is the easy 20%. The other 80% is writing things worth finding, repeatedly, for longer than feels reasonable. But the checklist still matters — because without it, even good content sits invisible.