Colorado Technical SEO Checklist

Why the order of checks matters

Technical SEO advice tends to arrive as a flat list of fifty items, which is how small businesses end up shaving 200 milliseconds off a page that Google cannot even index. The checks below run in dependency order. If a page cannot be crawled, nothing about its speed or markup matters. If it can be crawled but not rendered, its content does not exist to the engine. Only after those two are solid does performance and structure start to pay off.

The same order applies to AI answer engines, with one addition: several of them use their own crawlers, so a site can be perfectly healthy in Google and still invisible to ChatGPT search or Perplexity because of one line in robots.txt.

Layer 1: crawling and robots.txt

Start by opening yourdomain.com/robots.txt in a browser. It is a short text file, and it is the most common place we would expect to find an accidental block. Look for three things.

A blanket disallow

Disallow: / under User-agent: * tells every crawler to stay out. It is often left over from a staging site that went live. If you see it, that is the whole problem.

AI crawler rules you did not choose

Some hosting dashboards, CDNs and security plugins offer a one-click "block AI bots" setting. Read what it blocks. OpenAI documents OAI-SearchBot as the crawler for ChatGPT search results and GPTBot as a separate crawler related to training; Perplexity documents PerplexityBot. Blocking training crawlers is a reasonable business decision. Blocking the search crawlers means opting out of those answer engines. Make it a choice, not an accident.

Server errors and redirect chains

Google Search Console's Pages report and Bing Webmaster Tools both show URLs that return errors. Redirects should go straight from the old URL to the final one. A chain like http to https to www to the new slug wastes crawl effort and sometimes breaks.

Layer 2: rendering and indexing

A page that loads its main content through JavaScript after the initial HTML can look fine in your browser and nearly empty to some crawlers. Google renders JavaScript, but on a delay, and not every AI crawler renders it the way a browser does. The safe pattern for a business site is simple: the text that matters (services, location, hours, answers) is in the HTML the server sends.

Then check the gates that decide whether a crawled page is allowed into the index:

• noindex tags. Use Search Console's URL Inspection on your key pages. A stray noindex from a template or plugin is common.
• Canonical tags. Each page should point its canonical at itself unless it is a true duplicate. Location pages that all canonicalize to the home page disappear.
• Snippet controls. nosnippet or a very small max-snippet can keep a page out of Google's AI features. Google's documentation says these controls apply there.
• XML sitemap. Listing only the pages you want indexed, submitted in both Search Console and Bing Webmaster Tools.

Layer 3: speed on real Colorado connections

Google's Core Web Vitals measure three things from real visitors in Chrome: Largest Contentful Paint (how fast the main content appears), Interaction to Next Paint (how quickly the page responds to taps and clicks; it replaced First Input Delay in 2024) and Cumulative Layout Shift (whether things jump around). Search Console reports them per URL group once a site has enough traffic.

For Colorado businesses, the interesting edge case is the mountains. Visitors searching from a trailhead parking lot, a ski lift line or a pass with one bar of signal experience a slow page as a broken page. If your customers are tourists or people on the road, test on a throttled mobile connection, not your office fiber.

Layer 4: structured data and site structure

Structured data (schema.org markup, usually as JSON-LD) restates the facts on a page in a machine-readable form. For a local business, the useful types are Organization or LocalBusiness on the home or contact page, BreadcrumbList for navigation, and FAQPage only where the questions and answers are visible on the page. Google's guidelines are clear that markup must reflect visible content. Markup that claims reviews, prices or hours that are not on the page can get ignored or penalized.

Site structure matters as much as markup. Each service gets its own URL. Pages link to each other with descriptive anchor text ("water heater repair in Lakewood", not "click here"). Headings run in order. These are the things that let an engine, or an AI system lifting a passage, understand where one topic ends and the next begins. The local content guide covers what to put on those pages.

A one-page technical checklist

1. robots.txt allows Googlebot, Bingbot and any AI search crawlers you want to appear in.
2. Site verified in Google Search Console and Bing Webmaster Tools, sitemap submitted to both.
3. No key page returns an error, a redirect chain or a noindex tag.
4. Canonical tags point to the right URL on every page.
5. Main content is present in the server HTML, not injected later.
6. Core Web Vitals pass on mobile, tested on a slow connection.
7. Organization or LocalBusiness markup matches the visible facts and your listings.
8. One URL per service and per real location, linked to each other with descriptive anchors.

Run through this list once and you will know which layer your problems live on. If the list turns up more than you want to fix yourself, ask for the free audit; crawl and indexing basics are part of it. Then make sure your facts agree off-site too, with the listing consistency guide.