Technical SEO is a set of pass/fail gates, not optimization knobs. Either your content is crawlable, indexable, and servable or it isn't. For sites under a few hundred pages, getting the basics right takes an afternoon. After that, your time is better spent on content.
There's an entire industry built around making technical SEO feel complicated. Enterprise consultants audit million-page sites where crawl budget, canonical tag conflicts, and URL hierarchy restructuring genuinely move the needle. They publish guides. Those guides get read by people with 30-page sites who then spend weeks optimizing things that don't matter at their scale.
Here's the honest version: Google tells you exactly how its search works, and for small-to-medium sites, most of it is straightforward. Get the foundations right. Then move on to the work that actually affects your rankings — content quality and topical depth.
How Google Search Actually Works
Google operates in three stages. Every technical SEO concept maps to one of these:
Stage 1 — Crawling. Googlebot discovers your pages through links and sitemaps, then downloads them. It renders JavaScript using a recent version of Chrome. If Googlebot can't reach your page due to server errors, robots.txt blocks, network issues, your content doesn't exist to Google. This is the first gate.
Stage 2 — Indexing. Google analyzes your content, determines the canonical version among duplicates, and stores signals like language, country, and usability. Indexing is not guaranteed. Google says explicitly: "low quality content may not be indexed." If your content doesn't pass the quality bar, it stops here regardless of how clean your technical setup is.
Stage 3 — Serving. Hundreds of ranking factors determine what appears for a given query... location, language, device, content quality, freshness, relevance. This is where content strategy and topical authority live. Technical SEO gets you to this stage. Content quality determines what happens here.
"Google doesn't guarantee that it will crawl, index, or serve your page, even if your page follows the Google Search Essentials." That's Google's own words. Technical perfection doesn't guarantee rankings. But technical failure guarantees invisibility.
The Checklist That Actually Matters
Four priorities for sites under a few hundred pages:
1. Crawlability
Can Google find and access your pages?
- Robots.txt: Controls what Googlebot crawls, but does NOT control indexing. A common mistake: using robots.txt to hide pages from search results. That doesn't work. Use the
noindexmeta tag for that. - Sitemaps: Google calls them "a very important way to tell Google which pages are important to your site." Your CMS probably generates one automatically. Make sure it exists and is submitted in Search Console. Especially important for new sites, sites with content that changes frequently, or pages that aren't well-linked internally.
- Internal links: Pages that aren't linked from anywhere on your site are effectively hidden from crawlers. Every page should be reachable through internal navigation.
2. Rendering
Can Google see your content?
- JavaScript rendering: Google renders JavaScript using Chrome. But here's the 2026 problem: most AI agents, the systems that power AI search features, don't execute JavaScript. If your content is loaded entirely via client-side JavaScript, Google might see it, but AI engines might not. This is a growing concern for JS-heavy sites and single-page applications.
- Text over graphics: Google says directly: "Text is still the safest bet to help us understand the content of the page." Content embedded in images, infographics, or PDFs is harder to parse. Put key information in HTML text.
3. Indexing
Is Google storing your content correctly?
- Canonical URLs: When you have duplicate or near-duplicate content, tell Google which version is the canonical one via redirects or
rel="canonical". Google usually figures this out on its own — "don't worry too much about this" is their actual guidance — but setting it explicitly prevents edge cases. - Duplicate content: Having duplicates isn't a spam policy violation. But it wastes crawl resources and can confuse which page should rank. Clean up obvious duplicates. Don't panic about minor ones.
4. Page Experience
Does your site meet the baseline?
- HTTPS: Google recommends it. In 2026, not having HTTPS is a red flag to users and browsers alike. Just amke sure your site uses httpS.
- Mobile-friendly: Over 60% of web traffic is mobile. Google uses a mobile crawler as its default. If your site doesn't work on mobile, you're invisible to the majority of searches.
- Core Web Vitals: Loading speed, interactivity, visual stability. Google confirms CWV is used by ranking systems — but also says "trying to get a perfect score just for SEO reasons may not be the best use of your time." Get to "good." Don't obsess over "perfect."
- No intrusive interstitials: Full-screen popups that block content on mobile trigger penalties. Cookie banners and age verification are exempt.
Structured Data: Where Technical Meets Content
Schema.org markup helps Google understand your content structure and can earn rich results: review stars, FAQ accordions, recipe cards, how-to steps. These make your search listing stand out visually, which improves click-through rates.
Structured data also helps AI systems interpret your content. As search becomes more AI-driven, schema bridges the gap between your content and how machines parse it. It's a "two birds, one stone" investment; traditional SEO benefit plus AI visibility benefit.
Google provides free tools (Structured Data Markup Helper, Rich Results Test) to implement and validate schema. For most sites, adding FAQ, Article, or HowTo schema to relevant pages is a 15-minute task per page.
What About AI Crawler Access?
A newer concern: AI companies (Anthropic, OpenAI, Google) use separate crawlers to access your content for training and AI-generated responses. You can control access via robots.txt — but blocking a crawler means that AI system may not cite your content in its responses.
This is a business decision, not a technical one. If AI visibility matters to your strategy, ensure your robots.txt allows the major AI crawlers. If you'd rather your content not be used for AI training, you can block them, but you lose AI citation potential.
What This Means for You
If you have a small site (under 100 pages): spend one afternoon on this checklist. HTTPS, mobile, sitemaps submitted, no robots.txt mistakes, decent page speed. Then forget about technical SEO and focus on content.
If your SEO tool flags 847 "issues": most of them are warnings, not problems. An imperfect canonical tag on a page that gets 3 visits per month doesn't matter. Prioritize issues that affect crawling and indexing of your important pages. Ignore the rest.
If you're on a JavaScript-heavy framework: this is the one technical SEO concern worth real investment. Server-side rendering or static generation ensures both Google and AI systems can read your content. Client-side-only rendering is a growing risk.