Every entry below maps to a specific finding the scanner emits — there are 182 of themat last count, growing roughly weekly as scans surface new patterns. Each page covers one issue: what triggers the finding, why search engines or users care, the typical root cause, and a copy-pasteable fix with a code example. The fixes are written to be specific enough that a developer can ship them without further research — not generic "improve your SEO" advice.
Crawlable issue pages with root causes and fixes.
Built around the main issue types site owners search for.
Critical and high-severity problems that deserve fast action.
When the scanner first emits a brand-new finding type, the catalog grows automatically: a background job (gpt-4.1, costs about $0.02 per draft) writes the first version of the page from the finding's description, fix recipe, and tags. Then it's reviewed and edited before going live. As of the last build, that pipeline has produced 182 published issue pages across 6 categories, with new ones added every week.
The category split (security / performance / technical SEO / on-page SEO / crawl & links / best practices) maps to how I think about SEO triage in practice — if I'm looking at a site that lost rankings overnight, my first stops are technical SEO (canonical bug? robots change?) and crawl & links (404 cascade? sitemap error?). Browse to the category that matches your symptom, or search by issue title from the search box.
HTTPS, security headers, mixed content, and access controls.
Page speed, payload size, and resource loading efficiency.
Indexability, canonicalization, structured data, and international SEO.
Content quality, headings, meta descriptions, and duplicate content.
Broken pages, redirects, sitemaps, and internal linking structure.
Image formats, URL structure, alt text, and quick-win opportunities.
These featured links expose the most important pages in each topic cluster and make the library easier to crawl than a single endless directory.
HTTPS, security headers, mixed content, and access controls. Use the category hub to review the full library, or open one of the featured issue pages below for targeted remediation advice.
Pages delivered over plain HTTP expose user data, reduce trust, and receive a Google ranking penalty.
Some cookies lack Secure or HttpOnly flags, exposing them to interception or JavaScript access.
HTTPS pages that load resources (like images, scripts, or stylesheets) over HTTP create mixed content. This undermines security, can break page functionality, a
Missing recommended HTTP security headers leaves your site vulnerable to a range of attacks, including clickjacking, MIME-sniffing, and cross-site scripting (XS
Page speed, payload size, and resource loading efficiency. Use the category hub to review the full library, or open one of the featured issue pages below for targeted remediation advice.
Pages are taking longer than 3 seconds to respond, which negatively impacts user experience, search engine crawling, and Core Web Vitals scores. This issue is o
Scripts in <head> without defer/async block rendering, slowing page load and hurting Core Web Vitals.
One or more script URLs referenced by your site fail to load due to 404, 5xx, or timeout errors, breaking critical site functionality.
Meta refresh redirects are used on 2 pages, causing SEO and performance issues.
Indexability, canonicalization, structured data, and international SEO. Use the category hub to review the full library, or open one of the featured issue pages below for targeted remediation advice.
LocalBusiness schema is missing required telephone or address fields, affecting local SEO eligibility.
Product schema is missing required fields: name, image, or offers/price, preventing eligibility for rich results.
Pages are being excluded from Google's search index due to the presence of 'noindex' directives, either in the HTML meta tags or HTTP headers. This prevents the
Shallow pages (within 3 clicks from the homepage) that return non-200 HTTP status codes, such as 404, 410, 301, or 302, prevent search engines from accessing an
Content quality, headings, meta descriptions, and duplicate content. Use the category hub to review the full library, or open one of the featured issue pages below for targeted remediation advice.
Near-duplicate content clusters occur when multiple pages on a website have highly similar or almost identical content, differing only in minor details. This ca
When multiple pages on your site target the same search intent or keyword, they compete against each other in search results. This internal competition, known a
Some pages have fewer than 250 words, which can harm SEO by being classified as thin content.
Pages with thin content are those that contain very little meaningful text, typically fewer than 300 characters. These pages offer minimal value to users and ca
Broken pages, redirects, sitemaps, and internal linking structure. Use the category hub to review the full library, or open one of the featured issue pages below for targeted remediation advice.
Broken pages occur when URLs return 4xx HTTP status codes (such as 404 Not Found or 410 Gone). These errors indicate that the requested content is unavailable,
Orphaned pages are web pages that exist on your site but are not linked to from any other internal page. This makes them difficult for both users and search eng
This issue occurs when URLs included in your XML sitemap are also blocked by your site's robots.txt file. This creates conflicting instructions for search engin
Server error pages (5xx) occur when a web server fails to fulfill a request due to internal problems. These errors prevent users and search engines from accessi
Image formats, URL structure, alt text, and quick-win opportunities. Use the category hub to review the full library, or open one of the featured issue pages below for targeted remediation advice.
High-authority pages have strong links but less than 300 words, missing ranking potential due to thin content.
Pages render as empty SPA shells with no server-rendered links, harming crawlability and indexation.
More than 3 render-blocking CSS files in <head> delay page rendering and harm Core Web Vitals.
No Privacy Policy page was found on your website, which is a legal and trust requirement.
The category hubs above are the primary crawl path. Use the browser below when you already know what you're looking for and want to filter the full set of issues.