Technical SEO workbook
One task per module of the free technical SEO course, fill-in templates for your own site, and a 90-day plan you can follow with free tools and settings you already have.
Inside this Workbook
The companion to the Technical SEO Complete Course: a task, template or checklist for each of the 10 modules, using free tools only. Finish it and you know Google can find, index and load every page that earns you money, and you have a 90-day plan to keep it that way.
Who it's forBusiness owners and marketers who run their own website and want to fix technical SEO without hiring a developer for every check.
How to use it
Do these five things before anything else. If all five pass, your site has no locked doors and you can work through the modules at a calm pace.
That one line blocks crawling of the whole site.
If your homepage isn't indexed, start with Module 2 right away.
A leftover noindex is the fastest way to vanish from Google.
One version per page means signals aren't split across copies.
If it says 'Couldn't fetch', Google isn't reading your list of pages.
Technical SEO is about one question: can Google find, read and show the pages that make you money? So start by naming those pages. Every later module checks these first.
# | URL | What it sells / leads to | Leads or sales last month | Indexed? (Y/N) 1 | ____ | ____ | ____ | ____ 2 | ____ | ____ | ____ | ____ 3 | ____ | ____ | ____ | ____ 4 | ____ | ____ | ____ | ____ 5 | ____ | ____ | ____ | ____ 6 | ____ | ____ | ____ | ____ 7 | ____ | ____ | ____ | ____ 8 | ____ | ____ | ____ | ____ 9 | ____ | ____ | ____ | ____ 10 | ____ | ____ | ____ | ____
Date: ____ Search Console, last 28 days: clicks ____ impressions ____ Indexed pages (Pages report): ____ Not indexed: ____ Core Web Vitals, mobile: Good ____ Need improvement ____ Poor ____ Generative AI impressions, last 28 days (if the report shows for your site): ____ Money pages indexed: __ of 10 Leads from organic search last month: ____
Google crawls (fetches) pages by following links and sitemaps, renders them like a browser, then decides whether to index them. Your job is to remove anything in the way.
A rough look at what's indexed. It isn't an exact count. Use the Search Console Pages report for real numbers.
Check 'URL is on Google', the Google-selected canonical and the crawled page (Test live URL > View tested page > Screenshot). If the screenshot is blank or missing content, Google can't see what humans see.
Any 'N' goes straight to Module 2.
Open Indexing > Pages > 'Why pages aren't indexed'. Use this table to decide what each reason needs. Google says many of these are normal.
| Reason in the Pages report | Usually normal? | What to do if it's a money page |
|---|---|---|
| Excluded by noindex tag | Only if you meant it | Remove the noindex (SEO plugin setting or template), then Validate fix |
| Blocked by robots.txt | Only if you meant it | Remove the Disallow rule for that path |
| Page with redirect | Yes | Nothing, if the redirect goes to the right page. Update internal links to the final URL |
| Alternate page with proper canonical tag | Yes | Nothing. Google is indexing the canonical version |
| Duplicate, Google chose different canonical than user | Sometimes | Check why Google sees it as a copy. Merge, redirect or make the page clearly different |
| Not found (404) | Yes for deleted pages | If the page should exist, restore it or 301 it to the closest live page |
| Crawled - currently not indexed | Common on weak pages | Improve the page so it clearly answers something, and link to it from related pages |
| Discovered - currently not indexed | Common on new or large sites | Add internal links and keep it in the sitemap. Be patient |
Open it in a browser. It's a short text file you can read.
Google says robots.txt controls crawling, not indexing. A blocked URL can still be indexed without its content. Use noindex to keep a page out, and let Google crawl it so it can see the tag.
It helps any crawler find the sitemap, not just Google.
No redirects, no 404s, no noindexed pages. Google's limit is 50,000 URLs or 50 MB uncompressed per sitemap file.
If it says 'Couldn't fetch', Google isn't reading it.
AI tools like OpenAI, Perplexity and Anthropic send their own crawlers that you can allow or block by name in robots.txt. Google says AI Overviews and AI Mode need no extra crawler or file: indexed and snippet-eligible is enough.
Money page URL: ____ Internal links pointing to it (Search Console > Links > Internal links): ____ Linked from homepage? Y/N Linked from main menu? Y/N Clicks from homepage to reach it: ____ 3 related pages that should link to it: 1. ____ anchor text: ____ 2. ____ anchor text: ____ 3. ____ anchor text: ____
Money page: /bathroom-remodel-cost/ Internal links pointing to it: 2 Linked from homepage? N Linked from main menu? N Clicks from homepage: 4 New links added: 1. /bathroom-remodel/ (service page) anchor: 'what a bathroom remodel costs' 2. /blog/small-bathroom-ideas/ anchor: 'bathroom remodel cost guide' 3. /about/ (projects section) anchor: 'see typical remodel prices' After: 5 internal links, 2 clicks from homepage
Google's 'good' thresholds, at the 75th percentile of real visits: LCP 2.5 s or less, INP 200 ms or less, CLS 0.1 or less. Poor starts above 4 s, 500 ms and 0.25. INP replaced FID as a Core Web Vital in 2024.
Read the real-user data at the top first. The lab score below is a test, not what customers felt.
A group takes the status of its worst metric, so one template fix can clear many URLs.
Large images are a common cause of slow LCP. Squoosh (squoosh.app) is free in the browser.
web.dev says lazy-loading the LCP image delays it. Lazy-load images further down instead.
Practical advice: every script competes for the main thread, which hurts INP.
Stops the page jumping as things load, which is what CLS measures.
Google uses mobile-first indexing, so the mobile version is the one that counts.
If content is hidden or missing on mobile, Google may not see it.
Google's mobile-first guide asks for the same metadata on both.
It blocks the reader and can push layout around. Use a small banner instead.
Practical advice: mobile buyers want to call or book fast.
Shows broken internal links and redirect chains. The paid licence (£199/year) removes the 500-URL limit; most small sites don't need it.
Saves crawling and keeps link signals clean.
Google treats permanent server-side redirects as a strong signal the page moved. Use the Redesign SEO checklist for a full move.
Point every redirect straight at the final URL.
Google says redirecting lots of old URLs to one unrelated page might be treated as a soft 404.
Common ones for small businesses: Organization or LocalBusiness on the homepage, Product on product pages, Article on blog posts, BreadcrumbList site-wide.
Google recommends JSON-LD. Many CMS plugins add it without code.
Use the Rich Results Test for Google features and the Schema Markup Validator for general schema.org errors.
Markup must match what's visible on the page. Misleading markup can lead to a manual action, and valid markup doesn't guarantee a rich result.
Google stopped showing FAQ rich results from 7 May 2026. Don't spend time adding FAQ schema for a feature that no longer appears.
Nothing else matters if Google can't get in.
This is your fix list and your before picture.
Cleans the hallways before you add more rooms.
Start with LCP on mobile. It's usually images or a slow server.
Practical advice: this is the cheapest ranking lever most small sites ignore.
Fewer weak pages, clearer signals.
Helps Google understand who you are and what each page is.
That report shows how often your pages appear in AI Overviews and AI Mode (impressions only). Use the Search Console weekly checklist.
Write the before and after numbers down. That's your proof it worked, or your clue where it didn't.
A fast page Google can't index earns nothing. Door first, then foundation.
Redirects, canonical alternates and deleted pages are normal. Only act on money pages.
Google can't see the noindex if it can't crawl the page.
Map each to its closest new page instead.
It breaks Google's structured data policies.
Problems come back with every plugin update and redesign. The weekly routine catches them.
Every claim in this Workbook traces back to one of these. Checked 2026-11.
Keep going
Checklists, templates, tool lists and playbooks for SEO, AI search, marketing and growing a business or career. New ones every week.
ritiknamdev.com/resources