Technical SEO for Beginners: The Foundations That Let You Rank at All

Technical SEO has a reputation for being the intimidating end of search optimisation, reserved for developers. In reality, most of it is a small set of checks that determine one thing: can a search engine reach, understand and index your pages without tripping over something?

Here is the important framing. Technical SEO rarely wins you rankings on its own. Nobody outranks a competitor because their sitemap is tidier. But a technical problem can absolutely prevent you from ranking, no matter how good your writing is. It is a floor, not a ceiling — and you want to be standing on it.

Crawling: can bots find your pages?

Search engines discover pages by following links. If nothing links to a page and it is not in your sitemap, it may as well not exist.

Common crawling problems:

• Orphan pages. Published, but linked from nowhere. Fix with internal links.
• Blocked in robots.txt. A single stray Disallow: / can hide an entire site. It happens more often than you would believe, usually when a staging setting goes live.
• Broken internal links. They waste crawl effort and frustrate readers.
• Endless URL variations from filters or parameters, which burn crawl budget on near-duplicate pages.

Indexing: are your pages actually in the database?

Crawled is not the same as indexed. A page can be visited and then declined.

The quickest check is Google Search Console’s indexing report, which will tell you plainly which pages are indexed and, for those that are not, why.

Frequent culprits:

• A stray noindex tag. Often left over from development. It is the single most effective way to make a page invisible.
• Thin or duplicate content. If a page adds nothing, it may simply be omitted.
• Canonical tags pointing elsewhere, telling the engine “the real version is over there” when it is not.
• Discovered – currently not indexed. Usually a quality or priority signal. The answer is rarely technical: it is that the page is not compelling enough.

Sitemaps and robots.txt

An XML sitemap is a list of the pages you want indexed. It does not force indexing, but it helps discovery, especially on larger or poorly-linked sites. It should contain only canonical, indexable pages — not redirects, not error pages, not noindex pages.

robots.txt tells crawlers where they may and may not go. Two things worth internalising: it controls crawling, not indexing; and a mistake here is unusually expensive. Check it after any major site change.

Site speed and Core Web Vitals

Speed matters for two reasons: it is a (modest) ranking signal, and it is a very large conversion factor. Slow pages lose readers regardless of where they rank.

The main measures worth knowing:

• Largest Contentful Paint (LCP) — how quickly the main content appears. Usually dominated by images, fonts and slow servers.
• Cumulative Layout Shift (CLS) — how much the page jumps around while loading. Usually caused by images without dimensions, or ads and embeds injected without reserved space.
• Interaction responsiveness — how quickly the page reacts when tapped. Usually a JavaScript problem.

The highest-leverage fixes are unglamorous: compress your images, set explicit width and height on them, remove plugins and scripts you do not need, and use decent hosting.

Mobile usability

Search engines predominantly evaluate the mobile version of your site. That means the mobile version is your site, and the desktop version is a courtesy.

Check that text is legible without zooming, that tap targets are not crammed together, that nothing overflows horizontally, and that intrusive pop-ups are not the first thing a visitor meets.

HTTPS

Non-negotiable, universally expected, and usually free. A browser warning about an insecure site destroys trust instantly.

Duplicate content and canonicals

Duplicate content rarely earns a penalty, but it does cause confusion: search engines must guess which version to rank, and they may guess badly, or split signals between versions.

A canonical tag names the preferred version of a page. Use it when the same content is legitimately reachable at multiple URLs. Make sure the canonical points at the page you actually want ranked — self-referencing canonicals on normal pages are entirely fine.

Redirects

When a URL changes, redirect the old one to the new one with a permanent (301) redirect. This preserves most of the accumulated authority and prevents readers hitting a dead end.

Avoid long redirect chains, and never redirect everything indiscriminately to the homepage — it is a poor experience and search engines often treat it as a soft error.

Structured data

Schema markup describes your content in a machine-readable way: this is an article, this is its author, this is an FAQ. It can produce enhanced search results, which improves click-through.

It is a bonus, not a foundation. Add it once the basics are solid.

A practical technical audit

1. Connect Google Search Console. Everything below is easier with it.
2. Check the indexing report. Are your important pages indexed? If not, why?
3. Open your robots.txt. Confirm you are not blocking anything important.
4. Confirm your sitemap exists, is submitted, and contains only indexable pages.
5. Run your slowest page through a speed test. Fix the images first — it is almost always the images.
6. Load the site on a real phone and use it honestly.
7. Check for broken links and redirect chains.
8. Confirm HTTPS everywhere, with no mixed-content warnings.

How much time should this take?

For a small content site: a few hours to set up properly, then perhaps an hour a month to monitor.

Technical SEO is not where you should spend most of your effort — that belongs to content and genuine expertise. But when something is badly wrong technically, nothing else you do can compensate. Get the floor solid, then go and build on it.

Frequently asked questions about technical SEO

How do I know if my pages are actually indexed?

Search site:yourdomain.com in Google to see roughly what is included, then use Google Search Console’s indexing report for the authoritative answer. It will tell you which pages are indexed and, for those that are not, the specific reason — which is usually far more useful than the fact itself.

My page says “Discovered – currently not indexed”. What does that mean?

Google knows the page exists but has chosen not to index it. This is almost never a technical fault. It is usually a quality or priority judgement — the page is thin, duplicative, or simply not compelling enough to be worth including. The fix is editorial, not technical: make the page genuinely better, and strengthen the internal links pointing at it.

Do I need to submit a sitemap?

It helps, particularly on larger sites or where internal linking is weak. It does not guarantee indexing, and it will not rescue a page that Google has decided is not worth including. Submit one, keep it clean — canonical, indexable pages only — and do not expect it to do more than aid discovery.

How much does site speed really matter for rankings?

Less than people think for rankings, and far more than people think for revenue. Speed is a modest ranking signal, but a slow site loses readers, conversions and return visits regardless of where it ranks. Fix it because it costs you money, not because it costs you positions.