MyPhotoAI · pSEO case study

Results

This page documents what the pSEO work moved. Exact numbers are deliberately withheld; the disclosure boundaries for this case study are described at the top of overview. The shapes below are accurate; the absolute values would be misleading without context.

What moved

Indexed pages. The single largest shift was in the count of URLs Google indexed from the product domain. The growth shape was directional: a step change in week one (the sitemap submission), a steeper-than-organic curve over the following weeks (the IndexNow effect plus internal linking), then a plateau as the manifest stabilized. The plateau is the right shape for a curated pSEO surface; an unbounded curve usually means content sprawl.

Long-tail impressions. Impressions on long-tail queries grew significantly faster than impressions on head terms. This is the expected pattern: pSEO opens up surface area in the long tail, where competition is thinner and intent is sharper. Head terms are a separate game, won by editorial authority, not by manifest size.

Click-through rate. CTR moved into the double digits on a meaningful share of the new pSEO surface, against the single-digit baseline that broad-match impressions normally produce. The leaves that beat the baseline were the ones with the strongest internal-link blocks; this is consistent with the literature.

What did not move

Conversion rate on the indexed traffic. This is the part that is easy to ignore and important to call out. A pSEO surface that ranks but does not convert is doing search engines a favor, not the business. The case-study site addresses this by including a real conversion path (the /audit tool here) so the visitor has something to do other than bounce.

Time on page. The pSEO leaves are deliberately short. The visitor either finds what they came for in 30 seconds or leaves; the leaf is not a destination, it is a routing hop. Time-on-page is the wrong metric for this surface.

Sanitized scale

In ranges:

| Metric | Direction | Order of magnitude | |---|---|---| | Indexed pages | grew | roughly 10x from week 1 to month 3 | | Long-tail impressions | grew | comparable order to indexed pages | | Head-term impressions | flat | a non-event | | CTR on pSEO surface | moved up | into low-double-digits on the best leaves | | Conversion rate on pSEO traffic | small | as expected; the conversion path matters more than the volume |

The exact numbers, with context, are available on request from AlkenaCode under a brief that names the use case.

What this case study does not claim

  • That pSEO is a substitute for editorial work. The spine pieces matter more than the leaves; the leaves only work because the spine exists and links to them.
  • That the numbers above are guaranteed for any other site. Different products, different categories, different competitive density.
  • That an AI-only manifest would work. The human curate step is load-bearing; AI drafts that go unedited produce template fatigue, which is the failure mode this case study is built to demonstrate is avoidable.

If you want a working diagnostic for whether pSEO is a fit for your site: run the auditor. It will not return numbers; it will return a structured opinion.