features

Page Summaries

How AIO Radar generates AI-optimized summaries for your pages.

What Are Page Summaries?

Page summaries are AI-generated descriptions of your content, optimized for how large language models understand and represent information. Each synced page gets a unique summary that helps AI assistants accurately describe your offerings.

Why This Matters

A summary is the sentence an assistant repeats when someone asks what your page is about.

Write it, or the model writes it for you.

Why Summaries Matter

AI Needs Concise Context

When an AI assistant recommends your business, it needs:

  • Accurate descriptions of what you offer
  • Relevant details for the user's query
  • Concise information it can cite
  • Page summaries provide exactly this - distilled, AI-optimized descriptions of each page.

    Better Than Excerpts

    Standard WordPress excerpts aren't optimized for AI:

    WordPress ExcerptAI Summary
    First 55 wordsKey information extracted
    May cut mid-sentenceComplete, coherent summary
    Generic contentOptimized for AI comprehension
    Static contentCan be regenerated as needed

    Viewing Summaries

    In WordPress Admin

    Go to AIO Radar → Content → Summaries → Generated to see all generated summaries:

  • Page title and URL
  • Generated summary text
  • Generation date
  • AI model used
  • Via Dashboard

    Your AIO Radar dashboard shows summary coverage:

  • Total pages synced
  • Pages with summaries
  • Pending summaries
  • Using WP-CLI

    bash
    # List pages and their summary status
    wp aio summaries list
    
    # List only the pages that still need one
    wp aio summaries list --status=no_summary
    
    # Show the summary for one page
    wp aio summaries show 123
    
    # Export to CSV
    wp aio summaries list --format=csv > summaries.csv

    Summary Generation

    When Summaries Are Generated

    Summaries are created:

  • During content sync (for new pages)
  • On manual regeneration request
  • When LLMs.txt is generated (for pages without summaries)
  • Generation Process

  • Page content is extracted from WordPress
  • Content is sent to AI provider (OpenAI, Anthropic, or Google)
  • AI generates a 150-200 word summary
  • Summary is cached in AIO Radar database
  • Summary is used in LLMs.txt and other features
  • AI Models Used

    ProviderModelSummary Style
    OpenAIGPT-4oConcise, factual
    AnthropicClaude 3Detailed, nuanced
    GoogleGemini ProBalanced

    Summary Content

    What's Included

    A good summary covers:

  • What the page offers (products, services, information)
  • Who it's for (target audience)
  • Key details (pricing, features, benefits)
  • Unique value (what differentiates from competitors)
  • Example Summary

    Page: Costa Rica Adventure Tours

    Summary:

    Costa Rica Adventure Tours offers guided eco-tourism experiences throughout Costa Rica. Tours include zip-lining through rainforest canopies, whitewater rafting on Class III-IV rapids, volcano hiking at Arenal and Poás, and wildlife watching in Tortuguero. Small groups of 8-12 people with bilingual guides. Sustainable tourism certified. Tours range from half-day excursions ($89) to week-long adventure packages ($1,899). Based in San José with pickup from major hotels.

    Managing Summaries

    Regenerate a Summary

    If a summary is outdated or inaccurate:

  • Go to AIO Radar → Content → Summaries
  • Press Generate Summaries
  • Regenerate All Summaries

    After major content updates:

    bash
    wp aio summaries generate --force --limit=100

    ⚠️ This may take time and use AI credits depending on your plan.

    Check Summary Coverage

    bash
    wp aio summaries stats

    Using Summaries on the Page

    A summary that exists only in your llms.txt is invisible to the assistants that fetch the

    live page, which is most of the ones that cite sites. There are three ways to get it onto the

    page itself, and they all render exactly the same markup.

    Auto-Display

    AIO Radar → Content → Summaries → Generated carries the Content settings form:

    SettingWhat it doesDefault
    Auto-Display SummariesInsert the summary into every page that has oneOff
    Display PositionBefore or after the page contentBefore content
    Serving DestinationOn-page, machine-only, or bothBoth

    Auto-display is the one to reach for when you want summaries everywhere and do not want to

    edit each page. Turn it off and place them by hand where the position matters.

    The Block

    In the editor, add the AI Summary block wherever the summary should sit. It shows a

    placeholder until that page has a summary.

    The Shortcode

    For the classic editor, page builders, or a theme template:

    text
    [aio_summary]
    AttributeWhat it doesDefault
    idShow another page's summary instead of this page'sThe current page
    classAdd a class to the wrapperNone
    text
    [aio_summary id="42" class="intro-summary"]

    In a template: echo do_shortcode( '[aio_summary]' );

    Nothing Renders on Machine-Only Pages

    A page whose serving destination is machine-only serves its summary through llms.txt,

    llms-full.txt and its .md file alone. The block and the shortcode both deliberately render

    nothing there. See Serving Destination.

    Markup and Classes

    Every path emits the same skeleton:

    html
    <div class="aio-summary aio-summary--open">
      <span class="aio-summary-label">Summary</span>
      <div class="aio-summary-content"><p>…</p></div>
    </div>

    In collapsed mode the wrapper is a <details> and the label its <summary>. The block adds a

    .wp-block-aio-optimiser-summary wrapper around it.

    Colours, open or collapsed, whether the label shows, per-page overrides and Custom CSS are all

    in Appearance.

    Where Else Summaries Are Used

    In LLMs.txt

    Summaries appear in your LLMs.txt file:

    text
    ## Pages
    
    - Costa Rica Tours: /costa-rica-tours
      Costa Rica Adventure Tours offers guided eco-tourism experiences...
    
    - Volcano Hiking: /volcano-hiking
      Explore Costa Rica's active volcanoes with expert guides...

    Schema Markup

    Summaries inform schema markup descriptions for:

  • TourTrip schema
  • Product schema
  • LocalBusiness schema
  • AI Assistants

    When AI assistants cite your pages, they use summary content to accurately describe your offerings.

    Best Practices

    Improve Source Content

    Better page content leads to better summaries:

  • Write clear, descriptive titles
  • Include key information in the first few paragraphs
  • Use bullet points for features/benefits
  • Include pricing and availability when relevant
  • Review Summaries

    Periodically review summaries for accuracy:

  • Check factual information
  • Verify pricing is current
  • Ensure descriptions match offerings
  • Keep Content Fresh

    Regenerate summaries when you:

  • Update pricing or availability
  • Add new features or services
  • Rebrand or change messaging
  • Make significant content changes
  • Troubleshooting

    Summary Not Generated

    Possible causes:

  • Page not synced - run a content scan
  • Generation failed - check error logs
  • API credits exhausted - check your plan
  • Summary Is Inaccurate

    Solution:

  • Update the source page content
  • Regenerate the summary
  • Review the new summary
  • Summaries Missing Key Info

    Tips:

  • Add key information prominently in page content
  • Use clear headings and structure
  • Include specific details (prices, features, locations)