MyPhotoAI · pSEO case study

Programmatic SEO versus traditional SEO: when each one wins

Programmatic SEO is not a replacement for traditional editorial SEO; it is a different tool that wins on different problems. This leaf compares the two approaches across seven dimensions and ends with a recommendation tree for which to ship when. The numbers in the body come from the two production surfaces we run plus the editorial surface at alkenacode.dev itself.

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 run the editorial surface at alkenacode.dev/work and the programmatic surface here on myphotoai.alkenacode.dev. The cost and time numbers in this body are our own pipeline numbers, not industry averages.

Programmatic SEO versus traditional SEO: when each one wins

Speed to first index

Editorial: a single 1500-word piece, well-linked, indexes in three to seven calendar days. Programmatic: a 22-leaf surface starts indexing in five to fifteen days and reaches near-full coverage at thirty to sixty days. Editorial wins on first-impression speed for a single keyword; pSEO wins on volume because the long-tail surface scales independently. If you need to rank for one phrase tomorrow, write a single high-quality post and link to it from your homepage. If you need to be discoverable across two hundred phrases over the next quarter, build the surface.

Cost to ship

Editorial: a senior writer at fifty USD per hour, eight to twelve hours per piece, equals four hundred to six hundred USD per ranking page. Programmatic: an engineering team builds the surface once, roughly forty hours of focused work for a 22-leaf set, then the marginal cost per leaf is the author's writing time per slug, which is much lower if the slugs share a template. Our amortized cost per leaf on this surface is about eighty USD, including engineering setup. Editorial costs more per page; pSEO costs more upfront and amortizes.

Durability and defensibility

Editorial wins on durability when the piece is the canonical reference for its phrase; nobody is going to outrank a well-cited explainer that ages well. Programmatic surfaces face higher copy risk: a competitor can stand up a similar surface in a quarter. The defensibility for pSEO comes from internal-link density and the proof-by-example surrounding the surface, not from the leaves themselves. This is why our pSEO leaves all link back into spine pieces that are editorial in nature: the spine is durable, the leaves are the volume play.

Recommendation tree

If you sell to one persona on a small number of high-intent phrases, ship editorial. If you sell to many personas on a long-tail of low-intent phrases, ship programmatic. If you sell on a fast cycle to known accounts, neither: do outbound. If you sell to a regulated or YMYL audience, build author authority first and layer either editorial or programmatic on top once you have it. We have shipped all four shapes; this surface itself is the programmatic case, and alkenacode.dev/work is the editorial case.

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: sitemaps overview (Google Search Central)
  5. Google: spam policies for Google web search (Google Search Central)
  6. Google: managing crawl budget for large sites (Google Search Central)
  7. web.dev: Lighthouse SEO audits (Chrome for Developers)
  8. Google: title link and meta description best practices (Google Search Central)
  9. Google: site: search operator (Google Search Central)
  10. Google: page experience signals (Google Search Central)
Free site auditor

See how the pattern applies to your site

The auditor uses the same evidence bundle described above (robots, sitemap, page samples) and returns a structured opinion. No signup, no email required to see results.