feat(landing): IndexNow + Google Indexing API post-deploy pings — GEO/SEO Phase 1.3

[matheuspoleza]

Description

Ping IndexNow (Bing/Yandex) and Google Indexing API on every deploy so new URLs are indexed in hours instead of 3–14 days. This is what makes "rank #1 for long-tail queries = cited by LLMs in days" actually work.

Context

Part of GEO/SEO strategy v1 (28-day scope).

• Design doc: plans/geo-seo-strategy.md
• Full task spec: plans/geo-seo-strategy/phase-01-foundation-infra.md → Task 3
• Technical reviewer note: Google Indexing API is officially restricted to JobPosting/Livestream types; generic URL notifications often get rejected. IndexNow is the reliable path; Google API is best-effort.

Acceptance Criteria

BDD scenarios

describe('Feature: IndexNow + Google Indexing API pings', () => {
  describe('Given a deploy with changed URLs', () => {
    describe('When the deploy completes', () => {
      it('then IndexNow is pinged at api.indexnow.org with the changed URLs', () => {});
      it('then Google Indexing API is pinged for each URL (best-effort)', () => {});
      it('then server logs show ping success/failure per URL', () => {});
    });
  });

  describe('Given a new blog URL deployed', () => {
    describe('When GSC URL inspection runs 24h later', () => {
      it('then the URL appears as indexed or crawled', () => {});
    });
  });
});

Checklist

• public/sitemap.xml includes all blog posts + docs + landing routes (generator script)
• Sitemap validates at validator.w3.org
• IndexNow key file hosted at vertz.dev/<key>.txt
• Deploy workflow triggers IndexNow ping for changed URLs
• Deploy workflow triggers Google Indexing API ping for changed URLs
• Integration test: after deploy, new URL appears in GSC URL inspection within 24h

Dependencies

• Blocked by: feat(landing): blog — dogfood Vertz stack at /blog #2947 (needs stable blog URL structure in main) — can develop in parallel but not deploy until merge

Progress

• 2026-04-22: Opened