AI SEO for Beginners: A Step-by-Step GEO Tutorial

AI SEO is the practice of making a website easy to discover, understand, verify, and cite in AI-generated answers. Start with ordinary technical SEO, then clarify your brand entity, publish useful first-hand content, support claims with evidence, and measure mentions across answer engines. This tutorial turns those principles into a practical 30-day workflow for beginners.
What will you build with this AI SEO tutorial?
By the end of this guide, you will have a small but complete AI visibility system: a technical access check, one consistent brand statement, a map of real buyer questions, one answer-first page, accurate structured data, an internal-link plan, a list of third-party sources to pursue, and a weekly measurement sheet.
This is not a separate replacement for SEO. Google says its existing search fundamentals still apply to AI Overviews and AI Mode, and that no special AI file or markup is required. GEO and AEO add a useful operating layer: they ask whether a retrieved passage is clear, distinctive, supported, and easy to attribute after a search or answer engine finds it.
| Term | Practical meaning | Primary outcome |
|---|---|---|
| SEO | Help search engines crawl, index, understand, and rank pages | Qualified organic visits |
| AEO | Shape content so an answer system can resolve a question clearly | Answer inclusion and clicks |
| GEO | Improve how a brand and its evidence appear in generative answers | Mentions, citations, and assisted conversions |
Treat the labels as overlapping disciplines, not competing religions. The durable work is the same: build pages that people value and machines can retrieve without guessing.
Step 1: Record an AI visibility baseline before changing anything
A baseline prevents a common mistake: publishing for weeks without knowing whether the work changed discovery, citations, branded search, or conversions. Choose 10 questions a genuine prospect might ask before buying. Include problems, comparisons, alternatives, pricing, implementation, and risk.
For each question, test the AI surfaces your audience uses. Record the date, engine, whether your brand appeared, whether your site was cited, the competitors mentioned, and the cited URLs. Results can vary by location, account, model, and time, so treat one answer as an observation rather than a permanent rank.
| Field | Example |
|---|---|
| Buyer question | What is the best AI visibility tool for a small SaaS team? |
| Engine and date | ChatGPT Search, 2026-08-02 |
| Brand mentioned? | Yes / No |
| Domain cited? | Yes / No |
| Competing brands | Brand A, Brand B |
| Sources cited | Exact URLs, not only domain names |
| Next action | Improve comparison page or pursue missing source |
Run a free AI visibility check for a fast technical and content baseline, then keep the manual query sheet. A single score is useful for diagnosis; the query-level history tells you whether visibility is improving for questions that can create revenue.
Step 2: Define the entity you want answer engines to understand
An entity is the identifiable thing behind the page: your company, product, person, or service. Write one factual sentence that names your category, audience, primary job, and genuine differentiator. This is a positioning constraint, not a slogan.
Use this formula:
[Brand] is a [specific category] for [audience] that [primary job], distinguished by [verifiable difference].
Then make the core facts consistent across your homepage, About page, product page, social profiles, directory listings, and press material. Keep the official name, URL, logo, description, founder details, contact address, pricing facts, and social links aligned. Consistency does not mean repeating the same paragraph everywhere; it means not presenting contradictory facts about the same entity.
Copy-and-use prompt
Using only the facts below, write five factual entity statements for my company.
Each sentence must name the category, target customer, primary job, and one
verifiable differentiator. Do not invent awards, customer counts, performance
claims, or superlatives. Facts: [paste your verified facts].
Step 3: Make your important pages crawlable and indexable
AI visibility starts with access. Confirm that each important public page returns HTTP 200, has a self-referencing canonical URL, appears in the XML sitemap, is not marked noindex, and can be reached through an ordinary HTML link. Important content should be available as text, not only inside an image, video, canvas, or interaction that a crawler may not execute.
Crawler names also have different purposes. OpenAI documents OAI-SearchBot for inclusion in ChatGPT search, while GPTBot controls potential model-training access. Anthropic separates Claude-SearchBot for search indexing, Claude-User for user-requested retrieval, and ClaudeBot for potential model training. Google states that Googlebot governs Search eligibility and that Google-Extended does not affect inclusion or ranking in Google Search. Perplexity documents PerplexityBot as its search crawler. Choose each policy deliberately instead of treating every AI user-agent as interchangeable.
A permissive discovery-oriented robots.txt can include:
User-agent: Googlebot
Allow: /
User-agent: OAI-SearchBot
Allow: /
User-agent: PerplexityBot
Allow: /
User-agent: Claude-SearchBot
Allow: /
User-agent: Claude-User
Allow: /
Sitemap: https://example.com/sitemap.xml
This file is only one layer. A CDN, WAF, bot challenge, authentication wall, rate limit, or server error can still block the request. Test the final production URL and inspect server or CDN logs when a documented crawler receives 403, 429, or 5xx responses.
An optional llms.txt can summarize key pages for tools that choose to read it, but it is not a universal indexing protocol. Google explicitly says AI text files are not required for its generative search features. Keep llms.txt accurate if you publish one; never use it as a substitute for crawlable pages, a sitemap, and internal links.
Step 4: Find the questions buyers actually ask
Do not begin with a list of generic high-volume keywords. Start with the language found in sales calls, demos, support tickets, on-site search, customer interviews, community discussions, and honest reviews. Remove names and sensitive information before processing customer material.
Sort the questions into four intent groups:
| Intent | Typical question | Best page format |
|---|---|---|
| Problem | How do I measure whether ChatGPT mentions my brand? | Tutorial or diagnostic guide |
| Comparison | Tool A vs Tool B for a five-person agency | Transparent comparison |
| Alternative | What are the best alternatives to Tool A? | Alternatives page with selection criteria |
| Decision | Which AI visibility tool fits a small SaaS budget? | Category guide with pricing and trade-offs |
Choose one narrow question for the first page. It should be close enough to your product that the right reader could take a meaningful next step, but useful enough to answer honestly even when your product is not the best fit.
Copy-and-use prompt
Turn the anonymized customer questions below into an intent map. Group them as
problem, comparison, alternative, or decision queries. Preserve the customer's
language, merge true duplicates, and list the evidence each answer would need.
Do not create queries that are not supported by the input. Questions: [paste].
Step 5: Build one answer-first page that deserves to be cited
An answer-first page resolves the main question before asking the reader to work through background or brand narrative. A practical opening target is 40 to 80 words, but this is an editorial heuristic, not a ranking rule. The answer should name the subject, state the useful conclusion, define important limits, and make sense when read alone.
Use this page structure:
- H1: the exact subject and outcome of the page.
- Opening answer: a self-contained resolution in the first paragraph.
- Short decision table: options, costs, audience, or trade-offs when relevant.
- Question-led H2 sections: each begins with a direct answer, followed by proof and context.
- Original evidence: screenshots, tests, examples, data, expert observations, or a disclosed methodology.
- Limitations: who should not follow the recommendation and what remains uncertain.
- Visible FAQ: only recurring questions that the page can answer accurately.
- Clear next action: a relevant tool, template, product action, or related guide.
The isolated-paragraph test is useful: hide the rest of the page and read one section. If the brand, subject, date, units, or comparison basis disappears, rewrite the passage so it remains understandable without nearby context.
Avoid producing dozens of near-duplicate pages for tiny query variations. Google's current generative-search guidance prioritizes unique, first-hand, non-commodity content and warns against scaled pages created primarily to manipulate search systems. One strong tutorial with real evidence is more defensible than 20 paraphrases of public knowledge.
Step 6: Add evidence that a reader can verify
Evidence turns a fluent paragraph into a usable source. Prefer primary sources for product behavior, technical protocols, laws, scientific findings, and platform policies. Link directly to the document supporting the claim, name the source in the sentence, and include the verification date for fast-changing facts such as pricing or features.
Use first-party evidence where your experience is the value: a reproducible test, an anonymized dataset, screenshots, a benchmark methodology, or a case study with clear inputs and limitations. Never invent a customer count, ranking gain, quote, review, or benchmark. If a claim cannot be verified, remove it or label it as an observation or hypothesis.
Before publishing, create a simple evidence ledger:
| Claim | Source | Checked | Status |
|---|---|---|---|
| OAI-SearchBot controls ChatGPT search discovery | OpenAI publisher documentation | 2026-08-02 | Verified |
| Product starts at a stated price | Product's official pricing page | YYYY-MM-DD | Recheck before publishing |
| Our test improved a metric | Reproducible internal test and method | YYYY-MM-DD | Add limitations |
Step 7: Add structured data that matches the visible page
Structured data gives search systems explicit facts about a page, but it does not create authority and does not guarantee an AI citation or a rich result. Google recommends JSON-LD for maintainability and requires markup to represent visible, accurate content.
For a tutorial, the useful graph usually contains:
- Article or BlogPosting: headline, author, dates, image, publisher, and canonical page.
- Person: a real author with a bio and relevant profile links.
- Organization: official brand name, URL, logo, contact details, and verified
sameAsprofiles. - BreadcrumbList: the visible page hierarchy.
- FAQPage: only when the same questions and answers are visible on the page.
Use stable @id values to connect the author, publisher, website, and article rather than creating several contradictory versions of the same entity. Validate syntax, then compare every property with what a visitor can see. The FAQPage schema guide and Answer First structure guide provide implementation examples.
Step 8: Connect the page to a real topic cluster
Internal links help readers and crawlers discover context. Link the new page from a relevant hub and from older pages that already discuss the problem. Link back to focused supporting guides with descriptive anchor text. Do not add a fixed number of links for its own sake; every link should answer the reader's next likely question.
A simple cluster for AI visibility could connect:
- a broad Generative Engine Optimization guide;
- a practical GEO content audit checklist;
- platform guides for ChatGPT Search, Perplexity, and Google AI Overviews;
- a measurement guide for tracking brand mentions in AI engines.
Use one canonical URL for each language variant, accurate hreflang links, and descriptive link text. Avoid orphan pages and avoid several pages competing to answer exactly the same intent.
Step 9: Earn corroboration on third-party sources
Your own website establishes the claim; independent sources can corroborate it. Build profiles only where your buyers or their research tools genuinely look: relevant software directories, review platforms, professional communities, partner pages, podcasts, events, and specialist publications.
The safe approach is factual and earned. Complete profiles with consistent details, request honest reviews without dictating sentiment, contribute expert answers under a real identity, and pitch editors only when you add evidence their article is missing. Do not buy bulk links, fabricate discussions, create fake reviews, or publish disguised advertisements. Those tactics create reputation and search-policy risk without proving that real customers trust the brand.
Start your outreach from the citation baseline in Step 1. If several answer engines cite the same independent category guide and your product genuinely belongs there, inspect its selection criteria and send the editor concise, verifiable information. Accept that a fair article may identify a competitor as the better choice for some use cases.
Step 10: Publish, notify, and measure the business result
After publishing, link the tutorial from the blog index and at least one relevant existing page. Confirm the canonical URL, sitemap entry, server-rendered text, status code, social image, Article schema, author entity, and visible FAQ. Request indexing in Google Search Console when appropriate. IndexNow can notify participating search engines that a URL was added or updated, but a successful submission only confirms receipt, not indexing or ranking.
Review the same 10 buyer questions weekly at first, then monthly when results stabilize. Add conventional analytics so AI visibility is tied to outcomes rather than screenshots.
| Metric | What it answers |
|---|---|
| Mention rate | How often is the brand named across the tracked questions? |
| Citation rate | How often is an owned page linked as a source? |
| AI share of voice | How visible is the brand relative to selected competitors? |
| AI referral sessions | Do answer engines send visits to the site? |
| Branded search | Are more people searching for the brand after discovery elsewhere? |
| Assisted sign-ups | Do AI referrals or branded visits contribute to registration? |
Do not optimize only for the largest number. A citation on a high-intent comparison question can be more valuable than many mentions on educational questions that never lead to action.
A realistic 30-day AI SEO plan
| Period | Deliverable | Definition of done |
|---|---|---|
| Days 1-3 | Baseline | 10 buyer questions tested, competitors and cited URLs recorded |
| Days 4-7 | Technical and entity cleanup | Important pages crawlable; brand facts consistent; sitemap and canonical checked |
| Days 8-14 | One original tutorial | Direct answer, question-led sections, evidence, limitations, author, and CTA published |
| Days 15-18 | Structured data and links | Valid Article graph, visible FAQ match, hub and supporting links added |
| Days 19-24 | Corroboration | Five relevant third-party sources reviewed; factual outreach sent where justified |
| Days 25-30 | Measurement | Search Console, analytics, AI referrals, mention rate, and sign-up path reviewed |
At day 30, update the page based on evidence, not anxiety. Fix a concrete crawl issue, weak passage, missing source, or conversion leak. Do not rewrite the whole article because one model omitted the brand on one run.
Common AI SEO mistakes to avoid
- Treating GEO as a shortcut around SEO. A page still needs crawlability, indexing eligibility, useful content, and a good user experience.
- Confusing search and training crawlers.
OAI-SearchBotandGPTBot, orGooglebotandGoogle-Extended, do different jobs. - Publishing generic AI summaries. Repackaged public knowledge gives a search or answer system little reason to select your page over the original sources.
- Adding unsupported schema. Structured data must match visible facts; fabricated ratings, FAQs, authors, or organizations undermine trust.
- Tracking one vanity score. Pair diagnostic scores with query-level mentions, source URLs, qualified referrals, and conversions.
- Forcing the brand into every answer. Recommend your product only where it genuinely fits, and state limitations openly.
- Scaling before learning. Publish and measure one excellent page before turning a weak template into dozens of weak pages.
FAQ
Is AI SEO different from traditional SEO?
AI SEO focuses on visibility inside generated answers, while traditional SEO often focuses on ranked search results and clicks. In practice they share the same foundation: crawlable pages, useful content, clear entities, evidence, and authority. GEO and AEO add citation and answer-level measurement; they do not replace technical or editorial SEO.
How long does AI SEO take to work?
There is no guaranteed timeline. Crawling, indexing, source selection, and answer generation change by platform, query, location, and time. Measure a fixed set of buyer questions for at least several weeks, alongside search impressions, referrals, branded demand, and conversions, before deciding whether a change helped.
Does schema markup make ChatGPT cite a page?
No. Accurate schema can clarify entities and page properties for systems that process it, but it does not guarantee retrieval, citation, or ranking. The visible answer, evidence, crawlability, relevance, and independent trust signals still matter. Mark up only information that users can also verify on the page.
Do I need an llms.txt file for GEO?
No major search engine currently documents llms.txt as a universal requirement for appearing in generated answers. It can be a low-cost optional index for tools that support it, but it cannot replace robots.txt, internal links, a sitemap, indexable HTML, or strong content. Keep it current if you choose to publish one.
Should I allow every AI crawler in robots.txt?
Not automatically. Decide separately whether you want search discovery, user-triggered retrieval, model training, or none of those uses. Check each provider's current documentation, then test your CDN and firewall as well as robots.txt. A crawler allowed in the file can still be blocked elsewhere in the delivery stack.
What is the best first page to create for AI visibility?
Create the page that answers a recurring, high-intent customer question for which you have first-hand evidence. A transparent comparison, implementation tutorial, or diagnostic guide is often stronger than a broad definition because it helps a buyer make a decision and gives you room to contribute original experience.
Sources
- Optimizing your website for generative AI features on Google Search - Google Search Central
- AI features and your website - Google Search Central
- General structured data guidelines - Google Search Central
- ChatGPT Search - OpenAI Help Center
- Publishers and Developers FAQ - OpenAI Help Center
- Anthropic web crawler controls - Claude Help Center
- Perplexity crawlers - Perplexity documentation
- IndexNow protocol documentation
- GEO: Generative Engine Optimization - KDD 2024 paper
Youssef builds GEOCARA and has run visibility probes across AI engines since 2025. He writes from measured probe data, not speculation.
LinkedIn ↗Related GEO guides
Start your free trial
Audit your site and see how AI engines perceive you.