What Is Technical SEO?

Technical SEO is the work of making sure search engines can find and store your pages. Google describes search as crawling, then indexing, then serving results. Technical SEO addresses whatever keeps Google from crawling or indexing your pages, so the content you wrote can compete in the third stage.

Key takeaways

  • A page that is not crawled or not indexed cannot rank, however good the writing is.
  • Google says indexing is not guaranteed, so check which of your pages are in the index.
  • Fix crawl and index blockers first, then duplicate URLs, then speed.
  • Google recommends good Core Web Vitals, and says good scores do not guarantee a top ranking.
  • Technical fixes make pages eligible to rank. Links and content decide how well they rank, as covered in the SEO fundamentals guide.

How Google finds and stores a page

Google’s own documentation says it downloads content from pages with automated programs called crawlers, analyzes the content, and stores it in a large database called the index. When someone searches, it returns the relevant results from that index. The same page adds that “indexing isn’t guaranteed; not every page that Google processes will be indexed.” A page can be crawled and still be left out of the index, and Search Console shows where that happens.

A technical problem can break any step. A blocked URL is never crawled. A page crawled but judged a duplicate may not be indexed. A page that is indexed but slow or broken on a phone can lose the click to a competitor. Audit a site in that order, because a fix at the serving stage does nothing if crawling is failing.

Crawling: can Google reach your pages?

Start by checking whether Google can reach the pages that matter.

Robots.txt. Google describes the file as one that tells crawlers which URLs they can access on your site. The same page says it is not a mechanism for keeping a page out of Google. To keep a page out, use a noindex directive or password protection. A site that blocks a folder in robots.txt and then wonders why the pages still show up in search has mixed up the two jobs.

XML sitemap. Google says a sitemap can improve the crawling of larger or more complex sites, and it names new sites with few external links as a case where one helps. It also says a sitemap does not guarantee that every listed URL will be crawled and indexed. List only the URLs you want indexed, and remove redirects and error pages from the file.

Internal links. Google’s JavaScript documentation says Googlebot parses the response for URLs in the href attribute of HTML links. A menu item that works only through a click script, with no link underneath, gives the crawler nothing to follow. Every page you want found should be reachable through a normal link from another page on the site.

Log files. Server logs show which URLs bots request and how often. On a large site they reveal crawlers spending their visits on parameter URLs and old pages. On a small site, Google Search Console’s crawl and indexing reports usually answer the same question with less work.

Indexing: which version of a page does Google keep?

Duplicate and near-duplicate URLs are a common cause of indexing confusion. Filtered store categories and tracking parameters each produce extra addresses for one page.

Google’s guidance on consolidating duplicate URLs says that when a site has duplicate content, Google chooses the canonical URL. You can state your preference with redirects, a rel=”canonical” link, or a sitemap entry. Google calls redirects and rel=”canonical” strong signals and the sitemap a weak one. It also says none of these is required and that your site will likely do fine without them. That is a useful correction to an old belief that duplicate content brings a penalty. What you lose is control over which address gets shown.

The working rule is to pick one address per page and redirect the alternatives to it. Then check that the canonical tag, internal links and sitemap all point to that same preferred URL.

Two more indexing checks belong on every audit. First, confirm that important pages do not carry a stray noindex tag, which can be left over from a staging site. Second, open the Page indexing report in Google Search Console and read the reasons Google lists for pages it left out.

Rendering: can Google see what a visitor sees?

If your content loads through JavaScript, Google has to run that code before it can read the page. Its documentation says pages are queued for rendering, and a headless Chromium then executes the JavaScript, and the rendered HTML is used for indexing.

Check the rendered version of a key page with the URL Inspection tool in Search Console and confirm that your headings and links appear. If they do not, ask your developer whether the main content can be delivered in the initial HTML.

Speed and Core Web Vitals

Google’s Core Web Vitals page says it highly recommends site owners achieve good Core Web Vitals for success with Search, and that this aligns with what its core ranking systems seek to reward. Google’s page experience documentation (updated September 22, 2026) adds that good scores do not guarantee your pages will rank at the top of results, so treat speed as part of a sound site rather than a shortcut.

The three metrics and their “good” thresholds, as published on web.dev (last updated October 31, 2024):

MetricWhat it measuresGood threshold
Largest Contentful Paint (LCP)How quickly the main content appears2.5 seconds or less
Interaction to Next Paint (INP)How quickly the page responds to taps and clicks200 milliseconds or less
Cumulative Layout Shift (CLS)How much the layout jumps while loading0.1 or less

Google measures at the 75th percentile of page loads, split across mobile and desktop, and a page passes only when all three metrics meet their targets. INP replaced First Input Delay as a Core Web Vitals metric on March 12, 2024, so any report that still lists FID is out of date.

Slow pages are often traced to large image files, heavy plugins or third-party scripts, so test your own pages before guessing. When the cause is the theme or the build itself, the fix is development work, which is what website development covers.

What to check first on a new site

I have done SEO since 2008, and the order of the checks matters more than the tools. A sensible first pass looks like this:

  1. Is the site indexed at all? Search for the domain and check Search Console.
  2. Is anything important blocked by robots.txt or tagged noindex?
  3. Do the homepage and top service pages return a clean 200 status, and does every other version of the address redirect to one preferred version?
  4. Does the sitemap list only the pages worth indexing?
  5. Do the top pages pass Core Web Vitals on mobile?

If those five hold, the work moves to content and links. Fix anything that keeps important pages from being crawled or indexed before you work on anything else. For scale on timing, MBMI Metal Buildings was my first national number one, for “Steel Buildings” and “Metal Buildings”, and it took 12 to 16 months.

Where technical SEO stops

Technical SEO does not replace relevance. A fast, perfectly indexed page with thin content still loses to a better answer. It also does not produce results overnight, because Google has to recrawl and reprocess what you changed.

Technical access also matters for AI search. Engines like ChatGPT and Perplexity cannot cite a page they cannot reach, so a site that blocks crawlers by accident gives up that visibility. Check which AI crawlers your robots.txt file allows.

If you want help with technical work, start with our SEO services, and the ranges are listed on the pricing page.

FAQ

Is technical SEO different from on-page SEO?

The two cover different ground. Technical SEO covers how a site is built and served, from crawling to speed. On-page SEO covers what each page says, such as titles and copy. A page needs both, and the technical layer comes first because content nobody can crawl earns nothing.

Can I do technical SEO myself?

Many checks are free and need no code. Search Console shows indexing status, the URL Inspection tool shows the rendered page, and PageSpeed Insights reports Core Web Vitals. Fixes that touch server settings, redirects or JavaScript usually need a developer, so expect to diagnose yourself and hand off the repairs.

How long do technical fixes take to show results?

Nothing moves until Google recrawls the changed pages, and Google does not publish a schedule for that. A page that was blocked can appear in the index soon after the block is removed. Whether it then ranks depends on competition and content, which usually takes months.

Does duplicate content get my site penalized?

Duplicate URLs are not a penalty trigger. The cost is that Google decides which address appears in results, and it may not pick the one you want. Choose one preferred URL for each page, redirect the others to it, and make every canonical tag agree with that choice.

Do I need an XML sitemap?

It depends on the site. Large sites and brand-new sites gain the most, while a small, well-linked site may be crawled fine without one. Submitting a clean sitemap in Search Console costs little and shows you which listed URLs Google left out.

What does technical SEO cost?

Our monthly SEO pricing runs $1,000 to $1,600, and up to about $3,500 in highly competitive markets. The free AI-visibility audit comes first, then a 15-minute call to talk through what your site needs. Current ranges are listed on the pricing page.

Next step

Start with the Get your free AI-visibility audit page. If you would rather talk through your site first, Book a 15-minute call with Donnie Strompf. Meetings happen by Google Meet or Zoom.