<?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: Artak Harutyunyan</title>
    <description>The latest articles on DEV Community by Artak Harutyunyan (@harutyunyan).</description>
    <link>https://dev.to/harutyunyan</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3808213%2F08b2c623-75c3-4af2-ab79-2c6b2bb4e1e2.jpeg</url>
      <title>DEV Community: Artak Harutyunyan</title>
      <link>https://dev.to/harutyunyan</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/harutyunyan"/>
    <language>en</language>
    <item>
      <title>I Built a Real-Time SEO Linter That Lives Inside Your React App 🔍</title>
      <dc:creator>Artak Harutyunyan</dc:creator>
      <pubDate>Thu, 05 Mar 2026 16:07:46 +0000</pubDate>
      <link>https://dev.to/harutyunyan/-i-built-a-real-time-seo-linter-that-lives-inside-your-react-app-nd5</link>
      <guid>https://dev.to/harutyunyan/-i-built-a-real-time-seo-linter-that-lives-inside-your-react-app-nd5</guid>
      <description>&lt;p&gt;If you've ever deployed a React app only to realize you forgot a meta description, had duplicate &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt; tags, or were missing Open Graph images — this post is for you.&lt;/p&gt;

&lt;p&gt;I just shipped a major update to &lt;strong&gt;&lt;a href="https://github.com/artakharutyunyan/react-seo-analyzer" rel="noopener noreferrer"&gt;react-seo-analyzer&lt;/a&gt;&lt;/strong&gt; — a dev-mode SEO overlay that runs inside your browser as you build. No CLI, no external service, no manual audits.&lt;/p&gt;




&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;Lighthouse is great — but you only run it after you're done building. By then, SEO mistakes are already baked in across multiple components.&lt;/p&gt;

&lt;p&gt;What I wanted was something that behaved more like ESLint for SEO: &lt;strong&gt;instant, inline feedback while I'm coding.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;p&gt;Drop one component into your app:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight jsx"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nx"&gt;SEOAnalyzer&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;react-seo-analyzer&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;App&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="k"&gt;return &lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;&amp;gt;&lt;/span&gt;
      &lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;SEOAnalyzer&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="cm"&gt;/* your app */&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;&amp;lt;/&amp;gt;&lt;/span&gt;
  &lt;span class="p"&gt;);&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A floating panel appears in the corner of your browser with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;📊 An &lt;strong&gt;SEO score out of 100&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;🔴 &lt;strong&gt;Errors&lt;/strong&gt; — things that will hurt your rankings&lt;/li&gt;
&lt;li&gt;🟡 &lt;strong&gt;Warnings&lt;/strong&gt; — things you should fix&lt;/li&gt;
&lt;li&gt;🔵 &lt;strong&gt;Info&lt;/strong&gt; — nice-to-haves&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And it &lt;strong&gt;automatically disappears in production&lt;/strong&gt; (&lt;code&gt;NODE_ENV === 'production'&lt;/code&gt;), so you never ship it accidentally.&lt;/p&gt;




&lt;h2&gt;
  
  
  The 20+ checks it runs
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Errors (–15 pts each)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Missing &lt;code&gt;&amp;lt;title&amp;gt;&lt;/code&gt; tag&lt;/li&gt;
&lt;li&gt;Missing meta description&lt;/li&gt;
&lt;li&gt;No &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt; on the page&lt;/li&gt;
&lt;li&gt;Images without &lt;code&gt;alt&lt;/code&gt; attributes&lt;/li&gt;
&lt;li&gt;Missing viewport meta tag&lt;/li&gt;
&lt;li&gt;Page set to &lt;code&gt;noindex&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Warnings (–5 pts each)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Title too short or too long (ideal: 30–60 chars)&lt;/li&gt;
&lt;li&gt;Meta description out of range (ideal: 120–160 chars)&lt;/li&gt;
&lt;li&gt;Multiple &lt;code&gt;&amp;lt;h1&amp;gt;&lt;/code&gt; tags&lt;/li&gt;
&lt;li&gt;Missing canonical link&lt;/li&gt;
&lt;li&gt;No &lt;code&gt;lang&lt;/code&gt; attribute on &lt;code&gt;&amp;lt;html&amp;gt;&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Missing Open Graph tags (og:title, og:description, og:image)&lt;/li&gt;
&lt;li&gt;External links missing &lt;code&gt;rel="noopener noreferrer"&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Heading hierarchy skips levels&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Info (–1 pt each)&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Missing og:url&lt;/li&gt;
&lt;li&gt;Missing twitter:card / twitter:title&lt;/li&gt;
&lt;li&gt;No JSON-LD structured data&lt;/li&gt;
&lt;li&gt;No favicon&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  It's fully configurable
&lt;/h2&gt;

&lt;p&gt;You can disable specific rules, turn off the overlay (console-only mode), or hook into the results with a callback:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight jsx"&gt;&lt;code&gt;&lt;span class="c1"&gt;// Only console output, no visual overlay&lt;/span&gt;
&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;SEOAnalyzer&lt;/span&gt; &lt;span class="na"&gt;overlay&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="kc"&gt;false&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;

&lt;span class="c1"&gt;// Skip rules you don't care about&lt;/span&gt;
&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;SEOAnalyzer&lt;/span&gt; &lt;span class="na"&gt;disableRules&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;missingStructuredData&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;missingTwitterCard&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;

&lt;span class="c1"&gt;// Pipe results to your own monitoring / reporting&lt;/span&gt;
&lt;span class="p"&gt;&amp;lt;&lt;/span&gt;&lt;span class="nc"&gt;SEOAnalyzer&lt;/span&gt; &lt;span class="na"&gt;onIssues&lt;/span&gt;&lt;span class="p"&gt;=&lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;issues&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;score&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="nx"&gt;analytics&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;track&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;seo_score&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="nx"&gt;score&lt;/span&gt; &lt;span class="p"&gt;})&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt; &lt;span class="p"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Zero dependencies
&lt;/h2&gt;

&lt;p&gt;The whole thing is a single React component with no external dependencies. It works by querying the live DOM after React renders — so it catches dynamic issues too, not just static HTML.&lt;/p&gt;




&lt;h2&gt;
  
  
  Installation
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;npm &lt;span class="nb"&gt;install &lt;/span&gt;react-seo-analyzer
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Why I built this
&lt;/h2&gt;

&lt;p&gt;I kept making the same SEO mistakes on client projects — forgetting og:image, having &lt;code&gt;&amp;lt;h2&amp;gt;&lt;/code&gt; jump straight to &lt;code&gt;&amp;lt;h4&amp;gt;&lt;/code&gt;, images without alt text. Lighthouse was always an afterthought.&lt;/p&gt;

&lt;p&gt;Having a live badge in the corner of my dev environment that turns green when everything is right changed how I think about SEO. It's now part of my build process, not a post-launch checklist.&lt;/p&gt;




&lt;h2&gt;
  
  
  Links
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;📦 &lt;a href="https://www.npmjs.com/package/react-seo-analyzer" rel="noopener noreferrer"&gt;npm&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;⭐ &lt;a href="https://github.com/artakharutyunyan/react-seo-analyzer" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If this is useful to you, a ⭐ on GitHub helps a lot. And if you want a rule that doesn't exist yet, &lt;a href="https://github.com/artakharutyunyan/react-seo-analyzer/issues" rel="noopener noreferrer"&gt;open an issue&lt;/a&gt; — I'm actively developing it.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;What SEO checks do you wish your dev tools caught automatically? Let me know in the comments 👇&lt;/em&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>react</category>
      <category>seo</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
