Jonathan
Gouveia

Technical SEO and GEO

I help companies get found, in search results and in the AI assistants people now ask first.

Right now that means technical SEO and AI-search strategy at a top-5 US bank. Through PixelCove I take on both halves of the job: the design people see, and the technical SEO underneath it, on systems I build myself by directing AI coding agents.

Selected work

Four engagements, named with permission

PixelCove · 2025 to present · Shopify Hydrogen, design, SEO

Licorice Pizza Records

Storefront: Shopify Hydrogen, live in production
Catalog: ~40,000 titles via Admin bulk operations
Quote tool: replaced email quoting for 100 to 2,000 unit runs
Migration: Square to Shopify, self-managed, staged first

The problem

An LA record store trading since the 1970s, with real recognition across the city and a website that had fallen behind it. The store ran on an aging template, its architecture split across three systems that did not talk to each other, and mobile was the worst part of the experience.

The work

The engagement opened the way every PixelCove project opens, with a wireframe, before any timeline existed. From there: a bespoke Shopify Hydrogen storefront, a custom vinyl-pressing quote tool (a multi-step wizard with a live record visualizer) that replaced email quoting for runs of 100 to 2,000 units, a self-managed migration off the legacy POS stack, and a catalog import of roughly 40,000 titles run through Shopify's bulk operations, because the standard APIs cap out.

The result

The store is live in production. The designs did their own selling: Broadtime saw this work and asked for the same pattern across its own store network, with no outreach in between.

licoricepizzarecords.com

Before, June 2025. Captured from the Internet Archive. The homepage led with an apology about stock accuracy.

The rebuilt homepage: a photograph of the store's rooftop sign under the headline The Tastiest Music In Town, with buttons for vinyl pressing and shopping records. — **After.** Bespoke Shopify Hydrogen, live in production.

Both shots below are the current site. They are the two steps of the pressing funnel, not a comparison.

The Customize Your Vinyl Pressing landing page, over a photograph of a record on a turntable, listing a 100 unit minimum and a 6 to 8 week turnaround. — **Step one, the pressing landing page.** A 100 unit minimum, 6 to 8 weeks start to finish.

The quote tool it feeds: a multi-step form selecting project type, vinyl format and quantity, with a live estimate totalling $1,740. — **Step two, the quote tool it feeds.** A multi-step wizard that prices the run live, replacing the email thread.

PixelCove · 2025 to present · fleet SEO, measurement, design

Broadtime

Fleet: ~190 independent record stores
Analytics: shared container, per-store property, roll-up by store ID
Constraint: the 50-stream cap kills the naive design
Design: 3 homepage mockups shipped, brand extracted from each live site

The problem

Broadtime powers e-commerce for roughly 190 independent record stores. Nobody could say what the fleet was earning online. The traffic was real and the measurement was not.

The work

A fleet measurement architecture: one shared tag container feeding a per-store analytics property plus a roll-up keyed by store ID, because the obvious single-property design dies at the 50-stream cap. A reusable dashboard engine renders any store's numbers from config. On the front end, store audits and brand-refreshed homepage mockups, productized so that extracting a store's brand from its live site and rendering a new homepage takes minutes.

The result

The fleet has a measurement plan it can roll out, a dashboard that shows each store its own numbers, and a repeatable design refresh with three mockups shipped.

Homepage mockup for First City Records: slanted blue display type reading Your Record Store, Your Scene, over real catalog covers. — **First City Records.** I pulled the brand from the store's live site and rebuilt the homepage around it.

Homepage mockup for Vinyl Revival Records: a paper-and-ink search-first header reading Spin it again, above genre tiles. — **Vinyl Revival Records.** The same motion again, with a search-first header over a badged product grid.

A front-end redesign proposal for South Metro Records, headlined Same Store, New Front End, showing the proposed navigation and page map. — **South Metro Records.** A front-end proposal that keeps the store on the platform it already runs.

Technical SEO contractor · 2018 to 2023 · Adobe Experience Manager

Lands' End

Platform: Adobe Experience Manager
Scope: product listing and product detail templates
Organic demand: $100M to $120M in year one
Rankings: top 5 on "womens swimsuits" and "womens winter coats"

The problem

A catalog that size lives or dies on how well its product listing and detail pages are built for search, and the technical foundation across templates was leaving demand on the table.

The work

Programmatic technical SEO for product listing and detail pages: faceted-navigation URL structure, canonical logic, titles, headings, schema, and Core Web Vitals, built as scalable template requirements rather than one-off fixes. Training for the content, product, and merchandising teams on SEO writing workflows. An internal NLP content-generation program to produce SEO copy at scale, years before LLMs made that routine.

The result

Yearly organic search demand grew from about $100M to $120M after the first year, with top-5 rankings on competitive head terms.

SEO Manager · 2018 to 2025 · regulated fintech platform

Broadridge

Scale: 100,000+ advisor sites, 1M+ URLs
Platform clients: UBS, Wells Fargo, TD Bank, Stifel
Organic conversions: +453% after the technical and on-page work
Local visibility: +148% on geo-centric keywords

The problem

More than 100,000 advisor websites, over a million URLs, with no unified SEO foundation, in a regulated industry where consistency and E-E-A-T signals decide visibility.

The work

Founded and scaled the SEO program end to end: technical standards covering schema, crawlability, canonical and metadata logic; a local SEO strategy for advisors built on schema stacking, localized content, and quality citations; content guidelines the writing teams drafted against; reporting dashboards; and the governance process that kept it consistent at platform scale.

The result

Organic conversions rose 453% after the technical and on-page work. Geo-centric keyword visibility rose 148% after the local SEO program.

Work I can describe but not name

Client names withheld where the engagement requires it

Employer, name withheld

A top-5 US bank

Technical SEO Manager, 2026 to present. I own the GEO and LLM visibility strategy, and the agentic-web readiness of an enterprise site sitting behind an Akamai CDN and Bot Manager stack.

Ran a full crawl analysis of 1,599 URLs across 5 crawl types, then delivered the sitemap architecture (an index plus three sitemaps) and a robots.txt recommendation including AI-crawler policy.
Set the bank's GEO priority order, Copilot ahead of Claude and ChatGPT, from 25x year-over-year Copilot growth in B2B and finance, and built the authority framework behind it.
Two pages, 296KB and 340KB of HTML, both under Google's 2MB fetch limit, both passing every standard technical check. The real indexability problems were invisible to the checklist: rate content gated behind a ZIP-code prompt, store hours buried in a JavaScript accordion. A technical pass measures what is fetchable, not what is extractable.

Regulated, via agency partners

FDA-regulated patient-support programs

SEO, GEO and AEO across patient-support programs for regulated treatments, delivered through agency partners. All work cleared medical-legal review.

Shipped llms.txt live to production on a regulated pharmaceutical site, through medical-legal review.
Built the query strategy: 33 keywords, 55 AI prompts, 36 FAQs across two programs, plus a weekly 36-prompt GEO tracker measuring AI-answer visibility.
My technical audits caught sitewide missing structured data and a canonical-to-404 priority-zero defect.

# llms.txt
> Eligibility, enrollment, copay assistance.

## Eligibility
- [Who qualifies](/eligibility): income, insurance
## Enrollment
- [How to enroll](/enroll): forms, timelines
## Support
- [Copay assistance](/copay)
- [Contact a case manager](/contact)

Analytics / Measurement

The half of SEO that decides what gets funded

Nobody funds search work they cannot measure, so I build the measurement first and make the case for the SEO from what it shows.

At fleet scale that means an analytics architecture rather than a tag. One shared container feeds a per-store property plus a roll-up keyed by store ID, because the obvious single-property design dies at Google's 50-stream cap. Then verification in a real browser: load each live site, capture the network traffic, and see which tag actually fires. A container that is installed is not a container that collects, and the difference is usually where the revenue went missing.

On the reporting side I ship dashboards a client reads without me. A reusable Python engine renders any store's traffic, channels and revenue from config, and a separate report engine pulls Search Console and GA4 alongside AI-citation data into a matched before-and-after window, so a launch can be judged on production traffic rather than on a promise.

Architecture: shared container, per-property split, roll-up by store ID
Verification: every live site loaded in a real browser, traffic captured
Reporting: reusable dashboard engine, rendered from config
AI visibility: weekly prompt tracker, reported at citation level

GA4
GTM
BigQuery
Looker Studio
PowerBI
Tableau
Search Console API
CrUX
Adobe Analytics

An AI Search Visibility report: four summary tiles for citation presence, access terms, best position and generative-engine reach, above a table ranking ten tracked prompts by share of voice and most-cited source. — **AI search visibility, reported at citation level.** This is the report engine I built, rendered here for a fictional program on synthetic data. The real ones are client-confidential, so the layout is mine to show and the numbers are not.

> ls ~/tools

Custom-built tools

The SEO work runs on tools I build. Deterministic gates around LLM creativity, so the check runs every time and a written rule decays. Nothing auto-sends to a client, and no secret is ever stored at rest.

seo-agent-cli

$ seo-agent audit https://example.com --deep
  crawl        1,599 urls    5 crawl types
  schema       12 templates  3 invalid
  sitemap      index + 3     ok
  hreflang     0 errors      ok
  geo          llms.txt      missing
  visibility   41 prompts    12 cited
  competitor   8 pages       3 gaps
  plan         written -> audit.md + audit.json

  0 LLM calls. deterministic input layer for agents.
$

seo-agent-cli Review-first SEO audit CLI. Eight commands, markdown plus JSON reports, and no LLM inside the gate by design.
Bulk GSC URL Inspection Batches URL Inspection API calls under the 2,000 per day per property quota, with a rerun cache. Built because the Search Console UI inspects one URL at a time.
chatgpt-pipeline Parses a captured ChatGPT session to show how it actually picked sources: SERP against licensed against scraper pipelines, fan-out sub-queries, and whether your domain was fetched or cited.
site-health-monitor Four-layer monitoring (uptime, critical crawl, SEO, authority) with diff-based alerting and P0 to P3 severity routing, running on cron.
pp-google-search-console A Search Console CLI with an offline SQLite cache, powering period comparison, quick-win discovery, and cannibalization audits.

13 Claude Code skills I wrote

seo-audit-local
seo-audit-ecomm
seo-audit-saas
seo-geo-report
seo-distribution
parasite-seo
wireframe-proposal
prospect-design
broadtime-design
reddit-community-curation
mission-control
voiceprint
client report engine

Vertical-tuned client audits, a pre and post SEO plus GEO report built from real Search Console and GA4 alongside AI-citation data, and the wireframe-first offer productized as a skill. One report skill is named for its client, so it sits here unnamed.

Open source

gemini-interactions MIT. Single-file CLI for Google's Gemini Interactions API: image generation, music, speech, and grounded deep research. Zero install, runtime key resolution.
prove-it A Claude Code skill that makes a model distrust its own "done" and hunt for the bugs a confident finish hides.
fable-mode A disciplined working process (scope, evidence, verify, calibrate) packaged so any model can run it.
awesome-ai-automation A curated list of AI automation tools, platforms, and skills.

The Voiceprint workstream board: five pipeline stages from Pitched through Published, with drafts sitting as cards in the In Production column. — **Voiceprint.** An autonomous editorial desk that drafts, quality-gates and publishes behind deterministic checks: an X-weighted character count, a banned-phrase scan, and a sensitivity leak guard. Five scheduled jobs, each watched by a heartbeat. The only manual gate is *On your desk*.

Work experience

2002 to present

Roles held, most recent first. Figures are the ones I can attribute.
Role	Organization	Years	What came of it
Technical SEO Manager	A top-5 US bank	2026 to now	GEO strategy and a 1,599-URL enterprise crawl program
Founder	PixelCove	2025 to now	Design and technical SEO shipped in one engagement
Lead SEO Strategist, Enterprise	OuterBox	2025-2026	AEO and GEO programs; led two strategists
SEO Manager	Broadridge	2018-2025	+453% organic conversions across 100,000+ sites
SEO Technical Contractor	Lands' End	2018-2023	$100M to $120M in yearly organic search demand
SEO & Web Analytics Manager	State Street	2015-2018	+170% non-branded organic traffic, year one
SEO Manager	Didit	2012-2015	Fortune 100 financial, retail and SaaS clients
SEO Program Manager	Inceptor	2008-2012	Enterprise SEO strategy and dashboard reporting
Founder	Groomsday.com	2002-2008	SEO-centric ecommerce, built and ranked from zero

Shipped designs

50+ repositories, dozens of shipped systems

Client storefronts and my own products, designed and built by directing AI coding agents rather than by hand-writing production code. I say so plainly, because the credential is what shipped. Pearl, a text-message concierge for event weekends, is in a live pilot at askpearl.co behind 316 tests.