You can ship a beautiful site with perfect content and still watch it sink in search. The reason is usually not the copy. It is the code. Googlebot renders pages the way a browser does, and every render-blocking script, missing canonical, or slow server response is a ranking problem before a single word gets read.
Here are the seven code-level issues I check first on any site audit, what they cost you, and how to fix each one.
1. JavaScript that delays rendering
If your content only appears after JavaScript runs, Google has to render the page in a second wave. That costs crawl budget and, on large sites, means some pages never get indexed at all. The fix is boring but effective: server-side render the content that matters, or at least pre-render it. Keep client-side rendering for interactive widgets, not for the article text, product descriptions, or headings you want ranked.
2. Render-blocking CSS and scripts
A 200 KB stylesheet in the head and three synchronous scripts before the body will push your Largest Contentful Paint past the point Google cares about. Inline the critical CSS, defer everything else, and load third-party scripts with async or defer. Measure with PageSpeed Insights before and after — a one-second LCP improvement is often worth more than a month of link building.
3. Missing or wrong canonical tags
Duplicate URLs are everywhere: trailing slashes, UTM parameters, print versions, faceted filters. Without a canonical tag, Google picks one version itself, and it often picks the wrong one. Every page should carry a self-referencing canonical, and every duplicate should point at the version you want indexed. Check this in the rendered DOM, not just the source — a canonical injected by JavaScript after load may never be seen.
4. Broken hreflang
If you serve multiple languages or regions, hreflang is how Google knows which version belongs to which audience. The common mistakes are missing return links (page A points to page B, but B does not point back), wrong language codes, and hreflang on pages that 404. One broken link in the set can invalidate the whole cluster. Validate with a crawler, not by hand.
5. Slow server response (TTFB)
Time to First Byte over 600 ms is a red flag. The usual causes are an overloaded origin server, no caching layer, or a database query running on every request. Add server-side caching, put a CDN in front of static assets, and make sure your hosting can actually handle the crawl rate Google wants to use. A fast server is the cheapest SEO win there is.
6. Images with no dimensions
An image without width and height attributes shifts the layout as it loads, and that layout shift is measured as Cumulative Layout Shift — a Core Web Vitals metric that feeds directly into rankings. Always declare dimensions, serve modern formats like WebP or AVIF, and lazy-load anything below the fold. This is a ten-minute fix on most codebases and it shows up in the scores immediately.
7. Structured data errors
Schema markup is how you earn rich results, but invalid JSON-LD is worse than none at all — Google simply ignores the whole block. Validate every template change in the Rich Results Test before deploying, and watch Search Console for structured data errors after each release. The most common breakages are missing required fields after a redesign and prices or dates rendered in the wrong format.
When the audit is bigger than one sprint
These seven checks cover most of what goes wrong at the code level, and a developer can fix all of them without any SEO tooling beyond a crawler and PageSpeed Insights. But on a large site — hundreds of templates, multiple locales, years of accumulated redirects — the audit itself becomes the bottleneck. That is the point where it makes sense to bring in a team that does technical audits full-time. If you want that handled for you, Onyx Growth Labs runs full technical SEO audits and fixes, from crawl and rendering issues through to Core Web Vitals and structured data.
A checklist you can run today
- Fetch a key page as Googlebot and confirm the main content renders without JavaScript.
- Check LCP in PageSpeed Insights and list the render-blocking resources.
- Crawl the site and flag pages with missing, duplicate, or conflicting canonicals.
- Validate hreflang return links across every language version.
- Measure TTFB on your five most important pages.
- Confirm every image has width and height attributes.
- Run your structured data through the Rich Results Test after every deploy.
Do those seven checks once a quarter and most technical SEO problems never get the chance to become ranking problems.
Top comments (0)