What technical SEO covers
Technical SEO is the work that makes sure search engines can find, crawl, render, understand and index your pages. It does not replace good content or links, but it decides whether that content gets a fair chance. A business site with strong pages and a broken canonical tag, or a slow template, or a sitemap full of redirects, leaves rankings on the table. This technical SEO checklist covers the items we review on every site, in the order that usually produces results fastest.
Use it as an audit. Work through each section with Google Search Console and Bing Webmaster Tools open, plus a crawler that can render JavaScript. Fix the issues that affect the most important pages first.
1. Crawling and indexing basics
- robots.txt: confirm it does not block important sections, CSS or JavaScript files. Block only what should never be crawled, such as admin areas or internal search results.
- noindex tags: search the site for stray noindex directives. They often survive from a staging site after launch.
- HTTP status codes: important pages should return 200. Removed pages should return 404 or 410, or 301 to a genuinely relevant replacement. Avoid redirect chains.
- Soft 404s: "no results" or thin placeholder pages that return 200 waste crawling and can be flagged by Google. Return a real 404 or add real content.
- One version of the site: HTTPS only, and one host. Every variation of http, https, www and non-www should 301 to the canonical version in a single hop.
In Search Console, check the page indexing report. Look closely at "Crawled, currently not indexed" and "Discovered, currently not indexed." Large numbers there usually point to thin, duplicate or low-value pages, or to a site that is hard to crawl efficiently.
2. Canonical tags and duplicate content
Every indexable page should have a self-referencing canonical tag with the absolute, final URL. Duplicates, such as print versions, tracking parameter variants and filtered category pages, should point to the main version. Watch for common mistakes: canonical tags pointing to redirected or noindexed URLs, canonical tags added by JavaScript that disagree with the HTML, and trailing slash inconsistencies between canonicals, internal links and the sitemap.
Pick one URL format and use it everywhere. If your pages end in a slash, every internal link, canonical and sitemap entry should too.
3. XML sitemaps
A sitemap tells search engines which URLs you want indexed. Keep it clean:
- Include only canonical, indexable URLs that return 200.
- Remove redirects, 404s, noindexed pages and parameter URLs.
- Use accurate lastmod dates that change only when content meaningfully changes. Search engines learn to ignore lastmod values that are always "today."
- Split large sites into multiple sitemaps by type, such as pages, products and posts, with a sitemap index.
- Reference the sitemap in robots.txt and submit it in Search Console and Bing Webmaster Tools.
Generate sitemaps automatically from your content source so they never drift. On our own sites, the sitemap is built from the same registry that drives navigation, so a page cannot exist without being listed.
4. IndexNow for faster discovery
IndexNow is an open protocol that lets you notify participating search engines, including Bing and Yandex, the moment a URL is added, updated or deleted. Instead of waiting for a crawler to come back, your site sends a short request with the changed URLs and a key file hosted on your domain proves ownership. Google does not currently use IndexNow, so keep your sitemap and Search Console in good shape as well.
Implementation is simple: generate a key, host the key file at your site root, and send a request whenever content is published or changed. Most modern CMS platforms have a plugin or built-in option, and custom sites can trigger it from the publish or deploy step. Send only URLs that actually changed.
5. Core Web Vitals and page speed
Core Web Vitals are Google's measures of real-user experience. They are a ranking signal, and more importantly they affect whether visitors stay. Google's published thresholds for a "good" experience are:
- Largest Contentful Paint (LCP): 2.5 seconds or less. How fast the main content appears.
- Interaction to Next Paint (INP): 200 milliseconds or less. How quickly the page responds to taps, clicks and typing.
- Cumulative Layout Shift (CLS): 0.1 or less. How much content jumps around while loading.
Use field data from the Chrome User Experience Report in Search Console or PageSpeed Insights, not just lab tests, because field data reflects your actual visitors' devices and networks. Common fixes:
- LCP: serve the hero image in a modern format at the right size, preload it, do not lazy-load it, and cut server response time with caching and a CDN.
- INP: reduce JavaScript. Remove unused scripts, delay third-party tags such as chat widgets and trackers, and break long tasks into smaller pieces.
- CLS: set width and height on images and video, reserve space for ads and embeds, and load web fonts in a way that does not reflow text.
Speed problems are often template problems, so fixing one layout can improve hundreds of pages at once. When the fix needs deeper changes, our frontend development team handles the rendering and bundle work.
6. JavaScript rendering
Search engines can render JavaScript, but rendering costs time and can fail. If key content, links or metadata only exist after client-side JavaScript runs, you are relying on a second, slower processing step. For pages that need to rank, prefer server-side rendering or static generation so the HTML already contains the content. Check rendered HTML with the URL Inspection tool and confirm that titles, canonicals, headings, body text and internal links are all present.
7. Structured data (schema markup)
Structured data in JSON-LD helps search engines understand what a page is about and can make it eligible for rich results. For business sites, the most useful types are usually:
- Organization or LocalBusiness on the home or contact page, with name, logo, address, phone and social profiles.
- Service or Product on offering pages.
- Article or BlogPosting on posts, with author, dates and image.
- BreadcrumbList on all inner pages.
- FAQPage where you genuinely have questions and answers on the page.
Mark up only what is visible on the page, keep it accurate, and validate it with the Rich Results Test and the Schema Markup Validator. Markup that describes content users cannot see breaks Google's guidelines.
8. Crawl budget and site architecture
Crawl budget is roughly how many URLs a search engine is willing and able to crawl on your site in a given time. Small sites rarely need to worry about it. Sites with thousands of URLs, such as e-commerce catalogs, listings and large blogs, do. Waste comes from faceted navigation that produces endless filter combinations, session or tracking parameters, infinite calendars, duplicate pages and long redirect chains.
Control it by blocking low-value parameter patterns in robots.txt, using canonical tags on filtered pages, keeping links to filter combinations out of crawlable HTML where they add no value, and returning fast responses. A quick server makes crawlers willing to fetch more.
Architecture matters too. Important pages should be reachable within a few clicks of the home page, linked from relevant pages with descriptive anchor text, and never orphaned. Check internal links in your crawler and fix any page that has none pointing to it.
9. Mobile, security and international details
- Google indexes the mobile version of your site, so content, links and structured data must be the same on mobile as on desktop.
- Serve everything over HTTPS with no mixed content warnings.
- If you have language or regional versions, use hreflang tags that reference each other correctly.
- Set a clear title tag and meta description on every indexable page, unique and written for the searcher.
How to prioritize what you find
An audit of any real site produces a long list. Do not try to fix everything at once. Sort issues by two questions: how many important pages does this affect, and how badly? A sitewide noindex or a blocked CSS folder is an emergency. A missing alt attribute on one old blog image is not. Fix template-level problems first, because one change improves many pages. Then fix issues on your highest-value pages, such as service, product and location pages. Leave cosmetic warnings from audit tools for last, and ignore the ones that have no real effect on crawling, indexing or users.
10. Monitor after every release
Most technical SEO damage happens during redesigns, migrations and routine deploys. Add checks to your release process: robots.txt and noindex scans, a crawl of key templates, and a look at Search Console coverage a week after launch. For migrations, map every old URL to its new one with a 301 before launch, not after rankings drop.
Technical SEO is the foundation. Once it is solid, content and links do the heavy lifting. If you want a full audit with prioritized fixes, our SEO services team works with businesses in Houston and across the US, and our web development team can implement the fixes directly in your codebase.



