Start with the clicks a fix can lose
A fix is worth what it protects or adds. An error on a page that earns clicks every day matters more than the same error on a page nobody finds. So begin with the pages that already get search traffic.
The most urgent case is a page with search traffic that is noindex, canonicalised to another address, or broken. Google can drop it, and its clicks go with it. Fix these pages first, or confirm that the noindex or the canonical is there on purpose.
Then rank the rest by what each issue blocks
Sort the other issues by how far each one keeps a page from earning clicks:
- Indexing: indexable pages that are not in Google, canonical and hreflang conflicts, noindex pages in the sitemap.
- Crawling: broken internal links, sitemap addresses that fail, orphan pages and pages many clicks deep.
- Snippets: titles, descriptions and structured data, which shape what a search result shows.
- Content: what the page says.
- Cosmetic: the shape of an address, social tags, a noindex that is there on purpose.
Put notices after every error and warning, because a notice is a hint or a state and rarely the first job. Within one class, put errors before warnings, then an issue on more pages before one on fewer.
Fix each issue once, in its template
On a large site, most issues come from a template: the product layout, the category layout, the header. Count an issue by template, not by page. One change to the product template can fix thousands of pages, while ten separate pages need ten changes.
Group what is left by where the change goes: the whole site, one template or separate pages. Hand developers each template fix with an example page and the element to change.
Confirm each fix with a new crawl
A fix is done when a crawl reads the pages and the issue is gone, not when a ticket closes. Read the pages of the fix again after the release. Watch the next releases too, because a template change can bring an issue back.
In Fix Planner, Check if fixed reads the pages of one fix again and spends credits for the pages it reads. A fix that a later crawl finds again shows Came back.
Get the list from Fix Planner
Fix Planner builds this order after every crawl: one row per issue, its template fixes under it, the most important first. It lists search and content work first, then For developers, then Accessibility.
With Search Console connected, the pages with search traffic that are noindex, canonicalised or broken come first. That row shows their clicks at stake over the last 28 days. Notices come after every error and warning, and within those each fix is ordered by its class, then its severity, then its pages.
Each fix says why it ranks where it does and how to fix it. PerfBee writes the fix; a person applies it. Download this list gives CSV, Excel or PDF on every plan. The Fix Planner help article has every step.