SEO 101: Old Search, New Search, And The AI Answer Engine Era
Search did not die. It moved the finish line. The page that used to rank first now has to survive being cited, summarized, and skipped in the same breath — all by an AI that may never send the click. This guide covers the fundamentals that still run everything underneath, the new rules for AI answer engines, and a full VA playbook for running the whole thing operationally. Read it once. Then use the SOPs in Part VI to run it.
The game used to be easy to describe. You had a page. Someone had a query. Google made the match. The details were complicated — crawling, canonicals, backlinks, page speed — but the interface was not. A user typed something. Google returned ten blue links. Your page competed for positions one through ten. That mental model still matters. But it is no longer the whole game.
Now the search engine sometimes just answers. Google AI Overviews and AI Mode summarize and cite. ChatGPT search browses and quotes. Copilot blends assistant logic with web retrieval. Users ask longer, messier questions and get synthesized answers — not ten links and a "good luck." The referral is no longer guaranteed.
This does not mean technical SEO, links, keywords, and page quality stop mattering. It means they become the floor. The ceiling is now source-worthiness: original facts, entity clarity, evidence, topical depth, structured information, brand trust, and content that can be safely cited without a human reading the whole site first.
| Old SEO | New SEO |
|---|---|
| Rank for keywords | Be cited for questions, comparisons, entities, tasks, and decisions |
| Optimize page titles and headings | Design extractable answers, evidence blocks, definitions, tables, and sourceable claims |
| Build backlinks | Build reputation across web, communities, knowledge graphs, reviews, authors, and mentions |
| Measure clicks and rankings | Measure rankings, clicks, AI citations, branded demand, assisted conversions, and zero-click influence |
| Publish more content | Publish content with information gain, firsthand proof, and clear expertise |
| Write for crawlers and readers | Write for crawlers, readers, answer engines, and AI summarizers without making the page robotic |
Old search was patient. A user typed "best CRM for dentists," clicked four tabs, compared options, watched a YouTube review, asked Reddit, lost a weekend, then booked a demo. AI search skips most of that. One prompt: "compare GoHighLevel, HubSpot, and Pipedrive for a dental clinic with 3 locations and heavy SMS follow-up" — and the engine synthesizes an answer from sources it chose. Your page may or may not be one of them.
Many small searches
Users refine queries manually across pages and tabs.
One complex prompt
Users ask for synthesis, tradeoffs, and recommendations.
Ranked links
The search engine points at pages and lets users evaluate.
Summarized answer
The engine cites sources, pulls facts, and frames the decision.
This creates a new SEO job: your content must be useful to the answer construction process. A page full of vague claims is hard to cite. A page with clear definitions, tables, examples, data, authorship, and caveats is easier to use.
Search engines still need to crawl pages, index content, understand topics, evaluate quality, and decide what to show. AI search often depends on the same web substrate. If your site blocks crawlers, hides important content in inaccessible JavaScript, has no internal links, has weak titles, or provides thin content, AI will not magically rescue it.
Crawling is the first gate. Search engines discover pages through links, sitemaps, feeds, submissions, and crawling systems. If your important pages are orphaned, blocked, too slow, hidden behind forms, or rendered in ways crawlers cannot access, they might as well not exist.
Submit XML sitemap
Include canonical URLs you care about. Keep it clean.
Check robots.txt
Do not accidentally block CSS, JavaScript, images, or important directories.
Use internal links
Every important page should be reachable from other relevant pages.
Inspect logs
See what bots actually crawl, not just what you hope they crawl.
A page can be crawled but not indexed. Common reasons: duplication, canonical confusion, thin content, blocked snippets, noindex tags, low value, redirect issues, soft 404s, or content Google already has in better form elsewhere.
| Signal | What to check |
|---|---|
| Canonical | Does the canonical URL point to the real preferred page? |
| Noindex | Are meta robots or X-Robots-Tag headers blocking indexing? |
| Duplication | Does this page add enough value beyond similar pages? |
| Rendering | Can Google see the main content and links? |
| Snippets | Is the page eligible for snippets and supporting links? |
Old keyword research often treated queries like magic phrases. Modern keyword work maps intent: what the user is trying to do, what they already know, what decision they are making, what format they need, and what proof would make them trust the answer.
AI search makes long-tail intent more valuable because users can ask naturally. Build pages around complete problems, not exact-match fragments.
Architecture tells search engines what your site is about and which pages matter. A strong site has clear topical hubs, supporting pages, breadcrumbs, internal links, and URLs that humans can understand.
/seo/ /seo/technical-seo/ /seo/local-seo/ /seo/ai-search-optimization/ /seo/content-refresh/ /seo/schema-markup/ /case-studies/ /case-studies/local-seo-dental-clinic/ /case-studies/technical-seo-saas-site/
The point is not pretty folders. The point is semantic clarity. A crawler, a user, and an AI system should be able to infer the relationship between pages without detective work.
Title
Specific, descriptive, and honest. Do not overpromise.
H1
Clearly states the page topic. No mystery branding when clarity matters.
Intro
Answer the core intent quickly, then expand.
Sections
Use headings that map to real subquestions.
Media
Use images, video, charts, or examples when they make the answer better.
AI systems like extractable clarity. Humans like it too. That is the sweet spot.
Links remain a major web-native way to express trust, discovery, and importance. But the future of authority is wider than backlinks. Mentions, reviews, citations, community references, author reputation, datasets, videos, podcasts, and third-party profiles all help machines and humans decide whether you are real.
| Authority type | Example | Why it matters |
|---|---|---|
| Backlink | Industry publication links to your guide | Discovery and reputation |
| Brand mention | Forum compares your company to competitors | Entity confidence |
| Review | Customers review location/service | Trust and local relevance |
| Source citation | Other articles cite your data | AI and human source-worthiness |
The industry is still arguing about what to call this. AEO, GEO, LLMO, AI Search Optimization — pick one, they all point at the same shift. AEO usually means optimizing for answer engines: featured snippets, voice answers, People Also Ask, assistants, and direct answers. GEO usually means optimizing for generative engines: AI Overviews, AI Mode, ChatGPT search, Perplexity, Copilot, and systems that synthesize sources. The naming will settle. The underlying problem — how do you become the source an AI cites? — is the same regardless.
An entity is a thing with identity: a person, company, product, place, service, concept, event, or dataset. AI search is entity-hungry because it needs to connect facts. If your brand, authors, products, services, locations, and expertise are ambiguous, you make the machine work harder.
Who are you?
Name, logo, about page, founders, locations, social profiles, organization schema.
Who wrote this?
Author bios, credentials, reviewed-by fields, publication history.
What do you do?
Clear service pages, examples, pricing context, FAQs, case studies.
Where do you operate?
Business Profile, local pages, consistent NAP, reviews, local proof.
If your page says what every other page says, AI can summarize the topic without you. Your job is to contribute something the model and user cannot get everywhere else: original data, field experience, screenshots, tests, benchmarks, opinions with reasoning, case studies, decision trees, and examples from actual work.
| Weak content | Stronger content |
|---|---|
| "SEO is important for businesses." | "In our 42-location service audit, pages with service + city + proof blocks converted 31% higher than generic city pages." |
| "Use structured data." | "Here is the LocalBusiness + Service schema pattern we use, and when we avoid FAQ schema." |
| "AI search is changing SEO." | "Here are 12 prompts where ChatGPT cites competitors but not us, and the content gaps causing it." |
AI answer engines need facts they can safely attach to sources. You can help by designing pages with citation-friendly blocks: concise definitions, tables, statistics with methodology, step-by-step processes, pros/cons, dates, version notes, and clear claims.
State the claim
Use precise language. Avoid mushy marketing claims.
Show the evidence
Data, screenshots, examples, sources, test conditions, or author experience.
Explain the caveat
Tell readers where the claim applies and where it does not.
Format for extraction
Use tables, bullets, definitions, and descriptive headings without stripping personality.
Structured data is standardized markup that helps search systems understand the meaning of a page. It can enable rich results and clarify entities. It is not magic ranking dust, and it must match visible page content.
Organization LocalBusiness Person Article / BlogPosting Product Service FAQPage HowTo BreadcrumbList Review / AggregateRating VideoObject
AI discovery now involves more than Googlebot. OpenAI documents separate crawlers for search, training, ads validation, and user-triggered browsing. These controls are not the same. Blocking a training crawler is different from blocking a search crawler that may surface your site in ChatGPT search answers.
| Bot/control | What it affects | Strategic note |
|---|---|---|
| Googlebot | Google Search crawling and indexing | Usually allow for SEO visibility. |
| Google-Extended | Controls use for some Google generative AI model training/grounding use cases | Separate from normal Google Search crawling. |
| OAI-SearchBot | ChatGPT search result inclusion | Allow if you want to appear in ChatGPT search answers. |
| GPTBot | OpenAI model training crawl | Block or allow based on your content policy. |
| ChatGPT-User | User-triggered page visits | Robots.txt may not apply because the user initiated the action. |
User-agent: OAI-SearchBot Allow: / User-agent: GPTBot Disallow: / User-agent: Googlebot Allow: /
This is not legal advice. It is operational hygiene. Decide deliberately which systems can access what, then monitor logs to see what actually happens.
A modern SEO system has three layers: money pages, authority pages, and proof pages.
AI search raises the value of authority and proof pages because answer engines need sources that make claims easier to support.
Direct answer
Give the short answer in the first screen. Do not bury the point.
Definition block
One precise definition that can be safely quoted.
Context and caveats
Explain when the answer changes.
Evidence
Use data, examples, screenshots, source links, case studies, or methodology.
Comparison
Tables and pros/cons help both readers and answer engines.
Next action
Tell the user what to do after understanding the answer.
Claim: Local service pages should include service, city, proof, and conversion intent. Evidence: Show examples, screenshots, review excerpts, rankings, or conversion data. Caveat: Do not create doorway pages with duplicated content across every city. Action: Build unique pages only where you have real service relevance and proof.
For local businesses, SEO is not just the website. It is the website, Google Business Profile, Bing Places, Apple Business Connect, reviews, local citations, service area clarity, photos, menus/services/products, local landing pages, and reputation signals.
| Asset | What to optimize |
|---|---|
| Business Profile | Categories, services, hours, photos, products, posts, Q&A, booking links. |
| Reviews | Volume, freshness, specificity, response quality, service/location keywords naturally mentioned by customers. |
| Location pages | Real local proof, staff, photos, service area, FAQs, testimonials, directions, parking, nearby landmarks. |
| Citations | Consistent name, address, phone, website, categories across major directories. |
| Schema | LocalBusiness, PostalAddress, openingHours, geo, sameAs, aggregateRating if valid and visible. |
AI answers about local businesses will lean on whatever structured and semi-structured proof is easiest to verify. Keep the public facts clean.
Ecommerce search is especially vulnerable to AI summarization because users ask comparison and fit questions: best product for a use case, cheapest reliable option, difference between models, sizing, compatibility, return policies, and reviews.
Make facts complete
Specs, variants, compatibility, availability, shipping, returns, images, video, FAQs.
Help decisions
Buying guides, filters, comparisons, top use cases, expert picks, review summaries.
Surface real experience
Use review snippets ethically. Highlight verified buyer patterns.
Keep data clean
Merchant feeds, product schema, price, stock, GTINs, and variant identifiers.
Programmatic SEO still works. But AI search makes thin scaled pages easier to ignore than ever — because an AI can just answer the question instead of sending the traffic. If you create 2,000 pages from a template, each page needs unique data, local proof, user value, or a real reason to exist. The threshold for "worthwhile page" just got higher.
AI answers can reduce clicks while increasing influence. A user may read an AI summary, see your brand cited, search your brand later, or convert through another channel. SEO measurement has to widen.
| Metric | Why it matters |
|---|---|
| Organic clicks | Still the clearest direct traffic signal. |
| Impressions | Shows visibility even when CTR changes. |
| Branded search | AI and social discovery often reappear as brand demand. |
| AI citations | Track where AI systems cite or mention your pages. |
| Assisted conversions | SEO often begins the journey, not ends it. |
| Content decay | Shows when once-useful pages are losing relevance. |
Topical authority means your site covers a subject deeply enough that users and systems can trust you across the whole problem space. This is not just publishing many articles. It is building a coherent knowledge system.
Define the topic map
Core concepts, problems, alternatives, tools, mistakes, costs, examples, and FAQs.
Create hub pages
Big guides that organize the topic and link to deeper pages.
Add proof pages
Case studies, teardown posts, benchmarks, calculators, and examples.
Interlink intentionally
Pages should reinforce each other, not compete randomly.
Generic search is crowded. Brand search is clearer. A strong brand creates navigational demand, direct traffic, mentions, reviews, repeat visits, and trust signals that are harder to copy than a blog template.
Repeatable concepts
Name your frameworks, templates, tools, and signature processes.
Show outcomes
Case studies, public examples, testimonials, screenshots, and before/after evidence.
Leave the website
YouTube, LinkedIn, podcasts, newsletters, communities, GitHub, directories.
Be consistent
Same name, bios, handles, descriptions, logos, and links across the web.
Forums, Reddit, review sites, YouTube comments, community posts, and customer reviews often influence AI summaries because they contain lived experience. You should not manipulate them. You should earn real discussion by doing useful work, asking for reviews ethically, responding well, and participating where your audience already is.
Instead: build review request flows, answer community questions, publish transparent comparisons, and document real customer outcomes.
In AI search, stale pages are risky because summaries need current facts. Refresh cycles should focus on pages where freshness changes the answer: pricing, tools, laws, model capabilities, product comparisons, statistics, screenshots, and best-practice recommendations.
| Layer | Tools | Use |
|---|---|---|
| Indexing | Google Search Console, Bing Webmaster Tools | Coverage, queries, pages, sitemaps, errors. |
| Crawling | Screaming Frog, Sitebulb, server logs | Technical audits, internal links, status codes, canonical issues. |
| Content | Docs, CMS, content inventory, spreadsheet | Topic maps, refresh cycles, proof assets, briefs. |
| Rank/market | Ahrefs, Semrush, Sistrix, Similarweb | Competitors, keywords, links, SERP features. |
| AI visibility | Manual prompt set, Bing AI Performance if available, custom trackers | Citations, mentions, answer inclusion, competitor mentions. |
| Analytics | GA4, Plausible, PostHog, CRM attribution | Traffic quality, conversions, assisted revenue. |
Days 1-15: Baseline
Set up Search Console, Bing Webmaster Tools, analytics, sitemap, robots review, crawl audit, top page inventory, and AI prompt baseline.
Days 16-30: Technical cleanup
Fix index blockers, canonicals, broken links, internal linking gaps, slow templates, duplicate pages, and missing metadata.
Days 31-45: Entity foundation
Improve About, author bios, organization schema, service pages, location facts, sameAs profiles, and review flows.
Days 46-65: Content rebuild
Upgrade top pages with direct answers, proof blocks, tables, examples, schema, media, internal links, and clear CTAs.
Days 66-80: Authority push
Publish one original asset: report, calculator, comparison, template, dataset, case study, or teardown worth citing.
Days 81-90: Measure and iterate
Compare rankings, traffic, conversions, brand search, AI citations, crawl logs, and page-level improvements. Build the next sprint.
A VA or support specialist does not need to become a senior SEO strategist to be useful. They need a clear operating lane: collect data, follow checklists, update safe fields, prepare briefs, publish approved content, monitor issues, and escalate anything risky.
| Task | VA can own | Needs approval | Escalate immediately |
|---|---|---|---|
| Keyword collection | Export queries, group themes, collect competitor titles | Final keyword priorities | None usually |
| Metadata edits | Draft title tags and meta descriptions | Publishing on money pages | Brand/legal claims |
| Internal links | Suggest relevant links and anchors | Large sitewide changes | Links to wrong service, old offer, or legal/medical advice |
| Content publishing | Format, upload, add images, alt text, schema, links | Final publish | Broken layout, missing author, unsupported claims |
| Local SEO | Update hours, photos, services, review log | Category, address, phone, name changes | Suspension warning, duplicate listing, ownership issue |
| Technical SEO | Run checks and document issues | Implement fixes | Noindex, robots block, 5xx errors, hacked pages |
This is the weekly operating rhythm for a support SEO assistant. It is deliberately repetitive because SEO breaks quietly.
Monday: Search Console health
Check indexing pages, manual actions, security issues, sitemap status, top query movement, and pages with sudden drops.
Tuesday: Content queue
Update content tracker, collect missing assets, verify briefs, prep drafts, check internal links, and confirm assigned owners.
Wednesday: Local and reputation
Check Google Business Profile, reviews, photos, Q&A, service updates, and local citation consistency.
Thursday: Competitor and AI visibility
Run saved prompts, record cited sources, capture competitor pages, and note gaps in your content.
Friday: Report and cleanup
Send a short report: wins, issues, tasks completed, blockers, pages published, pages needing approval, urgent risks.
SEO Weekly Report - [Client / Site] 1. Completed this week: - 2. Performance notes: - Top improving page: - Top declining page: - New indexing issues: 3. Content status: - Drafts ready: - Published: - Waiting for approval: 4. Local SEO: - New reviews: - GBP updates: - Issues: 5. AI search visibility: - Prompts checked: - Our brand cited? yes/no - Competitors cited: 6. Blockers / approvals needed: -
The VA's job is not to pick the whole strategy alone. The VA's job is to gather clean evidence so the strategist or owner can decide faster.
Start from existing data
Export Search Console queries for the last 3 months. Include query, page, clicks, impressions, CTR, and position.
Group by intent
Label each keyword as informational, commercial, local, transactional, support, branded, or competitor.
Find page match
Mark whether the site already has a page for the keyword. If yes, paste the URL. If no, mark "gap."
Check the SERP manually
Search the keyword in an incognito window. Note what ranks: guides, local pack, videos, tools, category pages, forums, AI Overview.
Collect competitor examples
Save the top 3 useful competitor URLs and write one sentence on why each page satisfies the query.
| Column | Example |
|---|---|
| Keyword | local seo checklist for dentists |
| Intent | Informational / local niche |
| Current URL | /seo/local-seo/ or GAP |
| SERP type | Guides + local agencies + PAA |
| AI answer? | Yes, cites 3 guides |
| Competitor URL | example.com/dental-local-seo-guide |
| Recommended action | Refresh existing guide with dental examples |
Most support SEO work is not glamorous. It is making existing pages clearer, more trustworthy, easier to crawl, and easier to convert.
| Check | Pass condition | VA action |
|---|---|---|
| Title tag | Specific, under control, includes primary topic naturally | Draft improved version |
| Meta description | Clear value and reason to click | Draft 145-160 character version |
| H1 | One clear H1 matching page intent | Flag if missing/duplicated |
| Intro | Answers the core question quickly | Suggest direct answer paragraph |
| Internal links | Links to and from related pages | Add suggestions with anchor text |
| Proof | Examples, screenshots, reviews, data, author expertise | List missing proof assets |
| CTA | Next step is obvious | Flag weak/missing CTA |
| Schema | Relevant schema exists and matches visible content | Flag missing or suspicious schema |
| Freshness | Facts, screenshots, pricing, tools are current | Mark stale items |
Page: [URL] Target intent: [what the user wants] Quick diagnosis: - What works: - What is weak: - Missing proof: - Internal links to add: - Internal links from: - Suggested title: - Suggested meta: - Escalation needed? yes/no Priority: P1 = blocking / broken P2 = important improvement P3 = nice to have
A content brief prevents generic SEO slop. It tells the writer what the page must accomplish, what evidence to include, what angle is different, and what not to say.
Page title: Target URL: Primary keyword: Secondary keywords: Search intent: Audience: Conversion goal: SERP notes: - Top ranking formats: - Common sections: - Missing angle we can own: Required sections: 1. 2. 3. Evidence/proof needed: - Case study: - Screenshot: - Data/source: - Expert quote: - Product/service example: Internal links to include: - External sources to cite: - Schema target: Article / LocalBusiness / Product / FAQ / HowTo / none Do not claim: - CTA: -
Publishing is where many SEO mistakes happen: wrong slug, missing canonical, giant images, no internal links, broken formatting, missing author, copied metadata, or accidentally noindexing the page.
Before upload
Confirm approved title, URL slug, author, category, publish date, target keyword, CTA, and internal links.
During upload
Format headings, compress images, add alt text, add tables, add schema, add meta title/description.
Before publish
Preview desktop and mobile. Test links. Check noindex is off. Check canonical is correct.
After publish
Add internal links from 2-5 relevant old pages. Submit URL in Search Console if appropriate. Log in tracker.
Local SEO support is detail work. The business must look real, active, consistent, and locally relevant everywhere a customer or machine checks.
| Area | Weekly task | Monthly task |
|---|---|---|
| Google Business Profile | Check reviews, Q&A, photos, hours, alerts | Add fresh photos, update services/products, check categories |
| Reviews | Log new reviews and response status | Summarize recurring themes and service keywords |
| Citations | Flag wrong NAP if found | Audit top directories for name, address, phone, URL |
| Location pages | Check forms/calls work | Add local proof: photos, testimonials, staff, FAQs |
| Competitors | Note new GBP posts/photos/review spikes | Compare categories, services, review velocity |
A useful support report says what changed, why it matters, what was done, what is blocked, and what happens next. It does not dump screenshots without interpretation.
| Metric | What VA should say | Bad reporting |
|---|---|---|
| Clicks | "Organic clicks rose 12%, mostly from the local SEO guide." | "Clicks: 1,842." |
| Impressions | "Impressions grew but CTR fell, so titles may need testing." | "Impressions are up." |
| Indexing | "3 important pages are discovered but not indexed; requesting review." | "Coverage has warnings." |
| Rankings | "Two service pages moved from page 2 to page 1." | "Average position changed." |
| AI visibility | "ChatGPT cited competitor X for 4/10 prompts; our missing angle is pricing examples." | "AI search checked." |
Monthly SEO Summary - [Month] Headline: - [One sentence: what happened and why it matters] Wins: 1. 2. 3. Risks: 1. 2. Work completed: - Top pages: - Improving: - Declining: - Needs refresh: AI search notes: - Prompts tested: - We were cited for: - Competitors were cited for: Next month: 1. 2. 3.
AI visibility tracking is immature, so support teams need a simple prompt set and a consistent logging process. The goal is not perfect science. The goal is directional visibility: who gets cited, what claims appear, and which content gaps repeat.
Create 10-25 saved prompts
Use real customer questions, comparison prompts, local prompts, and buying-intent prompts.
Run monthly
Use the same prompts in ChatGPT search, Google AI features when available, Copilot/Bing, and any relevant answer engine.
Record citations
Log whether your brand/page appears, which competitors appear, and what source URLs are cited.
Extract gaps
If competitors are cited, note what their page has that yours lacks: data, table, definition, case study, comparison, author proof.
Date Prompt Platform Our brand mentioned? yes/no Our URL cited? yes/no Competitor brands mentioned Cited URLs Answer summary Missing content angle Recommended action Screenshot link
SEO support work needs a red flag list. The fastest way to lose trust is to make an invisible technical change that hurts indexing, rankings, local visibility, or conversions.
| Red flag | Why it matters | Action |
|---|---|---|
| Noindex found on important page | Page may disappear from search | Escalate immediately with URL and screenshot |
| Robots.txt blocks important folder | Crawlers may not access content | Do not edit; escalate |
| Canonical points to wrong page | Search may ignore the page | Escalate with current canonical |
| Traffic drop over 30% | Could be technical, update, tracking, or demand issue | Document date, pages, queries, possible site changes |
| GBP suspension or verification alert | Local visibility risk | Escalate immediately |
| Hacked/spam pages indexed | Security and reputation issue | Escalate immediately |
| Mass redirect request | Can destroy rankings if wrong | Requires senior approval |
| Legal/medical/financial claim | High-stakes content risk | Requires expert review |
[ ] Page URL works [ ] Page is not noindex [ ] Canonical looks correct [ ] Title and meta are filled [ ] H1 exists and matches topic [ ] Images compressed and alt text added [ ] Internal links added [ ] External links open correctly [ ] CTA works [ ] Mobile preview checked [ ] Claims supported by visible proof/source [ ] Tracker updated [ ] Approval requested with summary