Guides
Plain answers to the questions that stop people: being found, what it costs, and everything around the AI that nobody explains.
Being found
Why your AI-built site is not showing up on Google
Four causes, in the order they actually happen, and how to tell which one is yours.
02How to check whether search engines can see your site
Four checks, no tools, about five minutes. Do them before you write a word of content.
03Lovable and SEO: what goes wrong and what actually fixes it
The specific reason Lovable sites struggle in search, and the honest set of options.
04What a sitemap is, and why your builder probably has not made you one
The list of addresses that tells search engines your pages exist. Two minutes to check.
05Titles and descriptions, in plain words
The two lines that decide whether anybody clicks. Most AI-built sites get both wrong.
06Getting found when people ask ChatGPT instead of Google
Ranking and being quoted are two different jobs now. What the second one needs.
07Why sites built in Ura can be found
Not a feature. Just what happens when the output is ordinary code, deployed properly.
What it costs
Why AI app builders sell credits, and what it does to your project
Credits are not a pricing quirk. They are the shape the business has to take, and they change how you build.
02What AI app builders really cost for a finished project
The advertised price, the part that is not on the pricing page, and how to work out your own number.
03Building with the AI subscription you already pay for
What changes when nobody is standing between you and the model.
04The real bill for keeping something online
Building has a price that stops. Running has one that does not. Here is where it comes from.
05What 0% markup on AI actually means
A specific, checkable claim, not a slogan. Here is exactly what it does and does not cover.
06What Ura charges for, and what it does not
The whole commercial arrangement on one page, including the parts that are not flattering.
The engine, and everything around it
How to put a Claude Code project on the internet
The step nobody explains: you have built the thing, and it only exists on your laptop.
02Giving an app you built with AI a real database
The point most projects stall at, and the four questions that decide the bill.
03Pointing your own domain at an app you built with AI
What actually happens, why it takes an hour to settle, and the one rule about whose name it is in.
04Claude Code for people who do not write code
What it is genuinely good at, what it leaves you holding, and whether the terminal matters.
05Claude Code, Codex, Kimi and Qwen, compared for non-developers
Four engines, one question that matters: how quickly do you reach a first prompt, and what does it cost?
06What Claude Code costs, and what it does not cover
The subscription is one line. Here are the three that come after it.
07Sending email from an app you built yourself
Why the first one lands in spam, and the three records that stop it happening.
08Keeping a live app up to date without a deploy button
Why the version online drifts months behind the one on your laptop, and what to do about it.
Building well
What to build first, if you cannot code
The projects that finish, the ones that stall, and why the difference is not difficulty.
02How to describe what you want so the AI builds the right thing
The skill that replaces coding is being precise about outcomes. Here is what that looks like.
03Do you actually own what you build with an AI tool?
Three questions to ask of any platform before you build something that matters on it.
04Backing up something you built yourself
Three copies, and the one thing that must never be in any of them.