Technical SEO for Non-Technical Founders
Technical SEO is unglamorous but unforgiving. A single accidental noindex tag can wipe out months of content investment, and broken Core Web Vitals quietly suppress rankings without ever showing up in your analytics. This guide explains the technical fundamentals in plain English — what each lever does, why it matters, and exactly how to verify it.
Technical SEO is mostly about getting out of Google's way. Five fundamentals — crawlability, indexing, sitemaps, canonicals, and Core Web Vitals — cover 90% of the problems most sites face. Audit them quarterly, ship template-level fixes, and your content can do its job.
Key takeaways
- robots.txt and accidental noindex are the most common silent killers
- Sitemaps should list every indexable URL and exclude utility pages
- Canonical tags prevent duplicate-content cannibalization
- Core Web Vitals (LCP, INP, CLS) are pass/fail thresholds, not gradients
- Most technical issues are template-level — fix once, fix everywhere
- Quarterly audits are sufficient for most sites; weekly for high-velocity ones
Crawlability: can Google reach your pages?
Google's crawler (Googlebot) discovers pages by following links and reading your sitemap. If a page isn't linked from anywhere and isn't in your sitemap, it won't be crawled. Check that every important page is reachable from at least one indexed page.
robots.txt: the most dangerous file on your site
One accidental `Disallow: /` line blocks every crawler from your entire site. Audit robots.txt after every deploy. The file lives at yourdomain.com/robots.txt — it should explicitly allow important paths and block only utility paths (e.g., admin, search, API endpoints).
Indexing: can Google add your pages to its index?
Even a crawled page won't rank if it's not indexed. Common blockers: a meta robots noindex tag (often shipped accidentally from staging), a canonical pointing to a different URL, or low content quality. Use Google Search Console's URL Inspection tool to verify any specific page.
Sitemaps: the canonical list of what you want indexed
Your sitemap.xml should list every URL you want in Google's index — and nothing else. Include lastmod dates so Google knows when content changed. Submit the sitemap in Google Search Console and watch for indexation issues.
Canonical tags: preventing duplicate content cannibalization
Every page should have a `<link rel='canonical'>` tag pointing to itself (or to the canonical version if it's a variant). Common bugs: canonicals pointing to the homepage on every page, or canonicals from the old domain after a migration.
Core Web Vitals: the speed thresholds Google enforces
Three metrics matter: LCP under 2.5s (largest visible element loads quickly), INP under 200ms (page responds to input quickly), CLS under 0.1 (layout doesn't shift). All three should be measured on mobile, on real-world devices. PageSpeed Insights gives you both lab and field data.
Schema markup: the structured-data layer
Schema.org markup tells Google what each page is — an Article, a Product, an FAQ, a HowTo. It doesn't move rankings on its own, but it's required for rich results and dramatically improves AI Overview eligibility.
- Shipping a noindex tag from staging to production
- Disallow: / left over after a launch
- Canonical tags pointing to the wrong URL
- Sitemap listing 404s or thin utility pages
- Ignoring mobile Core Web Vitals because desktop scores look fine
- Adding schema to one page instead of templating it across the type
- 1Verify robots.txt allows crawling of all important paths
- 2Inspect 10 random URLs in Search Console — all should show 'Indexed'
- 3Confirm sitemap.xml contains every indexable URL and no junk
- 4Spot-check canonical tags on 5 pages of each template type
- 5Run PageSpeed Insights on mobile for top 10 pages
- 6Ship Article/Product/FAQ schema at the template level
- 7Set up Search Console alerts for indexing drops
- 8Schedule a quarterly technical audit
Related tools
Frequently asked questions
Do I need a developer to do technical SEO?
For the fundamentals, no — most checks are runnable in the browser or with free tools. For fixes (especially Core Web Vitals), you'll often need developer time, but you can usually identify the problem yourself.
How often should I do a technical audit?
Quarterly is sufficient for most sites. High-velocity sites (frequent deploys, large content teams) should audit monthly or set up continuous monitoring.
What's the single most damaging technical mistake?
Shipping a noindex tag to production. Sites lose entire indices in days and take weeks to recover.
Are Core Web Vitals actually a ranking factor?
Yes, but a small one. Their bigger impact is on conversion — slow sites lose users even if rankings hold.
Should I use AMP in 2026?
No. AMP is effectively deprecated. Build a fast standard mobile site instead.
Do I need schema on every page?
Every page that fits a schema type (Article, Product, FAQ, HowTo, BreadcrumbList) should have it. Schema-less pages still rank, but they miss rich results and AI Overview opportunities.