How to Read the SEO Audit Report
The audit report is primarily a list of identified issues across the site's pages. There are a total of 65 checks, categorized into six categories and three levels of importance. Understanding this structure saves hours: it becomes clear what to fix today and what can be left untouched forever. Besides the list of issues, the report includes a site profile, a speed block, Core Web Vitals, and a visibility block in AI search — more on these below.
Three Levels of Importance
| Level | What It Means | Number of Checks |
|---|---|---|
| Error | The page is inaccessible to search or is technically broken | 12 |
| Warning | It works but hinders ranking or user experience | 31 |
| Note | Not critical, should be fixed if possible | 22 |
Errors are 4xx and 5xx codes, inaccessibility, redirect loops, multiple canonicals, content rendered only by JavaScript, missing or duplicate Titles, broken JSON-LD markup, links to broken pages, mixed content, and unpassed Core Web Vitals. Everything else can wait.
Six Categories
| Category | About | Analysis |
|---|---|---|
| Indexing and Crawling | Will the page appear in search at all; robots.txt, access for AI bots, JavaScript sites | indexing issues |
| Meta and On-Page | Title, Description, headings, alt, microdata | meta tag issues |
| Content | Volume, duplicates, keyword stuffing, llms.txt, citation in AI search | content and speed |
| Performance | Response time, weight, blocking scripts, Core Web Vitals, mobile speed | content and speed |
| Links and Structure | Broken links, orphans, depth | links and security |
| Security and HTTPS | Mixed content, HSTS | links and security |
In What Order to Fix
- Errors on important pages. An inaccessible or closed page does not rank at all — nothing else matters for it.
- Mass warnings. One issue on five hundred pages is a template problem, fixed with one edit.
- Warnings on pages that bring traffic. Check the 'Traffic' column in the 'All Issues' table — more on that below.
- Notes — on a residual basis. Lack of Open Graph does not hinder ranking, although it spoils the appearance of the link in messengers.
Messages Above the Report
Sometimes a message appears above the report — it explains why the check saw the site differently than a visitor:
- “The site's content is rendered by JavaScript — we checked it in a browser.” The main code has almost no text and links, so the audit opened the pages in a real browser. The report is complete, but search engines and AI bots without rendering see a blank page. The solution is server-side rendering or pre-rendering.
- “The site's content is rendered by JavaScript” without mentioning the browser — the same situation, but it was not possible to check in a browser, so few pages were found.
- “The site redirects to…” — the main page redirects to another domain, there is nothing to check at this address. The button next to it starts an audit of the new domain.
- “The site is protected from bots” — the main page responds “access denied” (Cloudflare or hosting protection). Check in Search Console via “URL Inspection” whether Googlebot can access the page, and for the audit, add us to the protection exceptions.
If no pages opened, instead of a health score, there is a “—”: there is nothing to evaluate.
Site Profile
A summary of the site: CMS, how many pages are indexed by Google, and how many are indexable according to our crawl, links, robots.txt, sitemap, and llms.txt. Separately — domain metrics:
- Domain Rating — the authority of the domain based on the link profile from 0 to 100 according to Ahrefs. In parentheses — the change since the last audit of this site.
- Domain Age — based on the registration date from the domain registry.
- In the web archive since — the year of the first snapshot of the site in the Wayback Machine: shows how long the site has been on the domain.
Speed and Core Web Vitals
Data from Google PageSpeed Insights for the main page and several pages from different sections: in the free check — for three pages, in the full audit — for six. All pages are measured in the mobile version, the main page — also for desktop.
- Real Visitors. Chrome visitor statistics for 28 days: LCP (loading of the main block, norm ≤ 2.5 s), INP (response to clicks, norm ≤ 200 ms), and CLS (layout shifts, norm ≤ 0.1), and verdicts “Passed”, “On the Edge”, or “Not Passed”. If there is little data for the page itself, data for the entire site is shown. If visits from Chrome are few and for the site as a whole, there will be a note “Few Chrome Data” — then rely on the lab measurement.
- Lab Measurement. A table for pages: PageSpeed score from 0 to 100 on mobile and desktop (90+ — good, 50–89 — average, below 50 — slow), LCP, CLS, TBT (how much scripts block the page), and server response time.
- “What Will Speed It Up the Most”. Fixes that provide the greatest gain, with savings in seconds or kilobytes and the number of pages where this occurs.
Speed issues that make it to the general list are discussed in the article content and speed.
Visibility in AI Search
The audit asks the AI search engine Perplexity questions about the site's topic. If Search Console is connected, these are real queries without the brand name, for which the site is already displayed in Google; if not — questions that the AI composes based on the content of the main page in the site's language. Plus one question about the brand itself. In the free check — three topic questions and one about the brand, in the full audit — five and one.
- “Your site is cited: X out of N answers” — in how many answers your site appeared as a source.
- Does the AI know your brand — did it mention the site in response to a question about the company.
- Can AI bots read the site — are they blocked in robots.txt, and is there llms.txt.
- Transitions from AI in 28 days — if Google Analytics 4 is connected in SEO-Radar.
- “Who AI cites instead of you” — sites that AI refers to most often.
Next to it is a table of all questions: whether AI cites your site, only mentions it, or does not name it at all, and what sources it provided. Hover over the question to see the beginning of the answer.
The 'Traffic' Column
If Search Console is connected, the 'Traffic' column appears in the 'All Issues' table: how many clicks from Google in 28 days the pages with identified issues bring. If Google Analytics 4 is connected in SEO-Radar, visits are also visible there, and with set conversions — conversions and revenue from free transitions from Google. Start with issues that have the most traffic. Issues that affect the site as a whole (e.g., robots.txt or llms.txt) are not signed with the main traffic to avoid misleading.
Free Report, PDF, and Report Link
In the free check, some issues are hidden. If Search Console is connected, a hint will appear above the hidden ones: “Among the hidden are issues on pages that bring up to N clicks from Google per month”: this shows whether it is worth unlocking the full report.
The PDF report is available in the full audit and contains all blocks: site profile with Domain Rating, domain age, and web archive, speed and Core Web Vitals, visibility in AI search, and the 'Traffic' column for issues. The QR code in the PDF opens the same report via the link without logging into an account — convenient for passing to a contractor.
What Else Is in the Report
Besides the list of issues, the audit calculates Health Score — a summary assessment of the condition, builds a graph of internal links, and shows the “Lost Traffic” block: pages that are underperforming in clicks relative to their demand. An overview of the service as a whole — SEO Audit.