Technical SEO

Auto detailers should use AutomotiveBusiness (a LocalBusiness subtype) schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are. Schema clarifies content for AI; it never rescues a thin site or a buried answer.

2 min read

A detailing business needs a website rebuild for AEO when it lives on social media with no real site, is slow, or lacks per-package answer-first pages and schema — because the engine can only recommend what it can read. The rebuild is the access layer everything else depends on.

2 min read

Auto repair shops should use the AutoRepair (a LocalBusiness subtype) schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

An auto repair shop needs a website rebuild for AEO when the current site is slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Bookkeepers should use AccountingService (a LocalBusiness subtype) schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are and what you do. Schema clarifies clear content for AI; it never rescues a thin site or a buried answer.

2 min read

A bookkeeping firm needs a website rebuild for AEO when the site is thin or slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Concrete contractors should use the GeneralContractor (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A concrete contractor needs a website rebuild for AEO when the site is slow, an unreadable photo-heavy gallery, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

2 min read

Electricians should use the Electrician (a LocalBusiness subtype) schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies correct content for AI; it never rescues a slow site or a buried answer.

2 min read

An electrician needs a website rebuild for AEO when the current site is slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Excavation contractors should use GeneralContractor or HomeAndConstructionBusiness (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

An excavation contractor needs a website rebuild for AEO when the site is slow, an unreadable photo-heavy gallery, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

3 min read

Fence and deck builders should use the GeneralContractor or HomeAndConstructionBusiness (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A fence and deck builder needs a website rebuild for AEO when the site is slow, an unreadable photo-heavy portfolio, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

3 min read

Flooring contractors should use the GeneralContractor (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A flooring business needs a website rebuild for AEO when the site is slow, an unreadable image-heavy gallery, or built without per-material answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

2 min read

Florists should use the Florist (a LocalBusiness/Store subtype) schema with accurate name, address, phone, hours, and area served, plus FAQ schema on answer pages — it helps engines parse where you are and where you deliver. Schema clarifies readable content; it never rescues an image-only site.

2 min read

A florist needs a website rebuild for AEO when the site is all images with no readable text, slow, or built only in a third-party order widget — because the engine can only recommend what it can read. The rebuild puts your arrangements, occasions, and delivery info in readable text everything else depends on.

2 min read

Garage door companies should use LocalBusiness schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are and what you do. Schema clarifies correct content for AI; it never rescues a slow site or a buried answer.

2 min read

A garage door company needs a website rebuild for AEO when the current site is slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

General contractors should use the GeneralContractor (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A general contractor needs a website rebuild for AEO when the site is slow, an unreadable image-heavy portfolio, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

2 min read

Gyms should use the ExerciseGym or HealthClub (LocalBusiness subtypes) schema with accurate name, address, phone, hours, and offerings, plus FAQ schema on answer pages — it helps engines parse what you offer and confirm you're open. Schema clarifies readable content; it never rescues a booking widget.

2 min read

A gym needs a website rebuild for AEO when classes and pricing live in a booking widget, the site is slow, or content renders only in the browser — because the engine can only recommend what it can read. The rebuild puts your classes, pricing, and hours in readable text everything else depends on.

2 min read

Handyman services should use HomeAndConstructionBusiness (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A handyman business needs a website rebuild for AEO when the site is slow, a thin image-heavy one-pager, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

3 min read

House cleaning companies should use LocalBusiness schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are and what you do. Schema clarifies clear content for AI; it never rescues a thin site or a buried answer.

2 min read

A cleaning company needs a website rebuild for AEO when the site is thin or built in a booking widget, hard for AI crawlers to read, or without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

HVAC companies should use the HVACBusiness (a LocalBusiness subtype) schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

An HVAC company needs a website rebuild for AEO when the current site is slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Landscapers should use LocalBusiness schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are and what you do. Schema clarifies clear content for AI; it never rescues a gallery-only site or a buried answer.

2 min read

A landscaping company needs a website rebuild for AEO when the site is a slow photo gallery with little readable text, hard for AI crawlers to read, or built without per-service answer-first pages and schema. The rebuild is the access layer everything else depends on.

2 min read

Locksmiths should use the Locksmith (a LocalBusiness subtype) schema with accurate name, address, phone, service area, hours, license, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A locksmith needs a website rebuild for AEO when the current site is slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Martial arts schools should use SportsActivityLocation (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and programs, plus FAQ schema on answer pages — it helps engines parse what you teach and confirm you're open. Schema clarifies readable content; it never rescues a booking widget.

2 min read

A martial arts school needs a website rebuild for AEO when programs and pricing live in a booking widget, the site is slow, or content renders only in the browser — because the engine can only recommend what it can read. The rebuild puts your programs, pricing, and hours in readable text everything else depends on.

2 min read

Painters should use the HousePainter (a LocalBusiness subtype) schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are. Schema clarifies content for AI; it never rescues a gallery-only site or a buried answer.

2 min read

A painting company needs a website rebuild for AEO when the site is a slow photo gallery with little readable text, hard for AI crawlers to read, or without per-service answer-first pages and schema. The rebuild is the access layer everything else depends on.

2 min read

Personal trainers should use the SportsActivityLocation (a LocalBusiness subtype) or LocalBusiness schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages — it helps engines parse what you offer. Schema clarifies readable content; it never rescues a booking widget.

2 min read

A personal trainer needs a website rebuild for AEO when services and pricing live in a booking widget or Instagram bio, the site is slow, or content renders only in the browser — because the engine can only recommend what it can read. The rebuild puts your services and pricing in readable text.

3 min read

Pest control companies should use LocalBusiness schema with accurate name, address, phone, service area, hours, license, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A pest control company needs a website rebuild for AEO when the current site is slow, hard for AI crawlers to read, or built without per-pest answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Pool companies should use LocalBusiness schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are and what you do. Schema clarifies clear content for AI; it never rescues a thin site or a buried answer.

2 min read

A pool company needs a website rebuild for AEO when the site is thin or slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Climbing gyms and rec centers should use the SportsActivityLocation or ExerciseGym (LocalBusiness subtypes) schema with accurate name, address, phone, hours, and offerings, plus FAQ schema on answer pages — it helps engines parse what you offer. Schema clarifies readable content; it never rescues a booking widget.

2 min read

A climbing gym or rec center needs a website rebuild for AEO when passes and pricing live in a booking widget, the site is slow, or content renders only in the browser — because the engine can only recommend what it can read. The rebuild puts your passes, pricing, and hours in readable text the rest depends on.

2 min read

Remodelers should use the GeneralContractor (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A remodeling business needs a website rebuild for AEO when the site is slow, an unreadable image-heavy gallery, or built without per-project answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

2 min read

Restaurants should use Restaurant schema with accurate name, address, phone, hours, cuisine, price range, menu, and reservation info, plus FAQ schema on answer pages — it helps engines parse what you serve and confirm you're open. Schema clarifies a readable menu for AI; it never rescues a PDF menu or wrong hours.

2 min read

A restaurant needs a website rebuild for AEO when the menu is a PDF or image, the site is slow, or hours and content live in widgets AI crawlers can't read — because the engine can only recommend what it can parse. The rebuild puts your menu, hours, and answers in readable text everything else depends on.

2 min read

Solar installers should use a LocalBusiness subtype (HomeAndConstructionBusiness or Electrician) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages. Schema clarifies content for AI; it never rescues a slow site or a buried answer.

2 min read

A solar installer needs a website rebuild for AEO when the site is slow, an unreadable animation-heavy shell, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything depends on.

3 min read

Sports instructors should use SportsActivityLocation (a LocalBusiness subtype) schema with accurate name, address, phone, hours, and lessons, plus FAQ schema on answer pages — it helps engines parse what you teach and confirm you're open. Schema clarifies readable content; it never rescues a booking widget.

2 min read

A sports instructor needs a website rebuild for AEO when lessons and pricing live in a booking widget, the site is slow, or content renders only in the browser — because the engine can only recommend what it can read. The rebuild puts your lessons, pricing, and hours in readable text everything else depends on.

2 min read

Tire shops should use the TireShop (a LocalBusiness/Store subtype) schema with accurate name, address, phone, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are and when you're open. Schema clarifies content for AI; it never rescues a thin site or wrong hours.

2 min read

A tire shop needs a website rebuild for AEO when the site is thin or slow, hard for AI crawlers to read, or without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Window and gutter companies should use LocalBusiness schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse who you are and what you do. Schema clarifies clear content for AI; it never rescues a thin site or a buried answer.

2 min read

A window and gutter company needs a website rebuild for AEO when the site is thin or photo-only, hard for AI crawlers to read, or without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Yoga and Pilates studios should use the HealthClub or SportsActivityLocation (LocalBusiness subtypes) schema with accurate name, address, phone, hours, and class styles, plus FAQ schema — it helps engines parse what you offer. Schema clarifies readable content; it never rescues a booking widget.

2 min read

A yoga or Pilates studio needs a website rebuild for AEO when the schedule and pricing live in a booking widget, the site is slow, or content renders only in the browser — because the engine can only recommend what it can read. The rebuild puts your class styles, pricing, and hours in readable text.

2 min read

AI crawlers and Googlebot are separate bots with different jobs — Googlebot renders JavaScript and builds a search index, while most AI crawlers fetch raw HTML, skip JavaScript, and feed answer engines. The practical upshot is that ranking in Google does not guarantee an AI crawler can even read your page.

2 min read

Yes — both Squarespace and Wix serve server-rendered HTML that AI crawlers can read, so a site on either can be cited. Their trade-off is less control over technical details like schema, markup, and speed, so you compete on content while accepting tighter limits on fine-grained optimization.

2 min read

Usually yes — if an AI crawler can't get past your paywall to read the full text, it can't cite what it can't see, so hard paywalls effectively hide that content from answer engines. The fix is to expose a crawlable, answer-first summary or excerpt that engines can quote while your full piece stays gated.

2 min read

Yes — AI engines can read and cite PDFs when they're text-based, crawlable, and well-structured, but a clean HTML page is almost always easier to extract and cite. Use PDFs for documents that must be PDFs, and publish the key answers as HTML when you actually want the citation.

2 min read

Yes — a current XML sitemap helps AI crawlers discover and prioritize your pages, especially new or deep ones that internal links alone might miss. It's a discovery aid, not a ranking trick, so it speeds and broadens crawling but never substitutes for crawlable, answer-first content.

2 min read

Possibly — Cloudflare can block AI crawlers through its bot-management and one-click AI-bot-blocking features, and as of 2025 it began blocking known AI bots by default for new sites. If your content vanished from AI answers, check your Cloudflare bot settings before assuming the problem is your content.

2 min read

HTTPS is a baseline expectation, not a differentiator — having it won't boost your AI citations, but lacking it is a credibility and security red flag that can undercut trust. Treat HTTPS as table stakes you must have, then earn trust through accuracy, sourcing, and corroboration.

2 min read

It can — if content only loads as the user scrolls via JavaScript, an AI crawler that doesn't scroll or run scripts never sees it, so anything below the initial load is invisible. The fix is to make that content reachable through real, crawlable links or server-rendered HTML, not just scroll events.

2 min read

Republishing helps only when it reflects a genuine update on the same URL — substantively revising a page and refreshing its date restores freshness while keeping its authority. Changing the URL or just bumping the date without real changes hurts more than it helps, by resetting authority or sending a hollow signal.

2 min read

AEO and SEO aren't rivals — they're one discipline pointed at two surfaces, the ranked link and the AI answer. The same crawl, index, and authority signals feed both, and being ranked and being cited reinforce each other in a single compounding loop. Here's how the relationship actually works.

6 min read

AI crawlers visit on no fixed schedule — frequency scales with how often you publish, how authoritative your domain is, and how easily bots can reach your pages. Active, well-linked sites get crawled often; thin or hard-to-reach ones get crawled rarely, which is why server logs are the only reliable way to know.

2 min read

Yes — WordPress is well suited to AEO because it serves server-rendered HTML by default, which is exactly what AI crawlers can read. What decides your results isn't the platform but how you configure it — clean HTML, fast pages, structured content, and answer-first writing all matter more than the CMS name.

2 min read

Plumbers should use LocalBusiness/Plumber schema with accurate name, address, phone, service area, hours, and services, plus FAQ schema on answer pages — it helps engines parse and confirm who you are and what you do. Schema clarifies correct content for AI; it never rescues a slow site or a buried answer.

2 min read

A plumber needs a website rebuild for AEO when the current site is slow, hard for AI crawlers to read, or built without per-service answer-first pages and schema — because no amount of content fixes a foundation engines can't parse. The rebuild is the access layer everything else depends on.

2 min read

Roofers need RoofingContractor (a LocalBusiness subtype) schema with accurate name, address, phone, geo, hours, area served, services, and aggregate reviews — it labels your business data so engines can parse and trust it. Schema reinforces clean content and credentials rather than replacing them.

2 min read

A roofer needs a website rebuild for AEO when the current site is slow, image-heavy, or built so AI crawlers see an empty page — because if engines can't read it, no content or reputation can save it. If your site is already fast and crawlable, you may only need better pages instead.

2 min read

For almost every site that wants visibility, no — blocking AI crawlers removes you from the AI answers your customers now ask, which is the opposite of what AEO is for. Block only specific bots for a deliberate reason like protecting paid or proprietary content, never as a default.

2 min read

Dynamic rendering — serving crawlers a pre-rendered HTML version while users get the JavaScript app — can make a client-side site readable to AI bots, but it's a workaround. The more durable fix is real server-side or static rendering that gives everyone the same crawlable HTML, with no separate bot path to maintain.

2 min read

The first step is to confirm AI crawlers can actually read your pages — because if they can't, nothing else matters. Once access is verified, lead your most important page with a direct answer to the real question. Access first, answer-first second, everything else after.

2 min read

GPTBot usually isn't crawling your site for one specific, fixable reason — a robots.txt or CDN block, JavaScript-only content it can't render, orphaned pages with no links, or a new low-authority domain it hasn't prioritized yet. Check your server logs to confirm which, then fix that one gate.

2 min read

No — blocking GPTBot has zero effect on your Google rankings because GPTBot and Googlebot are completely separate crawlers. It only stops OpenAI from reading your pages, which costs you ChatGPT citations and the high-intent traffic they bring, with no offsetting SEO upside.

2 min read

Not all AI crawlers do the same job. Search and user-fetch bots (OAI-SearchBot, ChatGPT-User, Claude-SearchBot, PerplexityBot, Bingbot) drive citations and should be allowed; training crawlers (GPTBot, ClaudeBot) and Google-Extended are an opt-in choice. Here's what each one does.

3 min read

To implement structured data for AEO, add schema.org JSON-LD that labels your content type (Article, FAQPage, HowTo), keep it in sync with the visible page, and validate it so answer engines can confidently extract and cite your content.

1 min read

For AI crawlers, server-side rendering wins decisively. Vercel and MERJ analyzed 500M+ GPTBot requests and found zero JavaScript execution — so client-rendered content is invisible to most AI engines. If the answer isn't in the server HTML, you can't be cited. Here's how to decide.

3 min read

For AI citations, clean semantic HTML beats schema markup. Controlled tests found no measurable citation lift from adding schema, while readable, well-structured HTML is what engines actually extract. Schema still helps parsing and rich results — so do both, but prioritize the HTML.

3 min read

The schema.org sameAs property links your entity to its authoritative reference pages — Wikipedia, Wikidata, official profiles — so engines can confidently merge them into one identity. It won't directly lift citations, but it's a core disambiguation signal. Here's the JSON-LD and how to use it.

3 min read

Your server logs are the ground truth for whether AI crawlers reach your site. This guide gives copy-paste grep commands to find GPTBot, ClaudeBot, and PerplexityBot hits, count their visits, spot what they crawl, and catch the 403s and 404s that block citations.

3 min read

Yes — page speed affects AI citations. SE Ranking found pages with a First Contentful Paint under 0.4 seconds earned roughly three times more AI citations than slower pages. Crawlers have budgets and timeouts, so slow pages get fetched less. Here's how to measure and fix it.

3 min read

To be cited by AI in each language you serve, publish genuinely native, answer-first content per language — not machine-translated dumps — and signal language clearly with hreflang, the lang attribute, and distinct URLs. Earn authority within each language, because citations don't transfer between them.

2 min read

A client-rendered SPA ships an empty shell that AI crawlers can't read. To make it citable, get your content into the initial HTML — by migrating to an SSR/SSG framework, adding server rendering to your existing app, or prerendering routes to static HTML. Here are the patterns, with code.

4 min read

Vercel and MERJ analyzed 500M+ GPTBot requests and found zero JavaScript execution — so content rendered client-side is invisible to AI crawlers. If your answer only appears after JS runs, you can't be cited. Here are the SSR, SSG, and prerender fixes, with code.

4 min read

No — AEO is not replacing SEO, it is extending it. Roughly 70–80% of the fundamentals overlap, and the same crawlability, semantics, and authority feed both ranked links and AI citations.

6 min read

No — no major AI engine uses llms.txt. OtterlyAI found just 84 of 62,100 AI bot requests touched the file (0.1%), and Google's John Mueller compared it to the long-ignored keywords meta tag. It's harmless, low-cost infrastructure — not a citation lever.

3 min read

Most AI crawlers don't run JavaScript, so the test is simple — view what's in the raw HTML, not the rendered DOM. This guide walks through the JS-disabled browser test and curl checks that show you exactly what GPTBot and PerplexityBot see.

3 min read

AI engines can only cite pages their crawlers are allowed to fetch. This guide gives you a verified, copy-paste robots.txt block that explicitly allows GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, and Bingbot — plus the one mistake that silently blocks them all.

3 min read