Running a page audit

Enter any page URL on Reports and choose Run audit. If you leave out https://, Semhack adds it. The report opens straight away and fills in when the audit finishes, usually within seconds.

What Semhack fetches

• The page itself, following redirects, as SemhackBot (see the crawler page). It reads up to 5 MB of HTML.
• /robots.txt, the sitemap (the one listed in robots.txt, or /sitemap.xml), a random URL that shouldn’t exist (to test the 404 page) and, when the HTML declares no icon, /favicon.ico.

Semhack reads the HTML as the server sends it and doesn’t run JavaScript. Content that only appears after scripts run isn’t seen by the checks.

What the report shows

• A score from 0 to 100 and a score for each category: SEO, security, performance and other. See how the score works.
• All 40 checks, each with a result, why it matters and how to fix it, plus the affected URLs or elements. Failing checks open by default.
• When the same URL was audited before, the score change and the checks that changed since then.
• When the page belongs to a Search Console client, the page’s clicks and impressions next to the audit.

Use Run again after a fix to confirm it. Print or save as PDF gives a clean printable version, and Reports has a CSV export of every website’s latest audit.

Audits and the weekly list

When an audited page has Search Console data, its failing high- and medium-importance checks (up to 3) join the weekly list as Audit actions. They close by themselves when a later audit passes.

Limits

Your plan sets how many audits you can run per month and how many websites you can have; Billing shows what you’ve used. To keep things fair there is also a short-term limit of 20 audits per 10 minutes per workspace.