Ahrefs Site Audit
Two thirds of silverscreendesign.com carries a technical error. Three categories account for almost all of it, and the largest one is a single issue repeated 22,095 times.
Crawl completed 16 September 2026 · 39,926 internal URLs · both protocols, subdomains included
Every error the crawl found rolls up into one of six categories. These three carry 26,723 of the affected URLs between them — the other three carry 14. Fix these in order and the health score moves; fix anything else first and it does not.
122,103 URLs
22,095 pages on the site cannot be reached by clicking a link from any other page on the site. Search engines found them through the sitemap, not through the site's own structure. A page with no internal links pointing at it reads as unimportant — nothing on the site vouches for it — and it is the single largest technical problem here by a wide margin. At this volume it is almost certainly machine-generated catalog and web-store URLs rather than pages anyone wrote.
| Issue | URLs |
|---|
| Orphan page (has no incoming internal links) | 22,095 |
| Canonical URL has no incoming internal links | 4 |
| Page has links to broken page | 4 |
The fix
- 1Decide which of these 22,095 URLs should exist in search at all. Product and web-store variants that exist only as combinations of size, color or style usually should not.
- 2For the ones that should not: canonicalize them to the parent product or category page, or noindex them, so crawl budget stops being spent on them.
- 3For the ones that should: give them real internal links — from category pages, related-product modules and the main navigation — so the site itself says they matter.
- 4Prune or consolidate whatever is left over. A 39,926-URL site for a custom apparel printer is far larger than the business needs.
24,509 URLs
The XML sitemap is the list of URLs the site formally submits to Google as the pages worth indexing. 4,453 of the URLs on that list redirect somewhere else, and 48 return a server error. The sitemap is describing a version of the site that no longer exists, which wastes crawl budget and reduces how much Google trusts the file.
| Issue | URLs |
|---|
| 3XX redirect in sitemap | 4,453 |
| 5XX page in sitemap | 48 |
| Non-canonical page in sitemap | 6 |
| Noindex page in sitemap | 2 |
The fix
- 1Regenerate the sitemap so it contains only live, canonical URLs that return a 200 status.
- 2Remove every redirecting, erroring, non-canonical and noindexed URL from the file.
- 3Set the sitemap to rebuild automatically whenever URLs change, so it does not drift out of date again.
- 4Resubmit the corrected sitemap in Google Search Console and watch the coverage report for a fall in excluded URLs.
3111 URLs
These are pages the server failed to deliver during the crawl — 51 returning server errors, 46 of them hard 500s, and 10 that timed out before responding at all. This is the smallest category by URL count and the most urgent by severity: a customer who lands on one of these sees a broken page, not a slow one. The 10 timeouts sit alongside the slow mobile load time flagged in the website and brand analysis.
| Issue | URLs |
|---|
| 5XX page | 51 |
| 500 page | 46 |
| Timed out | 10 |
| 404 page | 2 |
| 4XX page | 2 |
The fix
- 1Pull the server error log for these URLs and identify the failing template, plugin or database query behind the 500s.
- 2Fix the underlying error rather than redirecting the URLs away — a redirect hides the fault and leaves the next page to hit it broken.
- 3Check whether the timeouts are hosting capacity under crawl load; if so, the hosting plan is the fix, not the code.
- 4Redirect the 2 genuine 404s to their closest live equivalent, and fix whatever still links to them.
Where to start
The 111 server errors and timeouts are the smallest job and the most urgent — they are the only errors here that a real customer can walk into. The sitemap regeneration is the next fastest win. The 22,095 orphan pages are the biggest piece of work and the one that moves the health score most, but it is a decision about which pages should exist before it is a technical task, so it is worth scoping together rather than fixing blind.
← Back to the portal