Apex pillar hub: 800–1500 word landing pages on conduction.nl/apps/<slug>/

[rubenvdlinde]

Part of #75 (SEO epic).

What

Beef up each https://www.conduction.nl/apps/<slug>/ page to 800–1500 words of standalone, citation-quality content. Today they ship Wikipedia-style ledes (3–4 sentences from the AI-baseline campaign) plus a hero, feature grid, and cross-link block. That works for AI summarisation but not for traditional ranking on the apex domain.

Why

The SEO audit flagged that Conduction's 17-subdomain docs fan-out fragments PageRank: every subdomain has to earn authority from zero. The apex conduction.nl is the single domain where authority compounds. Each /apps/<slug>/ page is the natural place for the brand to win "OpenRegister review", "Nextcloud data register", "ZGW open-source" type queries — but only if there's enough content for Google to rank.

Scope

15 app pages on conduction.nl (drop doriath + app-versions which are in-development).

Per-page content target

Section	Length
Lede (existing, 3–4 sentences)	60–80 words
What it does (existing FeatureGrid)	250–400 words
NEW: Who it's for (concrete user personas + use cases)	200–300 words
NEW: How it integrates (Nextcloud, OpenRegister, others)	150–250 words
NEW: One real customer case (anonymised if needed)	200–400 words
NEW: Comparison section ("vs. X" for one or two competitors)	150–250 words
Cross-links (existing AppCrossLinks)	bullet list
NEW: FAQ (3–5 Q&A using FAQ component)	200–300 words

Why the FAQ matters

FAQPage JSON-LD on the apex page = more SERP real estate + AI Overview citation pull. The preset's <FAQ> component auto-emits the schema.

Recommended sequencing

1. Start with the 5 highest-traffic apps (decide by current install count): OpenRegister, OpenCatalogi, OpenConnector, DocuDesk, MyDash.
2. Audit the per-app docs site once to extract real customer use cases (already-written content the apex page can adapt).
3. Hand-write the apex page; do not auto-translate from docs.

Acceptance per page

• >= 800 words of unique body copy in raw HTML
• FAQ block with 3+ items (FAQPage JSON-LD emits automatically)
• Cross-link block to docs subdomain
• At least one customer-shaped concrete fact (named municipality, named ZBO, named integration)
• Wikipedia-style lede preserved (don't remove existing structured intro)