AEO NIUEXA

Site Dashboard and What to Do Next

7 min read

One Page per Site

Every site you scan gets a dashboard. Open it from Dashboard → View report or from any page report's breadcrumb. It brings together the latest scan of each page and tells you what to fix first.

The site dashboard for harborlane.example: AEO Score 75 with +6.3 average per page, 0 critical, 17 quick wins, 76% pass rate, and the start of What to do next.
The top of a site dashboard: the site score, three counters and the first fix to make.
  • AEO Score - the average of the latest score of each counted page. The change next to it is the average change per re-scanned page, compared only with scans made under the same rule set.
  • Critical and Quick wins - counted from the ranked list below: critical problems, and low-effort fixes for critical, high and medium problems. Pass rate is the share of applicable checks that passed on the counted pages.
  • Client - assign the site to one of your clients (see Clients and white-label reports).
  • Export downloads the site report as PDF or HTML; Re-analyze scans the pages again, with the cost shown first.

What to Do Next

One ranked list of fixes for the whole site, built from the latest scan of every page. It is ordered by severity first, then by how much the check counts (its importance times how well the evidence supports it), then by how many pages fail it. The first ten are shown; the rest are in All findings on the Issues tab.

What to do next: numbered fixes, each with its check name, a plain description, who does it, the effort, the stage, how many pages are affected, How to fix, Copy ticket and Mark done.
Each fix says who usually does it, how big it is, at which stage it gets in the way and which pages are affected.
Who and how big

Who usually makes the fix (you, a developer or a writer) and the effort: quick, medium effort or a larger project.

Stage

Where, from crawler to visitor, the problem gets in the way: crawler access, indexing, answer quality, trust and citation, or clicks and visits. The stage helps you read the list; it never changes the order or the score.

How to fix

The fix in plain steps, example pages where it fails and, under Based on, the rule ids from our knowledge base that support the check. When Auto-Fix can apply the change, the fix says Auto-Fix available.

What is not ranked: unproven checks (the evidence that they affect AI answers is not strong enough) are counted in a note and shown in the full report, but not ranked. Results judged by a rule that no longer applies are left out until the page is re-scanned. The list never promises how many points a fix will add.

Developer Tickets

  • Copy ticket copies one fix as a ready-to-paste ticket in Markdown: why it matters, the evidence, the affected pages, how to fix it and how to check it is done.
  • Tickets (Markdown) and Spreadsheet (CSV) download every ranked fix at once, for your issue tracker or a spreadsheet.
  • When an Auto-Fix rule exists for the problem, the ticket also carries the permanent HTML or JSON-LD to paste into the page template.
  • Text that comes from the scanned pages is made harmless in the ticket, and spreadsheet cells never start a formula.

Marking Fixes Done

When a fix is made, choose Mark done. The Fixes you marked done panel then shows, for each page, the check's result before your mark and on the first scan after it, so you can see whether the change worked. The score change is shown only when both scans used the same rule set. Undo mark removes it.

Fixes you marked done: Publish a valid sitemap, marked done on Sep 29 with a note; the home page went from Failed to Passed, AEO Score change +6.3.
Before and after: the result of each page before your mark and on its first scan after it.

The Tabs

Overview
Average of each dimension, key metrics and the site score over the last 90 days
Pages
Every analyzed page with its score and issues by severity; search, filter by grade and open a page's report
Issues
All findings, most severe first, and the broken links found on your pages
Vitals
Speed per page from Google's lab test: LCP and TBT simulated, CLS observed
AI Visibility
The brand's visibility summary, or Enable Tracking to start
The Pages tab: each analyzed page with its score, its issues by severity and a View button; the home page shows 2 scans and its score change. Search and grade filters sit above the list.
The Pages tab.

Which Pages Count

  • A page is one address: we ignore the scheme and host spelling, the fragment, tracking parameters (utm_*, gclid, fbclid and similar) and a trailing slash, so a re-scan updates the same page.
  • When a page names another analyzed page as its canonical, it is listed as Counted as that page and left out of the page count, the scores and the fixes.
  • When some pages were scanned under an earlier rule set, a notice says how many. Their scores are not compared with newer ones; re-scan them to compare like with like. The 90-day trend uses the newest rule set only.