The Fixes tab turns a site's issues into a short list of things to fix, most important first. Each issue is grouped by the page template it comes from, so one change to a template can fix thousands of pages. Fixes is on every plan and costs no credits.
Open Site Crawler, then Fixes, and pick a site from My Sites. The list is rebuilt after every scan of that site. Title, heading, indexing and content fixes need a detailed scan; broken links come from any scan.
How issues are grouped
PerfBee puts the site's pages into templates: pages built from the same HTML skeleton (read in detailed scans) or with the same URL pattern, such as /products/{slug}. Then each issue becomes one of these fixes:
- Whole site: the issue is on at least 80% of the site's pages and of every larger template. It usually sits in something every page shares, such as the layout.
- Template: the issue is on at least 80% of one template's pages, for example "Missing H1 · Template /products/{slug} · 4,800 of 4,812 pages". Fix the template once.
- Separate pages: the rest of the pages with that issue.
- Broken link: one fix per broken URL, with the pages that link to it. When most of those links sit in the same place on the page, such as the menu or the footer, the fix says so: one change there fixes every page. A link that breaks the same way in every folder (for example
void(0)resolved against each folder) is one fix. - Broken URLs in the sitemap: URLs the sitemap lists that answer with an error and that no page links to, as one fix.
Broken links you marked resolved in a scan report are left out.
Why a fix ranks where it does
Fixes are ranked by how serious the issue is (error, warning or notice), how many pages have it, how well linked those pages are compared with the rest of the site, how close they are to the start page, how many are in the sitemap, and whether one change fixes them all. Content issues on pages search engines leave out (noindex, or a canonical pointing elsewhere) count less. Each fix shows the reason, for example: Why #1: Warning · 4,800 pages (39% of indexable pages) · one template change · median 140 inlinks · 98% in sitemap.
Open a fix to see what is wrong, why it matters and how to fix it, its history, and the pages it is about. Details on a page opens it in Site Pages.
Statuses
- Open: still on the site.
- Checking: a Check if fixed is running.
- Looks fixed: the check found every checked page fixed. The next detailed scan confirms the rest.
- Resolved: a scan measured the issue again and found no page left. A fast scan does not read titles or headings, so it never resolves those fixes.
- Came back: a resolved fix that a later scan found again.
Check if fixed
After you change the template, click Check if fixed on the fix. A detailed scan reads the 25 most linked pages of that fix and 5 others, or with Check all every page of it, up to 2,000. For a broken link it reads the pages that link to it. The button shows the credits: only the pages read are billed, at the detailed scan rate. A check cannot start while another scan of the site runs.
When it ends you see the result on the fix and in the notification bell: Looks fixed, or fixed on 18 of 25 checked pages, or that no page could be read. Issues that compare pages across the whole site, such as duplicate titles, canonical targets, orphan and deep pages, have no check button: the next detailed scan checks them.
A check appears in the Scans list as Fix check. It does not count as the site's latest scan, so comparisons, the dashboard and scheduled scans are not affected.
Download and share
Download the list on screen as CSV, Excel or PDF (Starter and up). The PDF, "What to fix first", has the list and how to fix the first ten fixes, ready for a client or a developer.
Notifications and AI apps
Two notifications tell you when something changed: Fix check finished and Fixes resolved, in the app and as webhooks. You can turn them off in Settings, Notifications.
With the PerfBee MCP server, Claude and ChatGPT can read the same list with the get_fixes tool: ask "What should I fix first on my site?".