Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

SEO › Intermediate

Checkpoint: Crawling, Indexing and Architecture

Scenario questions on the technical foundations module: robots rules, canonical disputes, crawl budget, click depth, pagination, quality exclusions and field data. Commit to a diagnosis for each, then read the reasoning and note which signal you misread.
CheckpointIntermediate levelModule 1: Technical foundations4 minUpdated

What this checkpoint covers

The questions draw on the crawling and indexing guide and the site architecture guide, with one question on field data from the Core Web Vitals guide. None asks for a definition. Each describes a site, a symptom and sometimes a proposed fix, and asks what you would do.

Task

  • Write a one-line diagnosis and the action you would take for every question before scrolling further.
  • Mark each answer as confident or unsure.
  • Read the explanations and, for each one you missed, write down the signal you misread.
  • Reread the linked section for any question you got wrong while marked confident; that is the gap that matters.

Questions

  1. A homeware shop disallows its filter URLs in robots.txt to keep them out of search. Weeks later, some filter URLs appear in results with no description. What went wrong, and what should the shop do?
  2. A category page declares a self-referencing canonical, but URL inspection shows Google selected the same page with a tracking parameter. What do you check first?
  3. A charity site with a few hundred pages receives an audit tool warning about crawl budget. Should it be a priority?
  4. A publisher's evergreen guides are reached only through a date-ordered archive, and their rankings are slipping. A colleague proposes adding them to the sitemap. Is that enough?
  5. A removals company has a page per town that differs only by the town name. Many are reported as crawled, currently not indexed. A colleague suggests requesting indexing for each. What would you do?
  6. A shop canonicalises every paginated category page to page one. Products listed only on later pages are not indexed. What is the fix?
  7. A product template passes in a lab test, but the Search Console report shows it failing loading speed on mobile. Which result do you trust, and where does the fix go?

Answers explained

  1. Robots.txt controls crawling, not indexing. Blocked URLs can still be indexed from links, shown without a snippet, and the crawler can never see a noindex on them. If the URLs must stay out of results, allow crawling and use noindex; if the aim is to stop crawlers entering an endless filter space, the disallow is right and the occasional bare listing is the accepted cost. Decide the goal first. See the controls table in the crawling and indexing guide.
  2. Look for the stronger competing signal. The Canonical Tag is a hint weighed with internal links, sitemap entries and redirects. Check whether navigation, the sitemap or internal links point at the parameter version, then align them on the clean URL and redirect where you can.
  3. No. Crawl Budget is a concern for very large sites with frequently changing content. Read what the warning actually lists; if it is redirects or errors, treat them as hygiene. A small site's lever is quality and links, not crawl allocation.
  4. No. A sitemap helps discovery but does not make a page important. Depth and internal links decide how often pages are crawled and how much authority they receive. Build topic hubs linked from the main navigation that list the guides first, as the site architecture guide describes.
  5. Treat it as a quality judgement, not a technical block. Requesting indexing does not change Google's view that the pages add nothing. Write genuinely local content for the towns that matter to the business, and consolidate or remove the rest.
  6. Make each paginated page self-canonical and link the pages with plain links. Canonicalising to page one tells the engine the later pages are duplicates, so the items on them disappear. Link important products from somewhere shallower as well, such as sub-category hubs.
  7. Trust the field data. Core Web Vitals are assessed on real users at a high percentile; the lab is for finding causes. Reproduce the failure on a throttled mobile profile, find the element responsible and fix it in the template, then confirm in the field data over the following weeks, as the Core Web Vitals guide explains.
Illustrative example — not a real result

Reading your score

A learner scores themselves out of 7. With 6 or 7 correct and marked confident, they move on to module 2. With 4 or 5, they reread the sections behind the ones they missed and answer those questions again a day later. With 3 or fewer, they redo the triage exercise with the controls table open before continuing. Any answer that was wrong but marked confident counts as a gap to fix, whatever the total.

Where to go next

If you missed the canonical or robots questions, redo the crawl and index triage exercise with the controls table open. Otherwise return to the intermediate SEO level and start the keyword strategy module.

Pages this lesson applies

Terms used on this page

Also related

Related