Technical SEO Problems That Are Costing You Rankings

Great Content Doesn't Matter If Google Can't Reach It

We've inherited more than one client site where a single leftover line in robots.txt — Disallow: / — was quietly blocking the entire production domain, left over from a staging environment that never got cleaned up. The copy was solid, the design was clean, and none of it mattered, because Google had never been allowed to look at any of it. Technical SEO doesn't get the attention that keyword research or content marketing does, but it's the layer everything else sits on top of. Get it wrong and the best content in the world sits invisible in an index that never sees it.

This is the unglamorous half of SEO & digital marketing: server responses, HTML structure, and the plumbing search engines rely on to find, understand, and rank a page. Here's what we check first on every site we take on, whether we built it ourselves or inherited it from someone else.

Crawling and Indexing Come Before Rankings

If a page isn't indexed, nothing else about it matters — not the keyword targeting, not the backlinks, not the internal links pointing at it. A few things we check on every audit:

• robots.txt — one misplaced disallow rule can block an entire section of a site, or the whole domain. We've seen agencies push a redesign live and forget to remove the disallow rule that was protecting the staging site.
• Noindex tags — these get left on pages after a CMS migration more often than you'd expect, especially on pages that were rebuilt from a staging template.
• XML sitemaps — a sitemap should list exactly the URLs you want indexed, nothing more. Sitemaps padded with old blog URLs, tag archive pages, or parameterized duplicates waste crawl budget and send mixed signals about what actually matters on the site.
• Canonical tags — every page needs one, and it needs to point at itself unless there's a genuine duplicate elsewhere. Self-referencing canonicals that accidentally point at a staging domain or an old URL structure are one of the more common bugs we find on inherited sites.

Google Search Console's URL Inspection tool will tell you, page by page, whether a URL is indexed and why not if it isn't. Run your important pages through it after any site change — a redesign, a CMS migration, a domain move — not just once a year.

Site Speed and Core Web Vitals Still Move Rankings

Page speed is a ranking factor, but more importantly it's a conversion factor — a slow site loses visitors before they ever see your offer. Google's Core Web Vitals measure this directly: how fast the largest visible element loads, how quickly the page responds to input, and whether elements jump around as it loads. You can check your own site's scores against Google's published thresholds at web.dev/vitals.

In practice, the fixes that move the needle most on small business and e-commerce sites are boring: compress and correctly size images, defer JavaScript that isn't needed for the initial render, and cut the number of third-party scripts — chat widgets, marketing pixels, font loaders — stacked on a single page. We've taken sites from a red Core Web Vitals score to green just by removing two unused tracking scripts and switching to a properly sized hero image. This is one of the first things we audit as part of any custom website design engagement, because speed problems tend to compound as a site grows.

Structured Data Gives Google Context It Can't Guess

Schema markup doesn't directly boost rankings, but it tells search engines exactly what they're looking at instead of making them guess from surrounding text — and it's often the difference between a plain blue link and a rich result with stars, hours, or pricing attached. A few examples we implement often:

• LocalBusiness schema with the correct name, address, phone number, and service area, kept identical to what's listed on the Google Business Profile.
• Attorney or LegalService schema for law firm sites, which can support practice-area rich results.
• Restaurant and Menu schema for restaurant sites, which can surface hours, price range, and menu items directly in search.
• Review and Product schema for e-commerce, which is what puts star ratings under a product listing.

Test every schema implementation with Google's Rich Results Test before it ships. Markup that's technically valid JSON-LD but doesn't match what's visibly on the page is a policy violation, not a growth hack — Google can and does ignore or penalize mismatched structured data.

Mobile-First Indexing and JavaScript Rendering

Google indexes the mobile version of a page, full stop. If your mobile site is missing content, navigation links, or metadata that exist on desktop, that's what Google sees — not the desktop version. This trips up sites that still serve a stripped-down “mobile-friendly” experience instead of a genuinely responsive one.

JavaScript-heavy sites add another layer of risk. Google can render client-side JavaScript, but it does so in a second pass, after the initial crawl, and it can time out on slow or complex scripts. Sites built as single-page applications need to make sure critical content — headings, body copy, links — is present in the server-rendered HTML, not injected entirely by client-side JavaScript after load. This is something we design around from day one on any custom web application that also needs to rank, using server-side rendering or static generation for the pages that need search visibility.

Duplicate Content and URL Cleanup

Duplicate and near-duplicate URLs are one of the most common technical issues we find on older sites: the same page reachable at the www and non-www version, with and without a trailing slash, over both HTTP and HTTPS, or with tracking parameters appended. Each variant can get indexed separately, splitting ranking signals across copies of the same page instead of consolidating them onto one.

The fix is almost always the same: pick one canonical version of every URL, 301-redirect every other variant to it, and make sure internal links point at the canonical version directly instead of relying on a redirect chain to get there.

Redirect chains — URL A to B to C — are worth hunting down separately. Each hop adds latency and dilutes the authority passed through the redirect. A quick site crawl with a tool like Screaming Frog will surface chains, orphaned pages, and broken internal links in one pass.

Where to Start

If you only have time to fix one thing this week, run your homepage and two or three key service pages through Search Console's URL Inspection tool and check the Core Web Vitals report. Between crawlability and page speed, that's where most of the visible damage on a site tends to live — and both are fixable without touching a single word of copy. Everything else on this list compounds from there.