Promote 10 articles' Common Questions to FAQPage schema

What was done

Promoted the existing “Common questions” sections in all 10 collection FAQ articles into frontmatter faq[] arrays. The schema-emission infrastructure was already shipped on the prior commit; this one just feeds it data.

77 new Q&A pairs are now in FAQPage JSON-LD across:

Article	Q&As
stormwater-management	7
entitlements	7
agency-coordination	8
neighborhood-meetings	8
public-hearings	7
preliminary-layout	8
road-parking-design	8
water-sewer-systems	8
irrigation-systems	8
value-engineering	8

Lifted verbatim from existing body content — every FAQ answer in schema also appears as visible body text, satisfying Google’s FAQPage “answers must be visible to users” rule (the same rule the schema-validation pass enforced earlier today). Markdown formatting markers (**bold**, *italic*) were stripped from the schema strings since JSON-LD renders as plain text; the rendered body still shows the formatting via Astro’s markdown pipeline. Internal double-quotes were unwrapped (e.g., "VE consultant" → VE consultant) to keep the YAML clean — the body text already conveys the same meaning, and Google’s match logic ignores quote characters anyway.

Build verified: 184 pages clean. FAQPage schema present on all 10 article URLs with the expected Question count per article.

Why

The audit’s #1 P0 win for AI visibility was extending FAQPage schema from the FAQ hub to every article. Prior commits shipped the infrastructure (frontmatter faq[] field + FaqArticle.astro emission). This commit puts it to work on the 10 articles where the answer text already existed in the body — pure structured-data extraction from prose, no new content writing.

That advances the SEO plan’s faqpage-articles item from in_progress → done, and gives 10 more pages rich-result eligibility for queries like “how long does plat approval take in Ada County?” / “is stormwater detention required in the Treasure Valley?” / “do I need a Section 404 permit?” — exactly the high-intent queries the April 28 baseline test showed Bailey was invisible on.

Files affected

Created:

• src/content/devlog/2026-04-28-faqpage-articles-sweep.md — this entry

Modified (faq[] block added to frontmatter, no body changes):

• src/content/faqs/stormwater-management.md
• src/content/faqs/entitlements.md
• src/content/faqs/agency-coordination.md
• src/content/faqs/neighborhood-meetings.md
• src/content/faqs/public-hearings.md
• src/content/faqs/preliminary-layout.md
• src/content/faqs/road-parking-design.md
• src/content/faqs/water-sewer-systems.md
• src/content/faqs/irrigation-systems.md
• src/content/faqs/value-engineering.md
• src/content/seo-plan/items.json — faqpage-articles marked done

What’s next

Re-run the schema validator after deploy to confirm zero warnings on all 10 article URLs. Then promote faq-rename from pending → in_progress: rewrite the existing 11 FAQ titles to question form with location qualifiers per the mapping in bailey_seo_aiseo_plan.md § 6 (e.g., “Stormwater management 101 for the Treasure Valley” → “Is stormwater detention required for my project in the Treasure Valley?”). That’s a title-only edit on 11 files plus the FAQ index — should take an afternoon.