Technical SEO Best Practices for Better Google Search Visibility
A developer's checklist for technical SEO: crawlability, canonical URLs, structured data, Core Web Vitals, internal linking and Search Console monitoring.
Editorial archive: 10 February 2026 · First published on this site
Great content cannot rank if search engines cannot crawl, render and understand it. Technical SEO is the foundation underneath keywords and backlinks: the structure, speed and signals that help Google index the right pages and present them well. As a developer who also handles SEO for clients, this is the checklist I work through on every site.
1. Crawlability: let Google in
- robots.txt should allow important sections and point to your sitemap. Block only genuinely private or duplicate areas.
- XML sitemap should list every canonical, indexable URL with accurate
lastmoddates, and nothing else. - Internal links should reach every important page within a few clicks of the homepage. Orphan pages are hard for Google to discover.
- Status codes matter: return real 404s for missing pages instead of redirecting everything to the homepage, which Google treats as a soft 404.
2. Indexability: tell Google which version counts
The same content often appears at several URLs: with and without www, with tracking parameters, with trailing slashes. Pick one version and enforce it.
- Redirect HTTP to HTTPS and choose one host with permanent (301) redirects.
- Add a self-referencing
<link rel="canonical">on every page. - Use
noindexfor thin pages such as internal search results or test pages. - Keep URL structures stable. Changing URLs without redirects throws away accumulated ranking signals.
3. Rendering: make content visible without JavaScript
Google renders JavaScript, but later and with limits. Important content, links and metadata should be present in the initial HTML. Server-side rendering or static generation is the safest option for public pages — one of the main reasons I discuss in React vs Next.js.
4. On-page signals
Titles and descriptions
Every page needs a unique title (roughly 50–60 characters) and meta description (roughly 140–160 characters) that describe that specific page. Duplicate titles across pages confuse both users and search engines.
Heading hierarchy
Use one H1 that states the page topic, then H2s for sections and H3s for subsections. Headings are structure, not styling; do not skip levels to get a smaller font.
Images
Use descriptive file names, meaningful alt text, modern formats like WebP and explicit width and height to prevent layout shift. Lazy-load images below the fold, but never the main hero image.
5. Structured data
Schema.org markup in JSON-LD helps search engines understand entities and relationships: who wrote an article, which organisation runs a site, how pages fit into a breadcrumb trail. Useful types include:
| Schema type | Use it for |
|---|---|
| Organization / Person | Identity of the business or individual, with sameAs links to official profiles |
| WebSite / WebPage | Site-level information and page context |
| BreadcrumbList | Page hierarchy shown in search results |
| Article / BlogPosting | Author, dates, headline and image for articles |
| Product / Offer | Price and availability in online stores |
| FAQPage | Question-and-answer content that is visible on the page |
Structured data must describe what is actually on the page. Marking up content that users cannot see, or inventing reviews and ratings, can lead to manual actions.
Use consistent @id values so the same person or organisation is recognised across every page. Validate markup with Google's Rich Results Test and the Schema Markup Validator.
6. Core Web Vitals and speed
Google measures real-user experience through three Core Web Vitals:
- Largest Contentful Paint (LCP) — how quickly the main content appears. Aim for under 2.5 seconds.
- Interaction to Next Paint (INP) — how quickly the page responds to input. Aim for under 200 milliseconds.
- Cumulative Layout Shift (CLS) — how much the layout jumps while loading. Aim for under 0.1.
The biggest wins usually come from compressing images, reducing third-party scripts, enabling caching and compression on the server, preloading the hero image and loading fonts without blocking rendering.
7. Mobile-first
Google indexes the mobile version of your site. Content, links and structured data must be equivalent on mobile and desktop. Check tap-target sizes, readable font sizes and that nothing important is hidden on small screens.
8. Site architecture and internal linking
Group related content into clear sections with logical URLs such as /blog/topic-name/. Link from broad pages to specific ones and between related articles using descriptive anchor text. Breadcrumbs help users and reinforce hierarchy for search engines.
9. Monitor with Search Console
Google Search Console is free and essential. Verify the domain, submit the sitemap and check regularly:
- Page indexing reports for excluded or erroring URLs.
- Core Web Vitals reports based on real users.
- Enhancements reports for structured data errors.
- Performance data to see which queries bring impressions and clicks.
10. A launch checklist
- HTTPS and a single canonical host enforced.
- Unique title, description and canonical on every page.
- One H1 and a logical heading order.
- Sitemap submitted; robots.txt reviewed.
- Structured data validated.
- Images optimised with alt text.
- Core Web Vitals checked on mobile.
- Old URLs redirected if anything moved.
Conclusion
Technical SEO does not replace useful content, but it ensures that content gets a fair chance. Most of it is good web development practice applied consistently. If you would like a technical review of your site, see my projects or request an SEO consultation.
