<?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: shanis</title>
    <description>The latest articles on DEV Community by shanis (@shaanis).</description>
    <link>https://dev.to/shaanis</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%2F3967623%2F55a46a3d-ab35-4e0c-a918-1c1b9eff4cea.png</url>
      <title>DEV Community: shanis</title>
      <link>https://dev.to/shaanis</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shaanis"/>
    <language>en</language>
    <item>
      <title>How I Improved My Portfolio SEO by Migrating from React to Next.js</title>
      <dc:creator>shanis</dc:creator>
      <pubDate>Thu, 04 Jun 2026 06:28:44 +0000</pubDate>
      <link>https://dev.to/shaanis/how-i-improved-my-portfolio-seo-by-migrating-from-react-to-nextjs-54lp</link>
      <guid>https://dev.to/shaanis/how-i-improved-my-portfolio-seo-by-migrating-from-react-to-nextjs-54lp</guid>
      <description>&lt;p&gt;**&lt;/p&gt;

&lt;h2&gt;
  
  
  How I Improved My Portfolio SEO by Migrating from React to Next.js
&lt;/h2&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;p&gt;As developers, we often focus heavily on UI design, animations, and performance. However, one important area that many portfolio websites ignore is SEO.&lt;/p&gt;

&lt;p&gt;A few months ago, I decided to migrate my portfolio from React (Vite) to Next.js. My goal wasn't to redesign the website. Instead, I wanted better search engine visibility, improved indexing, and stronger technical SEO.&lt;/p&gt;

&lt;p&gt;In this article, I'll share what I learned during the migration and why Next.js became the better choice for my portfolio.&lt;/p&gt;

&lt;p&gt;The Problem with Traditional React Portfolios&lt;/p&gt;

&lt;p&gt;React is excellent for building modern user interfaces.&lt;/p&gt;

&lt;p&gt;However, many React portfolios rely heavily on client-side rendering.&lt;/p&gt;

&lt;p&gt;This can create several challenges:&lt;/p&gt;

&lt;p&gt;Delayed content rendering&lt;br&gt;
Poor search engine discoverability&lt;br&gt;
Metadata management complexity&lt;br&gt;
Slower indexing of new content&lt;br&gt;
Reduced SEO effectiveness&lt;/p&gt;

&lt;p&gt;While Google can render JavaScript, it often takes additional crawling resources compared to server-rendered content.&lt;/p&gt;

&lt;p&gt;**&lt;/p&gt;
&lt;h2&gt;
  
  
  Why I Chose Next.js
&lt;/h2&gt;

&lt;p&gt;**&lt;/p&gt;

&lt;p&gt;Next.js provides several features that directly benefit SEO.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Server-Side Rendering&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Instead of waiting for JavaScript execution, content can be rendered on the server.&lt;/p&gt;

&lt;p&gt;Benefits:&lt;/p&gt;

&lt;p&gt;Faster content visibility&lt;br&gt;
Better search engine understanding&lt;br&gt;
Improved user experience&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Static Site Generation&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Many pages on my portfolio don't change frequently.&lt;/p&gt;

&lt;p&gt;Using static generation allowed me to:&lt;/p&gt;

&lt;p&gt;Improve loading speed&lt;br&gt;
Reduce server load&lt;br&gt;
Achieve better Core Web Vitals&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Dynamic Metadata&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Each page now generates unique metadata.&lt;/p&gt;

&lt;p&gt;Example:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight typescript"&gt;&lt;code&gt;&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;async&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;generateMetadata&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="na"&gt;title&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Projects | Mohammed Shanis&lt;/span&gt;&lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="na"&gt;description&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="dl"&gt;"&lt;/span&gt;&lt;span class="s2"&gt;Explore MERN stack, React and SaaS projects.&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="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This helps search engines understand page content more effectively.&lt;/p&gt;

&lt;p&gt;SEO Improvements I Implemented&lt;/p&gt;

&lt;p&gt;During migration, I added:&lt;/p&gt;

&lt;p&gt;XML Sitemap&lt;/p&gt;

&lt;p&gt;A sitemap helps search engines discover pages faster.&lt;/p&gt;

&lt;p&gt;Example pages:&lt;/p&gt;

&lt;p&gt;Home&lt;br&gt;
About&lt;br&gt;
Projects&lt;br&gt;
Services&lt;br&gt;
Blog&lt;br&gt;
Individual blog posts&lt;br&gt;
Structured Data&lt;/p&gt;

&lt;p&gt;I implemented:&lt;/p&gt;

&lt;p&gt;Person Schema&lt;br&gt;
Website Schema&lt;br&gt;
BlogPosting Schema&lt;br&gt;
Breadcrumb Schema&lt;/p&gt;

&lt;p&gt;This provides additional context to search engines.&lt;/p&gt;

&lt;p&gt;Canonical URLs&lt;/p&gt;

&lt;p&gt;Canonical URLs help prevent duplicate content issues.&lt;/p&gt;

&lt;p&gt;Better Internal Linking&lt;/p&gt;

&lt;p&gt;I connected:&lt;/p&gt;

&lt;p&gt;Homepage → Blog&lt;br&gt;
Blog → Projects&lt;br&gt;
Projects → Services&lt;/p&gt;

&lt;p&gt;This improved crawlability across the website.&lt;/p&gt;

&lt;p&gt;The Importance of Blogging&lt;/p&gt;

&lt;p&gt;One major lesson I learned:&lt;/p&gt;

&lt;p&gt;SEO is difficult without content.&lt;/p&gt;

&lt;p&gt;A portfolio with only static pages has limited ranking opportunities.&lt;/p&gt;

&lt;p&gt;That's why I started publishing technical articles about:&lt;/p&gt;

&lt;p&gt;React&lt;br&gt;
Next.js&lt;br&gt;
Node.js&lt;br&gt;
MERN Stack&lt;br&gt;
Performance Optimization&lt;br&gt;
UI Development&lt;/p&gt;

&lt;p&gt;Blogging creates additional entry points for search traffic.&lt;/p&gt;

&lt;p&gt;Results After Migration&lt;/p&gt;

&lt;p&gt;After implementing proper SEO fundamentals:&lt;/p&gt;

&lt;p&gt;Pages became easier to discover&lt;br&gt;
Search Console reported improved crawlability&lt;br&gt;
Metadata management became simpler&lt;br&gt;
Website architecture became more scalable&lt;/p&gt;

&lt;p&gt;Most importantly, the website now has a stronger long-term SEO foundation.&lt;/p&gt;

&lt;p&gt;Key Takeaways&lt;/p&gt;

&lt;p&gt;If you're building a portfolio in 2026:&lt;/p&gt;

&lt;p&gt;Don't ignore SEO.&lt;br&gt;
Implement proper metadata.&lt;br&gt;
Generate a sitemap.&lt;br&gt;
Use structured data.&lt;br&gt;
Create technical blog content.&lt;br&gt;
Optimize Core Web Vitals.&lt;br&gt;
Build meaningful internal links.&lt;br&gt;
Final Thoughts&lt;/p&gt;

&lt;p&gt;React remains an excellent frontend library.&lt;/p&gt;

&lt;p&gt;However, when SEO, discoverability, and content marketing become priorities, Next.js provides significant advantages.&lt;/p&gt;

&lt;p&gt;Migrating my portfolio helped me better understand modern web architecture, search engine optimization, and scalable content management.&lt;/p&gt;

&lt;p&gt;If you're interested in modern web development, MERN stack applications, SEO-friendly websites, and performance-focused engineering, you can explore my portfolio here:&lt;/p&gt;

&lt;p&gt;Full Stack Developer Portfolio: &lt;a href="https://shanis.in" rel="noopener noreferrer"&gt;https://shanis.in&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can also read more development articles on my blog:&lt;/p&gt;

&lt;p&gt;Web Development Blog: &lt;a href="https://shanis.in/blog" rel="noopener noreferrer"&gt;https://shanis.in/blog&lt;/a&gt;&lt;/p&gt;

</description>
      <category>nextjs</category>
      <category>webdev</category>
      <category>career</category>
      <category>seo</category>
    </item>
  </channel>
</rss>
