We took the photographer page on admiralbusiness.com as a representative example and scanned it line-by-line against current Google and AI-search ranking signals. Eight findings stand out below. Every one is a structural fix Bloxx ships automatically on every page it publishes, and most of the same gaps appear across the rest of the /who-we-cover pages.
Critical
Zero JSON-LD schema markup
No <script type="application/ld+json"> blocks. No Service, FAQPage, BreadcrumbList, or Organization schema. The single biggest AI-search and rich-result miss on the page.
Critical
FAQ exists but no FAQPage schema
The page has 5 well-written FAQ questions in an accordion, but they're not marked up as FAQPage. That's free SERP real estate Google would render today if the schema was attached.
Critical
Broken heading hierarchy
The page jumps H1 → H4 → H3/H5 with zero H2 tags. Both LLM crawlers and screen readers parse this as a broken outline. Easy fix, high impact.
High priority
No llms.txt or ai-content-summary
No machine-readable summary for AI crawlers. No site-level llms.txt. Generic CMS platforms don't ship these by default; Bloxx does.
High priority
No author or last-reviewed signal
Insurance is YMYL (your money, your life) content. Google's E-E-A-T guidance specifically rewards named author, expert reviewer, and last-reviewed dates. None present.
High priority
Templated boilerplate leakage
The photographer page contains hide-classed Tradespeople bullets left over from a shared template. Generic CMS shared-template tax that Bloxx's per-niche content generation eliminates.
Medium
Light body word count (~700 words)
Below the 1,000–1,500 word range typical for top-ranking UK insurance pages, particularly thin given Admiral's competitors have similar depth.
Smell test
Stale "Copyright @2025" footer
The page was republished 22 April 2026 but still shows 2025 in the footer. Tells you the publishing process has rough edges. Bloxx pages auto-update everywhere a date-bound element appears.