<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Faizan e Bahoo Chaudhry</title>
    <description>The latest articles on DEV Community by Faizan e Bahoo Chaudhry (@faizan_ebahoochaudhry_3).</description>
    <link>https://dev.to/faizan_ebahoochaudhry_3</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4037771%2Fb295b2e9-688f-461d-931d-21327535dbc9.jpg</url>
      <title>DEV Community: Faizan e Bahoo Chaudhry</title>
      <link>https://dev.to/faizan_ebahoochaudhry_3</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/faizan_ebahoochaudhry_3"/>
    <language>en</language>
    <item>
      <title>How I Structured SEO for a 20+ Page Indie Site Without Hiring an Agency</title>
      <dc:creator>Faizan e Bahoo Chaudhry</dc:creator>
      <pubDate>Mon, 20 Jul 2026 09:09:44 +0000</pubDate>
      <link>https://dev.to/faizan_ebahoochaudhry_3/how-i-structured-seo-for-a-20-page-indie-site-without-hiring-an-agency-k4</link>
      <guid>https://dev.to/faizan_ebahoochaudhry_3/how-i-structured-seo-for-a-20-page-indie-site-without-hiring-an-agency-k4</guid>
      <description>&lt;p&gt;I've been building &lt;a href="https://www.iambored.blog" rel="noopener noreferrer"&gt;I Am Bored&lt;/a&gt; solo, a small games-and-blog site, and doing all the content strategy and technical SEO myself instead of outsourcing it. This post is the actual architecture I landed on: how the content is clustered, what schema goes where, and how internal linking is structured so the site reads as one coherent thing to Google instead of a pile of disconnected pages. Sharing it mostly because most "SEO for developers" content stays abstract, and I wanted to write something with real, checkable examples instead.&lt;/p&gt;

&lt;h2&gt;
  
  
  The Core Problem With Most Indie Site SEO
&lt;/h2&gt;

&lt;p&gt;Most solo projects end up with a flat pile of pages: a homepage, some feature pages, a blog with no real structure connecting the posts to each other. Each page might individually be fine, but none of them reinforce each other, so Google has no signal that the site has any depth on a given topic. Topical authority isn't really about page count, it's about whether your pages form a legible cluster instead of a scatter plot.&lt;/p&gt;

&lt;p&gt;So before writing anything, I mapped out what the actual content clusters should be, and built every new piece to slot into one of them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cluster 1: Location-Based "Bored At X" Content
&lt;/h2&gt;

&lt;p&gt;The pillar here is &lt;a href="https://www.iambored.blog/blog/things-to-do-when-bored-at-home/" rel="noopener noreferrer"&gt;50 Things to Do When Bored at Home&lt;/a&gt;, and every spoke off it follows the same structural pattern: &lt;a href="https://www.iambored.blog/blog/things-to-do-when-bored-in-class/" rel="noopener noreferrer"&gt;bored in class&lt;/a&gt;, &lt;a href="https://www.iambored.blog/blog/things-to-do-in-the-car-when-bored/" rel="noopener noreferrer"&gt;bored in the car&lt;/a&gt;, &lt;a href="https://www.iambored.blog/blog/things-to-do-when-bored-in-a-waiting-room/" rel="noopener noreferrer"&gt;bored in a waiting room&lt;/a&gt;, &lt;a href="https://www.iambored.blog/blog/things-to-do-when-bored-at-night/" rel="noopener noreferrer"&gt;bored at night&lt;/a&gt;, and &lt;a href="https://www.iambored.blog/blog/bored-on-a-zoom-call/" rel="noopener noreferrer"&gt;bored on a Zoom call&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Each spoke deliberately shares the same shape: split by device availability or environment constraint, one genuinely relevant external citation (not a generic "studies show" link), and a link back to the pillar plus sideways to relevant games. Consistency here matters more than novelty, once a reader (or a crawler) understands the pattern from one post, every other post in the cluster reads as "more of the same trustworthy thing" instead of a one-off.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cluster 2: Party Games and Questions
&lt;/h2&gt;

&lt;p&gt;This is the highest-traffic-ceiling cluster on the whole site: &lt;a href="https://www.iambored.blog/blog/never-have-i-ever-questions/" rel="noopener noreferrer"&gt;150+ Never Have I Ever Questions&lt;/a&gt; and &lt;a href="https://www.iambored.blog/blog/would-you-rather-questions/" rel="noopener noreferrer"&gt;200+ Would You Rather Questions&lt;/a&gt;, both paired with actual working interactive versions of the game embedded on the site, not just static text lists like almost every competing page in this space.&lt;/p&gt;

&lt;p&gt;That pairing is a real structural advantage, not just a content angle. A list-only competitor page and a page with the same list &lt;em&gt;plus a working game&lt;/em&gt; are targeting the same keyword, but they're not really the same product. I built both posts to link to the toy explicitly and repeatedly (contextually, not spammed), since that's the actual differentiator worth reinforcing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cluster 3: Game Strategy Guides
&lt;/h2&gt;

&lt;p&gt;Every strategy post in this cluster links to its game two ways, and vice versa. &lt;a href="https://www.iambored.blog/blog/how-to-beat-2048/" rel="noopener noreferrer"&gt;How to Beat 2048&lt;/a&gt;, &lt;a href="https://www.iambored.blog/blog/whack-a-mole-high-score-tips/" rel="noopener noreferrer"&gt;Whack-a-Mole High Score Tips&lt;/a&gt;, &lt;a href="https://www.iambored.blog/blog/flappy-bird-why-you-keep-dying/" rel="noopener noreferrer"&gt;Flappy Bird: Why You Keep Dying at the Same Pipe&lt;/a&gt;, and &lt;a href="https://www.iambored.blog/blog/how-to-draw-a-perfect-circle/" rel="noopener noreferrer"&gt;How to Draw a Perfect Circle Freehand&lt;/a&gt; all follow this pattern.&lt;/p&gt;

&lt;p&gt;This cluster had the best competition-to-effort ratio of anything I researched. Whack-a-Mole specifically had almost no dedicated strategy content anywhere online when I checked, most competing pages are the game itself with a single throwaway tip. Writing an actual, specific technique breakdown (eye tracking, hand positioning, pacing as difficulty ramps) for a topic with that little existing competition is about as close to a guaranteed foothold as SEO gets.&lt;/p&gt;

&lt;p&gt;One honest note since I want this post to be accurate, not just a highlight reel: I initially assumed a couple of these topics (Flappy Bird tips specifically) had near-zero competition based on general reputation, and when I actually checked live search results, that assumption was wrong, there's real, recently-published competing content there now. Worth actually verifying competition live rather than trusting a topic's older reputation, I got burned by that assumption more than once during this project.&lt;/p&gt;

&lt;h2&gt;
  
  
  Cluster 4: Fiction
&lt;/h2&gt;

&lt;p&gt;Four original short stories live under &lt;code&gt;/blog/fiction/&lt;/code&gt;: &lt;a href="https://www.iambored.blog/blog/fiction/the-stenographers-echo/" rel="noopener noreferrer"&gt;The Stenographer's Echo&lt;/a&gt;, &lt;a href="https://www.iambored.blog/blog/fiction/the-floor-that-isnt-there/" rel="noopener noreferrer"&gt;The Floor That Isn't There&lt;/a&gt;, &lt;a href="https://www.iambored.blog/blog/fiction/the-camera-trap/" rel="noopener noreferrer"&gt;The Camera Trap&lt;/a&gt;, and &lt;a href="https://www.iambored.blog/blog/fiction/the-neighbor-who-waves-first/" rel="noopener noreferrer"&gt;The Neighbor Who Waves First&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;These use a distinct schema type, &lt;code&gt;ShortStory&lt;/code&gt; instead of &lt;code&gt;Article&lt;/code&gt;, which is a small detail but worth doing correctly, it lets Google (and eventually AI answer engines doing direct retrieval) understand these pages as a different content type from the listicles, not just more blog posts competing for the same intent.&lt;/p&gt;

&lt;h2&gt;
  
  
  Schema Strategy, By Content Type
&lt;/h2&gt;

&lt;p&gt;This is the part most "add schema to your site" advice skips: which schema type for which content, and why.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Games&lt;/strong&gt;: &lt;code&gt;Game&lt;/code&gt;/&lt;code&gt;SoftwareApplication&lt;/code&gt; plus &lt;code&gt;FAQPage&lt;/code&gt; for the how-to-play block&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Listicle/informational posts&lt;/strong&gt;: &lt;code&gt;Article&lt;/code&gt; plus &lt;code&gt;FAQPage&lt;/code&gt;, matched word-for-word to the visible FAQ copy (schema and visible content drifting apart is a real, checkable trust signal Google can penalize)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Technique posts with sequential steps&lt;/strong&gt;: &lt;code&gt;Article&lt;/code&gt; plus &lt;code&gt;HowTo&lt;/code&gt;, like the &lt;a href="https://www.iambored.blog/blog/how-to-beat-2048/" rel="noopener noreferrer"&gt;2048 strategy guide&lt;/a&gt;, where the steps genuinely are sequential and benefit from being marked up that way&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fiction&lt;/strong&gt;: &lt;code&gt;ShortStory&lt;/code&gt;, no &lt;code&gt;FAQPage&lt;/code&gt;, since forcing an FAQ onto a piece of fiction breaks the reading experience for no real SEO benefit&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Homepage&lt;/strong&gt;: &lt;code&gt;WebSite&lt;/code&gt; with a &lt;code&gt;SearchAction&lt;/code&gt;, plus a conservative &lt;code&gt;FAQPage&lt;/code&gt; covering only what's genuinely visible on the page
## The Technical Foundation Underneath All of This&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of the content strategy matters if the technical basics are wrong, so briefly, what's actually running under the hood: Astro static output, &lt;code&gt;@astrojs/sitemap&lt;/code&gt; for automatic sitemap generation, canonical tags pointing to the final production domain even while still testing on a preview URL (small thing, saves a real headache during domain migration), and a &lt;code&gt;robots.txt&lt;/code&gt; that's deliberately minimal, allow everything except nothing, since there's no admin panel or checkout flow to hide.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd Tell Past Me
&lt;/h2&gt;

&lt;p&gt;Build the cluster map before writing anything, not after. I wrote a handful of posts early on before I had the cluster structure clear in my head, and went back later to retrofit internal links between them. It worked, but it's meaningfully more effort than just knowing the cluster a post belongs to before you start writing it.&lt;/p&gt;

&lt;p&gt;If you're building something similar solo, the actual takeaway isn't any single tactic here, it's that a pile of good pages and a &lt;em&gt;cluster&lt;/em&gt; of good pages are different products, even when the page-level content quality is identical. The linking structure is the part that's easy to skip and expensive to retrofit.&lt;/p&gt;

</description>
      <category>seo</category>
      <category>gamedev</category>
      <category>boredom</category>
      <category>wecoded</category>
    </item>
  </channel>
</rss>
