The technical SEO work that reliably moves impressions, clicks and conversions comes in a fixed order: crawlability and indexation first, then Core Web Vitals, then structured data, then internal linking and redirects. Each layer only pays off once the one beneath it works. Cosmetic tasks like rewriting meta keywords or chasing a perfect audit score rarely change a single number in Search Console.
Technical SEO is the work that makes a site easy for search engines to find, render, understand and rank, separate from the words on the page. Content and links decide whether you deserve to rank. The technical layer decides whether Google can see that you do.
Can Google actually crawl and index the pages that make you money?
Often not all of them, and that is the first thing to check. A page that is not in the index earns zero impressions, so no other fix matters until your service and location pages are indexed.
Start with the Page indexing report in Search Console. Google is clear that you should not expect every URL on your site to be indexed, so the goal is not 100%. The goal is that every page you would pay to rank is in, and the “Crawled, currently not indexed” list holds only pages you do not care about.
Three checks cover most problems:
- The sitemap lists only real, canonical URLs. A single sitemap is capped at 50,000 URLs or 50MB uncompressed, and Google ignores priority and changefreq. It does use lastmod, but only when the date is accurate. A sitemap that stamps today’s date on every page teaches Google to ignore it.
- robots.txt manages crawling, not indexing. Google says robots.txt is not a mechanism for keeping a page out of Google. Use noindex for that. Staging rules left on a live site can block whole folders of service pages.
- No orphan pages. If nothing links to a page, crawlers struggle to find it and treat it as unimportant.
Do Core Web Vitals really affect search results?
Yes, as part of page experience, though they are not a magic ranking lever. Google says it highly recommends good Core Web Vitals for success with Search and that they align with what its core ranking systems reward.
The targets are specific, and they are measured on real visits, not on your laptop:
- Largest Contentful Paint (loading): 2.5 seconds or less at the 75th percentile of page loads, split by mobile and desktop.
- Interaction to Next Paint (responsiveness): 200 milliseconds or less is good, above 500 milliseconds is poor, again at the 75th percentile.
- Cumulative Layout Shift (visual stability): a score of 0.1 or less at the 75th percentile.
The 75th percentile matters. It means three out of four real visits must hit the target. A fast office connection hides the slow phone on a job site, which is exactly where a homeowner searches for a plumber.
Serve a properly sized hero image, reserve space for images and embeds so the layout does not jump, and cut the third-party scripts that block the main thread. On older WordPress builds, the cleanest fix is sometimes a rebuild, which I cover in the WordPress to Next.js migration playbook.
Is structured data worth adding to a small business site?
Yes, because it changes how your result looks, and that changes clicks. Structured data does not lift rankings on its own, but it can make a listing eligible for richer display.
Google’s own case studies are the clearest evidence. Rotten Tomatoes measured a 25% higher click-through rate on pages with structured data, and Nestlé saw an 82% higher click-through rate on pages shown as rich results. Google recommends JSON-LD, and its structured data guidelines say markup enables a feature but does not guarantee it will appear.
For a service business, the useful set is short: Organization or LocalBusiness with an exact name, address and phone, BreadcrumbList, Article on blog posts, and FAQPage where the content is a genuine FAQ. Mark up what is visible on the page and nothing else.
How do internal links and redirects protect the traffic you already have?
Internal links tell Google which pages matter, and redirects carry earned signals across URL changes. Get either wrong and you leak traffic you already paid for.
On internal links, Google’s rule is simple: it can only follow a link that is an a element with an href, and every page you care about should have a link from at least one other page. Anchor text should be descriptive and relevant. “Emergency drain cleaning in Austin” tells Google far more than “click here.”
Redirects matter most during a redesign or platform move. Google recommends a permanent server-side redirect whenever possible, and treats a 301 or 308 target as the canonical URL. For a site move, Google says to keep redirects for generally at least 1 year, redirect straight to the final destination, and keep any chain to ideally no more than 3 hops, and always fewer than 5.
How do I prioritize technical SEO work for a client site?
I run every audit through a four-step order I call Reach, Render, Read, Route. Each step is a gate, and I do not spend budget on a later step while an earlier one is failing.
| Step | Question it answers | Typical fix | Effort | What it moves |
|---|---|---|---|---|
| Reach | Can Google find and index the money pages? | Clean sitemap, fix robots.txt and noindex, link orphans | Low | Impressions |
| Render | Do real visitors get a fast, stable page? | Image sizing, layout space, script cuts | Medium to high | Rankings, conversions |
| Read | Does Google understand what the page is? | JSON-LD for business, breadcrumbs, articles | Low | Click-through rate |
| Route | Do links and redirects send signals to the right place? | Descriptive internal links, one-hop permanent (301/308) redirects | Low to medium | Retained traffic |
| Cosmetic busywork | Does the audit tool turn green? | Meta keywords, chasing 100/100 scores | Varies | Rarely anything |
I have delivered 350+ projects over 8+ years leading teams. Sites I build launch with Lighthouse scores of 90+, and my peak organic-traffic lift is 136%. On SLIQ client and internal sites, domain authority is up 9 points, session duration 117% and organic traffic 42%.
A common pattern: strong service pages sit in “Discovered, currently not indexed” because the navigation is script-driven, so Google finds no real links to them. Swapping in plain links fixes the Reach step, and only then can page speed work show up in the numbers.
If you want this run on your site, my SEO service starts with exactly this audit, and the SEO portfolio shows the results. Speed fixes that need code usually fold into web design and development, and ongoing monitoring sits under web care and delivery. To check whether the fixes turn into leads, connect the work to marketing and analytics tracking.
Frequently asked questions
How long does technical SEO take to show results?
It depends on which layer you fix. Indexation fixes can show up within weeks, because Google only needs to recrawl the affected pages and add them to the index. Core Web Vitals take longer to register, since Google reports them from real visits collected over a rolling window, so even a perfect fix needs time to fill the data. Structured data can change how a result looks as soon as the page is recrawled. Redirect work is defensive: success often looks like nothing happening, because traffic simply does not drop after a launch. Track each change with a dated note in Search Console so you can match cause to effect later.
Is a 100 Lighthouse score necessary to rank?
No. Lighthouse is a lab test run on one simulated device, while Google’s page experience signals come from field data at the 75th percentile of real visits. A page can score 100 in the lab and still fail for real users on slow phones, or score in the 80s and pass comfortably in the field. Aim for the field thresholds first: LCP within 2.5 seconds, INP within 200 milliseconds and CLS of 0.1 or less. Once those pass, extra lab points rarely change rankings. The time is usually better spent on indexation, internal links or content, where the return is easier to measure in clicks.
Can I do technical SEO myself on WordPress?
Partly. A WordPress owner can submit a sitemap, check the Page indexing report, fix obvious noindex mistakes and add internal links between related pages without touching code. Plugins also handle basic structured data. The harder parts are performance and architecture. Heavy themes, page builders and stacked plugins often make Core Web Vitals hard to pass, and no setting fixes that. If you have done the basics and speed still fails, read about building a CMS your team will actually use before deciding whether to optimize the current site or rebuild on a faster stack.
What is the difference between technical SEO and on-page SEO?
Technical work makes a site crawlable, fast, understandable and correctly linked. On-page work makes each page relevant to a search: the title, headings, copy, images and the questions the page answers. They depend on each other. Brilliant copy on a page Google never indexes earns nothing, and a perfectly engineered site with thin pages has nothing worth ranking. In practice, I fix the technical gates first because they are finite and measurable, then put ongoing effort into content. Security is part of that foundation too, since a hacked site can be flagged in results, which is why cybersecurity and hardening sits close to SEO work.
Where should you start this week?
Open Search Console, check which money pages are not indexed, and fix that before anything else. Then look at your Core Web Vitals report on mobile.
If you would rather have someone run the full Reach, Render, Read, Route audit for you, see the case studies, read more about how I work, and get in touch to talk through your site.
I do this work as a web design and SEO expert in Jacksonville, and the same audit applies to smaller local markets nearby. For a coastal business, see SEO in St. Augustine, or browse the full list of areas I serve in the footer.