# Programmatic SEO - Adding Millions of New Visits

DevFeed: [Programmatic SEO - Adding Millions of New Visits](<https://devfeed.tech/articles/programmatic-seo-adding-millions-of-new-visits-24995.md>)

Original publisher: [Read original article](<https://codeahoy.com/2022/07/15/programmatic-seo-millions-of-new-visits/>)

Author: umer

Published: 2022-07-15T00:00:00Z

Content type: opinion

Language: en

Sources: [Code Ahoy - Articles](<https://devfeed.tech/sources/code-ahoy-articles.md>)

Topics: [Search engine optimization (SEO)](<https://devfeed.tech/topics/seo.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Website](<https://devfeed.tech/topics/website.md>), [Google](<https://devfeed.tech/topics/google.md>), [WordPress](<https://devfeed.tech/topics/wordpress.md>)

Tags: [backend](<https://devfeed.tech/tags/backend.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [google](<https://devfeed.tech/tags/google.md>), [growth](<https://devfeed.tech/tags/growth.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [seo](<https://devfeed.tech/tags/seo.md>), [wordpress](<https://devfeed.tech/tags/wordpress.md>)

## AI overview

The article argues that an engineering team responsible for organic growth was focused mainly on SEO infrastructure and maintenance rather than measurable traffic growth. It describes redirecting the team toward customer outcomes, an owned traffic goal, and meaningful wins, while noting that much existing search traffic was branded.

## Source excerpt

I was a senior engineering manager once at a company that helps job seekers, and one of my teams owned organic growth. It was a (relatively) small team team of very capable engineers front and backend engineers responsible for driving 'organic growth' and traffic. On paper that meant getting more people to the site from Google. But in reality, the team wasn't doing that. They were doing SEO infrastructure and maintenance. Generating sitemaps; keeping the services behind them running. Updating headings and title tags. Reviewing internal links. Owning the 'header' and 'footer'. Owning some low value sections of the website that weren't important to users (or the company). Inheriting work that other teams didn't want e.g. keeping legacy WordPress servers running that were important all but once a year when the company ran its annual awards and increased the traffic many folds. None of it was bad work - and somebody had to do all of it. But they weren't driving anything. There was no number they owned, no goal they were chasing, and nothing coming up that anyone was excited about. The team was a long way from the customer and even further from any outcome they could point at and say we did that. Getting the team closer to the outcome I wanted to change what the team was pointed at. Not their skills, not their headcount, and not how hard they worked. Just what they were aimed at. That meant three things: Get them closer to the customer Get them closer to the outcome, with a number that they actually owned Get them some wins, because a team that hasn't shipped anything meaningful in a while stops believing it can So I went to the VP who owned organic growth and asked a simple question: what are we actually trying to achieve here? Not what tickets need closing. Or how many sitemaps are indexed. What's the goal? The answer was traffic. Real traffic. We looked at the roadmap together and realized that most of the upcoming work was slotted for regular maintenace, SEO infrastr