DaylytixEvery audit gets a score from 0 to 100. It is a quick way to see the overall technical health of a site and to track it over time. This page explains how it is calculated and how to raise it.
What the number means
| Score | Colour | Meaning |
|---|---|---|
| 80-100 | Green | Good. Most checks pass; focus on the remaining issues and on content. |
| 50-79 | Amber | Fair. Several areas have problems worth fixing. |
| 0-49 | Red | Poor. Start with the critical issues in the Overview tab. |
The score is not a Google metric. Google doesn’t use an overall SEO score. Treat it as a progress indicator for technical health, not a prediction of rankings.
How the score is calculated
The audit groups its checks into 21 areas. In each area, every passed check counts 1 point for the area and every issue counts against it by severity: a critical issue 5, a warning 2, a notice 1. An area with 8 passes and 2 warnings scores 8 out of 12, so 67; with 2 notices instead it scores 80. Performance is the one exception: it uses the PageSpeed Insights mobile score directly.
The overall score is a weighted average of the areas. An area with nothing to check on the site, such as hreflang on a site in one language, is left out and its weight is shared by the rest. The heaviest areas:
| Area | Weight |
|---|---|
| Performance (PageSpeed mobile score) | 10% |
| Basic SEO | 10% |
| On-page quality | 10% |
| Core Web Vitals | 8% |
| Technical | 8% |
| Links | 7% |
| Security | 5% |
| Mobile usability | 5% |
| Headings, structured data, images, content analysis | 4% each |
| Nine smaller areas (compression, caching, soft 404s, mixed content, hreflang and others) | 2-3% each |
Critical issues cap the score
An audit with at least one critical issue scores 59 at most, however well the rest of the site does. A serious problem, such as a site without HTTPS or pages blocked from Google, is never hidden behind a good average. Fix the critical issues first and the cap goes away on the next audit.
Severity and the issue counts
Issues are labelled Critical, Warning or Notice so you know what to fix first, and the label now changes the score, as above. The issue counts also include the findings of the technical tabs, such as response codes, redirect chains, duplicate content and internal links, without counting the same problem twice. Those tab findings count in the totals but not in the score.
What is not in the score
- Search Console and Analytics data - clicks, traffic and rankings are shown in their own tabs but don’t change the score.
- Accessibility - it has its own score in the Technical tab.
- Content decay, rank tracking and backlinks - reported separately.
Why the score changed between audits
- Different pages were crawled. A higher page limit or new pages on the site change the balance of passes and issues.
- PageSpeed varies. The mobile performance score moves from run to run, and it carries 10% of the total.
- The site changed. A deploy, a plugin update or a template change can fix or create issues on many pages at once.
- The scoring changed. Since October 16, 2026 issues weigh by severity and a critical issue caps the score, so audits from before that date can show a jump in Score History.
To see exactly what changed, open Compare Audits in the Monitoring group and pick the two runs. See Comparing audits.
How to raise your score
- Open the Overview tab and fix the critical issues first: they cap the score.
- Then the warnings, which weigh twice as much as notices.
- Look for template-level problems - the same issue on many pages often comes from one template, so one fix covers them all.
- Run the audit again, ideally with the same page limit, and compare the two runs.
Track the trend in Score History, and schedule the audit to repeat in Scheduled Audits so you notice drops early. The AI Fix Agent turns the titles, descriptions and alt texts of an audit into ready fixes.