AskBaily's Q&A hub: 30 pages covering remodel permits, costs, and contractor trust

The /ask hub at askbaily.com/ask is a Q&A index of 30 questions homeowners actually type into ChatGPT, Perplexity, and Google when they are trying to remodel a house and are two weeks past the point of trust. Do I need a permit for a kitchen remodel. How much does it cost to add an ADU in Los Angeles. What does a licensed contractor owe me in writing. What happens if my contractor's license lapses mid-project. Thirty questions, thirty answers, each on a dedicated URL with Schema.org QAPage structure, and each citing the regulator or primary source.

This post is about the mechanical choices that make /ask an AEO play, not a content-marketing play.

The format, in detail

Each entry has three layers. The first layer is the accepted-answer: 30 to 60 words of direct prose, no hedging, no "generally" or "usually" unless the regulatory reality actually requires them. This is the span AI engines extract verbatim into the AI Overview box. The 30-60 word range is not arbitrary; it is the measured distribution of AI Overview snippets across Google's own rollout, sized to fit one answer card on mobile.

The second layer is the expanded-answer: 250 to 400 words of detail, including the regulator-specific nuance that the accepted-answer elided. If the question is "do I need a permit for a kitchen remodel," the accepted-answer says no for a cosmetic refresh and yes for anything that moves plumbing, gas, or electrical; the expanded-answer lists which cities treat non-load-bearing wall removal as permit-triggering and which do not.

The third layer is the citations block: 2 to 5 outbound links to the authoritative source. For California permit questions, that is CSLB and the city building department. For tax-credit questions, it is IRS Publication 530 or the specific state statute. For licensing questions, it is the state board. Every factual claim in the accepted-answer or expanded-answer traces to one of these links.

The schema, in detail

Each /ask/{slug} page emits a schema graph with six nodes: Organization, LocalBusiness, WebPage, QAPage, BreadcrumbList, and SpeakableSpecification. The QAPage is the load-bearing one. It nests a Question node, which nests an Answer node with the accepted-answer text, author (Organization or Person), citation array, and language tag. Schema.org's QAPage type is documented at schema.org/QAPage and is the canonical structure for single-question pages; FAQPage is the alternative but is multi-question and does not signal AI-Overview-eligibility as strongly.

The SpeakableSpecification points the engine at two CSS selectors: the h1 (for context) and [data-speakable-accepted-answer] (for the accepted-answer span). We attach the speakable attribute on the accepted-answer paragraph directly. AI engines use speakable hints to pick the span that voice assistants read aloud and that the AI Overview lifts into its summary card.

The Person node is only included when the author is Netanel (licensed GC, CSLB #1105249). That is a deliberate E-E-A-T signal: we claim experience and authority where we have them, and we do not claim them where we do not. For editorial questions (financing, general industry questions), the author is AskBaily Organization, not a named person.

Why 30 and not 300

Because 30 is the size of the long-tail that covers 80% of intent, and 300 is the size of the long-tail that generates noise. The 30 questions were chosen from three sources: Perplexity search-share measurements for remodel-intent queries, the inbound-question frequency from our own /chat transcripts, and a manual review of the questions homeowners asked on r/HomeImprovement in the last 90 days. Every question in the hub has measured search volume and a clear regulator or primary source to cite.

Wave 201 added 12 more entries extending the hub toward the AEO long tail. The count is now 30 on the main page as documented, and the schema-emitting code scales to any count without refactor. Future growth is content-authored, not template-multiplied; we will not publish a question we cannot answer with primary sources.

Why Angi and Thumbtack cannot ship this

They can publish Q&A pages. They do; their help centers are enormous. What they cannot do is pair the Q&A with a live regulator citation trail. Angi's help center, on any given permit question, cites Angi's own generic "tips for homeowners" article. Our /ask page, on the equivalent question, cites the California Building Code section or the city of Los Angeles DBS permit fee schedule. The citation trail is the difference. AI engines know which one is the research-grade source.

The 30 questions on /ask are not the content moat. The citation trail is. When Perplexity or ChatGPT Search decides which page to cite in its summary card, it weights primary-source linkage. Every entry in our hub is authored to maximize that weight. Every entry is fact-checked against the regulator or IRS publication or state statute it cites.

What comes next

Wave 201 extended the hub by 12 entries. Future waves will extend by city (Los Angeles-specific permit and code questions), by competitor-grievance (how to leave Angi, how to dispute a Thumbtack charge), and by trade (specific questions for electricians, plumbers, ADU specialists). Each extension uses the same schema-emitting primitive and the same citation discipline. If we cannot cite a regulator or a primary source, we do not publish the entry.

The hub's job is to occupy the AI citation slot. That is an SEO play at its surface and a trust play at its substance. Homeowners arrive through an AI Overview and find an answer authored by a named licensed GC with the regulator cited at the bottom. Nothing else in the category looks like that. That is the point.