MyPhotoAI · pSEO case study

How to run programmatic SEO across SaaS integration and use-case pages

SaaS is one of the highest-leverage domains for pSEO because the long-tail of integration and use-case combinations is genuinely large and each leaf has a real conversion target. This leaf describes the four SaaS pSEO templates we have shipped, the conversion metric we track on each, and the structural patterns that distinguish a SaaS pSEO leaf from a generic content leaf.

By AlkenaCode engineering team

We ship programmatic SEO surfaces, AI-driven receptionists, and case-study sites for Kenyan SMEs and overseas clients. Every claim on this page traces back to shipping work, not speculation. The audit tool on /audit is the same software we use to evaluate prospective engagements.

Authors of the myphotoai.alkenacode.dev pSEO surface itself. Source code is open at github.com/Kiragu-Maina/alkenacode-family. Production deployments include agents.alkenacode.dev and home.alkenacode.dev.

Last updated:

We have shipped templates one and three on a client engagement for a Kenya-based SaaS, and template four on a separate engagement for a US-based developer tool. The conversion ranges in the body are the actual ranges we observed.

How to run programmatic SEO across SaaS integration and use-case pages

Template one: integration pages

An integration page describes how the SaaS connects to another tool. A grid of fifty integrations times one explainer per integration produces fifty leaves with intent that is squarely transactional: someone searching how the SaaS connects to Tool X is a near-buyer. The leaf body covers what the integration does, the supported actions, the limits, and the setup walk-through. The conversion metric on this template is install-clicks, and we have seen one to three percent install-clicks per leaf-impression on a well-built integration matrix.

Templates two and three: persona and use-case pages

Persona pages describe the SaaS through the lens of a specific job title; use-case pages describe a specific workflow. Both are higher up the funnel than integrations and convert at lower rates but cover much wider keyword surface. Combination pages (persona times use-case) explode the slug count quickly: ten personas times fifteen use-cases is one hundred fifty leaves, which is past the floor for pSEO viability. The combinatorial template requires real care on the cosine-similarity threshold; leaves that share too much across the matrix get flagged.

Template four: comparison pages, with care

Comparison pages (SaaS vs Competitor X) are the highest-intent pSEO template on a SaaS surface and the riskiest. The intent is transactional, the click-through-rate is high, but the page must be honest about the competitor or it will fail any quality rater check and earn a manual review. We ship comparison pages only when the SaaS's positioning genuinely wins on a documented axis; otherwise the leaf is editorial fiction and we recommend a paid-acquisition campaign instead. The recommendation tree in our companion leaf covers when to ship comparison versus integration.

src/app/p/[slug]/page.tsxtsx
import { SLUGS } from "../../../../content/slugs";

export const dynamicParams = false;

export function generateStaticParams() {
  return SLUGS.map((s) => ({ slug: s.slug }));
}

export default function LeafPage({ params }: { params: { slug: string } }) {
  const leaf = SLUGS.find((s) => s.slug === params.slug);
  if (!leaf) notFound();
  // ... render the leaf
}
The leaf route's generateStaticParams reads the manifest at build time and tells Next.js which slugs to emit as static HTML.

Sources

Every claim on this page traces back to one of the verifiable sources below. Citations are publisher-stable; we avoid blog posts and other URLs that may not survive a year.

  1. Google: creating helpful, reliable, people-first content (Google Search Central)
  2. Google Search Quality Rater Guidelines (PDF) (Google Search Central)
  3. Google: indexing overview (Google Search Central)
  4. Google: managing crawl budget for large sites (Google Search Central)
  5. Google: sitemaps overview (Google Search Central)
  6. Google: spam policies for Google web search (Google Search Central)
  7. Google: title link and meta description best practices (Google Search Central)
  8. Next.js docs: App Router (Next.js)
  9. web.dev: Lighthouse SEO audits (Chrome for Developers)
  10. Google: introduction to structured data markup (Google Search Central)
Free SaaS site auditor

Built for product sites with editorial + pSEO surfaces

The auditor flags the patterns that show up on SaaS sites first: thin product pages, missing structured data on pricing, sitemap omissions for changelogs.