MyPhotoAI · pSEO case study

When pSEO is the wrong tool, and what to ship instead

Programmatic SEO is over-recommended. We have turned down four engagements in the last twelve months where the client wanted a pSEO surface and we shipped them something else: an editorial blog, a paid-ads experiment, a feature on the core product. This leaf is the checklist we run before any pSEO engagement, including the ones we accept. If any signal in section two fires, the engagement converts to editorial or to nothing at all.

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 walked four clients away from pSEO engagements in the last twelve months using the checklist on this page. The audit tool on /audit applies the same first signal automatically to any URL you submit.

When pSEO is the wrong tool, and what to ship instead

Signal one: low keyword headroom

If the long-tail keyword space for your domain has fewer than two hundred reachable phrases, pSEO is the wrong tool. A 22-leaf surface like this one is at the floor of viability; a 5-leaf pSEO surface is just a small blog with delusions of grandeur. The right move at that scale is one or two strong editorial pieces, not a synthetic surface. We test for this with a free pass through the audit tool on /audit; if the slug-diversity score for a comparable existing site is below 4, the topic does not support pSEO.

Signal two: thin source material

If the data backing each leaf is going to be the same paragraph with a substituted noun, you will get a thin-content penalty within ninety days. Google's quality rater guidelines treat substituted-noun pages as auto-generated spam. The fix is not better templating; the fix is more content per leaf. If you do not have at least eight hundred words of genuinely distinct material per slug, do not ship pSEO. Ship editorial instead, or invest in the source data first.

Signal three: the buyer journey is short

pSEO pays off slowly. Time-to-index runs five to fifteen days, and the long-tail traffic curve takes six to twelve weeks to materialize. If your sales cycle is hours rather than weeks, the right channel is paid acquisition. We sent one client to Google Ads for a four-week sprint instead of starting a pSEO build; their cost per qualified lead beat the projected pSEO cost per lead at our four-week mark. pSEO is a slow channel that compounds; if you cannot afford the wait, do not start.

Signal four: the topic is regulated or YMYL

Your-money-or-your-life topics in Google's classification, medical, financial, legal, get heavier E-E-A-T scrutiny. A 22-leaf pSEO surface on a YMYL topic from an unknown author does not rank, no matter the structural quality. The right move there is to invest in author authority first, an actual practitioner with credentials, and then layer pSEO on top of an established reputation. Section five of this body covers the workaround for the regulated 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 Search Quality Rater Guidelines (PDF) (Google Search Central)
  2. Google: creating helpful, reliable, people-first content (Google Search Central)
  3. Google: spam policies for Google web search (Google Search Central)
  4. Google: spam policies, auto-generated content (Google Search Central)
  5. Google: indexing overview (Google Search Central)
  6. Google: site: search operator (Google Search Central)
  7. Google: managing crawl budget for large sites (Google Search Central)
  8. sitemaps.org: 0.9 protocol specification (sitemaps.org)
  9. Google: title link and meta description best practices (Google Search Central)
  10. web.dev: Lighthouse SEO audits (Chrome for Developers)
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.