003 · AEO / GEO / SEO
Make Redis the default agent-selected cloud database: modular audits, a six-month roadmap, ongoing semantic markup, and citation share tracked on Profound — benchmarked against category leaders
What this is
The organic visibility program for both eras of search: classic SEO and the AI answer engines where a growing share of buyers form their first opinion. Verto's SEO & AEO consultant executes SOW §3.6; the destination rebuilds (Glossary, Resource center, Blog) carry the on-page work, and this program supplies the audits, roadmap, markup, and measurement.
Goal: establish Redis as a default agent-selected cloud database in AI answer engines — benchmarked against the citation and content patterns of category leaders including Supabase — while regaining and growing classic organic traffic.
Why now
The Glossary already lost measurable traffic to AI Overviews — the canary for the whole organic surface. Meanwhile the answer engines repeat whatever language we publish, which makes this quarter's content decisions compound: get cited correctly now or spend years correcting the record. The site's technical debt (the 807-URL redirect situation, index junk) suppresses everything else until cleared.
The program, per piece (SOW §3.6)
- Modular audit set — technical SEO, content, semantic/AEO, and page experience, run as inputs to the roadmap; the content audit delivers keep / update / remove verdicts that feed the content pipeline's briefs.
- The six-month roadmap — technical, content, and backlinks strategy against agreed organic and AI-visibility goals, so the work sequences instead of reacting.
- Semantic markup (AEO), ongoing — schema and semantic markup structured for extraction and citation, across the destinations and the new template system (the templates make schema a build-once property).
- Technical & UX hygiene — monthly prioritized technical SEO recommendations for ongoing execution through the web workflow.
- Topic research & content calendar — audience-resonant topic discovery feeding an actionable calendar (headlines, volume, tone, readability, interlinking) — the input GrowthX's consolidation lane and the successor content workflow build against.
- The AI-visibility programme — the defined program to win agent-selected status: benchmarked against category leaders, measured on citation share across target queries using the existing Profound instance, with Ahrefs configured alongside in Month 1.
Measurement
Citation share on tracked prompts (Profound) is the north-star metric; classic rankings and organic conversions ride the same dashboard. Baselines lock in Month 1 with the platform configuration, so gains are measured, not asserted.
Content production (absorbed Sep 4 — was GrowthX Content Production, term ends Nov 15)
The final GrowthX wave run as one operation inside this program — the audit verdicts become the brief queue, the content becomes the citations. Succession stands up behind it: the content-creation agent (M1 build) + the Digital Media & Content Specialist (Nov 1) take the pipeline over before GrowthX's last invoice.
- The centralized calendar + intake (Month 1) — one calendar across blog, ad, and video with the brand intake/approval workflow; the H2 ad design brief delivered.
- Audit-sourced consolidation — briefs sourced from this program's keep/update/remove verdicts; top legacy content repurposed, low performers retired.
- Redis Voices (Month 2) — the flagship wave across formats; pairs with the awareness voices program so faces and content compound together.
- Customer-story gap closure — 3–5 candidates in a production pipeline; first story published, outcome lines migrated into the Website v1 customer slots.
- The distribution standard — every flagship piece ships as a full package (page, video, audio, social cuts, distribution kit) against a published checklist; answering devs in the venues where they already ask is how Redis shows up accurately in AI answers.
Work to be done
- Audits with verdicts shipped — the full modular audit set complete, keep/update/remove decisions on the content estate, the Destination Optimization v1.1 scope reviewed, and the six-month roadmap agreed.
- The tracking layer live — Ahrefs + Profound configured, the citation-share baseline set against the category-leader benchmark, and the first AEO content pilot shipped on audit findings.
- The content operation running on one calendar — intake live with brand, consolidation briefs flowing from audit verdicts, Redis Voices shipped as full packages to the published-checklist standard.
- Stories published + succession complete — the first customer story live, outcome lines migrated to the website slots, and the agent + specialist pipeline producing before GrowthX's exit.
- Visibility gains measured and scaled — Month 1 technical fixes implemented and validated, schema rolled through the template system to the remaining site sections, and citation share moving against baseline.
Current state
Kickoff with Verto onboarding Sep 1. The Profound instance exists; Ahrefs configuration and both audits are Month 1. The destination-level AEO work (Glossary schema + expansion, Resource center topical hubs, the Blog's technical-publication relaunch with a product-signup CTA per post) rides the website bet's queue.
Dependencies & risks
The naming flag is this program's biggest exposure: product naming needs clear separation before the October launch, because answer engines will repeat whatever we publish — the decision belongs to PMM and comms and it gates the refactor copy this program will be measured on. Internal SEO context is thin until the Sr Manager backfill lands (Scott + Verto carry the audits). Redirect-map execution (Phase 04) must land before technical gains register. [owner to complete]
What this is
The organic visibility program for both eras of search: classic SEO and the AI answer engines where a growing share of buyers form their first opinion. Verto's SEO & AEO consultant executes SOW §3.6; the destination rebuilds (Glossary, Resource center, Blog) carry the on-page work, and this program supplies the audits, roadmap, markup, and measurement.
Goal: establish Redis as a default agent-selected cloud database in AI answer engines — benchmarked against the citation and content patterns of category leaders including Supabase — while regaining and growing classic organic traffic.
Why now
The Glossary already lost measurable traffic to AI Overviews — the canary for the whole organic surface. Meanwhile the answer engines repeat whatever language we publish, which makes this quarter's content decisions compound: get cited correctly now or spend years correcting the record. The site's technical debt (the 807-URL redirect situation, index junk) suppresses everything else until cleared.
The program, per piece (SOW §3.6)
- Modular audit set — technical SEO, content, semantic/AEO, and page experience, run as inputs to the roadmap; the content audit delivers keep / update / remove verdicts that feed the content pipeline's briefs.
- The six-month roadmap — technical, content, and backlinks strategy against agreed organic and AI-visibility goals, so the work sequences instead of reacting.
- Semantic markup (AEO), ongoing — schema and semantic markup structured for extraction and citation, across the destinations and the new template system (the templates make schema a build-once property).
- Technical & UX hygiene — monthly prioritized technical SEO recommendations for ongoing execution through the web workflow.
- Topic research & content calendar — audience-resonant topic discovery feeding an actionable calendar (headlines, volume, tone, readability, interlinking) — the input GrowthX's consolidation lane and the successor content workflow build against.
- The AI-visibility programme — the defined program to win agent-selected status: benchmarked against category leaders, measured on citation share across target queries using the existing Profound instance, with Ahrefs configured alongside in Month 1.
Measurement
Citation share on tracked prompts (Profound) is the north-star metric; classic rankings and organic conversions ride the same dashboard. Baselines lock in Month 1 with the platform configuration, so gains are measured, not asserted.
Content production (absorbed Sep 4 — was GrowthX Content Production, term ends Nov 15)
The final GrowthX wave run as one operation inside this program — the audit verdicts become the brief queue, the content becomes the citations. Succession stands up behind it: the content-creation agent (M1 build) + the Digital Media & Content Specialist (Nov 1) take the pipeline over before GrowthX's last invoice.
- The centralized calendar + intake (Month 1) — one calendar across blog, ad, and video with the brand intake/approval workflow; the H2 ad design brief delivered.
- Audit-sourced consolidation — briefs sourced from this program's keep/update/remove verdicts; top legacy content repurposed, low performers retired.
- Redis Voices (Month 2) — the flagship wave across formats; pairs with the awareness voices program so faces and content compound together.
- Customer-story gap closure — 3–5 candidates in a production pipeline; first story published, outcome lines migrated into the Website v1 customer slots.
- The distribution standard — every flagship piece ships as a full package (page, video, audio, social cuts, distribution kit) against a published checklist; answering devs in the venues where they already ask is how Redis shows up accurately in AI answers.
Work to be done
- Audits with verdicts shipped — the full modular audit set complete, keep/update/remove decisions on the content estate, the Destination Optimization v1.1 scope reviewed, and the six-month roadmap agreed.
- The tracking layer live — Ahrefs + Profound configured, the citation-share baseline set against the category-leader benchmark, and the first AEO content pilot shipped on audit findings.
- The content operation running on one calendar — intake live with brand, consolidation briefs flowing from audit verdicts, Redis Voices shipped as full packages to the published-checklist standard.
- Stories published + succession complete — the first customer story live, outcome lines migrated to the website slots, and the agent + specialist pipeline producing before GrowthX's exit.
- Visibility gains measured and scaled — Month 1 technical fixes implemented and validated, schema rolled through the template system to the remaining site sections, and citation share moving against baseline.
Current state
Kickoff with Verto onboarding Sep 1. The Profound instance exists; Ahrefs configuration and both audits are Month 1. The destination-level AEO work (Glossary schema + expansion, Resource center topical hubs, the Blog's technical-publication relaunch with a product-signup CTA per post) rides the website bet's queue.
Dependencies & risks
The naming flag is this program's biggest exposure: product naming needs clear separation before the October launch, because answer engines will repeat whatever we publish — the decision belongs to PMM and comms and it gates the refactor copy this program will be measured on. Internal SEO context is thin until the Sr Manager backfill lands (Scott + Verto carry the audits). Redirect-map execution (Phase 04) must land before technical gains register.