P1 fix brief
GetBlock rendered H1/schema fix brief
Quick engineering/content fixes before sending high-intent directory traffic and before trying to improve AI citations.
| Page | Fix | Why it matters |
|---|---|---|
| /nodes/ | Add one visible rendered H1. | AI/directories extract the primary page subject from rendered heading hierarchy. |
| /enterprise-api/ | Keep one H1; demote extra H1s to H2/H3. | Multiple H1s create ambiguous entity/topic extraction. |
| /sla/ | Add Organization + Service/WebPage + FAQPage JSON-LD where FAQ exists. | SLA is a trust/procurement page; structured data makes it citable. |
| /case-studies/ | Keep one H1; use H2/H3 for case cards. | Review directories need clean proof pages; multiple H1s weaken hierarchy. |
| Comparison pages | Add FAQPage schema where FAQ blocks exist; keep claims source-checkable. | AlternativeTo/SaaSHub and AI answers parse comparison tables/FAQ heavily. |