Skip to content

Web design, software and technical support

Log in +90 539 219 79 78 WhatsApp
SEO & GEO

Technical SEO checklist: crawling, indexing, performance and schema

From crawling and indexing to structured data, performance, hreflang and server logs: the items to review in a technical SEO audit, with a priority table.

Boran KaradenizKarınca Bilişim Last updated: 8 min

Summarise this article with an AI tool

The tool opens in a new tab with a summary prompt that includes this article’s address.

A technical SEO checklist is an ordered list of the technical areas to review so that search engines can crawl a website, index the right pages and serve them quickly. This guide covers the eight groups Karınca Bilişim uses in audits: crawling and indexing, site architecture, on-page technical structure, structured data, performance, international setup, JavaScript and server logs.

Why use a technical SEO checklist?

A technical SEO checklist turns problem-finding from guesswork into a repeatable process. However good the content is, it cannot earn visibility if a search engine cannot reach the page, cannot tell which version is the main one, or has to wait too long for it to load.

A checklist also makes it easier to split the work. Developers take the server and template items, the content team handles headings and links, and the site owner makes priority decisions, all from the same document. We recommend reviewing the items below at least once a year and after every major change such as a new theme, a migration or a new language.

Crawling and indexing

Crawling and indexing checks confirm that important pages are open to search engines and that thin or duplicate pages are not. This is the most critical group: a mistake here can cancel out every other improvement.

  • robots.txt does not block important directories or CSS and JavaScript files.
  • No stray noindex tag remains on important pages, especially after moving from staging to production.
  • The XML sitemap lists only canonical, indexable URLs that return a 200 status code.
  • The sitemap is submitted to Search Console and Bing Webmaster Tools.
  • Unexpected exclusions in Search Console's page indexing report have been reviewed.
  • Soft 404s (empty pages that return 200) have been identified.
  • Search, filter and sort parameters do not generate endless URL variations.
  • The staging environment is password-protected and closed to indexing.

Site architecture and internal links

Good site architecture puts every important page a few clicks from the home page and makes the relationship between pages clear through links. Search engines and people both infer the structure of a site largely from its internal links.

  • Important pages are no more than three or four clicks from the home page.
  • There are no orphan pages without internal links.
  • Navigation, footer and in-content links are real anchor links, not JavaScript-only click handlers.
  • Anchor text describes the destination ("WooCommerce setup service" rather than "click here").
  • Breadcrumbs are in place and supported by structured data.
  • URLs are readable, lower case and consistent, without unnecessary folder depth.
  • Broken internal links and redirect chains have been cleaned up.

On-page technical structure

On-page technical checks confirm that every page presents one clear topic with the right tags. The goal is not keyword stuffing but making sure people and machines understand the page in the same way.

  • Every page has a unique title tag and meta description.
  • Each page has a single H1, with H2 and H3 headings in a logical hierarchy.
  • The canonical tag points to the correct version, and www/non-www and http/https variants redirect to one address.
  • Images have meaningful alt text and correct dimensions.
  • Thin or duplicate pages have been merged or differentiated.
  • The 404 page returns a real 404 status and helps the visitor find their way.
  • Permanently moved pages use 301 redirects.

Structured data

Structured data makes the information on a page machine-readable using the Schema.org vocabulary. Done properly, it helps search engines and generative answer systems understand your business and your content.

  • Organization and WebSite data are consistent across the whole site.
  • Service pages use Service; articles use BlogPosting or Article.
  • BreadcrumbList matches the visible breadcrumb.
  • Everything in the markup is visible on the page, with no invented ratings or reviews.
  • Rich Results Test and Schema Markup Validator report no errors.

Our structured data guide has detailed examples.

Performance and Core Web Vitals

Performance checks measure how quickly a page loads and how smoothly it responds for real visitors. Google's Core Web Vitals provide the shared language: an LCP of 2.5 seconds, an INP of 200 milliseconds and a CLS of 0.1, measured at the 75th percentile of visits, are the "good" thresholds.

  • The Core Web Vitals report in Search Console and PageSpeed Insights field data have been reviewed.
  • The largest image, usually the hero, is compressed, correctly sized and loaded with priority.
  • Off-screen images are lazy-loaded.
  • Unused CSS and JavaScript have been reduced and third-party scripts reviewed.
  • Server response time (TTFB) has been lowered with caching and suitable hosting.
  • Fonts and ad slots do not cause layout shifts.

See improving Core Web Vitals for the detail.

International setup and hreflang

On a multilingual site, hreflang tells search engines which language version of a page to show to which visitor. Incorrect hreflang can lead to problems such as an English page appearing in Turkish searches.

  • Each language version points to its own canonical URL.
  • hreflang annotations are reciprocal: the Turkish page lists the English one and vice versa.
  • An x-default version is defined.
  • Language codes are correct (tr, en, or regional codes such as en-GB).
  • Automatic language redirects do not lock search engine crawlers into a single language.

JavaScript-generated content

JavaScript checks confirm that important content and links are present in the HTML or reliably rendered. Google can render JavaScript, but rendering may be delayed, and some AI crawlers may not execute JavaScript at all.

  • With JavaScript disabled, the page source still shows the heading, main text and links.
  • The rendered HTML has been checked with the URL Inspection tool in Search Console.
  • Infinite scroll has paginated URL equivalents.
  • Important content is in the DOM without needing a click or a tab to open.

Server logs

Log analysis shows what search engine crawlers actually do on your site. Search Console data is sampled and delayed; logs record every request.

  • The URLs visited by Googlebot, Bingbot and any other crawlers you care about have been listed.
  • Wasteful URLs that consume crawl time (parameter pages, old images) have been identified.
  • 5xx server errors and timeouts are monitored.
  • You know how often key pages are crawled.

Which items come first?

Priority depends on how many pages a problem affects and how much it blocks visibility. The table below shows the general order we use in audits.

PriorityCheckWhy
UrgentStray noindex, robots.txt blocks, an open staging sitePages can drop out of search entirely
HighCanonical errors, redirect chains, broken linksSignals are split and crawl time is wasted
HighSlow LCP and high INPUser experience and conversions suffer
MediumMissing or incorrect structured dataSearch engines understand the page less easily
Mediumhreflang mismatchesThe wrong language version may be shown
LowMeta description length, alt text improvementsSmall individually, but they add up

Treat this as a general roadmap: filter parameters may matter more on an online shop, duplicate service pages more on a corporate site.

Who should run the audit?

Site owners can complete most basic checks with Search Console and free tools; fixes to servers, templates and redirects usually need a developer. On WordPress, plugin settings, theme structure and caching need to be reviewed together.

If you need help after working through this list, our technical SEO service turns the findings into a prioritised report and a remediation plan. For speed issues see website performance, and for WordPress sites the WordPress SEO service. Additional steps for generative answer systems are covered in our GEO guide.

Frequently asked questions

How often should a technical SEO audit be done?

A full audit once a year is enough for most corporate sites. Critical items should be rechecked after a theme change, a migration, a new language or a large content release.

Can technical SEO be checked with free tools?

Largely, yes. Search Console, PageSpeed Insights, Rich Results Test and browser developer tools cover most basic checks. On larger sites, crawling software and log analysis speed the process up.

Does technical SEO bring rankings on its own?

No. Technical SEO removes the obstacles that stop content from being found and understood. Rankings come from content quality, relevance to the question and the trustworthiness of the site as a whole.

What technical problems are most common on WordPress sites?

Problems we often see include the "discourage search engines" setting left switched on, conflicting SEO plugins, thin tag and archive pages, and heavy theme files. Most can be fixed at settings and template level.

All articles
Call nowWhatsApp