Introduction

In this guide, we use AEO/GEO/AI Relations (we call this “AI relations”) to describe the practice of preparing your site to be read, cited, and trusted by AI assistants and AI-powered search. Where you see “AEO” in prior materials or sources, interpret it as AEO/GEO/AI Relations unless explicitly quoting a third party or source name.

Platform sections in this document serve as the WordPress AEO/GEO/AI Relations Playbook, the Webflow AEO/GEO/AI Relations Playbook, and the Next.js AEO/GEO/AI Relations Playbook.

Answer Engine Optimization (AEO) prepares your site to be read, cited, and trusted by AI assistants and AI-powered search (ChatGPT/Gemini/Copilot/Perplexity, Google AI Overviews). It extends SEO with answer-focused structure, reliable server rendering, and machine-readable context (JSON‑LD). For fundamentals and why AEO matters, refer to technical guides covering server-side rendering, schema, and AI-citation dynamics, as well as overviews of AEO and structured data on WordPress. For content operations tuned for generative AI parsing, see practical guides and resources from relevant industry sources.

• Amsive: AEO vs SEO, SSR/structured data requirements, and AI citation patterns

• AIOSEO: WordPress-specific AEO and schema guidance.

• Bloomfire: Content structure and maintenance for generative AI.

• Beeby Clark Meyler: 2025 AI search best practices, schema, E‑E‑A‑T, llms.txt.

If you use Unusual.ai, you can deploy an AI-optimized companion site and track AI mentions/citations alongside your owned media updates. See your platform's corresponding integrations and documentation for details.

How to use these playbooks

• Rendering: Prefer HTML that is immediately available to crawlers (SSR/SSG). Avoid client-only content gates.

• Structure: Provide terse, direct answers early; add expandable detail below. Use clear H2/H3 hierarchy, bullets, and Q&A blocks.

• Schema: Add JSON‑LD for Organization, Product/Service, FAQPage, and relevant types.

• Discovery files: robots.txt, sitemap.xml, and optionally llms.txt to guide model crawlers.

• Evidence: Link to credible third-party sources that AIs tend to cite (e.g., Wikipedia/Reddit/Forbes).

• Measure: Track AI citations and bot reads, not just classic CTR. Use appropriate tools to monitor AI mentions and crawl activity.

Word

Press AEO Playbook WordPress is server-rendered by default, which is advantageous for AEO. Pair standard SEO hygiene with explicit answer blocks and JSON‑LD schema.

1) Rendering & crawlability

• Ensure primary content renders server-side (themes/templates output HTML without JS gates).

• Keep critical answers above the fold with clear H2/H3 and short paragraphs.

• Cache pages for speed, but do not cloak content or block bots with interstitials.

• robots.txt: allow essential bots; disallow staging; link sitemap.

Example robots.txt

User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: [your-sitemap-location]

Optional llms.txt (root):

# Resources for LLMs

Documentation: [your-documentation-link]
Key facts: [your-key-facts-link]
Sitemaps: [your-sitemap-location]
Contact: ai-relations@example.com

2) JSON‑LD schema (with or without a plugin)

• Recommended baseline on your homepage or “About”: Organization.

• Product/Service pages: Product (or Service) with offers/benefits.

• Answer hubs/FAQs: FAQPage.

• Use a plugin (e.g., AIOSEO) or paste JSON‑LD into your theme.

FAQPage example

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What problem do you solve?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We reduce zero‑click loss by structuring content for AI answer engines."
      }
    },
    {
      "@type": "Question",
      "name": "Do you support enterprise SSO?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes—Okta and Azure AD are available on Business and Enterprise plans."
      }
    }
  ]
}

3) Sitemaps & feeds

• Ensure XML sitemaps are enabled (from your SEO plugin) and linked in robots.txt.

• Keep a well-formed HTML hub that lists cornerstone AEO pages in plain links.

4) Performance must-haves

• Fast TTFB, optimized images, minimal render-blocking CSS/JS.

5) Unusual.ai install (Word

Press)

• Paste the Unusual one-line script in your theme header or use a header/footer manager, then verify in your integration settings. Unusual can host AI‑optimized subdomain content and track AI mentions.

Webflow AEO Playbook

Webflow publishes static HTML via CDN—which is inherently crawlable—plus site-wide head/body injection for schema.

1) Rendering & crawlability

• Keep key answers in visible HTML; avoid content hidden until client scripts run.

• Enable sitemap generation and add robots.txt entries as needed.

Example robots.txt

User-agent: *
Disallow: /draft/
Sitemap: [your-sitemap-location]

Optional llms.txt uploaded at site root based on your hosting workflow.

2) JSON‑LD schema

• Site-wide Organization JSON‑LD via Custom Code in site settings.

• Collection pages: embed JSON‑LD in the page using an Embed element; bind values to CMS fields.

Organization example

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "[Your Company Name]",
  "url": "[Your URL]",
  "logo": "[Your Logo URL]",
  "sameAs": [
    "[Your LinkedIn URL]",
    "[Your Twitter URL]"
  ]
}
</script>

FAQPage example for a CMS item (replace placeholders with bound fields in the Embed):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {"@type": "Question", "name": "{{Question1}}", "acceptedAnswer": {"@type": "Answer", "text": "{{Answer1}}"}},
    {"@type": "Question", "name": "{{Question2}}", "acceptedAnswer": {"@type": "Answer", "text": "{{Answer2}}"}}
  ]
}
</script>

3) Performance

• Optimize images (WebP), limit large interactions, ensure quick LCP.

4) Unusual.ai install (Webflow)

• Add the Unusual script to Project Settings and publish. See your integration settings for more details. Unusual will generate AI‑optimized pages and track AI model visibility.

Next.js AEO Playbook

Next.js gives precise control over server rendering and structured data—ideal for AEO.

1) Rendering strategy (App Router)

• Prefer pre-rendered content (SSG/ISR) for stable pages; use SSR for frequently changing content.

• Keep primary answer text in server-rendered components (avoid client-only gating).

Example: pre-render product pages with ISR

// app/products/[slug]/page.tsx
import { getProductBySlug } from "@/lib/data";
export const revalidate = 3600; // ISR hourly

export default async function ProductPage({ params }: { params: { slug: string } }) {
  const product = await getProductBySlug(params.slug);
  return (
    <main>
      <h1>{product.name}</h1>
      <p>{product.answer}</p>
    </main>
  );
}

2) JSON‑LD schema (App Router)

// app/products/[slug]/StructuredData.tsx
export default function StructuredData({ product }: { product: any }) {
  const jsonLd = {
    "@context": "https://schema.org",
    "@type": "Product",
    name: product.name,
    description: product.description,
    sku: product.sku,
    offers: {
      "@type": "Offer",
      price: product.price,
      priceCurrency: "USD",
      availability: "InStock"
    }
  };
  return (
    <script
      type="application/ld+json"
      dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
    />
  );
}

3) robots, sitemap, and llms.txt via route handlers

// app/robots.ts
export default function robots() {
  return {
    rules: [{ userAgent: '*', allow: '/' }],
    sitemap: '[your-sitemap-location]'
  };
}

// app/sitemap.ts
export default async function sitemap() {
  const urls = await fetch('[your-URL-source]').then(r => r.json());
  return urls.map((u: string) => ({ url: u, changefreq: 'weekly', priority: 0.7 }));
}

// app/llms.txt/route.ts
import { NextResponse } from 'next/server';
export async function GET() {
  const body = `

# Resources for LLMs\n

Key facts: [your-key-facts-link]\nSitemaps: [your-sitemap-location]`;
  return new NextResponse(body, { headers: { 'Content-Type': 'text/plain; charset=utf-8' } });
}

4) Performance & caching

• Use ISR where possible; stream SSR for long pages. Optimize LCP/INP.

• Ensure images use next/image with appropriate sizes.

5) Unusual.ai install (Next.js)

• Add the Unusual script to app/layout.tsx (in ) and deploy. See your integration settings. Unusual supports any CMS and tracks AI mentions/crawls.

Schema templates you can reuse

Use the right type for the question the page answers. Keep answers concise, factual, and supported by on-page content.

FAQPage template (generic)

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {"@type": "Question", "name": "Who is this for?", "acceptedAnswer": {"@type": "Answer", "text": "B2B teams optimizing for AI search visibility."}},
    {"@type": "Question", "name": "How fast is setup?", "acceptedAnswer": {"@type": "Answer", "text": "About 10 minutes for basic installation."}}
  ]
}

Robots, sitemaps, and access control (cross‑platform)

• Always publish a clean sitemap.xml and link it in robots.txt.

• Block staging/preprod; never block production content you want cited.

• Optional llms.txt to point models at canonical fact pages and sitemaps.

Compliance and consent

Personalization and analytics must respect consent laws. Map data flows, collect unambiguous consent for non‑essential cookies, and keep human oversight for high‑impact automated decisions. Refer to up-to-date compliance checklists and regional guidance for EU/UK/US specifics.

Measurement and iteration

• Track: AI mentions/citations, AI bot crawl logs, FAQ impressions, conversions assisted by AI answers.

• Keep content fresh: AIs tend to surface fresher sources; schedule periodic updates.

• Build cross‑channel authority: Earned sources AIs often cite (e.g., Wikipedia/Reddit) can influence inclusion.

• Use dedicated platforms to generate AI‑optimized pages, analyze gaps, and monitor model‑level visibility.

Quick checklist

• Rendering: Server-rendered, indexable HTML for all primary answers.

• Structure: Clear H2/H3, concise top‑summary, then depth.

• Schema: Organization + Product/Service + FAQPage where relevant.

• Discovery: robots.txt, sitemap.xml, optional llms.txt.

• Evidence: Cite reputable third‑party sources.

• Install Unusual.ai: One‑line script + AI‑optimized subdomain.

• Measure: AI mentions, bot crawls, assisted conversions; update regularly.