How to Find and Fix Technical SEO Issues on Your Business Website

Last Updated November 19, 2026 in SEO

Author: Nate McCallister
How to find and fix technical SEO issues on your business website

Imagine a small cleaning company owner who has just rewritten her main service page. It opens on her laptop and phone, and the contact form works. Yet the page does not show up when she searches its exact headline, and a customer says the link on an old flyer now leads to an error page.

Technical SEO is how you investigate that gap between a page that works in a browser and one that search engines and customers can actually reach. The symptom alone does not reveal the cause. The page might be excluded on purpose, blocked by a setting, waiting to be recrawled or simply ranking poorly for reasons that have nothing to do with code.

This find, fix and verify workflow is for owners who handle basic website edits and occasionally hire a developer. Each check covers what to inspect, how to correct it, how to confirm the fix and when to ask for help.

Build a Short Technical SEO Fix List

Technical SEO covers whether search engines can reach and read your pages and whether visitors can use them. Content relevance is a separate question: an accessible page can still rank poorly if it does not answer what people search for. Fixing an access problem removes an obstacle, but it does not guarantee a ranking.

Start with a sample. Check the homepage, main service page, contact page and a recently changed page before you open any sitewide report.

Fix access first. Important pages that search engines or customers cannot reach come before broken journeys, performance scores and cosmetic warnings.

Read the reason behind a status. Google’s Page indexing documentation notes that “Not indexed” is not necessarily bad. Decide whether the affected page should appear in search at all.

Verify every fix. Retest the live page, repeat the check that found the problem and record the result.

Tools. Google Search Console is free and covers monitoring and troubleshooting for your presence in Google Search. PageSpeed Insights handles performance diagnostics. For an optional site crawl, Ahrefs Free (formerly Ahrefs Webmaster Tools) includes 5,000 crawl credits per verified project per month and reports broken internal links. If you are still building your toolkit, this roundup of beginner SEO tools is a useful starting point.

Record findings in a simple tracker with eight columns: URL, symptom, evidence, affected template, priority, owner, change made and retest result. Under evidence, name the report that showed the problem. If several service pages share a fault, check their shared template before editing each page one by one.

Check Whether Google Can Access and Index Important Pages

If a page loads in your browser but does not appear in search, start with the Page indexing report, then run URL Inspection on that page. Thank-you pages and other intentionally excluded URLs belong under “Not indexed,” so focus on the pages you want customers to find.

Crawl access. A robots.txt file tells crawlers which URLs they may fetch. If URL Inspection says a page is blocked by robots.txt, check whether a rule covers that page or its section. Robots.txt controls crawling; it is not a reliable way to remove a page from search results.

Indexing permission. A noindex tag or header tells Google not to include a page. Check your content management system’s visibility settings and any per-page controls. Google must crawl a page to see its noindex instruction, so blocking that URL in robots.txt can hide the instruction. To make a page eligible for indexing, remove the noindex and confirm crawling is allowed.

Sitemap. Check the Sitemaps report for errors, then open the sitemap to confirm it lists your important URLs. Submitting a sitemap is a discovery hint, not a guarantee of crawling or indexing.

Verify. URL Inspection’s indexed view shows what Google saw at its last crawl, while Test live URL checks the page as it is now. A passing live test does not mean the page is indexed or ranked. You can request indexing, but recrawling can take days or weeks and inclusion is never guaranteed.

If your host or content delivery network (CDN) recently added bot protection, a challenge page may be blocking search crawlers. Google’s November 2026 CDN guidance recommends allowing verified bots through CDN and firewall controls, so ask your host to review verified-bot exemptions rather than switching security off.

In the cleaning company example, URL Inspection might show the service page is excluded by a noindex tag left over from drafting. The owner changes the setting, saves and runs Test live URL again. If she cannot find the setting, or an unfamiliar plugin is generating robots.txt rules, it is time to call a developer.

Business owner checking website pages for indexing issues on a laptop

Repair Broken Links and Redirect Dead Ends

A menu item, footer link or old blog post may send visitors to a page that no longer exists. Focus first on internal links that send customers and crawlers to a dead end.

Run a Site Audit crawl in Ahrefs Free, then open the “Page has links to broken page” issue. It lists the referring pages where the links need editing.

Picture a plumbing business that renamed its “Water Heater Repair” URL during a redesign. The old address now returns a 404, but the homepage banner and three blog posts still link to it. Pick the fix that matches what happened:

  • Restore the page if it was deleted by accident and the content still applies.
  • Update the link on each referring page when the content lives at a new URL.
  • Remove the link when the destination is obsolete and no replacement exists.
  • Add a permanent redirect (301 or 308) from the old URL to the new one when the page has moved for good.

In the plumbing example, redirect the old address and update the internal links to point straight to the new page, since direct links beat avoidable redirects. Never send every missing page to the homepage; someone looking for water heater repair needs a relevant destination.

For a law firm website, FirmPilot’s checklist offers a practice-specific way to address the technical issues found during checks of broken links and redirect chains.

Verify by opening the old URL and confirming it loads the restored page or redirects to the right replacement, then recrawl the referring pages. Editing links in content and menus is usually safe to do yourself, but leave server redirect rules and bulk redirects during a redesign to a developer, with a backup and a rollback plan.

Make Duplicate URLs Point to One Preferred Page

Search Console may flag “Duplicate without user-selected canonical” or “Google chose different canonical than user.” You might also spot the same content at two addresses, such as a service URL and a version with a campaign tracking parameter.

Duplicates do not always need fixing. Inspect the clean URL and compare the user-declared canonical with the Google-selected one. If both match your intended page, you may not need to change anything.

A rel=”canonical” tag names your preferred version, and Google treats it as a strong signal that other signals should support. Check the canonical setting in your content management system or SEO plugin and correct any wrong values.

Choose the treatment based on whether the alternate URL should stay live. A campaign URL can keep working while pointing to the preferred page through a canonical tag, while a page that has moved for good needs a permanent redirect. For sitewide choices such as HTTPS and www, agree on one form and have a developer set up redirects from the alternatives.

Then align internal links, canonical tags and sitemap entries with that choice. A sitemap listing the www version while internal links use the bare domain sends mixed signals.

Confirm the Mobile Page Contains Usable Content

A page can look perfect on a desktop while phone users struggle to find the number or read the service description. Google’s mobile-first indexing guidance focuses on the mobile version, so check it directly.

Use two checks together. Open your sample pages on a real phone and follow the customer’s path. Then run Test live URL in Search Console and open the rendered screenshot to see what Google’s renderer actually produced.

What to inspect. Check the service text, navigation, contact button and form. Look for cookie banners, chat widgets or pop-ups that cover content with no obvious way to close them.

Collapsed content. Text in a tab or accordion is not automatically a problem if it is already loaded in the page. The real issue is primary content that only loads after a click, because Google does not perform those interactions. If a “Read more” button has to fetch the main service description, change how that content loads.

Verify. Reload the page on your phone, repeat the journey including a form submission and run a fresh live test. Handle content and setting edits yourself, but ask a developer to change theme code or loading scripts.

Fix the Cause of Poor Performance

If a page loads slowly, responds late to taps or jumps around while loading, check PageSpeed Insights and the Core Web Vitals report in Search Console. Lab data comes from a controlled test, while field data reflects real visitors over time, so review both.

Search Console assesses the 75th percentile over a 28-day window, meaning roughly three out of four measured visits must meet each threshold.

Metric What it measures Good threshold
LCP (Largest Contentful Paint) How quickly the largest visible element appears 2.5 seconds or less
INP (Interaction to Next Paint) How quickly the page responds to interactions 200 milliseconds or less
CLS (Cumulative Layout Shift) How much the layout unexpectedly moves 0.1 or less

Thresholds from Google’s Core Web Vitals guidance (75th percentile of page loads).

A small service site may not have enough real visitor data for field metrics to appear. Missing data does not mean good performance, so lean on lab diagnostics and your own phone tests.

Slow main content. When LCP is poor, identify the slow element first. An oversized hero photo usually needs compressing, resizing or converting to a modern format.

Sluggish interactions. When INP is poor, look at scripts. Chat widgets, booking embeds and tag managers are common culprits. Removing an unused plugin is easy; changing how scripts load needs a developer.

Moving content. When CLS is poor, check for images without set dimensions and embeds that push content around as they load. Adding width and height values often fixes a local issue.

Retest the same page on the same device type after each change. Google uses Core Web Vitals in its ranking systems, but good scores do not guarantee top positions.

Reviewing website performance and Core Web Vitals data on a desktop monitor

Verify Each Fix and Keep a Maintenance Routine

Separate immediate verification from later observation. Right after a change, load the live page, repeat the diagnostic and recrawl any pages whose links you edited. Over the following weeks, check whether the indexed view reflects the change and whether field data improves.

Log the deployment date in your tracker. You can also add a custom annotation to the Search Console performance chart, a feature Google announced in November 2025. An annotation records when something changed; it does not prove the change caused a later rise or fall in clicks.

When you bring in a developer, hand over the affected URLs and shared template, the observed behaviour, your evidence (tool, status and date), the intended outcome, why the page matters and your backup and rollback plan. That saves them repeating your investigation.

A practical routine is a brief monthly look at the Page indexing report and your sample pages, plus a broader quarterly crawl and performance check. Run an extra round after any redesign, theme change or new booking or chat integration, and arrange specialist help before a site migration.

The Situation You receive a certain type of email that requires the

The Situation You want to email a large number of people at

If you’ve ever wondered “What the f*ck is an RSS feed?” you’re

Affiliate Disclosure: Some of the products and services mentioned on this website pay affiliate commissions to the creators at no cost to you. Thank you for your support!