Skip to main content

Demand and Growth System

A rebuilt content architecture, technical SEO foundation, and measurement layer that made a firm's expertise discoverable in both search results and AI-generated answers.

Client
Specialist B2B services firm
Industry
Business services

Note. Portfolio concepts shown here are anonymized and representative of the kinds of intelligent business systems Aqlyst delivers. Client names, screenshots, and measured results are published only with written approval.

The situation

  • Expertise that search could not see

    Deep subject knowledge existed inside the firm but was published as isolated posts with no topic structure, so nothing accumulated authority.

  • Inquiries with no attribution

    Leads arrived through a form that emailed a shared inbox, leaving no reliable link between a campaign, a page, and an inquiry.

  • A slow, heavy site

    Unoptimized media and third-party scripts pushed load times to a point where both visitors and crawlers were being lost.

How we worked

  1. Topic architecture before publishingWe defined the subjects the firm wanted to be known for and structured services, articles, and case content into clusters that reinforce each other.
  2. Answer-first content structurePages state the answer plainly and early, then provide supporting detail — the structure both readers and AI assistants can use.
  3. Static-first rebuildThe site was rebuilt as a static-first application with a strict asset budget and accessibility built into the component layer.
  4. Measurement wired end to endA consistent event taxonomy and UTM discipline connect channel activity to inquiries, with no personal data sent to analytics.

How the system fits together

A static-first publishing model with structured content, generated search metadata, and inquiry capture that writes to a system of record.

  1. Content

    • Typed content model
    • Topic clusters
    • Editorial review
  2. Delivery

    • Static export
    • CDN delivery
    • Asset budget
  3. Discovery

    • JSON-LD
    • Sitemap and robots
    • Search Console and Bing
  4. Capture

    • Serverless form endpoint
    • Dataverse
    • Notification
  5. Measurement

    • Microsoft Clarity
    • Event taxonomy
    • Campaign attribution

What was built

  • Restructured content architectureService, insight, and case content organised into topic clusters with deliberate internal linking.
  • Technical SEO foundationCanonical structure, unique metadata, JSON-LD, sitemap and robots generation, and Core Web Vitals work.
  • Structured inquiry captureForm submissions written to a system of record with source path and campaign context, replacing the shared inbox.
  • Behavior and conversion reportingMicrosoft Clarity with form masking, plus an event taxonomy that attributes inquiries to pages and channels.

What changed

Figures are published only once the client has approved them. Where a value reads “Illustrative”, the improvement is real but the number has not been cleared for publication.

Organic visibility for target topics
Not yet approved for publication
Inquiry attribution coverage
Source path and campaign on every submission
Personal data sent to analytics
None

Technology stack

  • Next.js
  • Structured data (JSON-LD)
  • Microsoft Clarity
  • Power Automate
  • Dataverse

Next step

Working on something similar?

Bring the problem as it actually is, including the parts that are messy. That is usually the fastest route to a useful first conversation.

We reply to every message, usually within one business day.
info@aqlyst.ai · (901) 232-2944