MB SuiteMB Suite

Audit a site's technical health (Site Audit)

Updated 2026-07-07

In two lines: in SEO > Site Audit you crawl a site and run a technical analysis that detects SEO, performance, and accessibility problems. Each problem (issue) tells you what's wrong, why it matters, and how to fix it, and you can create it as a task in one click.

It's the site's medical checkup: it doesn't just tell you what's wrong, but what to do about it.

How do I run an audit?

  • Go into the account and head to SEO > Site Audit.
  • Enter the site URL.
  • Click Audit now and wait for the crawl and analysis to finish.
  • Review the report, organized in tabs: Overview, Issues, Pages, Performance, History, and Configuration.

Issues: what to fix, why, and how

The Issues tab is the audit's actionable core. Each issue is explained in three parts, without you needing to be a technical expert:

  • What's wrong — the concrete problem, in clear language.
  • Why it matters — the impact on your SEO, so you know whether it's worth prioritizing.
  • How to fix — the steps or the change to apply.

You can filter the issues by category and search for a specific one.

Key note: on each issue you have the Create task button. With one click, Create task from issue opens (with the category, affected pages, and priority already filled in) and a task lands in the Tasks module. That way no optimization gets lost from sight: it goes from diagnosis to your team's work list. See Create and organize tasks.

Performance: speed up the site

The Performance tab brings the speed analysis (Lighthouse / PageSpeed Insights), on mobile and desktop:

  • Lighthouse Scores and Core Web Vitals — the metrics Google uses to evaluate the loading experience.
  • Improvement opportunities — concrete actions to speed up the page, with their estimated savings (for example, Reduce unused JavaScript or Avoid enormous network payloads).
  • Diagnostics — additional technical information about what's weighing down the load.
You don't have to tackle everything. Sort the Improvement opportunities by impact, take the top two or three, and hand them to your developer as tasks. Speed is a ranking and conversion factor.

Schedule and compare over time

From Configuration you schedule periodic audits. The History lets you compare runs and spot regressions as soon as they appear, instead of finding out once traffic has already dropped.

A weekly or biweekly cadence is enough for most sites. On very large sites, narrow the crawl scope so it finishes faster.

Share the report

For the client or the team, you export the audit as a PDF: Executive summary (PDF) (the executive version, ideal for the client) or Full report (PDF) (with all the technical detail). The issues also export to CSV or JSON.

If the crawl can't read the site

Some sites block crawls with a firewall or anti-bot protection. If the audit warns that it couldn't analyze pages, it's usually that: you have to allow the crawler's access from the site's security settings (or Cloudflare's); the audit itself links how to do it. It's an adjustment on the site's side, not MB Suite's.

Also, from this section you can generate a robots.txt or an llms.txt — the latter to tell AI assistants (like ChatGPT or Claude) how to treat your content.

Still have questions?

Ask MIA, the MB Suite AI assistant: open it with the MB AI button (⌘J) in the top bar. MIA knows the section you're in, so you can ask it about what you see on screen — and it can also answer how-to questions about using MB Suite.