"When I was assigned to the SEO project, I thought: ‘I build features, I fix bugs — why do I need to deal with Google rankings?’
But as I dug deeper into SEO, I began to realize its power — the ability to bring in highly targeted users, improve product visibility, and turn a well-built site into a constant source of organic traffic."
That realization inspired me to put together a brief SEO guide for developers — not full of marketing jargon, but focused on the technical aspects we can directly control.
If you’ve ever wondered how your code can influence search rankings, this guide is for you.
1. Push vs. Pull Marketing — Where SEO Fits
Before we talk about Google, we need to understand how SEO fits into the bigger marketing picture.
Push marketing – You reach out to the audience first (ads, emails, banners).
Users are passive and may have low interest.
Think: unsolicited API calls — you're sending data without a request.Pull marketing – Users come to you because they're searching for something.
Users are active and have high intent.
Think: an API request — they're asking for exactly what they want.
🔹 SEO is pull marketing — you make your site discoverable for people actively searching for answers or products.
2. How Google Search Works
This process has 3 steps.
Step 1 — Crawling
Googlebot (a crawler) visits your site, following links and reading HTML.
- Starts from a known set of URLs (seed list)
- Follows links on each page
- Respects
robots.txt
rules
What is robots.txt
?
robots.txt
is a plain text file placed at the root of your website (e.g., https://example.com/robots.txt
) that gives instructions to search engine crawlers about which pages or directories they are allowed or not allowed to visit.
Step 2 — Indexing
Once content is fetched, Google parses it into a structured format.
- Strips unnecessary markup
- Extracts text, images, structured data (JSON-LD, Microdata, RDFa)
- Stores in a giant index (like a search-optimized database)
Step 3 — Ranking
When a user searches, Google's algorithms match the query to indexed pages, ranking them based on hundreds of signals.
- Relevance to the search query
- Page quality (content depth, trustworthiness)
- User experience (speed, mobile-friendly)
- Authority (backlinks, brand reputation)
🔗 Google Ranking Systems Guide
3. On-Page SEO — Things You Control in Code
These are internal signals Google uses to understand and evaluate your pages.
Metadata
Title Tag
<title>React Performance Optimization Tips | MyDevBlog</title>
- Unique for every page
- ≤60 chars (EN) or ≤31 chars (JP)
- Describes page content accurately
Meta Description
<meta name="description" content="Learn React performance optimization tips for faster rendering and better UX.">
- Affects click-through rates, not direct rankings
- Include relevant keywords naturally
Heading Structure
<h1>React Performance Tips</h1>
<h2>Use Memoization</h2>
<h3>React.memo()</h3>
- One
<h1>
per page - Logical hierarchy
- Helps accessibility and SEO
Internal Linking
Links between related pages help Google discover and rank them
<a href="/react-optimization" title="Learn React Optimization">React Optimization</a>
- Descriptive anchor text > "click here"
Performance & Core Web Vitals
Core Web Vitals Metrics:
- LCP (Largest Contentful Paint) – ≤2.5s
- INP (Interaction to Next Paint) – ≤200ms (replaced FID in March 2024)
- CLS (Cumulative Layout Shift) – ≤0.1
Measurement Tools:
- Lighthouse
- PageSpeed Insights
- Web Vitals JS library
💡 Dev tip: Use next/image
, font-display: swap
, and SSR/SSG to improve scores.
Mobile-First Indexing
Google now uses the mobile version of your site for ranking and indexing.
- Always design mobile-first
- Test with Mobile-Friendly Test
4. Off-Page SEO — How Developers Can Influence It
Off-page SEO measures your site's authority and trust based on external signals.
- Backlinks – Links from other sites act like upvotes
- Citations – Brand mentions without links
Developer-driven link building:
- Publish high-quality API documentation
- Release open-source tools or libraries
- Create technical blog posts with code examples
- Build performance benchmarks or case studies
- Share demo apps that others embed or reference
When you build genuinely useful resources, links come naturally.
🔗 Link Building Best Practices
5. JavaScript SEO — CSR vs SSR
JavaScript-heavy sites face unique SEO challenges.
- CSR (Client-Side Rendering): HTML is almost empty initially; content is rendered in the browser → can delay or block indexing
- SSR (Server-Side Rendering): Full HTML is sent from the server → better for SEO
- SSG (Static Site Generation): HTML built at deploy time → fastest for crawlers
Best practices:
- Use SSR/SSG for key landing pages
- Pre-render or use hybrid rendering for dynamic content
- Test rendered HTML with "View Page Source" and URL Inspection Tool
6. Technical SEO — Under-the-Hood Adjustments
URL Strategy
Good:
/react-performance-tips
Bad:
/blog?id=123&cat=perf
- Lowercase, hyphen-separated words
- Include keywords
- One URL = one piece of content
Use canonical tags for duplicates:
<link rel="canonical" href="https://example.com/react-performance-tips">
robots.txt & Meta Robots
Control crawling:
User-agent: *
Disallow: /private/
Control indexing:
<meta name="robots" content="noindex, nofollow">
Structured Data
JSON-LD format (Google's recommended):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "SEO for Developers",
"author": "Jane Doe",
"datePublished": "2025-08-10"
}
</script>
Benefits:
- Rich snippets (stars, breadcrumbs)
- Better click-through rates
7. Practical SEO Debugging Workflow (Developer Edition)
1. Check Crawlability
- Tool: Google Search Console → Coverage Report
- Verify no essential pages are blocked in robots.txt
2. Fix Technical Errors
- Tool: Screaming Frog SEO Spider
- Identify broken links, wrong status codes, missing metadata
3. Optimize Performance
- Tool: Lighthouse CLI
- Focus on LCP, INP, CLS
4. Add Structured Data
- Tool: Rich Results Test
- Validate JSON-LD implementation
5. Validate Mobile-First
- Tool: Mobile-Friendly Test
- Ensure no content is hidden on mobile that exists on desktop
6. Simulate Googlebot
-
Tool:
curl -A "Googlebot"
or Chrome DevTools network throttling - See how fast and complete initial HTML is
7. Monitor & Iterate
- Tool: Google Search Console → Performance
- Track queries, impressions, CTR, and rankings
Final Thoughts
its important to make your site :
- Discoverable (crawlable, indexable)
- Understandable (structured HTML, clear metadata)
- Valuable (solves the searcher's problem)
As a developer, you have a huge advantage — you can build an SEO-friendly foundation from day one, while others are stuck patching technical debt later.
references
Nishiyama, Y., & Kobayashi, M. (2018). 現場のプロから学ぶ SEO技術バイブル. Maruyama, H. (Ed.). Tankobon Softcover.
Nice one! As a developer, it’s refreshing to see an SEO guide that skips the marketing jargon and dives straight into the technical stuff we can actually control. Your point about building an “SEO-friendly foundation from day one” resonates—avoid the late-stage patch jobs entirely. If you ever want to bring in some outside help, I’ve had good results with InfinityRank.com —they’re practical, clear about what they're doing and why, and actually implement the fixes instead of just talking about them.