All articles

    Web development

    Technical SEO: The Complete Checklist for Speed, Indexing, Core Web Vitals and Schema

    Written by Khalid NamraPublished: 19 September 2026Updated: 19 September 202611 min read
    Technical SEO: The Complete Checklist for Speed, Indexing, Core Web Vitals and Schema

    In three lines

    • Technical SEO is the part that content cannot compensate for.
    • Verify with the URL Inspection tool in Search Console: it shows whether a specific page is indexed, which canonical Google selected, and when it was last crawled.
    • Three metrics describe real user experience: how fast the main content appears, how quickly the page responds to the first interaction, and how much the layout shifts while loading.

    Technical SEO is the part that content cannot compensate for. If pages cannot be crawled, load slowly on a mobile connection, duplicate each other, or describe nothing to a machine, then every article you publish underperforms. This checklist covers the four areas we audit on every engagement, with the official tool that reports each one so you can verify the findings yourself instead of trusting a screenshot.

    1. Crawling and indexing

    Verify with the URL Inspection tool in Search Console: it shows whether a specific page is indexed, which canonical Google selected, and when it was last crawled.

    • robots.txt allows the pages that matter and blocks only what should stay private
    • An XML sitemap lists every public page and is submitted in Search Console
    • No accidental noindex tags on live pages
    • Canonical tags point to the preferred version of each page
    • Bilingual sites declare hreflang for Arabic and English versions

    2. Speed and Core Web Vitals

    Three metrics describe real user experience: how fast the main content appears, how quickly the page responds to the first interaction, and how much the layout shifts while loading. On Arabic sites the usual culprits are uncompressed hero images, heavy web fonts loaded for both scripts, and third-party scripts for chat and analytics that block rendering.

    • Serve images in modern formats at the size actually displayed
    • Reserve space for images and embeds to stop layout shift
    • Defer non-critical scripts and remove unused ones
    • Enable caching and compression at the server or CDN

    3. Architecture and duplication

    Every important page should be reachable within three clicks of the home page, and each page should exist at exactly one address. Duplication is created quietly by URL parameters, printable versions, session identifiers, and pages available with and without a trailing slash. The result is that search engines split the value of a page across several copies.

    4. Structured data

    Structured data tells a machine what a page is rather than leaving it to guess. At minimum, publish an Organization entity with your official name, logo, address, phone and social profiles; add LocalBusiness for physical locations, Service for each service page, Article with a named author for posts, and FAQPage for question sections. This is also the foundation of visibility in AI answers, which rely on a clear, consistent machine-readable identity.

    • Use one consistent organisation identifier across the whole site
    • Mark up only what is genuinely visible on the page
    • Validate with Google's Rich Results Test before publishing

    A monthly technical routine

    Technical health decays: new pages appear, plugins update, someone republishes a product with a new URL. Once a month, re-check indexing coverage, the speed scores of your three most valuable pages, any new crawl errors, and whether structured data still validates. Fifteen minutes of routine prevents the quiet decline that surprises everyone six months later.

    The practical takeaway

    Technical SEO is a maintenance discipline, not a one-off project: crawlable pages, fast rendering, one address per page, and structured data that states who you are. Fix these and content finally gets the chance it deserves.

    Frequently asked questions

    What is technical SEO?

    The engineering side of search visibility: making pages crawlable and indexable, fast to load, free of duplicate addresses, and described to machines with structured data.

    Why is my page not appearing in Google?

    The usual causes are a noindex tag, a robots.txt block, a canonical pointing elsewhere, a page not linked from anywhere, or content too thin to be worth indexing. The URL Inspection tool names the reason.

    How much does speed affect ranking?

    Speed is a real but secondary factor: it rarely beats a better answer, yet a slow page loses visitors before they read anything, which harms results either way.

    Is structured data necessary?

    It is not mandatory, but it removes guesswork about who you are and what the page offers, and it is the foundation of appearing in AI-generated answers.

    How often should a technical audit run?

    A full audit yearly or after any redesign or migration, plus a short monthly check of indexing coverage, speed on key pages, crawl errors and structured-data validity.

    Related RASED services

    Official references

    Written by Khalid Namra

    Founder & CEO, RASED Solutions — engineering lead of RASED Solutions

    Khalid Namra building software since 2015 and leads the engineering and security teams behind RASED Solutions in Riyadh.