10 Technical SEO Issues That Quietly Suppress Rankings (And How to Fix Each)
Most technical SEO issues never announce themselves. Your site loads, your pages look fine, and rankings just sit there. Here are the ten problems that hold small business sites back, with the check and the fix for each.
Key takeaways
- Indexing comes first. A page Google has not indexed cannot rank, however good it is.
- Most damage is accidental. A leftover staging setting costs more traffic than any competitor.
- Diagnose before you fix. Skip the check and you will spend a weekend on something that was never broken.
- Speed is measured on real visitors, not on one test from your office wifi.
- Fix in order of blast radius. A sitewide block costs everything; one slow image costs nothing.
How technical SEO issues suppress rankings without warning
Technical SEO deals with how search engines find, read, and load your pages, not with what those pages say. These problems hide because none of them break your website. What you lose is traffic you never see: the service page Google chose not to index, the location page that duplicates four others, the post nothing links to.
Run a five-minute triage first
Open Google Search Console and go to the page indexing report under the Indexing section. It splits every URL Google knows about into indexed and not indexed, with a reason. If you published 60 pages and 22 are indexed, you have your answer already. Then check your traffic trend using the free options in our guide on how to check website traffic. A cliff on one date almost always means something technical changed that day.
Issue 1: Your pages are not indexed
This is the most common and most expensive of the technical SEO issues. Search Console names a reason for every excluded page, but the labels need translating.
| Search Console reason | What it means | What to do |
|---|---|---|
| Discovered, currently not indexed | Google knows the URL exists but has not crawled it. | Add internal links from pages that rank. Check your sitemap. |
| Crawled, currently not indexed | Google read it and judged it not worth adding. | Expand it, or merge weak pages into one. |
| Duplicate, Google chose different canonical | Google treats another URL as the original. | Point the canonical tag at the URL you want indexed. |
| Excluded by noindex tag | Your site is telling Google to stay out. | See Issue 2. Almost always accidental. |
| Blocked by robots.txt | Crawl rules stop Google before it reads the page. | Remove the rule if unintentional. |
| Soft 404 | Returns success but looks empty. | Add real content, or return a proper 404. |
To check one URL, use the URL Inspection tool. It reports crawl and index status straight from Google’s index and whether the page is eligible to appear in results.
Issue 2: Accidental noindex and robots.txt blocking
A noindex instruction tells search engines not to show a page. Robots.txt is a file at your root domain telling crawlers which paths they may request. Both make sites vanish overnight.
- The WordPress search engine visibility setting. Ticked during the build, never unticked at launch.
- A staging robots.txt pushed to production, carrying one Disallow rule for the whole site.
- SEO plugin defaults that noindex archives, which can catch custom post types you sell from.
- A theme update reintroducing a meta robots tag you removed months ago.
Read yourdomain.com/robots.txt and look for any Disallow line covering more than you expect. Then view the source of an important page and search for “noindex”. If it is there and you did not put it there, remove it.
Tip: Never put noindex and a robots.txt block on the same URL. A noindex rule only works if the page is crawlable, because the crawler has to read the page to see it. Block it in robots.txt and the noindex is invisible, so the URL can still surface from links elsewhere. See Google on blocking indexing.
Not sure which of these is costing you traffic?
We will crawl your site, find the problems suppressing your rankings, and tell you what to fix. Get your free SEO audit.
Issue 3: Duplicate content and missing canonicals
Duplicate content rarely triggers a penalty. It splits your ranking signals across near-identical URLs so none is strong enough to win. A canonical tag is a line of code naming the preferred version of a page. Without one, Google picks.
- Your site resolves at both http and https, or www and non-www, with no redirect to one version.
- Trailing slash and non-slash versions of the same URL both load.
- Location pages built by copy and paste: ten city pages, same 400 words, city name swapped.
Pick one canonical version of your domain and 301 redirect everything else to it. A 301 is a permanent redirect that passes ranking signals through. Then give every page a self-referencing canonical tag. For city pages the answer is different content, not a canonical tag, and our guide to local SEO for small business covers that.
Issue 4: Slow Core Web Vitals
Core Web Vitals are Google’s three measures of real page experience, scored from actual Chrome visitors at the 75th percentile: three out of four visitors need a good experience to pass.
| Metric | What it measures | Google’s “good” threshold | Common cause on small business sites |
|---|---|---|---|
| Largest Contentful Paint (LCP) | Time until the biggest visible element loads | 2.5 seconds or less | A huge uncompressed hero image, or cheap shared hosting |
| Interaction to Next Paint (INP) | How fast the page responds to a tap or click | 200 milliseconds or less | Script pile-up: chat widget, booking tool, pixels, slider |
| Cumulative Layout Shift (CLS) | How much the page jumps while loading | 0.1 or less | Images with no width and height set, or a late-swapping font |
Core Web Vitals optimization without a developer
Use the Core Web Vitals report in Search Console to find which groups of pages fail, then run PageSpeed Insights on one URL from each group. It shows field data from real visitors alongside lab data, with specific opportunities listed. Fix the template, not one page. Three changes do most of the work: compress and correctly size images, remove scripts you no longer use, and add caching. See Google’s Core Web Vitals docs.
Tip: Field data moves slowly because it is a rolling window of real visits. If the report has not budged a week after your fix, that is normal. Confirm with lab data now, then wait for field data before concluding the fix failed.
Issue 5: Broken internal links and redirect chains
Every internal link is a vote and a path, and broken links waste both. A redirect chain, where A sends you to B which sends you to C, wastes crawl time and slows real visitors. Confirm with any technical crawler: Ahrefs Webmaster Tools includes a free Site Audit for domains you verify and flags both. Fix by pointing the source link at the final destination, not by stacking another redirect on top.
Issue 6: A sitemap that lies
An XML sitemap lists the URLs you want indexed. It does not force indexing, it tells Google what you consider important, which is why a wrong one hurts.
- It lists URLs that 404, redirect, or carry noindex, so you are asking Google to index pages you told it to ignore.
- It misses new pages because it was generated once and never regenerated.
- It exceeds the limit. One sitemap file caps at 50,000 URLs or 50MB uncompressed; past that you need a sitemap index file.
Generate it from your CMS so it updates itself, listing only canonical, indexable URLs, then submit it in Search Console and check the status.
Issue 7: Mobile problems you will never see on desktop
Google indexes the mobile version of your site, so the phone experience is what gets ranked. Search Console retired its mobile usability report at the end of 2023, so no single button grades this. Use Lighthouse in Chrome DevTools or PageSpeed Insights on a mobile setting, then open your site on your own phone and try to book an appointment. Watch for crowded tap targets, text that needs zooming, and numbers that are not tap-to-call.
Issue 8: Thin and orphaned pages
A thin page has too little substance to satisfy anyone searching. An orphaned page has no internal links pointing to it, so Google may never find it and visitors certainly will not. Orphans come from bulk imports, old campaign pages, and posts published before your categories existed. Compare the URLs in your sitemap against the pages your crawler reaches by following links: anything in the first list and not the second is orphaned. The fix is a link or a delete.
Issue 9: HTTPS and mixed content
Mixed content is when a secure page loads an insecure resource, usually an image or script with an http address hardcoded into it. Browsers block or warn about these, which breaks layout. Open the browser console and look for mixed content warnings, then fix the hardcoded http references in your database and templates. Confirm every http URL redirects to https, and that your certificate auto-renews. An expired one takes the site down behind a full-screen warning.
Issue 10: Messy URL parameters
Parameters are the bits after a question mark. Filters, sort orders, session IDs, and tracking tags all create them, and each combination is a separate URL to a crawler, so a site with a few filters can generate thousands of near-identical pages. Confirm it in the page indexing report by looking for large numbers of URLs containing question marks. Fix it by making every parameter URL output a canonical tag pointing at the clean version of that page, so Google consolidates them instead of treating each as its own page. Use robots.txt only for parameter paths you want Google to stop crawling entirely, and never on URLs you are relying on a canonical tag for, because a crawler that cannot fetch the page cannot read the canonical. Best of all, configure filters that do not mint a new URL in the first place.
Turn this into a repeatable technical SEO audit
Fixing these once is a project; catching them early is a habit. A technical SEO audit is this list on a schedule, so a plugin update never costs you three months of traffic.
| Issue | Priority | Effort | How you confirm it is fixed |
|---|---|---|---|
| Sitewide noindex or robots.txt block | Critical | Minutes | URL Inspection shows the page as indexable |
| Pages not indexed | Critical | Days to weeks | Indexed count rises in the page indexing report |
| HTTPS or mixed content errors | High | Hours | No console warnings, all http URLs redirect |
| Duplicate content and canonicals | High | Hours to days | One canonical URL per page, duplicates redirect |
| Core Web Vitals failures | Medium | Days | Field data moves into the passing range |
| Broken links, chains, sitemap errors | Medium | Hours | Clean crawl, sitemap counts match reality |
| Thin and orphaned pages | Low | Ongoing | Every page has an internal link |
Run the critical rows monthly and the rest quarterly, and run all of them after a redesign, migration, or hosting change. Our SEO audit checklist is the companion to this article: this page explains each problem and its fix, the checklist tells you what order to check in. For where technical work sits alongside content and links, see SEO services.
Want someone else to find the problems?
Our SEO audit services cover every issue here and hand you a prioritized fix list your developer can act on this week, or get started with a full program.
What are the most common technical SEO issues on small business websites?
Pages that are not indexed, accidental noindex tags left over from a build, duplicate pages with no canonical tag, and slow loading on mobile. Broken internal links and stale sitemaps come next. Nearly all are side effects of a redesign, plugin update, or hosting change.
How do I find technical SEO issues on my website for free?
Start with Google Search Console, which reports indexing status, sitemap errors, and Core Web Vitals for every page Google knows about. Add PageSpeed Insights for speed detail, and Ahrefs Webmaster Tools for a free crawl of any domain you verify.
What is the difference between a technical SEO audit and a full SEO audit?
A full SEO audit covers content quality, keyword targeting, backlinks, and technical health. A technical SEO audit looks only at whether search engines can crawl, index, and render your site, and how fast it is. Technical comes first, because content and links cannot pay off on unindexed pages.
How often should I run a technical SEO checklist?
Check the critical items monthly: indexing counts, robots.txt, and whether an important page has picked up a noindex tag. Work through the full technical SEO audit checklist quarterly, and run everything after a redesign, migration, or hosting move.
Do Core Web Vitals really affect rankings?
They are a ranking signal, but a modest one next to relevance and quality. A fast page will not outrank a genuinely better page. What they affect strongly is conversion, because slow and jumpy pages lose visitors before they read anything.
Why is my page indexed but still not ranking?
Indexing only means Google is willing to show the page. Ranking depends on whether it is the best answer, whether another page on your site competes with it, and whether anything links to it. No impressions at all usually means an unrealistic keyword or a near-duplicate of your own.