<?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: Akshansh Verma</title>
    <description>The latest articles on DEV Community by Akshansh Verma (@akshansh53).</description>
    <link>https://dev.to/akshansh53</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%2F3608607%2Fac00ad88-1341-4fcb-b479-60f64222e10d.png</url>
      <title>DEV Community: Akshansh Verma</title>
      <link>https://dev.to/akshansh53</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/akshansh53"/>
    <language>en</language>
    <item>
      <title>How to Prepare to Become a Software Engineer: A Practical Roadmap From Someone Who Took the Long Way</title>
      <dc:creator>Akshansh Verma</dc:creator>
      <pubDate>Sun, 22 Nov 2026 21:51:11 +0000</pubDate>
      <link>https://dev.to/akshansh53/how-to-prepare-to-become-a-software-engineer-a-practical-roadmap-from-someone-who-took-the-long-way-2394</link>
      <guid>https://dev.to/akshansh53/how-to-prepare-to-become-a-software-engineer-a-practical-roadmap-from-someone-who-took-the-long-way-2394</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;This article was drafted with AI assistance and reviewed and edited by me.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F70gov6slmytxjohcp8wl.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F70gov6slmytxjohcp8wl.jpg" alt="Akshansh Verma, software developer, sitting on a lawn and smiling" width="800" height="800"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Akshansh Verma, software developer at Oratrics&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I started poking at code when I was 12, mostly to change how games behaved. It took years, a Bachelor of Computer Applications and a lot of half-finished projects before I got my first job as a software developer at Oratrics in Lucknow.&lt;/p&gt;

&lt;p&gt;Looking back, I wasted time on things that didn't matter and skipped things that did. This is the roadmap I'd give anyone starting today, whether you're in college, switching careers or teaching yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Get the fundamentals right, once
&lt;/h2&gt;

&lt;p&gt;You don't need a computer science degree, but you do need what's in one:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;How a computer runs your code&lt;/strong&gt;: memory, processes, files.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;How the web works&lt;/strong&gt;: HTTP, DNS, what happens when you type a URL and press Enter.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Data structures and algorithms&lt;/strong&gt;: arrays, hash maps, trees, graphs, sorting, and Big-O notation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Databases&lt;/strong&gt;: tables, indexes, joins, and why transactions exist.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Learn these well once. You'll use them for your whole career, long after today's frameworks are gone.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Skip:&lt;/strong&gt; collecting certificates for every topic. One solid understanding beats ten badges.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Pick one language and go deep
&lt;/h2&gt;

&lt;p&gt;Beginners often jump between Python, Java, JavaScript and Go every few weeks. Don't.&lt;/p&gt;

&lt;p&gt;Pick one language that matches where you want to work and stay with it until you can build something real without a tutorial:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;If you want to build…&lt;/th&gt;
&lt;th&gt;Start with&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Websites and web apps&lt;/td&gt;
&lt;td&gt;JavaScript, then TypeScript&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Mobile apps (Android and iOS)&lt;/td&gt;
&lt;td&gt;JavaScript with React Native, or Kotlin / Swift&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Data, automation or AI&lt;/td&gt;
&lt;td&gt;Python&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Large backend systems&lt;/td&gt;
&lt;td&gt;Java, Go or C#&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;For me it was JavaScript. It took me from the browser to the server (Node.js) to mobile apps (React Native) without starting over.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Build projects that can break
&lt;/h2&gt;

&lt;p&gt;To-do apps teach syntax. Projects with real stakes teach engineering.&lt;/p&gt;

&lt;p&gt;A good learning project has:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Users or data that matter&lt;/strong&gt;, even if they're pretend: money, bookings, messages.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authentication&lt;/strong&gt;, so you deal with sessions, tokens and permissions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;A database&lt;/strong&gt; that you design yourself.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;At least one hard part&lt;/strong&gt;: real-time updates, search, payments, file uploads.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Three projects I built while learning:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;EazyPay&lt;/strong&gt;, a digital wallet. It taught me that moving money needs transactions, not hope.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;PropertEase&lt;/strong&gt;, a property listing platform. It taught me that search is a data-modelling problem before it's a UI problem.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Blog Nest&lt;/strong&gt;, a blogging platform with live feedback. It taught me that real-time features fail in ways that are hard to reproduce.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Two or three projects like this say more about you than twenty tutorial clones.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Learn how software fails
&lt;/h2&gt;

&lt;p&gt;Most courses teach how code is supposed to work. Employers pay for people who know how it breaks.&lt;/p&gt;

&lt;p&gt;As a teenager I spent time on web security and bug bounties, finding flaws in websites and reporting them. It changed how I think about code. Before you ship anything, ask: &lt;em&gt;"If I wanted to break this, where would I start?"&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;You can build the same instinct:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Read the &lt;a href="https://owasp.org/www-project-top-ten/" rel="noopener noreferrer"&gt;OWASP Top 10&lt;/a&gt; and try each attack against your own projects.&lt;/li&gt;
&lt;li&gt;Write tests for the unhappy paths: empty input, huge input, double clicks, slow networks.&lt;/li&gt;
&lt;li&gt;Read post-mortems that companies publish after outages.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Work like a team, even when you're alone
&lt;/h2&gt;

&lt;p&gt;Real jobs are collaboration. Practise it early:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Git every day&lt;/strong&gt;: branches, pull requests, meaningful commit messages, resolving merge conflicts.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write a README&lt;/strong&gt; for every project: what it does, how to run it, what you'd improve.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read other people's code.&lt;/strong&gt; Open-source repositories show you how experienced engineers structure real systems.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Contribute something small&lt;/strong&gt; to an open-source project: a bug fix, documentation, a test.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  6. Make yourself findable
&lt;/h2&gt;

&lt;p&gt;Recruiters will search your name before they reply to you. Give them something good to find:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;portfolio site&lt;/strong&gt; with your projects, what you built in each, and how to contact you.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;GitHub profile&lt;/strong&gt; with pinned projects and clear READMEs.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;LinkedIn profile&lt;/strong&gt; that uses the same name, photo and one-line description as everywhere else.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Write about what you learn.&lt;/strong&gt; A short post on a bug you fixed shows more skill than a list of buzzwords.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I wrote a separate guide on making search engines recognise you as one person across all of these: &lt;a href="https://dev.to/akshansh53/how-to-help-google-understand-who-you-are-a-developers-guide-to-person-schema-wikidata-and-16ib"&gt;How to Help Google Understand Who You Are&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Prepare for interviews deliberately
&lt;/h2&gt;

&lt;p&gt;Interviews are a separate skill. Prepare for them on purpose:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Problem solving:&lt;/strong&gt; practise data structure and algorithm problems regularly. Focus on patterns (two pointers, sliding window, BFS/DFS, dynamic programming), not on memorising answers.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Your projects:&lt;/strong&gt; be ready to explain every decision. Why this database? What broke? What would you change?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;System design basics:&lt;/strong&gt; how you'd build a URL shortener or a chat app, with caching, queues and scaling.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Communication:&lt;/strong&gt; think out loud. Interviewers grade your reasoning as much as your answer.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  8. Keep learning after you're hired
&lt;/h2&gt;

&lt;p&gt;Your first job isn't the finish line. It's where learning speeds up.&lt;/p&gt;

&lt;p&gt;Right now I'm moving from full-stack development into AI engineering. The tools are new, but the habits are the same ones from this list: fundamentals, building things that can break, and learning how they fail.&lt;/p&gt;

&lt;h2&gt;
  
  
  A simple 6-month plan
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Months&lt;/th&gt;
&lt;th&gt;Focus&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1–2&lt;/td&gt;
&lt;td&gt;Fundamentals and one language. Small exercises every day.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3–4&lt;/td&gt;
&lt;td&gt;Your first serious project, with authentication and a database. Git and README from day one.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;A second project with one hard feature. A security pass on both.&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Portfolio, profiles, interview practice. Start applying.&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Adjust it to your pace. Consistency matters more than speed.&lt;/p&gt;




&lt;p&gt;If you're preparing right now, tell me in the comments where you're stuck.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Akshansh Verma is a software developer at Oratrics in Lucknow, India, building full-stack web and React Native applications and moving into AI engineering. Find him at sde-akshanshverma.vercel.app and on &lt;a href="https://github.com/Akshansh53" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>career</category>
      <category>beginners</category>
      <category>programming</category>
      <category>webdev</category>
    </item>
    <item>
      <title>How to Help Google Understand Who You Are: A Developer's Guide to Person Schema, Wikidata and Knowledge Panels</title>
      <dc:creator>Akshansh Verma</dc:creator>
      <pubDate>Sun, 22 Nov 2026 21:25:49 +0000</pubDate>
      <link>https://dev.to/akshansh53/how-to-help-google-understand-who-you-are-a-developers-guide-to-person-schema-wikidata-and-16ib</link>
      <guid>https://dev.to/akshansh53/how-to-help-google-understand-who-you-are-a-developers-guide-to-person-schema-wikidata-and-16ib</guid>
      <description>&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;This article was drafted with AI assistance and reviewed and edited by me. The steps, code and results are from my own portfolio.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;When someone searches your name, what does Google actually know about you?&lt;/p&gt;

&lt;p&gt;For most developers the honest answer is "a pile of unconnected pages": a GitHub profile, a LinkedIn page, a portfolio on a free subdomain, maybe a Medium account. Each one says something about you, but nothing tells Google they are all the &lt;em&gt;same person&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;In November 2026 I worked on this for my own name. I'm a software developer from Lucknow, India, and my portfolio is a Next.js site that already had basic Person markup. I created a Wikidata item with sourced facts, and a few days later Google started showing a knowledge panel for "Akshansh Verma, Software developer". Then I audited the rest of my setup and found bugs I didn't know I had.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw8z4hxsy2ovpfyr3vgha.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw8z4hxsy2ovpfyr3vgha.jpg" alt="Akshansh Verma, software developer, standing at an Oratrics event" width="800" height="1297"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Akshansh Verma, software developer at Oratrics&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I can't promise the same result for you. Google decides who gets a panel, and it never publishes the rules. But every step here makes it easier for search engines to connect the dots, and most of them also fix real SEO bugs. Here's everything I checked and changed, with code.&lt;/p&gt;
&lt;h2&gt;
  
  
  What a knowledge panel is, and where it gets its data
&lt;/h2&gt;

&lt;p&gt;A knowledge panel is the box on the right of Google's results (or at the top on mobile) that summarises a person, place or thing. It's generated from Google's &lt;strong&gt;Knowledge Graph&lt;/strong&gt;, a database of &lt;em&gt;entities&lt;/em&gt; and the facts that connect them.&lt;/p&gt;

&lt;p&gt;To show a panel for you, Google has to be confident about three things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;You exist as one entity&lt;/strong&gt;, not as five unrelated profiles.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Which pages are about you&lt;/strong&gt;, and which one is your official home.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Facts about you&lt;/strong&gt;, ideally confirmed by sources you don't control.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The steps below map onto those three things.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 1: Pick one page as your "entity home"
&lt;/h2&gt;

&lt;p&gt;Choose one URL that represents you, usually your portfolio homepage, and treat it as the source of truth:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use your full name exactly the same way everywhere ("Akshansh Verma", not "Akshansh V." on one site and a handle on another).&lt;/li&gt;
&lt;li&gt;Write a short &lt;strong&gt;third-person bio&lt;/strong&gt; and reuse it on every profile:
&amp;gt; Akshansh Verma is an Indian software developer based in Lucknow, building full-stack web and React Native applications.&lt;/li&gt;
&lt;li&gt;Use the same headshot on your site, GitHub, LinkedIn and X.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Search engines love consistency. If every profile repeats the same name, photo and one-line description, it's much easier to merge them into one entity.&lt;/p&gt;
&lt;h2&gt;
  
  
  Step 2: Describe yourself with Person structured data
&lt;/h2&gt;

&lt;p&gt;Structured data is JSON-LD in your page that says, in machine-readable form, "this page is about this person, and these other pages are also about them".&lt;/p&gt;

&lt;p&gt;The important parts are:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;@id&lt;/code&gt;&lt;/strong&gt;: a stable identifier for you (I use &lt;code&gt;https://my-site/#person&lt;/code&gt;). Other schema blocks can then point to the same &lt;code&gt;@id&lt;/code&gt; instead of describing a new, separate person.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;sameAs&lt;/code&gt;&lt;/strong&gt;: links to your other profiles. This is the field that ties everything together.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;worksFor&lt;/code&gt; and &lt;code&gt;alumniOf&lt;/code&gt;&lt;/strong&gt; with their own &lt;code&gt;sameAs&lt;/code&gt; links, so Google knows &lt;em&gt;which&lt;/em&gt; organisation you mean.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Here is a trimmed version of the component in my Next.js App Router project:&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;// src/app/components/StructuredData.js&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="no"&gt;PERSON_ID&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;SITE_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="no"&gt;WEBSITE_ID&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s2"&gt;"../lib/site"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nc"&gt;StructuredData&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;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;person&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Person"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;PERSON_ID&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Akshansh Verma"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;givenName&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Akshansh"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;familyName&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Verma"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;description&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
      &lt;span class="s2"&gt;"Akshansh Verma is an Indian software developer based in Lucknow, building full-stack web and React Native applications."&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;SITE_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;jobTitle&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Software Developer"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;worksFor&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Organization"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Oratrics"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://oratrics.com"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;sameAs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://www.wikidata.org/wiki/Q142155242"&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;span class="n"&gt;alumniOf&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"CollegeOrUniversity"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Khwaja Moinuddin Chishti Language University"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;sameAs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://www.wikidata.org/wiki/Q24943422"&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;span class="n"&gt;sameAs&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
      &lt;span class="s2"&gt;"https://www.wikidata.org/wiki/Q142200681"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"https://www.linkedin.com/in/sde-akshansh/"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"https://github.com/Akshansh53"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"https://x.com/SDE_Akshansh"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="s2"&gt;"https://medium.com/@akshanshverma53"&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;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;website&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"WebSite"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;WEBSITE_ID&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Akshansh Verma"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;SITE_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;author&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s2"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;PERSON_ID&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;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="o"&gt;&amp;lt;&amp;gt;&lt;/span&gt;
      &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;script&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"application/ld+json"&lt;/span&gt; &lt;span class="n"&gt;dangerouslySetInnerHTML&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;__html&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;person&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;span class="o"&gt;/&amp;gt;&lt;/span&gt;
      &lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;script&lt;/span&gt; &lt;span class="kd"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"application/ld+json"&lt;/span&gt; &lt;span class="n"&gt;dangerouslySetInnerHTML&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;__html&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;JSON&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;stringify&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;website&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;span class="o"&gt;/&amp;gt;&lt;/span&gt;
    &lt;span class="o"&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;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Two mistakes I fixed in my own schema while doing this:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A fake &lt;code&gt;SearchAction&lt;/code&gt;.&lt;/strong&gt; My &lt;code&gt;WebSite&lt;/code&gt; schema advertised a site search (&lt;code&gt;?q={search_term_string}&lt;/code&gt;) that didn't exist. Don't describe features you don't have.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Spelling drift.&lt;/strong&gt; My schema spelled my university differently from every other source. Small inconsistencies like that make matching harder.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can check your markup with Google's &lt;a href="https://search.google.com/test/rich-results" rel="noopener noreferrer"&gt;Rich Results Test&lt;/a&gt; and the &lt;a href="https://validator.schema.org/" rel="noopener noreferrer"&gt;Schema Markup Validator&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: Make sure crawlers can actually read your site
&lt;/h2&gt;

&lt;p&gt;This was the most embarrassing bug I found. My project had a file at &lt;code&gt;public/robot.txt&lt;/code&gt;. Notice the missing "s". Crawlers request &lt;code&gt;/robots.txt&lt;/code&gt;, so mine returned &lt;strong&gt;404&lt;/strong&gt; the whole time.&lt;/p&gt;

&lt;p&gt;Worse, the file I &lt;em&gt;thought&lt;/em&gt; was protecting my site contained this:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Disallow: /_next/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;In a Next.js app, &lt;code&gt;/_next/&lt;/code&gt; holds your JavaScript, CSS and optimised images (&lt;code&gt;/_next/image&lt;/code&gt;). Blocking it can stop Google from rendering your page properly and from indexing your images, which are exactly what a knowledge panel needs.&lt;/p&gt;

&lt;p&gt;In the App Router you can generate &lt;code&gt;robots.txt&lt;/code&gt; from code, which makes the filename impossible to get wrong:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// src/app/robots.js&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="no"&gt;SITE_URL&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s2"&gt;"./lib/site"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;robots&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;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;userAgent&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"*"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;allow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"/"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;disallow&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"/api/"&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;span class="n"&gt;sitemap&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${SITE_URL}/sitemap.xml`&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;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Step 4: Clean up your sitemap
&lt;/h2&gt;

&lt;p&gt;My old sitemap listed &lt;code&gt;/#about&lt;/code&gt;, &lt;code&gt;/#projects&lt;/code&gt; and &lt;code&gt;/#contact&lt;/code&gt;, with a double slash (&lt;code&gt;//#about&lt;/code&gt;) for good measure. Search engines ignore everything after &lt;code&gt;#&lt;/code&gt;, so those were just the homepage four times.&lt;/p&gt;

&lt;p&gt;Only list real pages. Next.js can also add image entries, which helps Google find your photos:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// src/app/sitemap.js&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="no"&gt;SITE_URL&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s2"&gt;"./lib/site"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;photos&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt; &lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="s2"&gt;"./data/gallery"&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;

&lt;span class="k"&gt;export&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;sitemap&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;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;SITE_URL&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;lastModified&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nb"&gt;Date&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;span class="n"&gt;priority&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&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;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${SITE_URL}/gallery`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="n"&gt;lastModified&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="k"&gt;new&lt;/span&gt; &lt;span class="nb"&gt;Date&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;span class="n"&gt;images&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;photos&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="sb"&gt;`${SITE_URL}${p.src}`&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;span class="p"&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;h2&gt;
  
  
  Step 5: Link your profiles in both directions
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;sameAs&lt;/code&gt; says "these profiles are mine". It's stronger when the profiles agree:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Put your website link in the profile of GitHub, LinkedIn, X and Medium.&lt;/li&gt;
&lt;li&gt;On your own site, mark profile links with &lt;code&gt;rel="me"&lt;/code&gt;:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight jsx"&gt;&lt;code&gt;&lt;span class="o"&gt;&amp;lt;&lt;/span&gt;&lt;span class="n"&gt;a&lt;/span&gt; &lt;span class="n"&gt;href&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"https://github.com/Akshansh53"&lt;/span&gt; &lt;span class="n"&gt;rel&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"me noopener noreferrer"&lt;/span&gt; &lt;span class="n"&gt;target&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s2"&gt;"_blank"&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
  &lt;span class="nc"&gt;GitHub&lt;/span&gt;
&lt;span class="o"&gt;&amp;lt;/&lt;/span&gt;&lt;span class="n"&gt;a&lt;/span&gt;&lt;span class="o"&gt;&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;rel="me"&lt;/code&gt; is a long-standing convention for "this link points to another page about me", and some platforms use it to verify ownership.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: Create a careful, well-referenced Wikidata item
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.wikidata.org/" rel="noopener noreferrer"&gt;Wikidata&lt;/a&gt; is the structured database behind Wikipedia, and it's openly used by search engines and assistants. A Wikidata item for you is one of the clearest machine-readable statements that you exist as an entity.&lt;/p&gt;

&lt;p&gt;Be careful here. Wikidata has a &lt;a href="https://www.wikidata.org/wiki/Wikidata:Notability" rel="noopener noreferrer"&gt;notability policy&lt;/a&gt;. Items that read like self-promotion, or that only cite the subject's own pages, can be deleted. Add only facts you can back up, and add a source to every statement you can.&lt;/p&gt;

&lt;p&gt;The statements that matter most for a person:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Property&lt;/th&gt;
&lt;th&gt;Example&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;instance of&lt;/code&gt; (P31)&lt;/td&gt;
&lt;td&gt;human&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;occupation&lt;/code&gt; (P106)&lt;/td&gt;
&lt;td&gt;software developer&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;employer&lt;/code&gt; (P108)&lt;/td&gt;
&lt;td&gt;the organisation, with a &lt;code&gt;start time&lt;/code&gt; qualifier&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;educated at&lt;/code&gt; (P69)&lt;/td&gt;
&lt;td&gt;the university, with degree and years&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;official website&lt;/code&gt; (P856)&lt;/td&gt;
&lt;td&gt;your entity home&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;GitHub username&lt;/code&gt; (P2037), &lt;code&gt;LinkedIn personal profile ID&lt;/code&gt; (P6634), &lt;code&gt;X username&lt;/code&gt; (P2002)&lt;/td&gt;
&lt;td&gt;your profiles&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;code&gt;image&lt;/code&gt; (P18)&lt;/td&gt;
&lt;td&gt;a freely licensed photo on Wikimedia Commons&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Three things I learned the hard way:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Add "retrieved" (P813) to every reference.&lt;/strong&gt; A reference URL without a date is weaker, and Wikidata's checker flags it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"Retrieved" dates are in UTC.&lt;/strong&gt; I'm in India (UTC+5:30), so late-night edits got "tomorrow's" date, and Wikidata flagged every reference as dated in the future. If you edit after 18:30 IST, use the UTC date.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Run the constraint checker.&lt;/strong&gt; Each statement shows warning icons when something is off. Mine caught an occupation value that wasn't actually an occupation, and a blog URL missing its language qualifier.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 7: Give Google good photos of you
&lt;/h2&gt;

&lt;p&gt;Knowledge panels need an image, and Google prefers photos it can confidently tie to you. I added a &lt;code&gt;/gallery&lt;/code&gt; page with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Descriptive filenames&lt;/strong&gt; like &lt;code&gt;akshansh-verma-speaking-at-oratrics-event.jpg&lt;/code&gt;, not &lt;code&gt;IMG_2041.jpg&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Alt text and visible captions&lt;/strong&gt; that say who is in the photo and where.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;ImageGallery&lt;/code&gt; structured data&lt;/strong&gt; where each &lt;code&gt;ImageObject&lt;/code&gt; is &lt;code&gt;about&lt;/code&gt; the same &lt;code&gt;@id&lt;/code&gt; as my Person schema.
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;gallery&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="s2"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"ImageGallery"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;url&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${SITE_URL}/gallery`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;about&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s2"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;PERSON_ID&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;associatedMedia&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;photos&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="s2"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"ImageObject"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;contentUrl&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sb"&gt;`${SITE_URL}${p.src}`&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;caption&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;caption&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="n"&gt;about&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="s2"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="no"&gt;PERSON_ID&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;span class="p"&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;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;One safety tip: while the page held stock placeholder images, I set it to &lt;code&gt;noindex&lt;/code&gt; and kept it out of the sitemap. You don't want Google associating a stranger's photo with your name.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 8: Find your Knowledge Graph ID once a panel appears
&lt;/h2&gt;

&lt;p&gt;When a panel shows up, Google has given you an ID that looks like &lt;code&gt;/g/11y7f5mzmh&lt;/code&gt;. You can find it in the page source or in the panel's share link (the &lt;code&gt;kgmid=&lt;/code&gt; parameter). Then:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Open &lt;code&gt;https://www.google.com/search?kgmid=/g/...&lt;/code&gt; to confirm it's your panel. This is a stable link to share.&lt;/li&gt;
&lt;li&gt;Add it to your Wikidata item as &lt;strong&gt;Google Knowledge Graph ID (P2671)&lt;/strong&gt;. Don't use the Google search URL as the &lt;em&gt;reference&lt;/em&gt;; Wikidata doesn't allow search-result URLs as sources, and external IDs don't need one.&lt;/li&gt;
&lt;li&gt;Look for &lt;strong&gt;"Claim this knowledge panel"&lt;/strong&gt; at the bottom of the panel. It can take a few weeks to appear for new panels.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What matters more than any of this
&lt;/h2&gt;

&lt;p&gt;Everything above makes you &lt;em&gt;easy to understand&lt;/em&gt;. It doesn't make you &lt;em&gt;notable&lt;/em&gt;. The strongest signal for a knowledge panel, and for keeping your Wikidata item alive, is &lt;strong&gt;independent coverage&lt;/strong&gt;: articles about you, talks listed on event sites, interviews, and results pages that mention your name.&lt;/p&gt;

&lt;p&gt;So after the technical work, the next step is the human one: write, speak, and build things other people write about.&lt;/p&gt;

&lt;h2&gt;
  
  
  Checklist
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;✅ One entity home with a consistent name, photo and third-person bio&lt;/li&gt;
&lt;li&gt;✅ &lt;code&gt;Person&lt;/code&gt; JSON-LD with a stable &lt;code&gt;@id&lt;/code&gt; and a complete &lt;code&gt;sameAs&lt;/code&gt; list&lt;/li&gt;
&lt;li&gt;✅ &lt;code&gt;robots.txt&lt;/code&gt; reachable, and not blocking &lt;code&gt;/_next/&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;✅ Sitemap with real URLs only, plus image entries&lt;/li&gt;
&lt;li&gt;✅ Your website linked from every profile, and &lt;code&gt;rel="me"&lt;/code&gt; on your profile links&lt;/li&gt;
&lt;li&gt;✅ A well-referenced Wikidata item, with retrieved dates in UTC&lt;/li&gt;
&lt;li&gt;✅ A gallery page with descriptive filenames, captions and &lt;code&gt;ImageGallery&lt;/code&gt; schema&lt;/li&gt;
&lt;li&gt;✅ Your Knowledge Graph ID added to Wikidata once you have one&lt;/li&gt;
&lt;/ul&gt;




&lt;p&gt;&lt;em&gt;Akshansh Verma is a software developer at Oratrics in Lucknow, India, building full-stack web and React Native applications and moving into AI engineering. You can find his work at &lt;a href="https://sde-akshanshverma.vercel.app" rel="noopener noreferrer"&gt;sde-akshanshverma.vercel.app&lt;/a&gt; and on &lt;a href="https://github.com/Akshansh53" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

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