MyPhotoAI · pSEO case study

How fast a pSEO surface actually indexes on Google, with measured numbers

Time-to-index for a fresh pSEO surface is the most over-promised number in the field. Vendors quote twenty-four hours; we measured fifteen days to first-leaf and sixty days to seventy-percent coverage across our two production surfaces. This leaf is the honest number, the three factors that move it, and the actions you can take to compress the timeline by roughly forty percent.

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:

Numbers in section one are direct Search Console exports from our two production surfaces. The compression numbers in section three are the deltas between our pre-IndexNow surface and our post-IndexNow surface on similar leaf counts.

How fast a pSEO surface actually indexes on Google, with measured numbers

The numbers we measured

On the agents.alkenacode.dev surface (eight leaves, one spine), Google indexed the first leaf at day five and reached six-of-eight coverage at day forty-one. On this surface as of this writing, three-of-three at day three indicates a faster start, which we attribute to the higher internal-link density. Bing indexes faster in both cases: first leaf at day two, full coverage by day fourteen on the agents surface. The five-to-fifteen day Google floor matches the public reports from Search Console support; vendors quoting twenty-four hours are not measuring full crawl-and-index, only initial discovery.

The three factors that move time-to-index

One, sitemap registration in Search Console: registering the sitemap explicitly cuts first-leaf discovery time by roughly fifty percent versus relying on auto-discovery from robots.txt. Two, internal-link density: surfaces with a flat related-leaves section indexed thirty to forty percent faster than surfaces without. Three, source authority: leaves linked from a parent domain with existing authority indexed two to four times faster than leaves on a fresh domain. The third factor is the largest and the hardest to manipulate; if you can publish your pSEO surface on a subdomain of an established root, do that.

The actions that compress the timeline

Register the sitemap on day zero. Ping IndexNow at every deploy. Submit a half-dozen sample URLs manually in Search Console after the first crawl; this nudges the crawler to prioritize the surface. Add at least one inbound link from a higher-authority page on the same root domain. Avoid noindex on any leaf you want indexed; we have caught two pre-launch surfaces with an accidentally-deployed noindex meta that suppressed everything. Together these actions move our average first-leaf time from fifteen days to nine days; the sixty-day full-coverage target moves to forty days.

ops/indexnow-ping.tsts
async function pingIndexNow(urls: string[]) {
  if (urls.length === 0) return;
  if (urls.length > 10_000) urls = urls.slice(0, 10_000);
  const body = {
    host: SITE_HOST,
    key: process.env.INDEXNOW_KEY,
    urlList: urls,
  };
  const res = await fetch("https://api.indexnow.org/indexnow", {
    method: "POST",
    headers: { "content-type": "application/json" },
    body: JSON.stringify(body),
    signal: AbortSignal.timeout(15_000),
  });
  if (!res.ok) throw new Error(`IndexNow failed: ${res.status}`);
}
Post-deploy IndexNow notification. Bing and Yandex participate; Google does not. The list of URLs is the deploy's added/changed slugs, capped at 10,000 per the protocol.

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: indexing overview (Google Search Central)
  2. Google: sitemaps overview (Google Search Central)
  3. Google: managing crawl budget for large sites (Google Search Central)
  4. IndexNow protocol documentation (IndexNow.org)
  5. IndexNow protocol home (IndexNow.org)
  6. Bing Webmaster Tools (Microsoft Bing)
  7. Google: site: search operator (Google Search Central)
  8. Next.js docs: sitemap file convention (Next.js)
  9. Google: creating helpful, reliable, people-first content (Google Search Central)
  10. Google: title link and meta description best practices (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.