Carved out of #32. The landing pages shipped and are live; two of #32's per-page acceptance criteria are met unevenly across them.
Verified on production, 15 Aug 2026
Visible Q&A. #32 asked for a visible Q&A block per page; the issue's own note records that FAQPage rich results were deprecated Jun 2026, so the visible block is the deliverable, not the schema. Every page does carry at least one visible question with an answer. The gap is in depth, not presence:
/cheapest-pints and all seven /happy-hour/[day] pages: an answer-first question heading plus a two-question "Quick Q&A" block./happy-hour (hub): three visible questions under plain headings, and FAQPage JSON-LD./student-pints-perth and the four transport hubs (/pubs-near-perth-station, /pubs-near-optus-stadium, /pubs-near-rac-arena, /pubs-near-elizabeth-quay): the answer-first question heading only ("Where are the cheapest student pints in Perth?", "What is the best pub near RAC Arena?"). No second Q&A pair.
Intro length. #32 asked for a 200-word original editorial intro per page. Measured prose runs shorter:
| Page |
Intro |
Answer-first lead |
/cheapest-pints |
48w |
42w |
/happy-hour/monday |
39w |
45w |
/student-pints-perth |
33w |
34w |
/pubs-near-rac-arena |
45w |
50w |
Action
- Add a two-question Q&A pair to
/student-pints-perth and the four transport-hub pages, following the "Quick Q&A" pattern already on /cheapest-pints.
- Decide whether the 200-word intro target still stands. The current leads are short but answer-first and honest; padding them to hit a word count would make them worse. Either expand them with something worth reading, or record the decision to drop the 200-word criterion so it is not re-litigated later.
Also worth a look
/happy-hour (the hub) is the only one of the fifteen pages with no ItemList JSON-LD — it emits BreadcrumbList + FAQPage. Not a defect on its own, since the hub is a day rail rather than a ranked list, but confirm that is deliberate.
Not in scope
Everything else on these pages checks out: self-referencing canonical, no noindex, BreadcrumbList JSON-LD (plus ItemList on all but the happy-hour hub), internal-link rail, and presence in /sitemap-content.xml.
Carved out of #32. The landing pages shipped and are live; two of #32's per-page acceptance criteria are met unevenly across them.
Verified on production, 15 Aug 2026
Visible Q&A. #32 asked for a visible Q&A block per page; the issue's own note records that FAQPage rich results were deprecated Jun 2026, so the visible block is the deliverable, not the schema. Every page does carry at least one visible question with an answer. The gap is in depth, not presence:
/cheapest-pintsand all seven/happy-hour/[day]pages: an answer-first question heading plus a two-question "Quick Q&A" block./happy-hour(hub): three visible questions under plain headings, and FAQPage JSON-LD./student-pints-perthand the four transport hubs (/pubs-near-perth-station,/pubs-near-optus-stadium,/pubs-near-rac-arena,/pubs-near-elizabeth-quay): the answer-first question heading only ("Where are the cheapest student pints in Perth?", "What is the best pub near RAC Arena?"). No second Q&A pair.Intro length. #32 asked for a 200-word original editorial intro per page. Measured prose runs shorter:
/cheapest-pints/happy-hour/monday/student-pints-perth/pubs-near-rac-arenaAction
/student-pints-perthand the four transport-hub pages, following the "Quick Q&A" pattern already on/cheapest-pints.Also worth a look
/happy-hour(the hub) is the only one of the fifteen pages with no ItemList JSON-LD — it emits BreadcrumbList + FAQPage. Not a defect on its own, since the hub is a day rail rather than a ranked list, but confirm that is deliberate.Not in scope
Everything else on these pages checks out: self-referencing canonical, no
noindex, BreadcrumbList JSON-LD (plus ItemList on all but the happy-hour hub), internal-link rail, and presence in/sitemap-content.xml.