Site AI Audit: How to Read Your Score, Findings and Fix List

A website health report is only useful if you can tell what to do after reading it. Site AI Audit, the website health check built by Internet Solutions, runs about 50 checks in one pass and turns them into a score out of 100, a list of findings and instructions for fixing each one. This guide explains how to read that report: what the four area scores mean, how findings are ranked, what a typical finding looks like, and how to decide what to fix first. If you have run a check on your own site, keep the report open while you read.

Site AI Audit is one of our own products, available at getsiteaiaudit.com. Its claim is simple: SEO, speed, security headers and e-mail authentication in one report, with every finding explained in plain words and ranked by impact. The details below come from the product’s public pages at the time of writing; plans and limits may change, so check the product site for the current ones.

What the check covers

The report is organised around four vital signs of a website. Each has its own score, and together they form the overall score.

The check works from the outside, the way visitors and search engines see the site, so you do not install anything. It crawls up to 10,000 pages per check, using a crawler called SiteAuditBot that makes at most about three requests per second and follows your robots.txt rules, so the audit does not slow the website down.

What happens during the one to two minutes

A check typically takes one to two minutes, and the stages run in a fixed order:

1. Connection and SSL certificate. Is the site reachable, is the certificate valid, and how fast does the server answer?
2. robots.txt and sitemap. What search engines are allowed to see, and which pages you ask them to index.
3. Crawling pages. Titles, headings, links, images and indexing rules for up to 10,000 pages.
4. E-mail authentication. SPF, DKIM and DMARC records for your domain.
5. Google PageSpeed. Mobile speed and Core Web Vitals, measured by Google.
6. The report. A score out of 100, findings ranked by impact and how to fix each.

Knowing the order helps when you read the result. Problems with the certificate or robots.txt can affect everything that follows, so check those first.

Reading the scores

The report gives an overall score and one score per area. Think of them as a medical check: the overall score tells you whether to worry, the area scores tell you where.

A sample to practise on

The product’s own sample report, for a fictional shop, shows an overall score of 73 out of 100 with 17 findings, and area scores of 81 for SEO, 58 for speed, 67 for security and 92 for e-mail. Reading such a pattern is straightforward:

• The e-mail area is healthy, so authentication is mostly in place.
• SEO is decent but has room to improve.
• Security is middling and speed is the weakest, so the first effort goes to speed, then security.

That is a sample, not your site. Your own scores will differ, but the way of reading them is the same: find the lowest area, then look at the findings within it.

What counts as a good score

A score is a guide, not a trophy. A site can score 90 and still have one serious problem, such as a certificate about to expire, and a site can score 70 with nothing alarming. Treat the number as a trend: run the check, fix what matters, re-check, and watch whether the score rises. The findings behind the number matter more than the number itself.

How findings are ranked

The report lists findings in order of impact, so you do not have to decide what is urgent. Each finding follows the same pattern: a plain description of the problem, why it matters, and how to fix it. The product’s examples show the style:

• SEO warning: “12 pages share the same title.” Search engines cannot tell these pages apart and may show only one of them. The fix is to give every page a unique title of 50 to 60 characters with its main topic first.
• Speed warning: “Main content appears after 4.1 s on mobile.” Google counts anything above 2.5 seconds as slow. The fix is to compress the hero image, load it first and defer scripts below the fold.
• Security critical: “SSL certificate expires in 6 days.” When it expires, browsers show a full-page warning and most visitors leave. The fix is to turn on automatic renewal or renew the certificate now.
• E-mail warning: “No DMARC record.” Anyone can send e-mail that looks like it comes from you, and some providers may reject your mail. The fix is to add a DMARC record and tighten the policy after a trial period.

These are examples of how a finding reads, not results from any particular site. They show the labels you will meet: critical, warning and so on. Start with critical findings, then warnings with the widest effect.

A practical order for fixing

The reasoning is the same in any audit: first what hurts most and is simplest to fix, then what affects the most pages, then the rest. Our guide on running a technical SEO audit on a WordPress site follows a similar order.

Understanding each area in more depth

SEO findings

SEO findings concern whether pages can be found and shown. Typical items are missing or duplicated titles and descriptions, empty or repeated headings, images without alt text, broken links and redirects, and rules that accidentally keep pages out of search results. Check the sitemap and robots.txt first: a single wrong line can hide a whole section. Our guide to broken links and 404 errors shows how to repair link problems.

Speed findings

Speed is measured on a phone, using Google’s PageSpeed data and the Core Web Vitals: LCP, CLS and INP. LCP is how long the main content takes to appear, CLS is how much the layout jumps, and INP is how quickly the page responds to input. Google explains these on web.dev. Common fixes involve image sizes, script loading and compression. For a broader treatment of what a team can do, see website speed and Core Web Vitals.

Security findings

Security in this report means the basics that protect visitors and keep browsers from showing warnings: a valid, unexpired SSL certificate, a redirect from HTTP to HTTPS, security headers, and not exposing software versions to anyone who looks. A certificate that is about to expire is the classic emergency, and one reason to keep an eye on dates. See the guides on SSL certificate renewal and on security headers for the details.

E-mail findings

The e-mail checks look at SPF, DKIM, DMARC and MX records, which decide whether your messages are trusted and whether strangers can impersonate your domain. Missing records send e-mails to spam and let anyone send e-mail in your name. The guide on SPF, DKIM and DMARC explains each record.

Turning the report into a routine

A single check is a snapshot. The real value comes when the check becomes part of how you look after the website. A simple routine works well for small teams:

1. Run the first check and save the report. This is your baseline, with its score and the list of findings.
2. Sort findings into three piles. Things you can fix yourself today, things for your developer or hosting provider, and things you will deliberately leave. Write down the reason for the third pile so the decision is not forgotten.
3. Fix the top items, then re-check. Re-checks are available on the paid plans, and they show whether the score and the list of findings moved in the right direction.
4. Check again after any large change. A redesign, a migration, a new plugin or a change of hosting can introduce problems that were not there before.
5. Let alerts watch the urgent items. Depending on the plan, the service alerts you when SSL is about to expire or a page breaks, so the emergencies do not depend on someone remembering to look.

Who should own which finding

Findings often fall across several roles. Titles, descriptions, headings and alt texts belong to whoever manages the content. Redirects, certificates and security headers belong to whoever manages the server or hosting. Speed problems are shared between content, such as oversized images, and development, such as heavy scripts. E-mail records belong to whoever controls the domain’s DNS. Naming an owner for each pile keeps the list from stalling, and it makes the hand-off to a provider like us much easier, because the tasks are already separated.

What a report cannot tell you

An automated audit is a strong tool, but it has limits. It cannot judge whether your content is persuasive, whether your offer is competitive or whether your site structure suits your customers. It checks technical health and common best practice. For decisions about goals, competitors and keywords, a human analysis is still needed, and the audit is best seen as the foundation for that conversation rather than a replacement for it.

Free account and plans

At the time of writing, the free account runs one check of your website. The report is saved in your account but locked; any plan unlocks the score, every finding, the affected pages and the fixes. The plans on the product’s pricing section are Monitor at €9 a month, Business at €29 and Agency at €79, with more checks per month and, depending on the plan, re-checks, monitoring and alerts, and a PDF report. Alerts can cover situations such as an SSL certificate about to expire or a page that breaks. Because details change, always read the current plan table before you decide.

When you want help with the fixes

The report tells you what to fix; sometimes you want someone to do it. Internet Solutions has built and maintained websites, servers and e-mail since 2011, and the report includes a “Fix it for me” button that sends you an estimate. Our SEO service and website development teams can carry out the corrections or hand clear tasks to your own developers.

Frequently Asked Questions

Will the audit slow down my website?

No. SiteAuditBot makes at most about three requests per second and follows your robots.txt rules.

Do I need to install anything?

No. The check looks at your website from the outside, the way visitors and search engines see it.

How long does a check take?

About one to two minutes, covering up to 10,000 pages.

What does the free account include?

One check of your website. The report is saved in your account but locked, and any plan unlocks the score, every finding, the affected pages and the fixes.

Can you fix the problems for me?

Yes. Internet Solutions has built and maintained websites, servers and e-mail since 2011. Press “Fix it for me” in your report and we will send you an estimate.

What should I fix first?

Start with anything critical, then with problems that affect many pages, then speed and e-mail authentication, and leave small warnings for last.

The Bottom Line

A Site AI Audit report reduces a website to four vital signs, SEO, speed, security and e-mail, each with a score and a ranked list of findings written in plain words. Read the area scores to see where the weakness is, start with critical findings and with problems that affect many pages, fix, re-check and watch the score move. If you would rather hand the fixes to someone else, the estimate button and our SEO service are there for that. You can run a check at getsiteaiaudit.com.