Section 1
How Google actually meets your website
Google's own documentation describes search as a three-stage pipeline: crawling, where automated software follows links and sitemaps to discover URLs; indexing, where it renders each page and decides what it is about; and serving, where it ranks indexed pages against queries. Every technical SEO problem is a failure at stage one or two, and those failures are absolute, not gradual. A page Google cannot crawl does not rank lower; it does not exist. A robots.txt line left over from a developer's staging setup can hide your entire services section. The operator translation: before investing another dollar in content, verify the pipeline. Google Search Console, free, and the closest thing to a dashboard for this, shows exactly which of your pages are indexed and why others are not. Most service businesses have never opened it. A useful companion to this piece is [The Technical Foundations of a Website That Sells: Speed, Accessibility, and Trust](/blog/technical-foundations-website-that-sells).
Section 2
The plumbing inventory
The table below is the full inventory of technical SEO plumbing for a typical service-business site, with the symptom that tells you each piece is broken. Two notes. First, sitemaps are hints, not commands, Google's documentation is explicit that submitting one does not guarantee indexing, but missing one makes discovery slower and less reliable, especially for new or restructured sites. Second, schema markup is the piece most operators skip and the one with growing payoff: structured data tells Google, and increasingly, AI answer engines, exactly what your business is, where it operates, and what it offers, in a vocabulary machines parse without guessing. JSON-LD is Google's recommended format, and your developer can add it in an afternoon.
Section 3
Schema: the part that pays twice now
Structured data used to be an SEO garnish, markup that earned star ratings and FAQ dropdowns in results. It now pays a second dividend: answer engines. When a buyer asks an AI assistant for a recommendation, systems that synthesize answers lean on machine-readable signals to identify what a business is, whom it serves, and where. Google's documentation explains that structured data helps it understand page content and the broader entities behind it; the same legibility benefits any machine reading your site. For a service business the priority list is short: Organization or LocalBusiness schema on the homepage, Service schema on each offer page, FAQPage where you genuinely answer questions, and Article on your content. One rule from Google's guidelines is non-negotiable: markup must describe what is visibly on the page. Schema is testimony, not decoration. The thinking here builds on [What Is Conversion-First Web Design? A Plain-English Guide for Founders](/blog/what-is-conversion-first-web-design-a-plain-english-guide-for-founders).
Section 4
The quarterly plumbing check
Technical SEO is not a project with an end date; it is a low-frequency inspection routine, like checking the fire extinguishers. Quarterly, thirty minutes: open Search Console's Pages report and confirm your money pages are indexed and nothing important sits in the excluded list. Search site:yourdomain.com on Google and scan what shows up, and what is missing. Load yourdomain.com/robots.txt and confirm nothing vital is disallowed. Confirm the sitemap is current after any site changes. Run one money page through Google's Rich Results Test to confirm schema still validates. That cadence catches the silent failures, a migration that dropped redirects, a plugin that rewrote robots.txt, months before they show up as a traffic graph sliding downhill. Inside ConvertOS, this checklist is standing infrastructure for every client site; it can be for yours too. To see how this connects to the wider system, read [What Is AI-Driven Lead Generation? A Plain-English Guide for Founders](/blog/what-is-ai-driven-lead-generation-a-plain-english-guide-for-founders).