# B2B SaaS SEO execution sample

Illustrative specimen only. A live project adds the URL, owner, status, evidence link, due date, and retest result.

| Issue | Finding | Impact | Priority | Recommendation |
| --- | --- | --- | --- | --- |
| Inconsistent English URL rules | The root English pages and `/en/` English pages are both accessible. | Canonical and hreflang conflicts; duplicate indexing risk. | P0 | Choose one English URL rule, redirect or consolidate duplicates, then retest language signals. |
| Homepage crawled DOM repeats | Data Inputs, Proxy Infrastructure, and Web Access APIs appear in repeated output blocks. | Page bloat, diluted semantics, and weaker performance. | P0 | Output one canonical DOM representation of the content visible to users. |
| Homepage has no clear H1 | The main promise appears in crawled text but is not represented by one clear H1. | The page topic and primary promise are harder to interpret. | P0 | Set one descriptive H1 and keep supporting copy in paragraphs or secondary headings. |
| Root and `/en/` homepage duplication | Both routes return materially similar homepage content. | Authority and crawl signals can be split across two URLs. | P0 | Keep one canonical English route and use a permanent redirect for the duplicate. |

The table shows the handoff format, not a client result or a performance guarantee.