What is a broken key page?
Rubric check: broken key page (check id keystatus)
A broken key page is one of your most important URLs (the home page, your most-linked pages or pages in your sitemap) that returns an error instead of loading. Search engines and AI tools can't read, rank or cite a page that doesn't load.
Why it matters for SEO
When a key URL returns a 404 or a server error, Google eventually drops it from the index, and the links pointing at it stop passing value. A page that shows "not found" but returns a normal 200 status is a soft 404, which Google also treats as missing. Rubric looks at the status code each key URL actually returns.
Does this matter for ChatGPT and AI Overviews?
AI search tools fetch pages live or from a search index. If the page they pick returns an error, they move on to another source. Your most-linked pages are the ones other sites and AI tools are most likely to try, so an error there costs the most.
How Rubric scores it
MajorMajor checks cost twice as much as a standard check when they fail.
Why this tier: Your most important pages must load, or nothing else on them counts.
It is judged on your key pages: the home page, the pages your site links to most, and the pages in your sitemap.
Every Rubric score starts at 100. When this check fails, it takes up to 24 points off. Even one failing key page costs at least 12 points, and the rest comes off as the share of failing key pages grows. A made-up address that answers as a normal page instead of 'not found' costs the full 24, because it affects every missing page on the site.
This check doesn't cap your score. It only takes off its own points.
From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).
How common it is
Found on 94 of 364 sites where Rubric could judge it (26%). That is 83 of 287 judged sites in Rubric's 313-site test set and 11 of 77 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.
How accurate the check is
Lab test: failed. On test pages built with this problem, it caught 3 of 5. On clean test pages, it stayed quiet 2 of 2 times. The misses are cases the check's own rules leave out on purpose. (Engine build bbcec7c.)
Real sites: people checked 12 of its findings by hand and 2 were wrong (17%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.
Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.
How to fix it
WordPress
- Open each URL in the report. If the page was deleted, restore it from Trash or set up a 301 redirect to its closest replacement with a redirect plugin (Redirection, or the redirect manager in Rank Math or Yoast Premium).
- If the page shows a server error, check for a broken plugin or theme update: switch to a default theme or disable plugins one at a time.
- Update the menu links and sitemap entries that point at the old URL.
Shopify
- If a product, collection or page was deleted or its handle changed, add a redirect: search for URL redirects in the admin and create one from the old path to the new page.
- When you change a handle, tick Create a URL redirect so Shopify adds it for you.
- Update menu links that still point at the old URL.
Webflow
- Go to Site settings > Publishing > 301 redirects and add the old path and the new page.
- If a CMS item was archived or set to draft, publish it again or redirect its URL.
- Fix links to the old URL in navigation and rich text, then publish.
Custom code
For each key URL in the report:
- Make it return 200 again, or
- 301-redirect it to the closest live page, or
- If it's gone for good, return a real 404 or 410 and remove it from your internal links and sitemap.
Never serve a "not found" page with a 200 status. Check with curl -I https://example.com/page.
Related checks
More status codes and redirects checks · The full AI SEO glossary