Tucson Technical SEO Services:
The Foundation Nobody Sees Until It Breaks

Tucson SEO provides technical SEO that ensures Google can actually find, crawl, render, and rank your website - because the best content in the world is worthless if the plumbing behind it is broken.

I am David Cragg. I have been building and fixing websites since before Google launched its first crawler in 1998. My background is in engineering the kind of web infrastructure that Fortune 100 companies needed when MSD2D.com and Lotus411.com were serving thousands of Microsoft and IBM partners-platforms that had to load fast, stay indexed, and scale without falling apart. I sold both of those companies. These days I apply that same obsessive technical discipline to small business websites in Tucson, Oro Valley, Marana, and across Southern Arizona. When a client’s rankings suddenly drop and nobody can figure out why, the answer is almost always buried in the technical layer that their last agency never looked at. That is where I start.

What Is Technical SEO?

Technical SEO is everything that happens between your website and Google’s infrastructure that is not visible to a human visitor. It is the crawlability of your pages - whether Googlebot can reach them. It is the speed at which they load. It is the schema markup that tells Google a page is a local business listing versus a blog post versus an FAQ. It is the canonical tags that prevent duplicate content from splitting your ranking authority across multiple URLs. It is the redirect chains, the XML sitemaps, the robots.txt directives, the HTTPS certificates, the mobile rendering, and the Core Web Vitals scores that Google measures from real Chrome users visiting your site.

Think of it as the plumbing and wiring behind the walls of a house. When it works, nobody notices. When it breaks, everything stops functioning. The Google Search Central documentation explains how Google discovers, crawls, and indexes pages - and every step of that process involves technical requirements that most business owners and even many web designers do not know exist. A beautiful website built by a designer who does not understand technical SEO is a house with great paint and no plumbing.

I have been working with websites since before the phrase “technical SEO” existed. In the mid-1990s at MSD2D.com, we were solving crawlability and indexing problems for thousands of vendor websites across Microsoft and IBM’s partner channels - back when search engines were crude and getting found required understanding how crawler bots navigated HTML at a structural level. The tools have changed enormously since then. The principle has not: if the search engine cannot efficiently find, read, and understand your pages, nothing else matters.

Why Technical SEO Matters More Than Most Agencies Admit

Here is the conversation I have with roughly half of my new clients: “I paid an agency for SEO for a year and my rankings barely moved.” I pull up their site, run a crawl, and within twenty minutes I have found the reason - and it is almost never a content problem. It is a technical problem that the previous agency either did not check, did not understand, or noticed and chose not to fix because the fix required actual work rather than writing another blog post and calling it a deliverable.

The most common pattern: the site has decent content, a reasonable number of pages, maybe even some backlinks - but Google is only indexing half the pages because the other half have canonical conflicts, or the site loads so slowly on mobile that Core Web Vitals are failing, or a WordPress theme update six months ago broke the XML sitemap and nobody noticed, or every image on the site is a 4MB uncompressed PNG that takes eight seconds to load on a phone. Each of these is a real example from a real Tucson business I have audited in the past two years.

Good content on a technically broken site is like putting premium fuel in a car with a flat tire. It does not matter how good the fuel is - the car is not going anywhere. That analogy lands with clients because it is exactly what is happening. And the frustrating part is that most technical fixes are not expensive or time-consuming once someone who knows what they are looking at identifies them. The expensive part is the months of lost rankings that pile up while nobody looks.

Core Web Vitals in 2026: What Just Changed

Google’s March 2026 core update made the biggest change to technical ranking factors since Core Web Vitals were introduced in 2021. Two things happened simultaneously, and both matter for every Tucson business with a website:

The LCP threshold tightened. Largest Contentful Paint - how fast the main content element on your page loads - was reclassified. The “good” threshold dropped from 2.5 seconds to 2.0 seconds. That means sites that were passing LCP last year are now flagged as “needs improvement” if they load between 2.0 and 2.5 seconds. Google’s Web Vitals documentation now reflects this tighter standard, and Search Console reports have updated accordingly. Sites that were sitting comfortably at 2.3 seconds suddenly have a problem they did not have in February.

INP became a primary ranking signal. Interaction to Next Paint - how quickly your site responds when a user clicks, taps, or types - was elevated from a supplementary metric to a primary ranking factor with the same weight as LCP and CLS. The threshold for “good” is under 200 milliseconds, but sites below 150ms see the strongest ranking stability. Sites above 500ms are seeing ranking drops of 2 to 4 positions on competitive queries. INP problems are almost always caused by heavy JavaScript - page builder bloat, unoptimized plugins, and third-party scripts that block the main thread.

Here is the number that should get your attention: only 42% of mobile sites currently pass all three Core Web Vitals. If your site passes, you are ahead of the majority. If it does not, you are in the 58% that Google is actively deprioritizing in its ranking algorithm. Since the majority of Tucson local searches happen on mobile devices, failing mobile CWV means failing the searchers who are most likely to call you.

I check every client site against the current CWV thresholds monthly using field data from the Chrome User Experience Report (CrUX) - the same real-user data Google uses for ranking decisions, not the lab scores from PageSpeed Insights that look scary but do not directly affect rankings. If your site is failing, I identify the specific bottleneck (usually an oversized hero image for LCP, bloated JavaScript for INP, or layout-shifting ads and embeds for CLS) and fix it. Not report it. Fix it.

Crawlability and Indexing: Can Google Actually Find Your Pages?

This is the technical SEO problem that hides in plain sight. You build a beautiful page, you write great content, you publish it - and Google never indexes it. The page exists on your server but not in Google’s search results. It is a tree falling in a forest with nobody around.

Crawlability problems happen when:

• Robots.txt is misconfigured - accidentally blocking Googlebot from crawling important pages or entire directories. I have seen WordPress sites where a developer toggled “Discourage search engines from indexing this site” during staging and nobody unchecked it when the site went live. That single checkbox made the entire site invisible.
• Pages are orphaned - they exist on the server but no internal link points to them, so Googlebot never discovers them during a crawl. If Google’s crawler cannot reach a page by following links from other pages, it may as well not exist.
• Crawl budget is wasted - on large sites with thousands of URLs (product pages, tag archives, paginated blog posts), Google allocates a finite crawl budget. If that budget is spent crawling low-value pages, your important service pages may not get crawled frequently enough to stay competitive.
• XML sitemaps are broken, outdated, or missing - your sitemap is the roadmap you hand Google. If it lists pages that return 404 errors, or omits pages you want indexed, or was last updated in 2023, Google’s crawler is working from a bad map.
• Indexing directives conflict - noindex tags, canonical tags pointing to the wrong URL, and hreflang errors can all tell Google to ignore pages you want ranked. These problems are invisible to anyone who does not read the HTML source.

I check crawlability and indexation status on every site I work on - using Google Search Console’s Coverage and Pages reports, a full site crawl with professional tools, and manual spot-checks of the pages that matter most. If Google is not indexing a page, I find out why and fix the obstruction.

Site Architecture: The Blueprint Google Follows

Site architecture is how your pages are organized and linked to each other. Done well, it creates a logical hierarchy that helps Google understand which pages are most important, how topics relate, and where to distribute ranking authority. Done poorly - or not done at all, which is the default for most Tucson business websites - it leaves Google to figure out a random pile of pages with no clear structure.

The architecture that works for local service businesses is straightforward once you see it. Your homepage links to core service pages. Each service page links to related sub-services, location pages, and supporting blog content. Internal links pass authority from strong pages to weaker ones. A logical URL structure (domain.com/services/plumbing/ rather than domain.com/?p=3847) tells both Google and users what each page is about before they click.

When I build or rebuild a site through our website design service, I plan the architecture before a single page is designed - keyword-mapped, with internal linking paths documented. When I take over an existing site for SEO services, the architecture audit happens in month one and restructuring is prioritized based on which changes will have the most ranking impact. A site with 30 pages and no internal linking structure is leaving an enormous amount of authority on the floor.

Schema Markup: Telling Google What Your Pages Mean

Schema markup is structured data added to your page’s HTML that tells Google explicitly what the content represents. Instead of making Google guess that a page is about a local business, schema markup says: “This is a local business at this address, with this phone number, these hours, these services, and this aggregate rating.” Instead of making Google parse your FAQ section to determine the questions and answers, FAQPage schema presents them in a format Google can read instantly and display as rich results directly in the search listings.

The Google documentation on structured data lays out the technical specs. What matters for you as a business owner is this: schema markup earns you more visible, more clickable search results. FAQ schema can display expandable question-and-answer blocks directly on the search page. LocalBusiness schema feeds your address, phone, and hours into Google’s knowledge panels. Review schema can display star ratings next to your listing. These enhanced appearances take up more screen real estate and attract more clicks - which is the whole point.

Most Tucson business websites I audit have zero schema markup. Not bad schema - none. They are leaving visibility on the table because their web designer either did not know schema existed or did not want to write the JSON-LD. Every site I work on gets, at minimum, LocalBusiness, Service, FAQPage, and BreadcrumbList schema. If the site has reviews, products, or how-to content, those get schema too.

Site Speed: The Tiebreaker You Keep Losing

Let me be precise about what site speed does and does not do for your rankings, because the SEO industry has over-hyped this topic while simultaneously under-delivering on fixes.

Site speed is not the most important ranking factor. Content quality, relevance, and backlinks still outweigh it. But site speed is a baseline filter and tiebreaker. When two pages have similar content quality and authority, the faster one wins. In local search, you often find yourself in that tiebreaker scenario, competing against other Tucson businesses that offer the same services in the same area. You are not competing against Wikipedia or WebMD - you are competing against the other three plumbers in Oro Valley, and the one with the faster site gets the edge.

The practical fixes that move the needle for most small business websites are not exotic:

• Image optimization - compress, resize, serve in modern formats (WebP or AVIF), and lazy-load images below the fold. Oversized images are the number-one LCP killer on the sites I audit. A 4MB hero image that takes 6 seconds to load will tank your CWV by itself.
• JavaScript cleanup - remove unused plugins, defer non-critical scripts, and minimize main-thread blocking. This is the primary INP fix. WordPress sites with 20+ active plugins are almost always failing INP because each plugin adds JavaScript that competes for the browser’s attention.
• Hosting quality - a $4/month shared hosting plan running on an overloaded server will never pass Core Web Vitals consistently. Server response time (Time to First Byte) is the floor beneath everything else. If TTFB is slow, no amount of front-end optimization can compensate.
• Caching and CDN - proper browser caching, server-side caching, and a content delivery network reduce load times for repeat visitors and distribute your content closer to the user geographically.
• Render-blocking resource elimination - CSS and JavaScript files that block the initial page render need to be deferred, inlined, or loaded asynchronously so the visible content appears first.

I measure speed using real field data from CrUX and Search Console - not just lab scores from PageSpeed Insights. Lab scores are useful for diagnostics but do not directly drive rankings. Google ranks you based on what real users on real devices actually experience, measured over a 28-day rolling window. That distinction matters, and it is one most agencies do not explain clearly.

The Technical Problems I Find Most Often in Tucson

After auditing hundreds of small business websites over the past decade, the same problems show up again and again. Here is what I fix most frequently for Tucson clients, roughly in order of how often I encounter them:

• No schema markup at all. Probably 80% of the Tucson business sites I audit have zero structured data. This is the easiest technical win available - it costs nothing but time to implement and immediately makes your search listings more competitive.
• Oversized, unoptimized images. A designer uploads full-resolution photos from a DSLR, the CMS does not compress them, and every page loads a 3-5MB image that murders your LCP score. I see this on almost every WordPress site built by a designer who does not do SEO.
• Plugin bloat on WordPress. Twenty, thirty, sometimes forty active plugins - each adding JavaScript, CSS, and database queries. The site loads slowly because it is doing the work of forty applications on every page view. I audit the plugin list, remove what is not needed, and replace heavy plugins with lightweight alternatives.
• Broken redirect chains. Page A redirects to Page B, which redirects to Page C, which redirects to Page D. Each hop adds latency and wastes crawl budget. These accumulate over years of site updates and URL changes and nobody cleans them up.
• Canonical tag conflicts. The canonical tag says one URL is the “real” version, but the sitemap lists a different URL, and the internal links point to a third variation. Google sees three versions of the same page and splits authority between them instead of consolidating it.
• Missing or broken XML sitemaps. The sitemap was auto-generated by a plugin three years ago, never updated, and now lists pages that return 404 errors while omitting the 15 new pages published since.
• Mixed HTTP/HTTPS content. The site runs on HTTPS, but some internal links, images, or scripts still reference HTTP URLs. This triggers mixed-content warnings and can affect how Google treats the page’s security status.
• Thin or duplicate title tags and meta descriptions. Half the pages on the site use the same boilerplate title tag because nobody customized them, so Google has no way to distinguish what each page is about.

Every one of these is fixable. Most of them are fixable in a single work session. The problem is not that the fixes are hard - it is that nobody looked.

How I Handle Technical SEO

1. Full Technical Audit (Month One)

I run a complete crawl of your site, review Search Console data, check Core Web Vitals field data, audit schema, test mobile rendering, and document every technical issue with its priority level and expected ranking impact. This is not a $5,000 standalone report - it is included in the first month of service. By the end of month one, you have a clear picture of your technical health and the fixes are already underway.

2. Critical Fixes First

Crawlability blockers, indexing errors, and Core Web Vitals failures get fixed immediately because they suppress everything else. If Google cannot crawl your pages or your site fails CWV, no amount of content or link building will compensate. I prioritize ruthlessly - highest-impact fixes first, cosmetic issues later.

3. Schema Implementation

LocalBusiness, Service, FAQPage, and BreadcrumbList schema go on every site I work on. If you have reviews, products, or how-to content, those get schema too. Implementation is in JSON-LD format following Schema.org specifications and validated with Google’s Rich Results Test before going live.

4. Speed Optimization

Image compression and format conversion, JavaScript cleanup, plugin audit, caching configuration, and hosting evaluation. The goal is passing all three Core Web Vitals in field data - not just hitting a green score in a lab test - because field data is what Google uses for rankings.

5. Architecture and Internal Linking

I restructure internal links to pass authority where it matters, fix orphaned pages, consolidate duplicate content, and ensure the site hierarchy matches the keyword strategy. This is the technical work that amplifies the content I produce through the monthly content service.

6. Monthly Monitoring

Technical SEO is not a one-time fix. I check crawl health, indexation status, Core Web Vitals, and new errors monthly. WordPress updates, plugin changes, and Google algorithm shifts can create new problems at any time. Catching them in the monthly check prevents the slow bleed of rankings that happens when nobody is watching.

Technical SEO vs. On-Page SEO: What Is the Difference?

Factor	Technical SEO	On-Page SEO
What it covers	Crawlability, indexing, speed, Core Web Vitals, schema, redirects, sitemaps, HTTPS, mobile rendering	Title tags, meta descriptions, headings, content, keywords, internal links, image alt text
Who sees it	Search engine bots and the browser engine - invisible to the average visitor	Both visitors and search engines - the visible content and its markup
Analogy	The plumbing, wiring, and foundation of a house	The furniture, paint, and signage inside the house
What happens if broken	Google cannot find or properly render your pages - rankings are suppressed silently	Google can find your pages but does not rank them because the content does not match search intent
My approach	Audit, fix, implement schema, optimize speed, monitor monthly	Keyword-optimized content, internal linking, title/meta optimization, 3-10 new pages monthly

You need both. Great content on a technically broken site cannot rank. A technically perfect site with no content has nothing to rank for. My $1,000/month service covers both - because separating them into separate line items is how agencies inflate invoices, not how effective SEO works.

Why a 35-Year Veteran Does Technical SEO Differently

Most SEO agencies delegate technical work to a junior developer with a Screaming Frog license and a checklist. The report comes back with 200 issues, the client’s eyes glaze over, and nothing gets fixed. I know this because I have inherited clients from those agencies and seen the “technical audits” they received - thick PDFs with every warning from every tool, no prioritization, and no execution.

My background is different. I started building websites in the 1990s, before CSS existed, when you wrote HTML by hand and understood exactly what the browser - and later the crawler - was doing with your code. I ran platforms that served thousands of vendor microsites for Microsoft and IBM, where a single misconfigured redirect or a broken sitemap could affect hundreds of pages overnight. That experience built an instinct for where technical problems hide and which ones actually affect rankings versus which ones are noise.

When I look at your site, I am not running a tool and forwarding the output. I am reading the crawl data, cross-referencing it with Search Console, checking the source code, testing the real-user experience, and making a judgment call about what matters and what does not. The tool finds 200 issues. I tell you which 8 are actually costing you rankings and I fix them this week. That is the difference between 35 years of experience and a checklist.

One of my clients described the way I work: “Dave does much more than ‘just’ SEO, or at least he does everything even tangentially related to SEO. Not just finding keywords and maximizing them, but rather looking at things at their foundation so we get the best possible results.” That “foundation” is technical SEO. It is where I start with every client, it is what I monitor every month, and it is the reason my clients’ rankings hold steady while competitors who invested only in content see theirs erode when Google updates its algorithm and the technical debt finally catches up.

---

FAQs

What is technical SEO?

Technical SEO covers everything that affects whether Google can crawl, index, and render your website: site speed, Core Web Vitals, crawlability, indexation, mobile rendering, schema markup, redirects, canonical tags, HTTPS, XML sitemaps, and site architecture. It is the infrastructure behind the content - invisible when it works, ranking-killing when it doesn’t.

Why does site speed matter for SEO in 2026?

Google’s March 2026 core update tightened Core Web Vitals thresholds - LCP now needs to be under 2.0 seconds (down from 2.5), and INP is a primary ranking signal. Speed acts as a baseline filter. If two pages have similar content and authority, the faster one wins. Only 42% of mobile sites pass all three CWV - passing puts you in the minority that Google favors.

What are Core Web Vitals?

Three metrics Google uses to measure real-user experience: LCP (how fast the main content loads - under 2.0 seconds), INP (how quickly the page responds to interaction - under 200ms), and CLS (how much the layout shifts during loading - under 0.1). Google measures these from real Chrome users visiting your site, not from lab tests.

How do I know if my site has technical problems?

Google Search Console reports crawl errors, indexing issues, CWV failures, and mobile problems. But it does not catch everything - redirect chains, canonical conflicts, orphaned pages, schema errors, and architecture problems need a full crawl audit to surface. I run that audit in month one of every engagement.

How much does a technical SEO audit cost?

It is included in my $1,000/month service - not a separate charge. Most agencies bill $2,000 to $5,000 for a standalone audit. I include it because technical problems undermine everything else the monthly service builds.

What is schema markup and does my site need it?

Schema is structured data code that tells Google what your content represents - a local business, a service, an FAQ, a review. It earns richer, more clickable search results. Most Tucson business sites have zero schema. Every site I work on gets LocalBusiness, Service, FAQ, and BreadcrumbList schema at minimum.

Can technical problems hurt rankings even if my content is good?

Yes - this is the most common frustration I see. Clients invest in content, rankings stay flat, and the problem is technical: Google cannot crawl half the site, CWV are failing, or canonical conflicts are splitting authority. Good content on a broken foundation cannot perform.

How often should technical SEO be checked?

Monthly. WordPress updates, plugin changes, hosting issues, and Google threshold changes (like the March 2026 CWV update) can create new problems at any time. Monthly monitoring catches issues before they compound into ranking losses.

Do you fix the problems or just report them?

I fix them. If the fix is within the site - speed optimization, schema implementation, redirect cleanup, sitemap corrections - I handle it directly. If it requires server-level changes from your hosting provider, I tell you exactly what to request and verify it is done correctly.

Is technical SEO a one-time fix?

No. Websites are living systems. Plugins update, content is added, hosting environments change, Google updates its requirements. Monthly monitoring is the only way to keep the technical foundation healthy long-term.

What is the difference between technical SEO and on-page SEO?

On-page SEO is about what the page says - titles, content, keywords. Technical SEO is about whether Google can find, load, and understand the page at all. Both are necessary. My service covers both because they are inseparable in practice.

Why should I hire you instead of a bigger agency?

Because I have been doing this since 1990, I have built and sold two internet marketing companies that served Fortune 100 clients, and I do the work myself instead of delegating it to a junior with a checklist. You get a 35-year veteran reading your crawl data - not a PDF from a tool and an invoice. At $1,000/month with no contract, the risk is almost zero. Call (520) 207-6000 and I will show you what your site looks like under the hood.

---

Want to know what is really going on with your website?

Call (520) 207-6000 or request a free consultation. I will pull up your site, check your Core Web Vitals, crawl your pages, and tell you exactly what is holding your rankings back - in plain English, with no jargon and no obligation. I answer my own phone.

---

Categories: Services / Tags: Technical SEO, Core Web Vitals, Site Speed, Schema Markup, Tucson SEO