malik7mb7.com Free sample
Free sample — the complete first chapter

Technical SEO 101

This book is written for the smart site owner and the junior marketer who is tired of generic content that explains "what SEO is" without ever teaching you how to actually fix your site. Technical SEO is the foundation everything else is built on: the best content in the world will never show up in Google if the search engine cannot crawl your pages, index them, or understand them. That is exactly what you will learn to fix here.

Chapter 1 / 12

How Search Actually Works: Crawl, Index, Rank

Why This Chapter Comes First

A real scenario I see constantly in Amman: a services company pays good money for a new bilingual Arabic/English site on a .jo domain. Beautiful pages, professional photos. Six months later, nobody finds them on Google unless they type the company name letter for letter. The problem is usually not the design and not the content — the problem is that Google either never reached the pages, reached them but never stored them, or stored them but saw no reason to rank them. Those three stages are this chapter's whole subject. Skip this foundation and you will spend months fixing things that are not broken while the broken thing sits untouched.

The Pipeline: From Discovery to Ranking

A search engine is not a magic box; it is a production line with distinct stages, and each stage can fail independently:

  1. Discovery: Google learns your URL exists at all — through links from other pages, a sitemap, or a previous visit. A page nothing links to and no sitemap lists may never be discovered (orphan pages — fixed in Chapter 4).
  2. Crawling: A program called Googlebot — a crawler — requests your page exactly like a browser does: an HTTP request that returns a status code and content. If the URL is blocked in robots.txt or returns an error code, everything stops here (Chapter 2).
  3. Rendering: Google runs the page in a headless Chrome to execute JavaScript and see the page as a visitor would. Sites whose content only appears after JS execution can fail at this stage (Chapter 7).
  4. Indexing: Google decides whether the page earns a place in the index — the massive database search results are pulled from. Duplication, canonical signals, and noindex directives all decide the outcome here (Chapter 3).
  5. Ranking: For every search, only indexed pages get ordered, using hundreds of signals: relevance to the query, page quality, external links, user experience and speed (Chapter 6), and more.

Memorize the rule: each stage is a prerequisite for the next. No indexing without crawling, no ranking without indexing. Correct diagnosis therefore always starts at the top of the pipeline, never the bottom.

Where Technical SEO Sits

SEO has three territories:

TerritoryIts questionExamples
Technical SEOCan Google reach and understand the site?Crawling, indexing, speed, structured data
On-page / contentDoes the page answer the searcher's question?Copy, headings, search intent
Off-page / linksDo others vouch for the site?Backlinks, reputation

This book covers only the first territory. Content and links are out of scope — but remember both directions of the dependency: the best content in Jordan will never surface if the technical layer hides it from Google, and a technically flawless site with weak content is just a zero, beautifully indexed.

Crawled ≠ Indexed ≠ Ranking

A realistic example: a bilingual Jordanian services site with 50 pages. Inspection reveals:

The owner thinks he has one "SEO problem." In reality he has three different problems at three different stages, each with a different cure.

Is My Page Indexed Right Now?

Two methods:

Dead Myths — Stop Wasting Time on These

The Diagnostic Mindset

This chapter deliberately gave you no fixes. Reason: the most dangerous habit in this field is jumping to solutions before locating the broken stage. When a page is invisible, ask in order: Can Google reach it? (Chapter 2) Did we allow it to be indexed? (Chapter 3) Does Google understand its structure and language? (Chapters 4, 7, 9) And only then: does it deserve to rank? Every coming chapter is a repair tool for one specific stage of this pipeline.

Do It Now

Ten minutes on your own site before Chapter 2:

  1. Search Google for site:yourdomain and note the approximate result count. Compare it with the real number of pages on your site — the gap is your first diagnostic clue.
  2. Pick your 3 most important pages (homepage + two service pages) and check each with site:full-url.
  3. If you have a Search Console account, paste those three URLs into URL Inspection and record the verdicts. If you don't have an account yet, note that down — you will create it in Chapter 11.
  4. Write on paper: how many pages do I have? Roughly how many does Google know about? That gap is what the rest of this book hunts down.

Common Mistake

The single most repeated mistake among site owners: assuming "the site is live" means "Google sees it." Publishing to a server does not even enter you into the pipeline — discovery, crawling, and indexing are sequential gates, and each can fail completely silently: no error message, no alert, just absence from results. From today, stop saying "my site is online" and start asking "which pipeline stage is my site stuck at?"

That was the full sample — here is the rest

What you just read is one part. The full edition includes:

Subscribe now