A concrete example showing how one SEO finding should connect evidence, impact, scope, action and verification without pretending to audit a real client.
Illustrative context: a replaced service URL
Folio detail
This is a fictional, generalised training example, not a finding from a client site. Assume a business replaced /office-cleaning with /commercial-cleaning during a redesign. The old URL still appears in internal links and external search results, but it returns a 404 response. The new page loads normally and covers the successor service. The audit question is narrow: can existing routes to the old page be preserved and transferred to the appropriate replacement without misleading visitors?
Evidence recorded before interpretation
Folio detail
A reproducible finding lists what was checked. In this example: requesting the old URL returns HTTP 404; requesting the new URL returns HTTP 200; two navigation or body links still point to the old URL; and no redirect is returned. Search Console evidence, analytics or backlink data is not assumed because none has been supplied. The finding therefore does not claim lost revenue, traffic or link value. It only records a broken historical route with an apparently relevant successor.
Recommendation with boundaries
Folio detail
Confirm content ownership with the business, then add a single permanent redirect from /office-cleaning to /commercial-cleaning. Update the two known internal links to point directly to the new URL, so visitors and crawlers do not depend on the redirect. Keep the old URL out of the XML sitemap. Do not create a chain through another retired URL and do not redirect every missing page to the homepage. Before release, export the redirect rule and affected links for review.
Why the issue matters
Folio detail
People following an old bookmark, internal link or search result reach an error instead of the replacement service. Google advises using permanent server-side redirects when a page has moved and redirecting to a relevant destination rather than an unrelated home page. A 404 is correct when content truly has no replacement; it is not automatically an SEO error. Here the recommendation depends on confirming that the new page genuinely succeeds the old service rather than merely sharing a few words.
Verification closes the finding
Folio detail
After deployment, request the old URL without a cached browser session and record the response chain. It should make one permanent hop to the intended new URL, which should return 200. Crawl or recheck the two internal links and confirm they now use the destination directly. Inspect canonical and indexability signals on the new page. If Search Console is available, monitor the relevant URLs over time, but do not set a guaranteed ranking or traffic outcome: implementation success is the corrected route, not an invented performance uplift.
Illustrative example — not a real client or result.
Practical sample
Labelled sample finding: retired service URL has no redirect
Illustrative example only; replace every field with evidence from the site actually being audited.
Finding IDSEO-REDIRECT-01.
StatusOpen; technical correction proposed, business equivalence still to be confirmed.
Affected URLIllustrative old path: https://example.test/office-cleaning.
Observed evidenceOld path returns 404; illustrative replacement https://example.test/commercial-cleaning returns 200; two internal links still use the old path; no redirect observed.
InterpretationA retired route appears to have a relevant successor, leaving visitors on an avoidable error page. No traffic, revenue or backlink impact is claimed.
PriorityMedium in this example: user-facing breakage with a bounded fix, but no evidence of a site-wide outage.
Recommended actionAfter confirming equivalence, add one permanent server-side redirect, update internal links directly, and remove the retired URL from the sitemap.
Do not doDo not send unrelated missing URLs to the homepage, create redirect chains, or describe the redirect as guaranteed to restore rankings.
Acceptance testOld path makes one permanent hop; destination returns 200; known internal links point straight to destination; destination remains indexable and self-canonical where appropriate.
Evidence attachmentSave dated status-code output, the redirect chain and a list of corrected internal-link source pages.