FREEFirst project with us? Your landing page design is on the house.See the offer

Chapter 3 of 6

SEO basics most AI-built sites miss

Seven basics, what good looks like for each, and a fix order.

6 min readUpdated 2026-11-16
All chaptersChapter 3 of 6
  1. 01What AI builders get right and what they leave out
  2. 02The 20 minute check: can Google and AI assistants read it?
  3. 03SEO basics most AI-built sites miss
  4. 04Speed and phones
  5. 05Fix in place, render on the server, or rebuild
  6. 06Moving to the new site without losing traffic

The short answer

Seven basics cover most of the gap: a title per page, a description per page, one clear H1, a sitemap of real URLs, a robots.txt that lets crawlers in, a canonical URL on each page, and schema plus a social image where they fit. Each one must be in the first HTML, not added by a script after load. None of it is advanced. It is just easy to skip when a tool builds the page from a prompt.

Fix them in that order. Titles and descriptions change what people see in search results today. The rest helps search engines find and understand your pages.

1. A title for every page

Google uses the title element as a main source for the title link in search results. Its title link guidance asks for distinct text that describes each page, warns against repeated boilerplate, and says to brand titles concisely.

PageWeakBetter
HomeKookiesKookies: cookie boxes for teams and events
PricingKookiesPricing: cookie boxes from 12 to 500 | Kookies
Blog postKookies | BlogHow to plan treats for a 200 person offsite | Kookies

The examples use a made-up cookie shop. Write yours the same way: what the page is, then the brand. If you rebuild in Webflow, its help page on SEO titles and meta descriptions says SEO settings apply only to the page they are set on, and suggests keeping titles under 60 characters. Our free meta tag tool writes the tags and previews them.

2. A description for every page

The meta description does not change rankings much, but it can change what people read under your title. Google's snippet guidance says it mostly builds snippets from the page content, uses the description when it describes the page better, and that identical or similar descriptions on every page are not helpful.

  • One to two plain sentences that say what the page offers and who it is for.
  • Different on every page. Site-wide text suits the home page only.
  • True to the page. A promise the page does not keep loses the click later.

3. One H1 and headings in order

AI tools often pick heading tags for their size, not their meaning. You end up with three H1s on one page, or an H4 straight after the H1 because it looked right. Screen readers and crawlers use headings to understand the page.

  • One H1 per page that says what the page is.
  • H2s for the main sections, H3s inside them. No skipped levels.
  • Size is a style choice. Change the look in CSS, not the tag.
  • Headings as text, not inside images.

Answer-first headings help AI answer tools too. Our AEO Readiness Guide covers how to write them.

4. A sitemap and robots.txt

Google's sitemap overview says you may not need a sitemap if your site has about 500 pages or fewer and every important page is linked from your home page. It also says a sitemap does not guarantee that every listed page is crawled and indexed. Add one anyway: it costs nothing, and it is how you tell Google about new URLs after a move.

  • Lists only real, final URLs on your real domain, with the same form as your canonical URLs (trailing slash or not).
  • Updates itself when you publish. Webflow can auto-generate one and update it on every publish. On Astro, the sitemap integration lists statically built pages; it cannot list dynamic routes rendered on demand, so add those yourself.
  • Named in robots.txt with a Sitemap: line, and submitted in Search Console.

Remember that robots.txt is not a way to keep a page out of Google. Use noindex or a password for that. Our post on what to put in an XML sitemap goes into detail.

5. A canonical URL on each page

The same page can often be reached at more than one address: with and without www, with tracking codes, on the tool's own preview domain. A canonical tag tells search engines which one you mean. Google's duplicate URL guide treats it as a signal, not a command, recommends absolute URLs over relative ones, and says the best place for it is the HTML source.

  • Every page has <link rel="canonical" href="https://www.yoursite.com/page"> pointing to itself.
  • The preview or tool domain redirects to your real domain, or is kept out of the index.
  • Sitemap, internal links and canonicals all use the same form of each URL.

6. Schema and social images

Schema, structured data in JSON-LD, describes the page to machines: your organisation, a product, a set of FAQs, a breadcrumb trail. Google's structured data policies say it must be a true representation of the page, must not describe content readers cannot see, and does not guarantee a rich result. Read any schema a tool generated. Check every rating, address and founder name against the facts, and delete what is not true.

Social images decide what shows when someone pastes your link into Slack, LinkedIn or a chat app. The Open Graph protocol lists four required properties: og:title, og:type, og:image and og:url. Give each page its own image where you can. Our free schema generator writes JSON-LD, and our post on social images per page shows a simple system.

A fix order you can follow

#FixProof it worked
1Unique title and description on every pageView source on 3 pages shows 3 different titles
2One H1, headings in orderEach page has one <h1> in the source
3Real links in the menu and footerSource shows <a href for each item
4Sitemap on the real domain, named in robots.txtSearch Console reads the sitemap without errors
5Canonical on every page, preview domain handledURL Inspection shows your URL as the Google-selected canonical
6True schema where it fitsRich Results Test reads it with no errors
7Social image per pageLink pasted into a chat app shows the right image

Decision rule If your tool can only set titles and descriptions with a script after load, that is a rendering problem, not an SEO settings problem. Go to chapter 5.

Takeaways

What to remember from chapter 3.

  • Titles and descriptions per page come first. They change what people see in search today.
  • Every basic must be in the first HTML, not added by a script after load.
  • One H1 per page. Pick heading tags for meaning and change size in CSS.
  • A sitemap of real URLs, a robots.txt that lets crawlers in, and a canonical on every page.
  • Generated schema must be true to the page. Check every fact and delete what is not.

Your turn

Let's kook
what you krave.

Hi Kookies, I need a built on . I'd love to launch . Reach me at
or book a callSent. We reply within one working day.