You asked AI to build a page, and it did a good job. The layout is clean, the copy reads well, the buttons work. Then you share the link and get a blank gray card with a bare URL. Or you check whether it shows up in a search and it is nowhere. The page is fine. The SEO is missing, and SEO for AI-generated pages is almost always missing for the same reason: nobody asked for it.
AI models optimize for what you request. Ask for “a landing page for my app” and you get a landing page. You do not get a title tag, a meta description, Open Graph tags, or a favicon, because none of those are visible in the page itself, so they never come up. The result is a page that looks finished and is invisible to everything that reads pages for a living: search crawlers and the link-preview bots behind Slack, iMessage, LinkedIn, and the rest.
This is a quick fix. You do not need to learn SEO as a discipline. You need to know the short list of tags and content habits that matter for a simple page, and you need to ask the AI for them. This guide is that list, plus a copy-paste prompt so you never have to retrofit it again.
TL;DR
- AI builds the visible page and skips the invisible SEO tags. You have to ask.
- The essentials live in the
<head>: a real title, a meta description, a canonical URL, Open Graph and Twitter card tags with an image, and a favicon. - At the content level: exactly one H1, descriptive subheadings, alt text on every image, and semantic HTML.
- Structured data (a little JSON-LD) is an optional bonus for FAQs, articles, and products.
- None of it works until the page lives at a real, crawlable URL. A screenshot or a file on your laptop cannot be indexed or unfurled.
Why does AI skip SEO by default?
Because SEO is metadata, and metadata is invisible. When you look at a page, you see the hero, the headings, the images. You do not see the <title> the browser reads, or the <meta name="description"> Google shows in results, or the og:image that becomes your preview card. The model builds what you can see and what you described, and stops there.
There is also a reasonable-sounding default that makes it worse: AI often fills the title with something generic like “Document” or repeats your H1 verbatim, and leaves the description out entirely. That is not broken, exactly. It is just the bare minimum, and the bare minimum is what makes your page look unfinished the moment it leaves the browser.
The whole problem is solved by naming these tags in your prompt. Here is what to name.
The <head> essentials
Everything a search engine or a link-preview bot reads first lives in the <head> of your HTML. Five things belong there.
The title tag. This is the clickable blue line in search results and the text on the browser tab. Keep it under about 60 characters, lead with the thing people would actually search for, and make it specific. “Acme Invoicing, Free Invoice Generator for Freelancers” beats “Home.”
The meta description. This is the gray summary line under the title in search results. It does not directly change your ranking, but it heavily influences whether anyone clicks. Write 150 to 160 characters that describe the page and include the main keyword naturally.
The canonical URL. A <link rel="canonical"> tells search engines the one definitive address for this page, so you do not get penalized for the same content appearing at slightly different URLs. For a single published page, it is simply the page’s own live URL.
Open Graph and Twitter card tags. These control the preview card when someone shares your link. og:title, og:description, and og:image are the big three, plus their twitter: equivalents and twitter:card set to summary_large_image. The image is what turns a blank gray rectangle into a card people actually click.
The favicon. The little icon on the browser tab. A missing favicon is the visual equivalent of a typo: small, but it reads as unfinished. Even a simple SVG or a single PNG makes the tab look intentional.
Here is the difference those tags make to a shared link, before and after.
Same page. The only difference is whether the tags exist and whether the link points at something a preview bot can fetch.
What to ask the AI for
Add this to any build prompt and the model fills the head in properly:
Also add complete SEO and social metadata to the <head>:
- A <title> under 60 characters, leading with the primary keyword.
- A <meta name="description"> of 150 to 160 characters with the keyword.
- A <link rel="canonical"> set to the page's own URL.
- Open Graph tags: og:title, og:description, og:image, og:type, og:url.
- Twitter card tags: twitter:card set to summary_large_image, twitter:title,
twitter:description, twitter:image.
- A favicon (an inline SVG favicon or a linked icon is fine).
In the body, use exactly one <h1>, descriptive <h2> and <h3> subheadings,
semantic HTML (header, main, section, footer), and alt text on every image.Leave a placeholder for the og:image and canonical URL if you do not have the final link yet, then fill them in once the page is live.
Content-level SEO: the part inside the page
The head tags get you found and shared. The content decides whether you stay found. For a page built with AI, four content habits matter most.
One H1, used once. The H1 is the page’s main heading and its strongest on-page signal. AI sometimes sprinkles several, or wraps a logo in one. Ask for exactly one H1 that states what the page is, then H2s and H3s for the sections beneath it.
Alt text on every image. Alt text describes an image for screen readers and for image search. AI skips it constantly. A one-line instruction fixes it, and it doubles as an accessibility win. This overlaps heavily with making AI pages accessible and with adding images to AI pages the right way.
Semantic HTML. header, main, section, article, footer, and real heading tags give crawlers a structure to read, instead of a soup of unlabeled divs. It costs nothing and both search engines and assistive tech benefit.
Copy that answers a real question. The single biggest ranking factor is whether the page genuinely addresses what someone searched for. If you are writing the words with AI, point it at a specific reader and a specific question rather than generic filler. The patterns in writing page copy with AI apply directly.
Two more things that quietly affect ranking: speed and mobile. Google uses both as signals, and AI pages are prone to bloat, so trimming weight the way making AI pages load fast describes is SEO work too, not just performance work.
A quick word on structured data
If you want to go one step further, add a small block of JSON-LD: structured data that tells search engines exactly what the page represents. An FAQ page can mark up its questions and answers, an article can declare its headline and author, a product can state its price. Google sometimes rewards this with richer results, like the expandable FAQ entries you have seen in search.
It is optional. For most simple pages, the title, description, and Open Graph tags do the heavy lifting. If you do want it, ask the AI to “add JSON-LD structured data describing this as a [FAQPage / Article / Product]” and it will generate a valid block you can drop in.
What AI does by default, and what to ask for instead
| SEO element | What the AI does by default | Ask for this instead |
|---|---|---|
| Title tag | Generic (“Document”) or missing | Keyword-led, under 60 characters |
| Meta description | Omitted entirely | 150 to 160 characters with the keyword |
| Open Graph tags | Not included | og:title, og:description, og:image, og:url |
| Twitter card | Not included | summary_large_image with title, description, image |
| Favicon | Missing | Inline SVG or linked icon |
| Headings | Multiple H1s or none | Exactly one H1, then H2/H3 |
| Images | No alt text | Descriptive alt on every image |
| Markup | Generic div soup | Semantic header/main/section/footer |
The last piece: a real, indexable URL
Here is the part no prompt can fix. Every tag above is useless if the page does not live somewhere a search crawler and a link-preview bot can reach. A screenshot cannot be indexed. An HTML file on your laptop cannot be unfurled. A ZIP in someone’s inbox has no URL at all. The og:image you carefully set only renders when there is a live address to fetch it from.
So the final step is publishing the page at a real URL. With VisiblePage you paste your HTML or drop a ZIP and get a live link immediately, with no build step, toolchain, or domain setup. The page is served fast from the edge, which is itself a ranking signal, and every chart, button, and animation keeps working because you are sharing the real page. You can keep it public so it gets crawled and indexed, or private or password-protected while you polish, point a custom domain at it so the URL is your own, and because it is one canonical link, improving the page and re-publishing updates what everyone sees without changing the address. That matters for SEO: you build link equity at one stable URL instead of scattering versions.
The flow, start to finish:
Try it now: Publish your AI-generated HTML with VisiblePage and get a live, indexable link in seconds.
Frequently asked questions
Do AI tools add SEO tags automatically? Mostly no. AI will build a beautiful page and leave the head almost empty: no meta description, no Open Graph tags, often a generic or missing title. You have to ask for the SEO tags explicitly, which is why a short prompt block is the easiest fix.
What SEO tags does an AI-generated page actually need? A short, keyword-led title tag, a 150 to 160 character meta description, a canonical URL, Open Graph and Twitter card tags including an og:image, and a favicon. At the content level: exactly one H1, descriptive subheadings, alt text on every image, and semantic HTML.
Why does my shared AI page show a blank or ugly preview? The page is missing Open Graph tags, so there is nothing for the preview card to render, and it may not be hosted at a real URL that link unfurlers can fetch. Add og:title, og:description, and og:image, publish at a live canonical link, and the card fills in.
Can a page built with AI rank in Google? Yes. Google does not care whether a human or an AI wrote the HTML. It cares that the page is crawlable, loads fast, reads well on mobile, has a clear title and description, and answers what someone searched for.
Do I need structured data or schema markup? It is optional and worth adding for FAQs, articles, and products, where a small block of JSON-LD can earn richer results. For a basic page it is a nice-to-have. Get the title, description, and Open Graph tags right first.