SEO Basics Every Developer Should Know Before Launching a Website
A practical checklist for developers who want to ship sites that actually get found.
You just finished building a website. The design is clean, the code is solid, it works on all devices. You hand it over to the client.
Three months later, the client calls asking why their website doesn't show up on Google.
This happens all the time. Most developers don't learn SEO — it's not in the curriculum, not in bootcamps, and rarely comes up in interviews. But it directly affects whether the thing you built actually gets found.
This isn't advanced SEO strategy. Just the things that, if you skip them, make an otherwise great website invisible.
1. Title Tags and Meta Descriptions
Every page needs a unique <title> tag and a unique <meta name="description">. Not the same one copy-pasted across every page. Not "Home" or "Welcome."
The title tag is the single most important on-page SEO element — it's the clickable headline in search results. Keep it under 60 characters. Keep the description under 155. Include what the page is actually about.
Five minutes per page. Makes a massive difference.
2. Heading Hierarchy
Your H1 is not a design choice — it's a content signal.
Every page should have exactly one H1. H2s and H3s should follow a logical structure based on meaning, not appearance. Google reads heading structure to understand what a page is about. A page with five H1s sends a confusing signal.
3. Sitemap — Generate It and Submit It
A sitemap lists all the pages on a website. Google uses it to discover and index content.
Generate an XML sitemap and submit it to Google Search Console and Bing Webmaster Tools. Without this, Google might find your pages eventually — or it might not. Don't leave it to chance.
4. robots.txt
The robots.txt file tells search engines which parts of your site to crawl. Most developers either copy-paste a generic one or ignore it entirely.
Check that you're not accidentally blocking important pages. And worth noting: AI crawlers (GPTBot, ClaudeBot, PerplexityBot) also respect robots.txt — if you want the site to appear in AI search results, don't block them.
5. Alt Text on Every Image
Every image needs a descriptive alt attribute. Not "image1.jpg." Not empty. A short description of what the image actually shows.
It affects SEO, accessibility, and provides fallback text if the image fails to load. One line per image. No excuse to skip it.
6. Server-Side Rendering
If you're building with React, Vue, or Angular, pay attention to how content is rendered. Client-side rendering means the page is empty until JavaScript runs — and while Google can usually handle this, it's slower to index and less reliable.
Use SSR or SSG for pages that need to rank. Next.js, Nuxt, and similar frameworks make this straightforward. Don't hand over a fully client-rendered site to a client whose business depends on search traffic.
7. URL Structure
Clean URLs matter. /services/web-design is better than /page?id=42.
Keep URLs lowercase, use hyphens not underscores, avoid dynamic parameters where possible. And never change URLs after launch without setting up proper redirects.
8. Schema Markup
Schema is structured data that tells Google exactly what type of content a page contains — a business, a product, a review, an event. Google uses it to generate rich results in search.
For any local business, implement LocalBusiness schema at minimum: name, address, phone, hours. Use JSON-LD format and test with Google's Rich Results Test.
It's underused and high-impact.
9. Internal Linking
When you build a site's navigation and templates, you're building the internal linking structure. This is how search engines discover and understand the relationship between pages.
Every important page should be reachable within 2–3 clicks from the homepage. Build this into your components from the start — don't leave it for someone else to figure out later.
10. Page Speed
Core Web Vitals affect rankings. A slow website doesn't just frustrate users — it ranks lower.
Minify CSS and JavaScript. Enable compression. Use a CDN. Eliminate render-blocking resources. Test with Google PageSpeed Insights and aim for green on mobile.
This is developer territory. Own it.
11. Analytics and Search Console — Before Launch
Before handing over any website, set up:
- Google Search Console — how the site appears in Google, indexing issues, search queries
- Bing Webmaster Tools — same for Bing and AI-powered search
- Google Analytics (GA4) — actual user behavior on the site
Don't wait for the client to ask. Set it up and hand it over with the site.
Before Every Launch
Run through this before you ship anything:
- Unique title and meta description on every page
- One H1 per page, logical heading hierarchy
- XML sitemap submitted to Google and Bing
- robots.txt reviewed
- All images have alt text
- Content is server-rendered for bots
- Clean URL structure
- Schema markup implemented
- Internal linking makes sense
- Core Web Vitals passing on mobile
- Search Console, Bing Webmaster Tools, and GA4 connected
- Open Graph meta tags for social sharing
None of these take more than a few hours total. All of them directly affect whether the site gets found.
Why It Matters
If you're a freelancer, this makes you more valuable than 90% of developers who just write code and walk away. Clients remember the developer who built a site that actually brings in business.
If you work at an agency, this means fewer "why isn't it ranking?" calls three months after launch.
If there's no dedicated SEO person at your company — this knowledge fills a critical gap.
At ArkSolutions, we build every client project with these fundamentals in from day one — including YallaPlay. It's not extra work. It's part of the job.
If you build websites for a living, SEO isn't someone else's problem. It's yours.