<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Natasha Ghosh on Medium]]></title>
        <description><![CDATA[Stories by Natasha Ghosh on Medium]]></description>
        <link>https://medium.com/@natasha.ghosh21?source=rss-092b83fc5e56------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Wh6Uohqm7GnGx1PG</url>
            <title>Stories by Natasha Ghosh on Medium</title>
            <link>https://medium.com/@natasha.ghosh21?source=rss-092b83fc5e56------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 21:50:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@natasha.ghosh21/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[One Does Not Simply “Work” In SEO Anymore]]></title>
            <link>https://medium.com/@natasha.ghosh21/one-does-not-simply-work-in-seo-anymore-722dbe54a8f7?source=rss-092b83fc5e56------2</link>
            <guid isPermaLink="false">https://medium.com/p/722dbe54a8f7</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Natasha Ghosh]]></dc:creator>
            <pubDate>Fri, 20 Nov 2026 09:59:03 GMT</pubDate>
            <atom:updated>2026-11-20T09:59:03.516Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JjDmWPmScLGJ3ROAk7SAPg.png" /></figure><p>I work in SEO.</p><p>SEO is my job.</p><p>I also love SEO, and always have.</p><p>But…</p><p>Of late, SEO has become more my job than I fully enjoy. And in becoming so, it has somehow… become less.</p><h3>Industries In Flux</h3><p>We’ve all been witnessing the rapid evolution in the search and SEO landscape over the last two years. For so many of us, search has been synonymous with Google Search for quite some time now. With Google completely upending the model, the discipline as a whole is in a state of flux.</p><ol><li>With AI-powered search, the lines between technical, content and off-page SEO begin to get somewhat blurred. These lines have served as distinct specializations within SEO that many of us have structured our very careers around. But these only represent one layer of existential uncertainty.</li><li>While SEO as a whole evolves, practically all of us have come head-to-head with this one common existential dread — are AEO and GEO subdisciplines within SEO? Or are they cousins? And are content, technical and off-page… nieces and nephews in the new model?</li><li>Then there is yet another layer — are you at an org that believes AI can replace the entire SEO function? Or are you at an org where you’re being encouraged to learn how to incorporate AI more and more into your everyday workflow? Or are you somewhere in the middle, like me, yelling at ChatGPT for sending me an emoji when I was being sarcastic about its erroneous calculations of QoQ % increase?</li></ol><p>I think the answer will be different depending on who is asked. While AEO and GEO seem like SEO’s new cousins to me, somebody who works in a different industry and tackles a different problem space might have a completely different view. And they might also think their SEO function could and should be replaced by AI. I don’t think there are any wrong answers yet; everything is still too new.</p><h3>Feeling Stretched</h3><p>Honestly, I am scrambling. I am scrambling to hire the right folks with the right experience while making sure I am not being tricked by AI interviewing software or worse, AI candidates. Scrambling to ask candidates the right questions so I am not wasting my time or theirs… or my company’s. I am scrambling to keep up with the latest updates in the industry, while scrambling to ensure our strategic direction encompasses it.</p><p>I am stretched across three disciplines that are quickly expanding in scope, even while they are components of a larger discipline: user discovery. And I am setting stretch goals every quarter to make sure I feel like I am doing enough.</p><p>I have gone from being a somewhat invisible subject-matter-expert to a highly visible one. I have gone from being pulled in to projects at the last moment, to being pulled into too many projects and early enough that I am not allowed to say at what point.</p><p>Once upon a time, PTO used to be my most cherished currency; for a while now, it has been the trust of my coworkers. Whether it is regarding the quality of my work, my commitment to my customers, or simply the fact that I will be late to dinner but not to a client meeting, I work hard to keep and reciprocate that trust.</p><p>Through all this, adopting the patience of the Buddha and the passion of Kali is the unlikely corporate survival strategy nobody told me about… and it is heavily underrated.</p><h3>New Tools and MORE New Acronyms</h3><p>I am also scrambling to find the right tools and the right vendors. I am scrambling from one meeting to another and then I am scrambling to lunch with a different vendor while reminding myself to grab the shrimp Pad Thai my partner wants from the cafeteria. Then I am scrambling to spend time with my pups while secretly worrying if I messed anything up with the new-vendor contract I just hit “Approve” on earlier.</p><p>All the while, I am trying to memorize what TAVI, ARS, SSI, PDI and SoP are before explaining those terms to a group of teammates. And that’s just within one vendor’s platform.</p><p>It. Is. A. Storm.</p><p>An “Alphabet Soup Storm”.</p><p>Because OF COURSE every new AI visibility platform is going to end up with their own brand-new metrics, calculations, definitions and acronyms.</p><p>And I get why.</p><p>It still doesn’t stop being migraine-worthy for the rest of us.</p><p>If they don’t start teaching SEO as a specialization within a major degree, or as a minor, I am going to have a job forever. Even when I want to retire.</p><h3>Neither Here Nor There</h3><p>Through all this “storminess”, SEO has become a little less for me.</p><p>The stillness of analyzing data, the quiet relief of a low-text-to-HTML-ratio article starting to rank, the pulsing victory of winning a SERP feature within a few days of publishing, the thrill of investigating a log file, learning little things about CDNs and DNSes every single day… these little things made SEO feel so much bigger for me.</p><p>This story has no resolution today because to flatten it into one would be dishonest. Sometimes, we inhabit liminal spaces and that is okay. Perhaps, it feels lonely sometimes because there is more room to grow into.</p><p>My mother once taught me about ikigai. And for many years, SEO completed that structure for me. Now, SEO’s siblings threaten to unbalance it.</p><p>I miss the thrill of using human language to make a difference in a world built of machine languages.</p><p>But I would be lying if I said I was tired. I am not.</p><p>Not being able to play with language the way I used to, that’s not really my kind of SEO work. But not knowing where the ship is heading through dark and stormy seas, that’s my kind of adventure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=722dbe54a8f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Everybody is an SEO Product Manager Now]]></title>
            <link>https://medium.com/@natasha.ghosh21/everybody-is-an-seo-product-manager-now-62f387c9b774?source=rss-092b83fc5e56------2</link>
            <guid isPermaLink="false">https://medium.com/p/62f387c9b774</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[seo]]></category>
            <dc:creator><![CDATA[Natasha Ghosh]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 20:24:31 GMT</pubDate>
            <atom:updated>2026-11-12T20:25:49.581Z</atom:updated>
            <content:encoded><![CDATA[<h3>“Everybody is a Product Manager Now”</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7ZRZKJmKAEO47eqzNKWlXQ.jpeg" /><figcaption>Image generated by an LLM</figcaption></figure><p>A product manager, who I respected (and still do), who gave me my big break in my career and had managed me for about a year, shocked me with her response to my successful lane swap from Marketing to Product.</p><blockquote>“Oh wow, they’re making everybody a product manager these days.”</blockquote><p>While that caught me by surprise, it was also the validation that I needed. It wasn’t that “everybody” was becoming a product manager. It was that “every” engineering team was realizing why they needed one.</p><h4>Origins</h4><p>I come from a Literature background. My passion is language. SEO was a natural exit on the endless freeway of content specialist. Fascinated by the math, logic and data science involved, I was lured into the darker murky waters of web development as a means to better control the impact of the written word.</p><p>Today, I love how language is part of a technical system that two entirely different sets of audiences interact within, all while speaking two entirely unique languages.</p><p>I think my own seemingly-insatiable curiosity is going to one day be my own demise, really. But for now, it results in incredibly satisfying professional and career growth.</p><h4>Learning</h4><p>When I had wanted to become a product manager, I had naturally informed my manager of my decision, and begun to demonstrate the impact of my work.</p><p>But I had also taken a course at The Product School. I loved it and I adored the instructor. My favorite thing about her was that she laid out the most complete, perfect and wholesome structure of a single product strategy idea and then she told us, it would never actually play out like that. The deliverable from that course was a PRD. Years later, I use that PRD as a reference point to this day. It was the most perfect and complete PRD I have ever written to date. But it is not for a real product haha or one I would ever actually build.</p><p>But what was made clear to me by my instructor was that it was an ambitious career move (lane-swapping from Marketing to Product, while keeping my P4 leveling), and that nobody wanted to hire a new product manager from outside their org, or one who had no referrals.</p><p>Three supremely important truths emerged during this time in my career.</p><ol><li>Outside my company, “nobody” wanted to hire new product managers</li><li>Within my company, “everybody” was being converted to a product manager</li><li>SEO was evolving into a new, different group of functions</li></ol><p>Conclusion: Get into a company as their SEO lead and convert the function into a product surface. Use the company’s problem space to ground the product vision, strategy and objectives of your new product-led SEO function. Hire accordingly.</p><h4>Transitioning</h4><p>I was already at a company where my manager was supportive of my transition. The outcomes expected of my work had already begun demanding a productized approach.</p><p>So I then reorganized the SEO function at my company into a product-led framework. I pitched the model, its potential impact, and known trade-offs. That eventually led to my lane-swap into Product Management.</p><p>Being somebody who “grew up” in SEO, I often feel like an impostor in the world of PMs — there still are not very many SEO PMs haha. But there are some.</p><p>Very soon, I’ll find myself saying “They’re making everybody a(n SEO) product manager now” but with a different attitude.</p><p>“Everybody” likely has to be one in order to survive the changes in the world of SEO.</p><h4>To Conclude</h4><p>I personally love websites so much, I had wanted to be one well before I wanted to build one. It is the single-most fascinating thing in the world, to feel connected to a whole unseen world through code and cables and networks. Who wouldn’t want to be one?</p><p>I know I obviously can’t be one, and I also don’t think I want to go back to school to become a developer. The best way for me to love these fascinating systems moving forward is to by treating organic search as a product surface.</p><blockquote>Productize your SEO. You’ll thank yourself. And me.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62f387c9b774" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Navigating SEO, AEO, GEO and SXO “Creatively”]]></title>
            <link>https://medium.com/@natasha.ghosh21/navigating-seo-aeo-geo-and-sxo-creatively-ff4f88b3300e?source=rss-092b83fc5e56------2</link>
            <guid isPermaLink="false">https://medium.com/p/ff4f88b3300e</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Natasha Ghosh]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 01:28:26 GMT</pubDate>
            <atom:updated>2026-11-11T01:28:26.894Z</atom:updated>
            <content:encoded><![CDATA[<h3>Oh Goodie, More SEO Acronyms</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BwfoyhLnEXTVgOW-0sbOiA.png" /><figcaption>Image generated by an LLM</figcaption></figure><p>There were signs back in 2017 and 2018 that the type-a-few-words-find-many-links search experience on search engines was going to be replaced by a more immersive one.</p><p>I personally remember Google releasing the Transformers research paper in 2017, and then open-sourcing BERT the next year. Naturally, the BERT Update was a huge deal for us SEOs in 2019. While I did not fully grasp what it meant, the BERT update felt huge, and like we were beginning to envision a more immediate reality with some form of consumer-facing artificial intelligence, and not some rudimentary tech either. The industry was already beginning to reek of generative AI to me.</p><p>So naturally, I concluded that that AI would extend to the search experience eventually. I am selfish, I worried primarily about my job and the security of my role and function. But, it forced me to ask some important questions and scrutinize industry patterns more closely.</p><p>We already had a WEALTH of content on the web. In fact, in the mid-2000s, humans the world over were still painstakingly taking the time to digitize their content and workflows, both external and internal. Whatever AI the more advanced tech companies built would either involve the conversion of digital and print content into a whole other machine-ingestable format. This would require an expensive and high-friction adoption commitment.</p><p>These tech companies could not afford that. The product had to feel valuable quickly and for free. They were going to find ways to use the vast wealth of content on the web. That would essentially change the job of SEOs from merely optimizing for search engines to optimizing for whatever the tech companies built. (If somebody did not see this all coming, you need to hire me, friend.)</p><p>SEOs the world over are now forced to cope with an ignominy: the rise of <em>even </em>more acronyms. For those of you who dislike the alphabet soup that is now our lives, here is a quick glossary:</p><ol><li>SEO: search engine optimization, as if you didn’t know that. Spans optimizing blue links, rich results, whatever the chatbots say, whatever Google summarizes, Google business profiles too</li><li>AEO: whatever Google summarizes</li><li>GEO: whatever the chatbots say</li><li>SXO: I saw this one on LinkedIn and nearly had an embolism. Search everywhere optimization or search experience optimization. So I guess that’s, SEO+AEO+GEO+internal search? The posters didn’t specify</li><li>(L)LMA(I)O: what my manager called it because he was tired of the acronyms</li></ol><p>I personally think AEO and GEO are sub-disciplines of SEO. That is because of the specific websites I have worked with. Had I worked on different websites, focused on different problem spaces, been on differently-structured teams, I might think that AEO and GEO are NOT in fact sub-disciplines of SEO. Each SEO professional is going to have a different perspective on how they relate to each other based on their unique learnings. Let’s normalize this.</p><p>What is significant is that very few argue that the three are not deeply linked.</p><p>There are also some common risks we see with customers’ usage of AI models for searching. There are few fallback options we as publishers can provide to our users who are on these third-party search surfaces when their searches have undesirable outcomes.</p><p>To add to that, many of us are working rather “blind”.</p><ul><li>Google Search Console data for AI Mode performance is inadequate;</li><li>The AEO and GEO counterpart tools are still only being built;</li><li>The ones that are ready are often quite expensive</li><li>Each new tool comes with its own unique acronyms for all their invented metrics</li></ul><p>And personally, every tool I have used still has a ways to go before they are reliable, established AEO and GEO tools.</p><p>The solution therefore cannot be to wait till tools hit the market. If we are to take matters into our own hands, we have to start mitigating dependence on external search surfaces by building search experiences internally.</p><ul><li>This allows publishers access to richer and more complete data</li><li>It allows SEO+AEO+GEO become a complete lifecycle function, not just a top-of-funnel function</li><li>You get to keep your users within your ecosystem longer</li><li>Creative and product freedom</li></ul><p>If you’re with me so far, the biggest opportunity I see for us in this stack is the creative and product freedom. For a long time, search engines have defined the standard for digital search experiences. But now, you can and should build whatever you think makes sense for your customers.</p><p>And honestly, you could build out all kinds of in-eco search experiences. AI-driven ones, chatbots, RAG engine-powered ones, conversational ones, one-shot document retrieval ones. You could build out different types of search functions on different parts of your ecosystem. And the best part is that you get to build out search experiences based on your org’s unique problem spaces, not just as a templated, document-retrieval search function.</p><blockquote><em>Don’t rely solely on external search surfaces. Build in-ecosystem search experiences directly for your users’ needs.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ff4f88b3300e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>