10 Steps to Get Found in AI Search (SEO + AEO)
1. Use the “bouncer” strategy (dynamic rendering)
Dynamic rendering is like having a bouncer at the door of your website. When a human visitor arrives, they see the full interactive SPA. When a crawler like Googlebot or GPTBot shows up, the bouncer hands them a clean, pre‑rendered HTML version of the page.
2. Generate pre‑rendered HTML for key pages
Most AI and search crawlers still struggle to execute heavy JavaScript. If all your content only exists after React/Vue hydrates in the browser, crawlers miss it.
On modern hosting you have several options: - Vercel: Use SSR/ISR/SSG via frameworks like Next.js. - Netlify: Enable built-in prerendering. - Cloudflare: Use Workers/Pages to generate or serve HTML snapshots from the edge.
3. Tighten your meta tags for AI context
Crawlers want fast, unambiguous context. For every pre‑rendered page, make sure you have:
- A unique, descriptive <title>
- A rich <meta name="description">
- Open Graph (og:title, og:description, og:image) and Twitter Card tags.
4. Add JSON‑LD structured data
Structured data is how you talk to AI in its native language. JSON-LD blocks in your HTML explicitly define what’s on the page: an Organization, a ProfessionalService, an Article, and so on.
5. Put an edge layer in front of your app
To implement the “bouncer,” you need something sitting in front of your SPA that can see every request and decide what to serve.
6. Route AI crawlers to the pre‑rendered version
In that edge layer, detect important search and AI user agents - for example: Googlebot, GPTBot (OpenAI), Perplexity-User, and ClaudeBot.
7. Make sure your security isn’t blocking AI
A lot of security setups now block AI crawlers by default. Review your Cloudflare or Vercel bot-blocking settings to ensure you aren't blocking legitimate AI scrapers.
8. Give crawlers a map: robots.txt and sitemap.xml
Don’t make bots guess where your best content lives. Create a sitemap.xml and point to it in your robots.txt.
9. Test your setup like a bot
Your browser is the worst debugging tool here. Instead, test like a bot using curl:
curl -s -H "User-Agent: GPTBot" https://yourdomain.com/home
10. Monitor both SEO and AEO over time
Track Google Search Console, hosting analytics, and periodically ask the AI answer engines directly to see if they cite your site.