AEO NIUEXA

Quick Wins

Low-effort fixes
Start with access: These are small changes most sites can make in under an hour. They fix problems that stop crawlers from reaching or understanding a page. Re-scan after each change to see whether its check now passes; the AEO Score points to what to look at, it does not promise what a fix will do.

5-Minute Fixes

Start here - these quick changes take little effort:

Instant Wins
  • Let AI search crawlers fetch your pages (robots.txt)
  • Add a meta description
  • Add a canonical URL that opens a live page
  • Fix missing alt text
15-30 Minutes
  • Remove accidental noindex or nosnippet settings
  • Add basic Schema.org that matches the page
  • Add Open Graph tags
  • Improve heading hierarchy

Let AI Search Crawlers Fetch Your Pages

Time: 2 minutes

AI search and assistants can only use pages their crawlers are allowed to open. Search crawlers (OAI-SearchBot, PerplexityBot, Claude-SearchBot, Bingbot, Googlebot) and user-fetch crawlers (ChatGPT-User, Perplexity-User, Claude-User) should not be blocked on pages you want found. Training crawlers (GPTBot, ClaudeBot, CCBot, Google-Extended and similar) are a separate choice: blocking them does not hide your pages from AI search. This example allows search and declines training:

# robots.txt - allow AI search, decline training (example policy)
User-agent: OAI-SearchBot
User-agent: Claude-SearchBot
User-agent: PerplexityBot
Allow: /
Disallow: /admin/

User-agent: GPTBot
User-agent: ClaudeBot
User-agent: CCBot
User-agent: Google-Extended
Disallow: /

User-agent: *
Allow: /
Disallow: /admin/
Check existing rules: A crawler follows the group that names it and otherwise the "User-agent: *" group, so you do not need a line for every bot. If your "*" group says "Disallow: /", every crawler without its own group is blocked. A named group does not inherit the "*" rules, so repeat your private-path Disallow lines in it. When rules overlap, the longest matching rule wins and Allow wins a tie; the order of the lines does not matter.

Optional: Add llms.txt

Time: 10 minutes

llms.txt is an optional summary file. Google does not use it and no major AI engine is shown to, so your report shows this check as unproven and does not score it. If you want one, create a file at /llms.txt:

# Your Company Name
> A brief description of what your company/site does

## About
Your company provides [products/services]. We specialize in [key areas].

## Key Pages
- Homepage: https://example.com/
- Products: https://example.com/products/
- About Us: https://example.com/about/
- Contact: https://example.com/contact/

## Topics We Cover
- Topic 1
- Topic 2
- Topic 3

## Contact
- Email: contact@example.com
- Support: https://example.com/support/

## Content Guidelines
- Our content is factual and regularly updated
- Last reviewed: [Date]
- For the most current information, please visit our website

Add Basic Schema.org Markup

Time: 15 minutes

Add this JSON-LD to your homepage's <head> section, and keep every value in it the same as what visitors see on the page (the Markup Matches Page check compares them):

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#organization",
      "name": "Your Company Name",
      "url": "https://example.com",
      "logo": {
        "@type": "ImageObject",
        "url": "https://example.com/logo.png"
      },
      "description": "Brief description of your company",
      "sameAs": [
        "https://twitter.com/yourcompany",
        "https://linkedin.com/company/yourcompany"
      ]
    },
    {
      "@type": "WebSite",
      "@id": "https://example.com/#website",
      "url": "https://example.com",
      "name": "Your Site Name",
      "publisher": {"@id": "https://example.com/#organization"}
    }
  ]
}
</script>

For Blog Posts / Articles

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "description": "Article description",
  "author": {
    "@type": "Person",
    "name": "Author Name"
  },
  "datePublished": "2024-01-15",
  "dateModified": "2024-01-20",
  "publisher": {
    "@type": "Organization",
    "name": "Your Company",
    "logo": {
      "@type": "ImageObject",
      "url": "https://example.com/logo.png"
    }
  }
}
</script>

Fix Common Meta Tag Issues

Time: 10 minutes

Ensure your pages have these essential meta tags in the <head>:

<!-- Essential Meta Tags -->
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<meta name="description" content="Your page description (150-160 characters)">
<meta name="robots" content="index, follow">
<link rel="canonical" href="https://example.com/current-page/">

<!-- Open Graph for social sharing -->
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Your page description">
<meta property="og:type" content="website">
<meta property="og:url" content="https://example.com/current-page/">
<meta property="og:image" content="https://example.com/image.jpg">

<!-- Twitter Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="Your page description">
Auto-Fix: Add one script tag and Auto-Fix inserts the missing tags in the visitor's browser, with no source-code changes. Most AI fetchers do not run scripts, so they will not see those changes. Use "Copy permanent fix" on a rule to get the same tag as plain HTML to paste into your own template.